To which a partial answer is you silo them in a separate company with a culture not inimical to engineering, you compensate them with equity, and you eat a lot of free cultural lunches. (e.g. Revealed preferences mean some people value dress codes at literally billions.)
-
-
Show this thread
-
Repeatable way to find startup opportunities: look for large organizations with important problems that really need to hire 10 people who know what a for loop is and implement their recommendations but have a deeply felt reason why they can’t do that.
Show this thread -
Five years from now they’ve got three options: rethink how they make decisions, buy the startup and almost inevitably kill it for the same reason they couldn’t do it internally, or compete with the startup. (Not a given they’d lose the competition but risk-adjusted ROI is great.)
Show this thread
End of conversation
New conversation -
-
-
Feel like
@Twilio (and other “API-wrapper-around-existing-infrastructure) are *wonderful* examples of this. The tech to make telecom easy has been there for decades- they had the culture and engineers to make it happen. -
well that & timing. They were starting out right around the time it became popular to call rest/json APIs from JavaScript. There was (and still is) lots of XML/SMTP/SNMP stuff that make telco super easy, it’s just that digging into those stacks was never particularly popular.
End of conversation
New conversation -
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Hi, you can read this thread from
@patio11 here:https://threader.app/thread/1203797508566048768 …
End of conversation
New conversation
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.