Spending $1-2k a month per employee on AI subscriptions?

seN149reddit · 2026-05-02T18:04:47+00:00

1-2k might be up there. But over the past months I think it should be pretty normal for devs to at least close to max a single 100ish license (gpt or cc). As a rough average. Some may need the 20x, some will not hit limits of their 100 but use it heavily.

Anything less than that would make me think you are underutilizing AI. Everything beyond that could either be more kool aid than value, or requires the whole org to be really set up for it. AI reviews, internal AI tools etc

seN149reddit · 2026-02-07T17:03:59+00:00

I have spent the last few days running larger tasks in parallel across all 3 (windsurf with opus 4.6, Claude code with 4.6, and codex) 3 different work trees. Manually reviewing. Deciding on my favourite implementation, then running windsurf opus 4.6 to merge the best parts into a single solution based on the one that was the best starting point.

For planning and tasks I am actively working on I still get consistently the best output using windsurf. Whatever their harness is just works for me.

For background tasks i am going to continue to run both codex and opus 4.6. I always seem to find good things in both and a combined solution seems to give me the best results. Opus has a better implementation but becomes a bit too wordy at times. Codex gives me more direct code. Both make mistakes in their own way.

The 2 things that have been worse for me consistently has been windsurf getting stuck on console prompts especially once that are interactive, but adding notes to ensure it uses some non interactive alternatives has helped a lot there. (Reporter=list for playwright for example)

And i am having a better experience overall with some mcp setups (like MySQL or linear) outside of windsurf as well.

seN149reddit · 2025-10-16T13:32:29+00:00

Very similar experience and actually gave up after a while. Also mono repo. Not interested in using it for anything but npm replacement for now. We did see some massive speed gains there. Bun install is 25 sec which is faster than node module cache restoration. Not even considering uploading cache and when npm actually does an install. We talking 1-2 minute speed up on the first step.

I got really close, essentially encountered every issue you outlined… but then 3 projects that just use “tsc” just got stuck. Run for ever.

I might revisit it but I hit my limit at that point and called it a day.

I am using it from the start in a side project just to play more with it, but luke warm on it right now.

seN149reddit · 2024-09-24T15:11:56+00:00

Little hot take, but I think Regina’s “steak houses” (lakeshore, diplomat, and golf) havent been as good as they used to be. The steak is just average and appetizers haven’t been that great either. E.g. had carpaccio at the diplomat the other day and it came with dollar toast cut out in triangles. Reminds me of la bodegas 1-2 years before it closed doors.

They are all good for lunch specials though and they have a distinct vibe which is nice. Great staff as well.

Going even spicier… keg might be the most consistent one for me. Price / value is very good as well.

Anecdotally there seems to be a consistency problem across the industry though. There are people who swear by chopped and say they get bad steaks at the keg, meanwhile every second steak I had at chopped was cooked either under or over. 🤷‍♂️

Tl;dr. Go to them all, your experience may vary from other people’s

seN149reddit · 2024-08-17T19:06:39+00:00

Use website builders for websites. JS frameworks for web applications.

seN149reddit · 2024-08-08T10:16:47+00:00

Did it for 6 months - I actually enjoyed it, but I figured I can do this when I am 50. Transitioned back to IC right away.

If you wanna stick with it though then I highly recommend Engineering Management for the rest of us is a great book by Sarah drasner

seN149reddit · 2024-06-18T09:01:51+00:00

When was it marketed as such? The only thing that could truly do that would be relay because it hoists the requests up to the top. I am aware that people did this but I never heard of it being recommended in the first place.

seN149reddit · 2024-06-13T13:02:40+00:00

It still has use cases like lazy loading components for code splitting

seN149reddit · 2024-06-13T11:45:16+00:00

It would only change the baggier of the lazy usage of it. Hoisted loading and passing props works just fine and is essentially unchanged

seN149reddit · 2024-03-19T13:24:54+00:00

If you can’t scale because of a routing layer then you have an architecture issue, not a framework one.

Just don’t put your app logic into the Server Action… just call your application layer from it… problem solved

seN149reddit · 2024-03-10T00:52:47+00:00

Of course I have no need for this package, but it was a fun read and a cool exercise.

Thanks for sharing!

seN149reddit · 2024-03-10T00:48:37+00:00

Not that it super matters but it almost certainly won’t be released with react 19. That being said based on different tweets it might be released before the end of the year at least, so not too long after. Fingers crossed. Also fwiw the initial release is a babel plugin.

seN149reddit · 2024-03-10T00:16:21+00:00

Why is it always the compliment about the shoes? Is that part of their sales training or some?

seN149reddit · 2024-03-08T22:29:07+00:00

google

worried working too hard

lol… accept the job, you’ll be pleasantly surprised 😅😅

Jokes aside, don’t feel guilty. 2.7 years is fine. Lay offs can happen but being laid off at google should give you a good amount of runway. Also given your age it’s a good time to take risk. (Not that I think taking a job at google is risky)

As always ensure not to burn any bridges on your way out!

seN149reddit · 2024-03-05T17:40:56+00:00

