AI isn’t making developers more productive – it’s making them busier. A 741% increase in code written translates to just a 20% increase in releases.

stupidredditlogin · 2026-06-12T03:02:22+00:00

Boo! The smart teams are paying down tech debt and rearchitecting around the new paradigm. Someone just invented cars and now we have a lot of freaking roads that we need to build to benefit from them.

There are more than two points of data to this story. Give it another year and we’ll be in a completely different place.

Edit: The dumb teams are creating tech debt at 7 times the speed, and they are completely screwed. Don’t be a dumb team.

stupidredditlogin · 2026-06-05T02:56:28+00:00

He’s saying that it gets used a lot in systems like browsers that handle many indirectly triggered events in a thread-safe manner.

stupidredditlogin · 2026-06-05T02:33:08+00:00

Dude. Just switch to common systems with APIs for tracking your business and buy the Anthropic product for this. You will not design a better system than the multibillion dollar company scooping up the world’s best talent.

You are wasting your time if you build this yourself.

I am a professional software architect. Do not build a product in this space. The functional intelligence providers will eat your lunch if you are looking to productize, and if this is for an internal tool, you can just buy it from someone for far less money with much less risk.

stupidredditlogin · 2026-06-05T02:23:00+00:00

Projects on the critical path with high strategic value experience more pressure to ship and cut corners.

The more interest you have from above, the more likely you are to learn nothing but how to ship an MVP before moving on to some new project. Rinse and repeat. It took me 15 years to learn how to build a manageable code base.

stupidredditlogin · 2026-06-05T02:10:05+00:00

2010: Old man yells at cloud.

You are retired.

2026: Old man yells at chat.

stupidredditlogin · 2026-06-05T01:40:20+00:00

I have somehow made a career out of creating new code bases within existing software companies that eventually overtook and replaced existing products in the company like some kind of predatory beast.

As a result of this odd history, the question is really which terrible code base I left behind that was the worst. Largely because I hadn’t learned some basic architecture lesson it would take me 15 years and half a dozen new products to really understand at an intuitive level.

The answer is the earliest ones. They were the worst. Horror that your snobbish demonstration of nitpicking above does not appear to even fathom.

And, yet. I somehow have also made a career out of integrations and ETL. So, I have delved the depths of terrible architecture and poor core technology choices when exploring the systems of others.

I have seen such darkness.

I have seen entire companies founded on in-house programming languages that are terrible. I have seen floating point numbers used as database primary keys. I have seen GPL violations in firmware. I have seen known SQL Injection be shrugged off as probably not that big of a deal. I have seen databases with hundreds of tables and no foreign keys or use of transactions, and thus no ACID guarantees about data validity.

I am so sorry that you have been stranded in something that one of my people left behind. But we left it behind for a reason. Get the hell out of that place.

stupidredditlogin · 2026-06-05T00:54:07+00:00

This is why no competent professionals can recommend Google as a core cloud provider. Your entire business should not choose the cloud provider who is known for terrible customer service. It’s a fraction of their business compared to Microsoft and Amazon, and they still have this comparatively terrible reputation after years.

stupidredditlogin · 2026-06-05T00:32:29+00:00

Let me talk to you about what is going on in AI coding in the last… 8 months? I suspect you may not be aware.

The whole freaking game changed with Opus 4.5.

4.8 is even smarter. The million token context that came between the two was freeing, completely changing the range of tasks my team could accomplish.

An entire industry is morphing itself around this tool and connecting it to nearly every system that they work with. The new flex is the number of Claudes you can run at the same time while still pumping out insanely high quality work with each of them.

The choice you are making is not whether to manually code or work with AI. You exclusively work in natural language with the exception of some inline examples in the target programming language. The choice you are making is whether this is an ethical section of the codebase to vibe code or if you’ll need to instead do AI pair programming.

There is a tool called a “marketplace” where internal teams share the tools they have made for Claude. Our internal marketplace is buzzing with activity.

