Hacker News Reader

Comment by actsasbuffoon | Hacker News Reader

I was the first dev at my current company to experiment with Claude Code back when it first came out. Some of my coworkers tried it, and some didn’t like it at all.

But now literally all of us are using it. The company gives us a $100 monthly stipend for it. We’re a small dev team, but our CEO is thrilled. He keeps bragging about how customers are gobsmacked by how quickly we’re delivering new features and he’s been asked if we’ve made a ton of hires in the last year. We’re actually down two developers from when I started.

I don’t love the code it writes, but the speed is unbeatable. We still need devs, and I don’t think that’s ever going to change. But we don’t need as many devs. We’re shipping like crazy with a small team. I don’t think more people would speed us up much at all.

View on HN

Where I work, we hired a developer that was supposed to be familiar with SQL. It turns out, he can't even write simple queries (and spends 0 time outside of work getting up to speed).

The director purchased a subscription to Claude and will most likely get rid of him at the beginning of the new year, because the job can pretty much be automated at this point.

Many Marketing/copyrighting people have also been laid off over the last year due to the same reasons.

"I don’t love the code it writes, but the speed is unbeatable. We still need devs"

I think this will be the problem going forward: Less positions to fill and the same amount of potential candidates. You will need to have more experience and credentials to compete.

This is what I'm seeing in the design market. With Figma Make, you can write a prompt, tell it to use your design library, generate a flow, and then hand it off to developers and say "Hey, look at this, can you implement this?". Alternatively, you can use Cursor/Claude Code/Codex to pull in Figma design system elements via MCP, and generate flows that way. You can push features so much faster with the same or fewer people, and lets be honest, pushing more features in less time is the #1 metric at a lot of companies even if they claim otherwise.

Why use Figma at all instead of going from prompt to code?

Presumably you can iterate on and manually tweak the design first, which is much quicker and less cumbersome than iterating on and tweaking the design when it's in clunky HTML/CSS/JS form and all the non-vector graphical assets are flattened/cropped etc.

Good point. There are emerging tools that focus on AI UI creation workflow like https://stitch.withgoogle.com/

I find it to be sometimes easier to utilize my Figma library to design what I want as I generally don't have to do rework. It gets annoying after awhile to waste tokens and context dealing with stupid small things like "Hey, the icon in the icon button is wrong." if you do prompting. Pulling in the same icon & icon button through a MCP is generally easier.

I own a small agency and it’s the same for me, but that doesn’t explain the urgency nor the layoffs in the big companies. Yes we are not hiring juniors, but we still hire seniors because they are now more productive. That’s not what we are seeing in big companies.

To me it’s the cumulated effects of many things happening coincidentally: - Massive offshoring

- Money becoming scarce after the ZIRP era and in the recession except for AI investments

- Near monopoly positions that allow layoffs as a strategy to push stock price, without penalty for the decline in quality (enshittification)

- Cherry on the top, LLMs being able to do the work of juniors when used by seniors

If it was only about AI productivity we wouldn’t see this urgency.

> but the speed is unbeatable

... for "now". Wait until the debt kicks in.

> But we don’t need as many devs. We’re shipping like crazy with a small team.

... for "now". Wait until the debt kicks in.

If you mean technical debt, this can be prevented with a good senior reviewing all of the code.

And then your good senior leaves and you're stuck with a bunch of juniors who mostly vibe coded for the past X months or god forbid years.

The point is that you don't allow vibe coded slop to get into production by having seniors review it first.

Or more accurately, it will be resolved in the inevitable AI refactoring.

Oh man, software is about to get so much shittier.

Reply on news.ycombinator.com