"Why would a software company not just build that? It's a ~1 engineer job?" Software companies find it difficult to reliably staff one-offs.
-
-
There's also no fallback plan if e.g. the engineer takes a new job, gets married and moves, etc etc. Bus number of 1 is terrifying.
Show this thread -
If you're having difficulty visualizing, the general pattern is "We just need one dev for email. One dev for analytics. One dev for BTC."
Show this thread -
(It would be a terrible idea to employ a non-zero number of engineers for BTC but BTC is a classic example of deep, narrow specialization.)
Show this thread -
So what do companies, which know that ~1 engineer is not realistic, do? They either hire consultancies or buy "solutions", at higher cost.
Show this thread -
You can totally be the person selling those things, if you understand the business context and can provide ~1 engineer of work.
Show this thread
End of conversation
New conversation -
-
-
The story of modern software companies is the story of career pathing software engineers.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
may be offering equity to the engineer and a CTO/VP of Eng. role, making it clear that for a long time he'll also be the only coder
-
equity AND a salary, of course, an engineer capable of fulfilling that role won't be lacking job offers that pay real money
End of conversation
New conversation -
-
-
I disagree... Smart people are often finishers.. Like stability. Sweeping generalizations are just that...
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.