Fast pace environments = we didn’t do any planning or architecture so you’ll be fire fighting 24/7. Oh and our management doesn’t understand software development so they’ll be blind to the issues

A junior with a LLM is like a gorilla with a sledge hammer. Good luck getting to to do anything useful. You’ll need even more luck getting to not break anything.

Time comes for us all

There’s a middle ground

Junior devs not abstracting anything and now the app is unmaintainable

There are some that only cause death up to two weeks after ingestion. So just make some soup ig

I have th same feeling. People keep saying all this stuff all I see are non-novel toy application.

That’s what I’ve noticed to. Mm I have co worker who don’t even read the code anymore. Full on vibe. Makes me so frustrated

AI written code ≠ work you’ve done yourself

They should make their cars more home mechanics friendly first

It’s literally a single small python file.

Start small first. Try to build a 2d engine

I usually think "they are lying*

I’m not even sure. From a LLM standpoint that’s even a good idea. From all my research on getting good output context matters. So if you throw too much junk in the middle it’ll get evens stupider then it already is

Sometimes it the model just decides it’s perfect sometimes it keeps adding unit tests and features. I’ve also heard of cases where it determines it’s in a loop a kills it’s PID lol

That’s just miss representing the data for political reasons. Again it’s just politics which has no place in engineering

deleted by creator

Communication ≠ politics.

Communication in engineering should rely on empirical data not personal opinion or vibes.

The post above only has one sentence where they make a unsupported claim that being involved in politics was necessary to have completed the feature.

The bridge example is to show that personal opinion has no place in projects and that workers should not capitulate to their superiors when they determine unsafe situations are occuring. The “shoddy bolt my boss designed” would be a stand in for whatever crummy practice people are being political about in a software project. From a shitty tech stack to bad project management practices.

Ego and politics is the death of a project.

Politics has no place in engineering disciplines. Imagine if we talked about building bridges like this. “Sorry your entire family died when the bridge failed. My boss has an ego and we have to use the shitty bolts he designed. I’m just doing my job”

Granted not all projects carry this degree of risk but we shouldn’t normalize sub standard practice. Long term risk is generated by bad code which can be and often is detrimental to the profitablity of a project. One of your jobs as a software developer is to be able to communicate this effectively with management. There are cost implications to churning out shitty code.

Bad form > poor product > unsatisfied users > loss in sales to competitors

I half way agree. I always say form shapes function. Sure you can write good code in any language. But some encourage it more then others. Ultimately it’s the programmer fault when things get over complex though