3 ms·
I find the whole we (investors, "founders")/they (non-generalists who can't move up and down the stack) kind of jarring, especially since I somehow managed to f
by ojbyrne 14y ago
I find the whole we (investors, "founders")/they (non-generalists who can't move up and down the stack) kind of jarring, especially since I somehow managed to fall into the gap between founders and employees. Programmers are generally opinionated, especially about the domain they work in. My impression of Kevin's problems with programmers when I was there (inception to October 2007) is that they gave him too much shit, criticized his ideas, and generally created hassles for him (all good things, IMO), and he didn't really handle that well (IMO). Forget "moving up and down the stack," they wanted to _architect_ the stack.
If you're non-technical and come back from some conference and say we're now rearchitecting in Rails/Node/Brainfuck/whatever cool new tech you just heard about, you're probably going to get some pushback. And that pushback, from the other side's perspective, could be presented as "you're just a non-generalist who can't move up and down the stack."
Its important to remember that Kevin isn't really technical.
- duaneb 14y agoI know little to nothing about Digg and even less about Kevin Rose, internal drama, et al... however, hiring people who are locked into certain technologies, especially non-optimal ones like PHP, seems to be a bad idea.
- ojbyrne 14y agoMy point was that nobody was locked into any language. But if you have a large complex website with hundreds of thousands of lines of code, the company is somewhat locked in to the language. When some non-technical executive mandates that we're all switching to language X and everything is going to be rebuilt from scratch, you will get some pushback.