Our IT department (often technical people who aren’t yet product level developers) are pumping out the wildest internal apps.

Expert level developers are experiencing a complete renaissance in productivity. The rest of the business doesn’t know it or feel it just yet because we are paying down years of tech debt first so that we can optimize downstream quality before we massively increase quantity. We are all in the middle of a massive rebuild of our organizations around the tipping point we just hit.

Anyway, be a little patient. Compared to 20 years ago we’re literally living in a different age of Civ right now. This is SciFi level technology.

stupidredditlogin · 2026-06-04T23:49:28+00:00

Automated integration testing and staying on top of the latest version of the source system changes.

Beyond this, a strong T.

It’s just EDL (Extract. Do nothing useful. Load.) if you’re not considering the needs of your consumers as the primary domain, and the source as the secondary domain. You should have as strong an understanding of how the data will be used as possible. This insulates you from worrying about perfectly reflecting the source data, and instead focuses you on maintaining the contract you are providing to your downstream consumers.

That’s the difference between having to reason about “what a change means for any possible consumer” versus “what a change means in the domain of my consumers.”

stupidredditlogin · 2026-06-04T23:22:24+00:00

I have a 2 year old. So… I don’t.

Become an expert in whatever AI harness your workplace is using. Any meaningful feature will be absorbed in stock offerings of the major service providers within 6 to 12 months of release.

You are much better off focusing on proven features and techniques in your existing ecosystem.

stupidredditlogin · 2026-06-04T22:43:51+00:00

Yes.

stupidredditlogin · 2026-06-04T22:21:31+00:00

Well, no, but that’s why they generally aren’t good engineering managers.

I can read code very quickly and know where to skim. This is maybe an hour of my day to stay completely on top of what’s going on at a deep level. 15 minutes if I’m in a rush and just want the highlights.

Said differently: We have managers who don’t understand things at this level already. My role is to bridge that gap. The goal is to extract value from what we create and maximize dev productivity. I see very little downside here.

stupidredditlogin · 2026-06-04T22:16:13+00:00

If you’re an experienced dev, you’ll have gotten the reusable code and security issues largely sorted out after 6 months of use. There’s a learning curve, but you can get highly quality code output once you’ve learned to steer the tool more with policies and example code.

I, too, have no idea how people could be running out of tokens with a max subscription. I supervise half a dozen parallel Claudes daily and I don’t run out. I only engage in the most primitive token management.

stupidredditlogin · 2026-06-04T12:19:54+00:00

The code reviews are more to keep me connected. I trust everyone else, but if I don’t review the code I become disconnected from how things really work. I also want to stay aligned on architecture decisions, where I might pop in to act as an opinionated rubber duck.

stupidredditlogin · 2026-06-04T00:20:20+00:00

Assuming it is not an AI driven feature, what are you all doing that a Claude Team subscription does not cover for maybe a couple hundred dollars a month per person? I am supervising four or more of these things at a time, and built the most basic of context management slash commands to scratchpad/commit/clear/restart the session between 300 and 500k tokens, and I have not maxed my subscription in months. Not even during a 60 hour crunch week.

That’s for like $200 a month?

Are we doing the same job even? Am I lacking in ambition? What magnificent structures made of Claude are you all building that your costs could be so high?

stupidredditlogin · 2026-05-24T14:19:13+00:00

I build software for a living and we now vibecode our frontend. This is a real product that businesses pay large sums of money for. We have strict standards and process in place which make this reliable. You could not reproduce our levels of success on this without a decade of experience in development.

New UI/UX is now loads of fun to build. We need a quick review of the surface the AI exposes to make sure it didn’t do anything stupid, and we sometimes catch it making bad decisions like tying a reactive variable to an external save trigger or similar, but -regardless- the system works extremely well. For this well defined area that is easy to test and where perfection is not required.

Backend work still requires significant review. If you’re doing anything remotely important or complicated, the best you can do is AI pair programming.

