http://disqus.com/by/oliverish/enWed, 12 Aug 2009 08:28:52 -0000http://www.codesoftly.com/2009/08/an-ideal-number-of-idea-people-please.html#comment-14708763<p>Has anyone considered how the term "craftsman" might apply in these cases?<br>From my experience at building things, you want everyone to be a craftsman.<br>You want your "doers" to have some sense of the overall goal and not just put on blinders and produce things. Likewise you want your "ideas" people to have a sense of how the details might play out while maintaining a broader vision and to push the "doers" beyond their perceived limitations.</p><p>Just keep in mind that sometimes the craftsmen nearly complete a job, realize its messed up, and rip it all out to start again.</p>oliverishWed, 12 Aug 2009 08:28:52 -0000http://www.codesoftly.com/2009/07/grow-or-die.html#comment-12028197<p>I think the item on the list about software does still apply to programming. I read it as B. Mau cautioning against basing your skills/work on a single piece of software, rather than understanding the underlying issues/principles and being able to apply them over a broad range of applications.</p><p>The (probably flawed) example that comes to mind is when Dreamweaver came out, all us design-types relied on it to do web stuff. Turns out, unless you know the "guts" of what it is doing, it becomes a very limiting piece of software, if not detrimental.</p><p>More straightforward, if you base everything on software, you can never get beyond the limitations of the software, you can't explore new avenues (i.e. if the software you're using only lets you display 6 widgets at a time, you'll never be able to display 12 or 14. Furthermore, you'll probably never conceive of displaying more than 6 widgets because that's the limit that your software sets).</p>oliverishThu, 02 Jul 2009 08:40:49 -0000