Show Navigation
Conversation
Notices
-
> experienced engineer who volunteered to to a 12-week "internship" at Twitter to try and fix things. He seemed motivated and determined to make an impact β but threw in the towel after 4 weeks.
farside.link/nitter/GergelyOroβ¦
/via mastodon.cloud/@cspam/10955807β¦
Has this "experienced software engineer" worked at big companies? How does he expect to understand a complex distributed software system in only twelve weeks, much less make any significant changes?
The rest of the thread agrees, and the answer to the first question is that no, he is a "10x" type programmer (start things, run away) who only worked at startups.
-
> no desire to rethink and change, despite massive gutting to the org
(tweet seems deleted)
mastodon.cloud/@cspam/10955808β¦
This guy is such a comedian (unintentional). Again zero insight. With massive gutting of the org, how does anyone think of a reorg? All you are thinking is "omg everything is on fire and the guy who knew where the fire blanket is was fired".
-
> The problem Twitter will have on the engineering side is they would need to hire experienced *software engineers*, going forward, but they will only get experienced coders/programmers/hackers.
> They also only reward those approaches. Software engineering is longer term focused.
farside.link/nitter/GergelyOroβ¦
That sums it up nicely.
-
@clacke After reading that thread, I'm struck by the way no one mentions that Twitter's infra was constructed in the hair on fire "fail whale" days. There are probably still millions of finger in dike scripts and patches that no one wants to touch because they don't want to crash the system.
It is likely and expected that the new super programmer would stumble over these, and if there wasn't the culture of communication--the time spent talking about random stuff that opens a new employee to discussing the issues they're finding--to teach the intern to talk about such things, I'm not sure an "engineer" would do more than a programmer, except maybe stick around long enough to figure things out.
-
@LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} From my impression, nobody over there will be allowed to sit down and understand how things work. They need to poop code all day or they're out.
Things can only get worse from this point.