Viewing profile — practicingdev

The way I use it is to assume certain things, and then consider the consequences of them. I wish I could have discussed this more in the article, but the specific example got long …

I'm the author of this article. If you find it interesting, here are some links to a couple other articles I've really enjoyed on the topic: # Queues don't fix overload http://ferd…

Oh hi! I wasn't expected this to be posted on HN, but I'm happy to discuss in the comments rather than having folks head over to Twitter. I assume many people here already are self…

Tying this back to the main point... Salience is a big part of proficiency. If you're productive and familiar with a tool, and it wouldn't be terribly important to your actual need…

This is roughly the full Dreyfus model: (1) Novice... does not understand anything but basic knowledge in the abstract sense (2) Competent... knows how to apply knowledge to solve …

To me the terms are roughly interchangeable if taken in their general meaning, or at least easy to confuse with one another. But when I wrote this article, I hinged it off of speci…

I am the author of the essay, so... yes! The context I currently apply this in is that in the apprenticeship I'm running. So for example, we work on business applications and some …

The web of foundational skills for software development is vast enough that you can't really build it out from the bottom up. What you can do though, is start with small projects a…

Given that the goal of software development is to build tools, toys, etc... it can help to work backwards from projects to skills. No matter what level of skill you're at, you can …