1) R&D engineer: invent something
2) Process & tooling engineer: invent the manufacturing process and design the tools to build the thing
3) Manufacturing & product engineer: monitor and improve product quality and yield
Many software companies, especially startups focus too much on 1 and not enough on 2 and 3. Also, there's always some friction between the R&D and process/manufacturing camps, the former typically look down on the latter as technicians or paper pushers. In the other direction there's often the perception of R&D as being out of touch with the real world. Also, it's easier to hide incompetence in R&D because the metrics are foggy.
[1] http://en.wikipedia.org/wiki/Rule_of_three_(computer_program...
This is also my problem with people who talk about being "builders" and "makers". Are you building and making things that need to exist, or sating your need to build and make? Not that that's inherently wrong, but it is certainly not inherently noble or impressive.
http://www.google.com/analytics/ at Urchin
Unix was an internal tool at Bell Labs, as was C.
Rails was pretty much just a framework over at 37signals before it spread.
~
This happens a lot in software.
The cult of the Swiss Army Knife is right up there with the cult of the Leatherman and the cult of WD-40 in encouraging people to fetishize general-purpose but dull tools. The Leatherman is a bit better than the SAK, but it is nothing like a set of top quality tools, just as WD-40 is both a cleaner and lubricant which means it isn't good at either.
I do have a, non-leatherman brand Leatherman and it's totally great.
It's great because I have it on me when I need it, and that's not going to happen with the rest of my tools, as I'm not bringing an entire tool box on a camping trip, or a bike tour, or traveling around the country.
I mean, ask Aron Ralston what he thinks was a good tool to bring along (other than a freakin' clue on things to do, before going on the types of trips he goes on).