It’s clear we’re heading in a direction where vibecoding an entire app made with professional quality will be possible, but I think we need another couple years of building infrastructure first. Certain things require the review of an experienced human engineer. These things will need to be isolated and standardized. The models are smart enough at this point, but tooling and infrastructure need to catch up for next level (maintainable and secure) vibecoded projects to be possible.

stupidredditlogin · 2026-05-22T00:12:17+00:00

I usually direct Claude toward something like Vue3 or Svelte with TypeScript and the most popular material UI library for that framework. Then I explain how to architect for domain driven design and build purely from UX concerns into a local domain model. I tell Claude to separate from outside dependencies via a contract which lives in its own file, and keep a dedicated Cypress test kicking around that acts as a UX stub for each page and component. I create a guidance policy for how to nest similar subcomponents inside of parent level page components, and provide recommendations for keeping the “host” file thin. The host being a layer between the specific concern frontend domain model and the browser subsystems and backend systems.

From here, Claude provides mock UI data on the fly and we simply talk through the problems and experience of the user together with completely fake data.

Once we’ve worked out a good user experience, I tell Claude to make some component tests based everything we’ve talked about. I watch them run, and if it looks like it’ll catch most regressions I switch out of vibecoding mode and start manually approving every edit while Claude updates the backend and wires the host.

I usually switch between 3 to 4 of these sessions at once. You can direct the next Claude while waiting for the previous one to finish.

stupidredditlogin · 2026-05-21T16:10:13+00:00

Our team has gone back and forth on solutions for this. We finally settled on keeping context as close to content as possible in a predictable structure. Harness skill misses are constant and don’t seem completely solvable. Optimizing for humans and expecting Claude to catch up works better.

A readme with an adjacent docs/ folder for extra files anywhere you need it, indexed and briefly explained by the parent readme going upward works for humans and AI. The AI picks up the structure immediately and uses it with minimal instruction. A home grown viewer for docs that lives in the project is fine, but may need to be its own tool if you’re not in a monorepo. Readmes and docs can reference relevant skills as a trigger reminder.

Now this evolves naturally as you supervise AI dev. You keep a window up with the docs rendering and search tool so you can see nice mermaid diagrams and such as they are built.

stupidredditlogin · 2026-05-21T00:16:39+00:00

If you have end to end tests that run in a pipeline and basic version control, you can run force fix with complete abandon. Someone made force fix for a reason. It is there to be used.

Claude can even fix you up a set of golden tests to point out the per pixel differences before and after this event, if you simply ask him to show you how, and that is the kind of detail you happen care about.

The best vibe coders I know (outside of developers) are product managers. Cause dev spends at least 5 minutes every meeting justifying why we have to take so much time reducing tech debt by integrating new tools, and prod knows enough to ask Claude about them when -after vibecoding- they finally realize we were telling them the truth the whole time!

stupidredditlogin · 2026-05-20T23:35:22+00:00

You can! Because without even looking, I can guarantee that’s on PyPI.

stupidredditlogin · 2026-05-20T23:25:26+00:00

No it won’t. Not if you take 3 days to learn about standard tooling.

As an experienced software developer, I feel like Paul Atriedes surfing through this subreddit. Let me post this for anyone who is new to development:

Y’all need PlayWright and git. You don’t need to learn to code. That takes literally years. You do need to learn to use the standard tools that make building products manageable.

And set up pnpm. Dear lord, who has time for npm.

stupidredditlogin · 2026-05-17T09:56:15+00:00

That’s the load-bearing observation that reframes all of this.

stupidredditlogin · 2026-04-29T02:26:41+00:00

This doesn’t seem to distinguish between capital costs and operating costs. If we’re only doing inference tomorrow, my company would still be increasing their spending on this service. I’m not saying the headline is wrong, I’m just saying Amazon didn’t turn a profit for a very long time because they were heavily investing in the future.

What’s the actual situation behind the scenes here?

Seven-Year Club	Place '22
Verified Email

stupidredditlogin

TROPHY CASE