One of the most important "ilities" in software is the ability to delete it and start over. In this talk we will look at this "ility", why it is important, and how we can optimize for it. Imagine never being afraid of your code ever again!

A treasure trove of books for people who love code. Curated by Eric Elliott.

Arranged by topic, loosely in learning order.

Suppose you’re a startup looking to grow into a mid-sized tech company — somewhere between 30 and 100 engineers. Hiring is happening fast, and the amount of code you’re churning out is growing fast as well. At an earlier stage, your company was focused on proving the product. Everything was smaller in scale and you were able to iterate fast. Now, as you grow, you have many more developers writing code and many more variables in the mix.

It seems like every application I’ve ever written, at some point needs to run a task in the background that is to be scheduled at some point in the future. My need for tasks as reoccurring batch jobs has decreased significantly over the years because of my applications being more event driven. Nowadays, I will often use Event Stores Persistent Subscriptions with my event stream as a queue. However, I’m not event sourcing all parts of the application and not always using Event Store.

Douglas Crockford accurately described JavaScript as the world’s most misunderstood language. A lot of programmers tend to think of it as not a “proper" language because it lacks the common object-oriented programming concepts.