10 private links
Interesting, I didn't know that there is a federal institution mandated to land management, which also includes camping areas!
The language for beginners in functional programming, not for production
The title says it all. Now, my new monitor is better set up!
This is interesting. A page with only 100 links to high-quality content over the web
A great article (first time contributor) from Zendesk Engineering
Interesting article shared by Jon Moter (Zendesk)
Interesting alternative to oh-my-zsh
Beautiful color scheme
A great article by the author of the PubGrub algorithm, discovered when reading more about the gel gem, an alternative to bundler
Some conventions on naming your gem.
Very well written article explaining everything that comes into a gem specification file. Doesn't take you for a fool, explain things one by one so you can get a better understanding of what you are doing.
Also, use a generator once you understand it!
A new type of function in JS that I had no idea existed! Seems pretty nifty and borrow from Ruby blocks it fells. Well, at least the yield keyword is really nice!
A good introduction to the Rust language, an alternative to the Rust book
We are back to 1915, and we need the new gatekeepers [algorithms] to embed a stronger sense of ethic
To leave us the choice, to be accountable, to be understandable.
The most basic modern day hardware is so complicated trying to understand the basics feels like trying to find a needle in a haystack. Fortunately, there are people out there like Daniel Thornburgh who through sheer laziness take such complicated structures and break them down into the simplest form. In this informative article, Daniel designs and builds as basic of a CPU, giving us a good understanding of how it works and showering him in nostalgia.
I did not read that but it was shared at Zendesk. Seems like a good read.
Really really really good article about the best use of your time at work. Sometimes, it's about getting the job done, even if it means asking the same question, over and over again.
A key engineering skill is noticing what’s blocked, and figuring out why, following a thread of hints from person to person until you can see what's not moving. You might end up asking the same question again and again. You might get handwavy responses that seem like answers but don't actually give you extra information. That’s how these games go.
Big-O notation, beyond the coding interview