You've not seen it until you find the right twitchy engineer to solve something that your corporate division has had trouble with for a while, and he does it in a weekend.

He isn't always the cerebral engineer that long-term integrates it into your system, doesn't know how to make the final build, doesn't necessarily know how to document it properly, but he fucking busted through the core problem in a weekend and built a path that the others can figure out more thoroughly afterward.

Separately, it's a web of them coordinating on things, technical or social, especially if they also have some coordinators/organizers to keep all those pieces together. 🔥

nostr:nevent1qvzqqqqqqypzpeq8qdexw2mfwzc2y96r309lsepu2a80mdkjtalts9hkhrem4ug7qqsqtswsgd5nlzcd574t2echp3ljuh332qs7m9p4pltn6q7n8fd6nhsq2ue3g

Reply to this note

Please Login to reply.

Discussion

accurate

Beware the eye twitch

What this feels like is hard to put into words. Once you have an idea, you have to code it. Whether it's a fix or a new solution, the urge to make it extant is incredibly powerful.

I've heard writers describe a kind of animal spirit that takes over them and forces their words into the page. This is the closest I relate to: it's almost painful for me to discuss a technical problem without itching to write up the solution I've found.

I had a junior colleague at a large company get admonished once for solving a problem "which had been assigned to someone else" (and had been for weeks). I get that from an organizational POV but: these are not your people, time to move on.

Also, time is limited, and deciding when and where to unleash this ability is the secret to being a functional (and happy!) being.

i had a CTO of a shitcoin project take over a task i was assigned to one time... shortly after that i was fired... and it was because i said that some stupid, insecure thing a colleague said was stupid and insecure

how insecure*/ _inSINcere* lolz culda used that infamous line by the terminator "I'll B Bach"/