I think my least favorite part of Lemmy is all the posted screenshots of tweets. It just took me 3 tries to get to these comments.
What benefit do tweet screenshots serve?
I know what context they are looking at and I don’t need to make a twitter account to view the relevant replies.
Slop points aside, I found 5.4 to be pretty ass compared to 5.3 codex. Took way longer and wasted more tokens.
more tokens
= more money for Amazon = more profitssss.
that’s good, mandatory meetings always (ALWAYS) solve the problem! /s
I like that this is lowkey a Polymarket Advertisement too. The internet truly is a wonderous place.
hhnhnhn polymarket
Come see why you’re all wrong sore losers, here in a lenghty rantarticle I explain why AI is so good and is going to replace you all:
pointing to 80 port was the salt in the wound, i presume?
With https no less
Theres too many s’s in https
That page is filthy. You should be ashamed of yourself.
I love the https and port 80 combo. Really sells the incompetence.
That’s what makes it obvious that this person has been around the block. Or a few blocks.
Should have been brought round back.
Goddammit, I clicked.
Hey thats my website! Gemini, call the police!
You rang? (My user’s name in my laptop is gemini, and in my home pc, and anywhere i use my flake really), btw check out my terminal cool right?:
It doesnt look right in the tty though, i havent bothered to make it change the characters for some it can print, i use oh-my-posh btw, and fish.
So did you call the police yet?
Every breath you take starts playing on the background…
Look mommy, I made big poo poo.
I use AI to reduce my overly complex shite and automate making boilerplate stuff I can’t be bothered with.
I’d never ever just let it run roughshod over the whole code base unattended.
I just make some shell scripts to automate boilerplate.
That way, once I have properly debugged it, I know it will give the correct output everytime in the future and I don’t need to keep checking it.That’s nice too I guess, and more eco friendly
But there are different types of boilerplate, planning for all of them can be a bit of a pain
I don’t plan for all of them.
Just when I realise some specific one is getting too repetitive, I make a script for it.Never needed to do so at home (yet), because my IDEs usually provide good enough boilerplate and I am mostly doing learning projects (i.e. hardly any repetition), but I did make a few in one of my previous work places, which someone else might be using rn (hopefully not, because it was meant for me and not for users).
Positive diff? Pfft, amateurs. If I ever see even a 1000 line PR I’m instantly rejecting and closing it. Learn to code, not generate bullshit.
If you write tests and add features you can easily go up to 1000, don’t know what you’re talking about
1000 lines isn’t that unreasonable for a PR. Commit size matters more.
I’m pretty sure the shitty Windows upgrades as of late has been vibecoded as well.
ms themselves confirmed it, “bragging” that 30% of windows updates are written by ai
Figures Reddit has a Codex sub, where they are all shilling for it.
Live by the vibes, die by the vibes.
You know what’s funny?
I use AI to develop software. However when I’m looking for libraries to do things if I see a CLAUDE.md file I have to look and see when it was added and hold it against the library if it’s early in the history.
It’s like prewar steel.
I also recognize it’s hypocritical.
meow
Interesting. I’m unfamiliar with the purpose of that file as originally intended, but if I understand it right, it probably can be used to detect PRs with ai-made code. Tell Claude to write a particular string in every PR, and then reject all PRs with that string.
I love this sabotage. Has this worked against anyone that you know of yet?
It’s not hypocritical. Because you use AI to code, you know how easy it is to just let the AI do it’s thing and not check it’s work. It’s almost like a sirens song. So you know the odds that a library that was coded with AI probably wasn’t checked by a human. That’s just called experience.
It’s the difference between checking for questions in stack overflow and implementing solutions VS pasting every SO solution blindly until something works.
I do use autocomplete and ask plenty questions, sometimes even use an agent so it makes small changes that I then review and test, but I would never commit unchecked changes, and a claude.md implies that the AI is coding AND committing without supervision.
I can’t stress enough how different those scenarios are.
People who share the size of a codechange as a mark of how effective ai coding agents are truly miasbthe point of code changes.
Big Diff Energy
You reminded me of a story I recently read, where the author highlighted just how much awesome programming someone had done by describing how their hands were cramping up.
It’s like estimating how well an artist paints by looking at how much paint is on their clothes, or judging how good a cook is by how many cuts and burns they have. The actions that cause those things are incidental to the process, not central, and an excessive amount points to incompetence, not hard and skillful work.
Didn’t you hear? We’re going back to KLOC for measurement of f productivity.
If we’re going back to the 80s, do we at least get the company provided cocaine?
I’m just a hobbyist, but I’m always more proud of commits that remove stuff.
i refactored some web code i wrote ten years ago and it’s more elegant and a tenth the size with new features because of language advancements. feels great.
Removing shit and it still working perfectly the same is absolutely a goal everyone should have. Less code means less to maintain.
And being more performant, the perfect trio
Unless its template voodoo magic
those aren’t upvotes?
Lines added, lines deleted
Might as well be bragging about pictures they’ve taken of their bowel movements.
Please tell me this subreddit is satire
No, this is the most serious subreddit in all of reddit.
People who’ve never reviewed a PR be like. Wow green number big, is good.
Number of lines of code written is a shitty metric to measure productivity.
In college, on the first day of orientation, someone in my class bragged that they wrote 50,000 lines of code for a game that was similar to tic tac toe, emphasizing that he “wrote a lot of code”. A TA told him that it wasn’t a sign that his program was decent and that it really didn’t seem like it should take 50k lines of code to make something as simple as his game.
He dropped out after the first week of intro to programming.
That’s nothing, I wrote the code to return if the input is even or not in 1M lines of code.
If 1 no else if 2 yes else if 3 no…
If you want to learn natural language processing, this is actually a fun example to generate code for.
Exactly…
And yet I experience it so often. That or “effort points” as the metric being used to determine who all stars are.
Either as a metric just encourages gaming of the system:
- Why write one line when I can write the same thing in 20?
- Why take this one effort point task I think will take three when I can just skip it and grab these one effort points I think will take 20 minutes?
I’ve been on teams that on the surface didn’t have these metrics matter, but the top effort points achiever got bonuses on the DL.
What did you do?? You refacted the code and now it’s better organized but you overall got rid of lines?
I’ll set up a PMD meeting to help you out of this problem, but fair to say don’t expect a raise or a bonus this year.
I wouldn’t say PR size is a bad metric, you usually just need yo read it the opposite of how sloppers do it, i.e. the most productive PRs are short and focused.
I’m working with a legacy codebase for the last few months, where a simple PR often ends up crossing a 1000 lines count due to testing and commenting, and I can’t stop apologizing for those.
Yet there are people out there bragging about 10x changesets.
PR size is an awful metric. The bigger the PR, the less reviewable it is.
Yes, that’s what the comment said — smaller PRs are better.
PR size is still an awful metric. It should be within bounds but it should never be an actual metric. Treating it as a metric is an idiotic idea.
Then Devs focus on minifying the code into an unreadable mess
I’m not saying it’s a good individual metric. In fact, applying individual metrics to developers (or most workers really), will only land you in Goodhart’s hell.
But as part of holistic operational health tracking, it’s a useful team level metric, as there is ample evidence that shorter PRs tend to result in less operational issues. And, of course, this is only valid if you don’t try to tie financial rewards to it, otherwise people will forget that PR size is a proxy measure for how easy changes are to review and rollback.
We are n weeks away for not needing developers anymore
Let n be a natural number, and b be the time to the next major extinction event.
About 6 months to replace devs since 2023.
Well, they do it Japanese style - by forcing developers to leave due to burnout.
Anytime now… Anytime…
