practicingdev

9 ms·

1.
How to become a leader of more than just thoughts, a partial roadmap(medium.com)
5 points by practicingdev 10y ago|0 comments
2.
Dealing with growing pains without sacrificing sustainability(oreilly.com)
2 points by practicingdev 10y ago|0 comments
3.
by practicingdev 10y ago
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 enough that a theory tie-in would have been a lot for a blog
4.
by practicingdev 10y ago
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.ca/queues-don-t-fix-overload
5.
The critical role of systems thinking in software development(oreilly.com)
3 points by practicingdev 10y ago|0 comments
6.
by practicingdev 10y ago
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-employed or work remotely, but I can throw in my
7.
by practicingdev 10y ago
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 needs to optimize that aspect of things... then even i
8.
by practicingdev 10y ago
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 concrete problems (3) Proficient... sees how particular solu
9.
by practicingdev 10y ago
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 specific definitions assigned to the terms in the Dreyfus Model,
10.
by practicingdev 10y ago
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 amount of complex analysis is needed because we work wi
11.
by practicingdev 10y ago
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 and try to understand every piece involved in them, and
12.
by practicingdev 10y ago
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 start looking at the software you use day to day and th
13.
The traits of a proficient programmer(oreilly.com)
2 points by practicingdev 10y ago|0 comments