or subscribe with
Join 15,000+ readers for one email each week.
Digests » 259
monday.com is a visual and intuitive project management tool. It's designed to work with ease and allows you to see the bigger picture in a single glance. Organize your design layouts & code languages, create custom roadmaps & schedule your tasks. Collaborate with your team & never miss a deadline with a visual timeline view. Stay-on-top of your team's entire workflow - start using monday.com today!
this week's favorite
There are lots of patterns to choose when developing software, such as Test Driven, Behaviour Driven or even Document Driven Development. But now, we are witnessing very dangerous type of development type, it’s Hype Driven Development.
This is one of those questions where I thought I’d known the answer for a long time, but as I inspected my understanding, I realized there were pretty significant gaps. Through an exploration of electromagnetic radiation, optical biology, colorimetry, and display hardware, I hope to start filling in some of these gaps.
Patterson started his talk with the 1960s and the groundbreaking IBM System/360 project, which built upon Maurice Wilkes’s early development of microprogramming in 1951. That was long, long ago in computer years.
This project intends to provide a complete description and re-implementation of the WhatsApp Web API, which will eventually lead to a custom client. WhatsApp Web internally works using WebSockets; this project does as well.
A common FP critique of imperative programming goes like this: “How can a = a + 1? That’s like saying 1 = 2. Mutable assignment makes no sense.” This is a notation mismatch: “equals” should mean “equality”, when it really means “assign”. I agree with this criticism and think it’s bad notation. But I also know some languages don’t write a = a + 1, instead writing a := a + 1. Why isn’t that the norm?