I don’t necessarily want the people I share the link with to know my potentially pseudonymous user.
6,458 karma · joined March 8, 2019
I don’t necessarily want the people I share the link with to know my potentially pseudonymous user.
It’s not their problem that you, or anybody else, think you are owed 24/7/365 emergency support.
You would not judge what people think about politics by only reading comments on a Hasan Piker video (or only on a Nick Fuentes video).
To me, tech debt, captures the idea that we cut corners now to move faster, with the understanding that it will need to be "re-paid" and cleaned up later, otherwise we take on too much tech debt, and everyone knows too much debt is bad...
AI slop code means people feed their tasks to a model, trust it to drive the changes, they might do some cosmetic clean ups, then generate a 3 pager PR description they didn't even read themselves, then toss it over to the code reviewer, let that chump figure out what the hell I was doing while I ship 3-4 more PRs...
I was thinking about this when I tried a faster model (Cursor released something fast about a month ago?). It was such a joy to use (well, at least compared to other models, where you wait 5-10 mins for even simpler tasks), and I noticed I felt much closer to the problems, and I got closer to a "flow" state... ...but unfortunately, the models are faster for a reason, and the output got worse. While I did enjoy my job more, I was also left worried that the model missed important things (and it did when cross referenced with other models or just doing the thinking myself).
IMO we need much faster yet capable models to bring back a bit of a flow state.
Another approach worth trying is to get some agents researching 4-5 tasks thoroughly in the background, discovering all the relevant details, collecting all the files likely to be edited, their content etc..., then work on one thing at a time with a better focus for yourself, maybe use a faster model.
One thing I try to do is code manually if I know that I can be faster and better. It's convenient to stick to one tool, the agents, when editing code, but for smaller clean up tasks, they just never get it right, and sometimes it's better to do 1 min manual work over 5 mins of explaining what you want and the agents still not delivering it...
I’m working at an AI pilled company and I just don’t see the gigantic improvements. Not in my work, not in anyone else’s. It’s a great technology, we finish some tasks faster, some tasks really 100x faster, sure, but it’s a <2x improvement at an organization scale. It’s not like suddenly we cleaned out the defect list. It’s not like I can use any app without seeing 5 bugs in the first five minutes. It’s not like I got any meaningful new features.
I tried to get it to work for five minutes, it couldn’t get it to work.
Then I was so pissed that tried for another thirty minutes to “prompt” my way to get the events created correctly, highlighted the timezone issues…
Then gave up and did it manually in 2 minutes.
This lady says you should let your children get hooked on YouTube, who knows what could happen if you don't!
Looks like biased research, fake coverage amplifies it, it's all manufacturing consent.
The “fact checkers” pretend they are objective and authoritative, but they are not, they are just one more opinion.
For the research, the four classification options are too many, it should be true, false, and maybe “can’t be determined”.
It's not only an AI company, it's the symbol of AI hype. This AI hype is significant part of the US economy, and the AI infrastructure spending basically half of its growth.
("it's not this it's that", I swear it's human generated slop)
In my own experience, newer products get more love automatically, because the testers, the devs, the team are on newer devices. Perf regressions are also harder to catch than simpler bugs and sometimes require extended usage to notice smaller perf degradation, and devs and QA do not really test like that (often enough).
The way I see it, older products will naturally decline with updates, as they are less of a focus while validating a new release. Sure, they get some "freebie" improvements, but I'm guessing the accidental "decay" outweighs any improvements.
I'm not saying they couldn't make it on purpose. I'm saying that (IMO) it's more likely that it gets worse with every update even without malicious, conniving people trying to get you to upgrade by worsening your OS.
I wouldn't be surprised older phones get slower with updates, in fact, that feels like the most likely scenario for me, based on my experience as a software developer.
But IMO, Hanlon's (maybe Occam's, too?) Razor applies. Most likely, the teams just need to ship features, make fixes, and they mostly test on higher end, recent devices. Sure, at some point, someone tests on a lower end device that everything still works, but they probably either do not notice the issues, or shrug it off, or rationalize it (it might make x worse, but users get y in exchange, so it's fine).
Well apparently a lot of people did. Maybe Jarred didn’t, maybe you didn’t, but most people correctly predicted what was coming.
or if I want to be cynical… so that they have a big enough project where they can force gigantic rewrites without considering the outcome from the project’s point of view, all so that they can fuel their marketing strategy.
To be honest, kind of obvious looking back.
Of course it can still be fake.
But from this person’s perspective: without Claude 0 BTC recovered in x years, with Claude 5 BTC recovered in x hours.
But maybe it’s about discussing an issue with 10 other people from different teams when it’s not necessary.
But we will never now. I guess OP didn’t want to pay the communication tax on expressing this idea clearly :)
I want to be better month after month, I want to be able to discover new areas.
Using AI tools makes sense to me. It’s important that you don’t believe everything the hype men are telling on Twitter, but it would also be a mistake to believe there is nothing valuable in this technology.
Young "AI native" coworker opens PRs with 3 screen slop description, I flagged that "I know he ain't reading all that, and therefore I ain't reading all that", so he should just give a max half-screen overview. I expect that the PR description makes sense, is correct, and have been reviewed by the person opening the PR. You can still use agents for that, but at least there is a chance with shorter descriptions that it's not completely bs.