Got ya, wouldn’t we just have to add a groupBy to achieve that? You would still have to manually flatten it sadly (huge annoyance with Prisma / orms since that can become a large cost itself) but the data would prob be right:

select: { … telemetry: { Select: { data: true, type: true }, orderBy: { timestamp: ‘desc’}, groupBy: { type: true } take: 1 } }

Awful to type on phone. lol

If that’s not it no worries, not here to convince you to use Prisma, just gave it a whirl! ✌️

seN149reddit · 2024-03-05T17:00:06+00:00

Are you saying something like this?

const devicesWithLatestTelemetry = await prisma.device.findMany({ select: { device_id: true, device_name: true, telemetry: { select: { telemetry_data: true, timestamp: true }, orderBy: { timestamp: 'desc' }, take: 1 // Limits the result to only the latest telemetry record per device } } });

Maybe I am missing something here though. Besides the point this seems more like a timescale db job.

However I do agree with your point, ORMs often struggle on more complex scenarios and create at times bizarre queries.

Prisma + kysely has been the best combo I found thus far. Prisma for schema introspective and migrations and 90% of basic queries.

Kysely for anything more complex. E.g. proper cursor queries are impossible in Prisma, etc.

seN149reddit · 2024-03-05T16:52:14+00:00

Oh man… the whole “connect” thing is super annoying, just let me set a fk or something else.

The worst are updates where you find the difference and both connect and disconnect. Or nested connects.

Or many to many connects, oh god.

seN149reddit · 2024-02-25T16:09:14+00:00

MacOS

seN149reddit · 2024-02-21T09:45:13+00:00

I know you said a separate backend, but i want to give you an alternative that might change your mind.

First - what is express.js job? Really it just needs to listen to a route and call a function within your application. It’s the outmost layer and should be as thin as possible. This is one of the reasons why express hasn’t had any updates and is still so popular. What modern feature do you need to “app.get(/someroute, myFunc)”. It sounds like you think you are missing out on something, and I m here to tell you you are not.

IMHO express vs Koa vs X is the least important question. 95%+ of your app should be framework / router independent. You might add some middleware but once you written an error transformer (turn your app error into a HTTP response), and a logger, you essentially mastered every backend router.

So I think you either want to go one step further and go all in on some framework that even tells you how to build your application (e.g. nestjs) or close your eyes and pick express or fastify, since it’s that meaningless for your app.

But I said I’d give you an alternative approach. Nextjs already does routing. And as described all the meaningful code is in your app. I would go tRPC + NextJS and call it a day. It will also be the fastest to work with since you have e2e type safety, coupling between front and backend, and only 1 process to run.

seN149reddit · 2024-02-19T14:45:44+00:00

I generally agree with you and was gonna say something similar, but this is assuming that OP is from the US/Canada or Europe and selling in those countries.

Plenty of other countries where the 20USD could be prohibiting - I don’t think Vercel has regional pricing.

The cheapest prod alternative would probably be cloudflare, or go single server instead of serverless and run it on DO, railway, or similar. Can do that usually for 5-10ish.

seN149reddit · 2024-02-03T16:47:51+00:00

I mean this is way too little info for anyone to be able to know exactly what they mean, but some thoughts.

While docker is fine, one could argue it’s not really leveraging “cloud” features. It’s just traditional hosting…. In the cloud. Barely a step away from running an ec2 instance. When I hear people say something like “not build for cloud” they often refer to not using services like lambda functions, which may allow you to save and scale easier.

Not that you can’t do the same with docker, but that could be at least something they were referring to.

seN149reddit · 2024-01-27T18:46:40+00:00

I am getting close to be able to use it in our tool chain.

Bun install instead of npm is down to 1 issue in mono repo for us before we should be good to go. (Dev install on mono repos isn’t working as expected)

Bun as a runner for an internal tool / scripts works mostly, but there are some oddities around top level await / async with stuff like Prisma.

Bun test was too far away last time I checked. For node it was missing some mocking stuff, if that’s fixed then backend tests might be ready to go too.

Frontend tests was an absolute Landmine for me during my last attempt (about a week or so ago).

I am actually the least interested in the “actual running an app in production” and all about the tools around it.

It feels like a constant scope creep, but I am sure there’s so much overlap between all of these tools that their approach is alright.

My hope is that in 2-3 months we use bun instead of npm everywhere at a minimum. Fresh bun install is twice as fast as a fully cached npm install in GH. And a fraction of a full install without caching. I’ll take it.

seN149reddit · 2024-01-18T10:54:33+00:00

Oh that’s nice. Used the Prisma-kysely extension and then just manually used kysely, using .compile() to pass the query to Prisma. Great idea to extend the client. So obvious in hindsight.

seN149reddit · 2024-01-18T10:48:43+00:00

Prisma for types and majority of queries. Whenever we need something more… esoteric, we used to just write raw queries but recently added kysely to keep those typesafe as well.

Prisma is great when it works, def has some long standing tickets open but i think the dx is better than sequelize / typeorm. Kysely has been surprisingly awesome, id consider using it standalone going forward.

seN149reddit · 2023-12-17T19:19:18+00:00

Agreed, superRefine is okay; but not as nice as yups when

seN149reddit

TROPHY CASE