These are the kinds of facts I come here for!
But that’s why we have code review. Pair programming is amazing for knowledge transfer, not really as good for writing bug-free code.
hey now. those weren’t bugs, they were future features
That’s the thing where the programmers mail their boss screenshots of bits of the code they have written, right?
… elon couldn’t figure out how to open the pdf’s
Manager (Denholm Reynholm voice)
— This bit (points dramatically) This looks interesting. What is it?
Programmer (nervously)
— (peers at screen where finger is pointing) Um, that’s a semicolon, sir.
Manager
— Hm. Fascinating. Why is it there?
Programmer
— Because… the code doesn’t work if it isn’t?
Manager
— EXCELLENT that all seems to be in order, then. Well done. You are not fired. Please go back to your dank cubicle in the basement now. That is all. NEXT!
The hits keep coming!
Such Management, Much Technical, Wow!
Aside from the insane micromanagement; mandating all those fields in the subject line when email already provides the sender and a timestamp and (if the people who used to maintain it haven’t already been fired) having some flavor of directory where you can pull department and organizational information is more or less ubiquitous seems like something that should embarrass you when you are on a zOMG way hardcore 10x coders! kick.
It’s honestly a bit of a surprise in that respect. I was certainly expecting him to do it disastrously wrong; but doing it wrong in a very manual and labor intensive way seems at odds with the theory of making twitter efficient and engineering driven; where, say, pulling a couple of your tesla loyalists away from failing to implement the promised full self driving to build a deeply flawed machine learning system that monitors twitter’s revision control system looking for slackers and traitors would provide results at least as bad; but with a veneer of cutting edge efficiency.
Well, that’s hardcore for you, innit.
Fuck sake. Isn’t that why we have tools like Jira?
Hey, enough with the nerd talk, and let’s stop lollygagging on those TPS reports, mmmkay?
This isn’t just limited to coding. Have you ever written an email, read it over half a dozen times, then received a reply 30 seconds after sending it pointing out an obvious typo?
Our brains are very good at understanding what we meant to write, to the point where they can tell us that we wrote what we meant rather than what we actually put in the document. If we have to explain it to someone else (during a code review) or to an inanimate object (rubber duck debugging, or perhaps during the pandemic when lots of people worked from home “pet debugging”) we can’t as easily gloss over those differences between intent and implementation.
This might drive more people to jump ship.
I wonder if Gab, Parler, Truth Social, etc, will put back the ActivityPub code, only to find out that no one will federate with them – and they can’t stand each other.
Shakes head We don’t talk about Jira.
I’m hardcore about Subject: line use (and don’t get me started about proper filenames!), but yah, that’s insane!
… but it says right here, “teams build better with Jira Software, the #1 tool for agile teams”
THEY COULDN’T SAY IT IF IT WASN’T TRUE
Is it wrong that I heard that to the tune of We don’t talk about Bruno from Encanto?
I wonder if Gab, Parler, Truth Social, etc, will put back the ActivityPub code, only to find out that no one will federate with them – and they can’t stand each other.
I would love to see them eat each other!
That is some interesting news about Tumblr, though. That could be the jumping-off point for a lot of people to see how the Fediverse works.
I think they will probably see exactly how it works when a bunch of instances don’t federate with tumblr. Tumblr has such a huge and diverse population that there is something for everyone as far as reasons decide not to federate - plus they just let porn back on and never did get rid of their Nazis…