top | item 44097166

(no title)

vijucat | 9 months ago

Not directly related, but an anecdote: well before AI, I was talking to a Portfolio Solutions Manager or something from JP Morgan. He was an MD at the firm and very full of himself. He told me, "You guys, your job is....you just Google search your problem and copy paste a solution, right?". What I found hilarious is that he also told me, "The quants, I hate that they keep their C++ code secret. I opened up the executable in Notepad to read it and it was just gibberish". Lesson: people with grave incompetence at programming feel completely competent to judge what programming is and should be.

discuss

order

JKCalhoun|9 months ago

My own tangential gripe (a bit related to yours though): the factory work began when Agile crept into the workplace. Additionally, lint, unit tests, code reviews... all this crap just piled on making programming worse still.

It stopped being fun to code around that point. Too many i's to dot to make management happy.

FooBarBizBazz|9 months ago

If you give up on unit tests and code review then the code is "yours" instead of "ours" and your coworkers will not want to collaborate on it with you.

However, this has to be substantive code review by technical peers who actually care.

Unit tests also need the be valued as integral to the implementation task. The author writes the unit tests. It helps to guide the thought process. You should not offload unit tests to an intern as "scutwork".

If your code is sloppy, a stylistic mess, and unreviewed, then I am going to put it behind an interface as best I can, refer to it as "legacy", rely on you for bugfixes (I'm not touching that stinking pile), and will probably try to rally people behind a replacement.

rwmj|9 months ago

Agile yes, it's micromanagement at scale. But writing tests and doing code reviews is good practice.

thinkingtoilet|9 months ago

What's wrong with writing tests? I sleep well at night when we push to production because of our robust test suite.

myvoiceismypass|9 months ago

I never found linting or writing unit tests to be particularly un-fun, but I generally really really value correctness in my code, and both of those things tend to help on that front.

HDThoreaun|9 months ago

It turns out that doing a good job at work is more important than having fun.

bumby|9 months ago

I used to work in aerospace R&D. The number of times I heard some variant of “it’s just software” to disregard a safety critical concern was mind boggling. My favorite is a high-level person equating it to writing directions on a napkin.

game_the0ry|9 months ago

> Lesson: people with grave incompetence at programming feel completely competent to judge what programming is and should be.

As an employee at a company with a similar attitude, I cannot agree more with this.

dwaltrip|9 months ago

Hubris and fragile egos run amok

A burning need to dominate in a misguided attempt to fill the gaping void inside

Broken and hurting people spreading their pain as they flail blindly for relief

Our world creaks, cracks splintering out like spider thread

The foundations tremble

varjag|9 months ago

It doesn't help that most "tech visionaries" or people considered tech bros these days more often come from accounting or legal background than anything technical. They are widely perceived as authorities but come without the expertise. This is why it's so perplexing for the techies when the industry gets caught up in some ridiculous hype cycle apparently neglecting the physical realities.