2 ms·
This is gold. Here’s a horror story for you. A few years ago I worked for this startup as a principal engineer. The engineering manager kept touting how he wa
by reactordev 11mo ago
This is gold.
Here’s a horror story for you.
A few years ago I worked for this startup as a principal engineer. The engineering manager kept touting how he was from XYZ and that he ran Pythonista meetups and how vast his knowledge of Python was. We were building a security product and needed to scan hundreds of thousands of documents quickly so we built a fan out with coroutines. I came on board well into this effort to assist in adding another adapter to this other platform that worked similarly. After seeing all the coroutines, being pickled and stored in S3, so that nodes could “resume” if they crashed yet - not a single create_task was present. All of this awaiting, pickling, attempting to resume, check, stuff, report, pickle, happened synchronously.
When trying to point out the issue with the architecture and getting into a shouting match with Mr. Ego, I was let go.
- jacquesm 11mo agoClassic. I had a similar run-in with the CTO of a company a decade or so ago who point blank refused to use version control for the source code. He insisted on having directories that got zipped and passed around from developer to developer and good luck figuring out how to integrate someone else's changes. I won that particular battle but it was uphill all the way, at least he had the grace to afterwards admit that he'd been an idiot.
- arresin 11mo agoThat is a very different run in.
- jacquesm 11mo agoEgo can get in the way of progress, that's the similarity here. The OP was let go, fortunately I was not but the differences in programming environment or task have less to do with the issue here than the similarities.
- reactordev 11mo agoWhen you assume you know, you shut the door to the possible. Ego is the worst thing an engineer can possess.