Spyke

Replies

Comment on

Work harder, slave, or no promotion.

There's a few weird bullet points in there (the fact that it tells you you shouldn't be happy to be where you're at being one 🙄), but, all in all, I wouldn't call qualify this as "LinkedIn lunacy" for once.

You have no business leading a team if you say things like "this is not my job" on the regular and deflect responsibility and lack direction more generally.

Comment on

look at this junk!

As soon as I stopped trying to write textbook OOP stuff, this stopped occurring to me. That was years ago.

I'm not saying I write perfect code, no. But when I read bad stuff I wrote, I can understand it and think of ideas about how to improve it if that becomes necessary.

On top of writing more functional-style code, the way I achieved this was:

  • Absolutely no inheritance whatsoever. Composition + interfaces work wonders for what I do.
  • Minimal mutable state. This pays dividends when debugging.
  • Ditto for type-system-encoded nullability markers (ie. ? in C#, std::optional in C++...)
  • I avoid writing code just-in-case something happens. If I haven't run it manually or via unit tests, it goes to the garbage bin (not an absolute, just a guiding principle). There's a chance that code isn't even correct to begin with and you'll have to throw it away should you ever need it.
  • Low indirection. I don't want to jump through 10 functions to see what something is doing, and nobody else does either.

Comment on

AI Software Development Is Near-Impossible

Reply in thread

At least, human agents can take responsibility for their actions, and they learn. When they fail to do so, they get fired.

You're right, it's not only that the subordinate is an idiot. It's also a pathological liar that never learns and can't take the blame for their fuckups.

If a subordinate persistently sneaks in bad code despite being told not to, this is grounds for dismissal as far as I'm concerned.