It helps! Ive seen it with two jobs completely change the culture around code review.

• Instead of you/team lead being the bad guy, its now the code/process.
• Code becomes more stable and releases actually become more frequent.
• If something goes wrong, your VM/docker/box/etc… can just be re-spun up by the same process.
• Easier to onboard since the same build process is in the CI. And is constantly being used rather than relying on the README (that may not have been updated in a while).

Mind you its not perfect of course. You can still “Vibe” test and/or remove tests that dont work. And make the project more brittle. Or go overboard with lint rules (I actually had to break up a fight with that one). But its much better than the old process of merge and pray.

Make ci/cd part of the process. It stops a lot of people who push huge unmaintanable changes.

If it doesent pass the tests and cant build then it stops them from merging.

It would be fun to create a CURL converter. Just simple aliases or conversion tool.

I just looked it up, looks like there may be something like it here: https://github.com/christianhelle/curlgenerator

I like the look of this: https://www.createopenapi.com/

How interesting! Very nice visualization.

I still have one. Its good.

I mean you can …but its gonna be slop.

I remember some crazy stuff back when I had to work with a Java + ember.js project. Everything was like that.

Thats kind of you to say 😀

WTF

Cool, good to know someone else has the same experience.

Ive been on a couple of multi-year projects and they are NOT fun with OOP + developer went crazy with patterns they were experimenting at the time. Its what made the “rule” pop up to begin with.

Its the best/worst thing about OOP no matter what language.

We had a rule at work that if you are 3 levels or more down an inheritance tree, then you are too far. The cognitive load is just too much, plus everything stops making sense.

One level can be great (MVC all have great conventions, MCP as well). Two can be pushing it (Strategy pattern when you have physical devices and cant be connected all the time, Certain kinds of business logic that repeat hundreds of times, etc…) But even there you are kinda pushing it.

I need code that I can look at a month from now and know WTF is happening. And sometimes its better to have less DRY and more comprehension. Or maybe im just a forever mediocre dev and dont see the “light”. I dunno.

Llms do create a lot of slop code thats for sure. Makes me want to get off github.

I had a job that used COBOL and programmed in it. Its not terrible. It even works with sql.

The issue is the decades of code with little to o documentation, the fixes for issues like y2k that wirked at the time but now have problems, and greedy companies that want you to pay per processor. All the while you yourself are one of three people in the city that are looking to slowly pull everything out of COBOL, making it just a bit harder to get a job next time.

The account is deleted now, but theres still records: https://piefed.social/user/lookup/cohen_drz/lemmy.world

Piefed keeps the accoint just for this reason.

Here is yet another post with the same observation: https://discuss.tchncs.de/post/53070513

I tried bringing this up and got downvoted pretty hard last week. We have accounts that will post a huge amount, slam servers all in one go, then disappear. Its causing issues with federation. Especially with smaller instances.

I like comics and prior to say a couple of months ago, it was a great conmunity.

To get a surgery done.

Please do

We should commission the individual behind !unix_surrealism@lemmy.sdf.org for a sequel :D.

I remember the comic being much larger than I expected back in the day.

I can see the dependencies mucking everything up.