John Allspaw: “On Being A Senior Engineer”

Absolutely one of the best posts on what I consider to be the responsibilities of my work and what I aspire to practice, John Allspaw has written required reading for anyone looking to become a Senior Engineer or anyone who wants to grow into a better one: “On Being A Senior Engineer” (via rc3.org).

Continue reading →

Thought Provokers From Python’s Guido Van Rossum and Clojure’s Rich Hickey

At Strange Loop 2011 Clojure’s Rich Hickey gave a presentation (video) on programming and simplicity that rankled some feathers and triggered a heated discussion at reddit. Duncan McGreggor, decided to contact Python’s Guido Van Rossum to interview him about his keynote talk at PyCon US 2012 (video), specifically his thoughts on callbacks.

Continue reading →

Dizzying but invisible depth: on complexity

Jean-Baptiste Queru, on his Google+ profile, posts a poetic and doozy of a post, “Dizzying but invisible depth”: Today’s computers are so complex that they can only be designed and manufactured with slightly less complex computers. In turn the computers used for the design and manufacture are so complex that they themselves can only be […]

Continue reading →

Metrics and damn metrics: on systems

Sometimes we get caught in numbers and miss what’s real. This can happen especially when we focus on the wrong numbers writes Arpit Mathur in a sharp post. I’d add even if you were looking at the right numbers, without context, just like a soundbite, you could derive the wrong lessons or encourage behavior that […]

Continue reading →

Impermanence and Software Design: on systems

When you’re building software, it is probably best to look at things half-Buddhist. Kent Beck writes about building software that won’t be around longer than him in a recent Facebook note: …nothing I am doing now with software will remain in a hundred years. Indeed, there was a time not long ago when the only […]

Continue reading →

On ever growing complexity in programming: on systems

Edsger W. Dijkstra gave a lecture, in 1972, that has since been come to be called “The Humble Programmer”. It’s a short piece that explains why software development, why programming, was growing more, not less complex over time, and some inspiration to be found in the dealing with it. There’s some choice quotes in here […]

Continue reading →

A Mathematician’s Lament: on education

Paul Lockhart wrote an accessible read on what is wrong with math education and the popular perception of math that is reinforced in culture that has been shared on the Web in quite a few corners. It deserves a wider read: “A Mathematician’s Lament”: The art of proof has been replaced by a rigid step-by […]

Continue reading →

Screaming Architecture: on systems

In “Screaming Architecture” Uncle Bob lays out one of the biggest wins by designing to the problem domain, instead of your weapon (ahem.. framework) of choice: “If you system architecture is all about the use cases, and if you have kept your frameworks at arms-length. Then you should be able to unit-test all those use […]

Continue reading →

Anemic Domain Model: on systems

Martin Fowler wrote a piece in 2003 that addresses a subtle anti-pattern – developing your domain model code devoid of behavior. It’s a short, interesting read, that is related to the development of fat controllers in MVCish applications: “AnemicDomainModel”: “In general, the more behavior you find in the services, the more likely you are to […]

Continue reading →