Can definitely attest to this. The frequency of outages at my company have increased drastically the past year, especially ever since incorporating agentic development. I’m seeing all of the dev best practices go out the window. We have a few vibe coders that are posting 15-30 PR’s per day. It’s way too much for us to review. We’re not a big shop.
I think we’re going to have to hire more people just to review code across the industry I think. And those people will have to know how to actually write software otherwise what are they even reviewing. Maybe the models will get so good they never make a mistake. Doubt it.
When you edit a commit, it creates a new commit. They are immutable. You can still find the old commit via the reflog, until it gets eventually gc'd.
If I had to guess a reason they were downvoted (and I didn't downvote, to be clear), it's probably because people see stacked diffs as specifically solving "reviews clearly taking too long, too much content in there", and so it feels contradictory. Then again, as I said, I didn't downvote!
"a pricing model based on seats, a product roadmap built around features rather than outcomes [is outdated]"
I disagree with this.
On pricing, I get that agents and tokens can scale in a way that's unrelated to # of users. But for much SaaS software, AI remains helpful to a human and the human remains the receiver of value. Seat-based pricing is easy to understand and you can always layer in token/agent costs thresholds.
On features vs. outcomes, the latter is hard to define and measure in many industries. In marketing SaaS, which I know well, you can't often tell what outcome to expect. You have to try a lot of ideas and some will hit. No way a SaaS vendor can guarantee that.
If if this person really is a distinguished engineer, then they are part of leadership and it's their responsibility to set realistic expectations. Leadership knows this, they just don't care and won't care until the job market improves.
> "80 percent of Gen Z say that they want a romantic relationship, but 55 percent say they’re not ready...We’ve screwed up a whole generation with this idea you need to overly self actualize before you can be in a relationship."
In big companies, the why is 80% of the work. I could swear actual dev work is less than 20% of a “developer’s” job at a standard large (non-SV/FAANG/tech-first) company. The rest is holding a lot of really weird organization-specific context in your head to make the right decision.
To be clear, I'm in favor of nuclear, but people attack it saying it does change the local ecosystem (heating up water for cooling and pumping the warm water into rivers, and of course the nuclear waste).
Here we just had someone say that hydro is fine because it only changes the local ecosystem so I jumped on that line of reasoning. I would argue with you that nuclear changes the local ecosystem way, way less than a dam does and so it's even better.
I often have 10+ running in parallel. I’m attacking parallel problems that aren’t interdependent. Sometimes adding additional products can bring me up to 15+.
Gotta have really good test harnesses so they can largely fix themselves.
This page is buggy for me and doesn't show any plans. But when I go to their main pricing page, it's got some contradictory info about which plans include "Kimi Code". The $19 per month plan says that it comes with "Kimi Code available" but then shows an "X" near Kimi Code while the others have labels like "1x credits". So I guess they meant to say that it doesn't have it?
> The inevitable and unfortunate result of "handing out 'free' stuff" however will always be widespread fraud.
The optimal amount of fraud is not "zero".
The goal is to enforce just enough to keep the fraud below a threshold while not making it too onerous for the people who need and receive the benefit.
And, if you really want to go after fraud, you are far better going after the people who commit it at an organized institutional level: see GOP leadership in Florida and Medicare.
Unless the big universities “expand” by linking up with the regional colleges, giving them a branding cachet that will attract students, there is one group that will benefit enormously:
Conservatives.
They require an uneducated and ignorant electorate. It’s the only way they can hoodwink voters into voting against their own best interests.
tl;dr - for the same reason as any other coastline or complex border.
Also, it annoys me that the trail in question is advertised as allowing one to walk the entire English coast - but fails to mention Wales and Scotland are in the way (the trail is not contiguous).
Market saturation for tech products + new competition from vibe coded startups moving into mature enterprise spaces.
The rate of non-tech business growth has slowed, who is going to continue to buy all these cloud software services? Tricking consumers into subscribing to AI tools or extra storage only goes so far.
the best implementation i've worked with was SuperSmartLog (SSL) at Meta, which was open-sourced at interactive smartlog (https://sapling-scm.com/docs/addons/isl/). There are also extension for it in VSCode, etc.
Surprisingly it never gained the adoption it deserved.
They confirmed below that you should be able to use this with jj just fine, just like you can already use gh to create a PR that you've authored with jj: https://news.ycombinator.com/item?id=47759426
I’ve gotten pushback from customers on this point a few times, so I wrote up my reasoning and wanted to see how others think about it.
My argument is that giving this information to customers who need it is different from publishing it openly to the whole internet. I think many companies treat public subprocessor lists as a default best practice without thinking enough about the security tradeoff.
Would be useful to hear from people who have handled enterprise security reviews, privacy reviews, or trust-center decisions.
IBKR relentlessly advertises on the radio, so I’m aware that on their scheme you earn an interest like incentive coupon for every day you hold open the position.
> The industry calls this “10x productivity.” I call it what it is: a system that generates output at machine speed and forces humans to process it at biological speed.
The question is can you tolerate the amount of PRs thrown at you per day on top of reviewing the exponentially growing mess of code that continues to double every hour and being paid less for it.
Just learn to say no and leave. Why do you tolerate the increasing comprehension debt that is loaded on to you.
You will never get that time back. Just give it to someone else that thinks it is worth maintaining that slop for less.
> The bottleneck is no longer engineering. It’s moving up the stack to judgment, customer insight for desired outcomes and distribution.
My posit is this: engineering never was the bottleneck, or at least hasn't been for 10 years now. Frameworks and best practices are pretty well known at this point. AI is simply exposing this reality to engineers' faces.
Proof point - most publicly traded SaaS first businesses S&M equals their R&D spend, if not dwarfs it. You're going to see this even more lopsided going forward.
I think we’re going to have to hire more people just to review code across the industry I think. And those people will have to know how to actually write software otherwise what are they even reviewing. Maybe the models will get so good they never make a mistake. Doubt it.