Operationally intensive tech companies are both a) still tech companies and b) still operationally intensive.
-
-
Replying to @patio11
If I had a dollar for every time I'd seen a great engineering team get smacked in the face by not anticipating ops problems, I'd have $8.
2 replies 2 retweets 15 likes -
Replying to @patio11
Ops here means, typically, "A human has to interact w/ either atoms or another human in a way which is not conveniently replaced with API."
1 reply 0 retweets 8 likes -
Replying to @patio11
Representative example: smart, engineering-heavy teams might assume a labor pool for a service universally possess smartphones and literacy.
1 reply 0 retweets 3 likes -
Replying to @patio11
Tech folks often assume that expensive ops problems trivially solvable with a CRUD app, failing to recognize that BigCo has CRUD apps, too.
1 reply 2 retweets 5 likes -
Replying to @patio11
"Hah we can totally CRUD app our way to FedEx quality ops." I have bad news for you about number of very smart ops people working at FedEx.
2 replies 1 retweet 9 likes -
Replying to @patio11
"We'll be able to cut CS load by 90% with good UX and software fixes." I have bad news re: what 10% of CS team for X0k trans/day looks like.
2 replies 0 retweets 4 likes -
Replying to @patio11
(n.b. I'm not-so-secretly terrified of the post-launch ops burden at Starfighter, which has engineering talent oozing out of our ears.)
2 replies 0 retweets 4 likes
(Recruiting has vastly higher transaction values than most on-demand companies, still implies LOTS of phone calls and invoice chasing.)
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.