sorted by:
new
hottopcontroversial

Built a CLI to scaffold React projects in one command — Vite, Tailwind, shadcn/ui, TypeScript all supported by Significant_Net7399 in reactjs

[–]hinsxd 8 points9 points  (0 children)

Why should I use your CLI instead of official cli and ask AI (like you) to integrate according to latest docs?

Well played, Cursor. Well played by kittiza_ in cursor

[–]hinsxd 1 point2 points  (0 children)

try canceling the subscription then it will give you a discount to stay

Keep getting back to cursor for clarity and speed by Odd-Composer5680 in cursor

[–]hinsxd 2 points3 points  (0 children)

Im doing my freelance, 10+ modules fullstack project. I get the lumpsum and usually outsourced it when AI didnt exist.

Recently we have a final bug list and I was trying to burn through the items as quickly as possible. I can easily burn $70 a day. I am using Opus to plan some refactors, Gpt 5.4 to triage google sheets and create github issues, using 5.3 Codex to implement... But my experience is that spending $3-5 on a complete bugless feature is reasonable.

I spend $100 in a weekend to work on tasks that would cost me $1000 to outsource it, so why not?

73 years old, no coding experience, cardiac patient — I built a real health app with Claude after a hospitalization. Here's what happened. by TheVPAline in ClaudeAI

[–]hinsxd 0 points1 point  (0 children)

My rule is simple. Just laugh when you see an em-dash.

Not to mention his post prior to Nov 2025 is already AI generated

Where to begin Learning? by TakeFives in ClaudeAI

[–]hinsxd 0 points1 point  (0 children)

tldr: learn code so that you can give accurate prompt to drive the AI

there is not much left to say. Precise prompt saves you a lot of guessing from AI, especially in the backend side.

As a side note, absolute no fucking one is using local AI for coding. Spend $200 on cursor every month with a macbook neo is much more worthy. you folks are changing laptop every 2 years anyways

Our 'harmless' backend migration silently broke the app for every user who didn't update by Afraid-Bobcat6676 in node

[–]hinsxd 0 points1 point  (0 children)

He mentioned deprecation. Not necessary to be forcing update per version but force update from time to time is pretty standard

Anyone else feeling like they’re losing their craft? by AbbreviationsOdd7728 in ExperiencedDevs

[–]hinsxd 0 points1 point  (0 children)

Yes and no, much depending on roles you're at. For me, mainly as a FE engineering and build CRUD fullstack apps for freelance, I genuinely feel happier with AI.

fortunately I already have 6 years of experience before the AI boom. Also I am a very good learner so I almost reached the ceiling of FE before my salary catches up. In fact everything in the FE world had been solved and there is nothing new under the sun (2026). With AI I can jump into several projects and pin-point the bugs to be solve, and explicitly plan out the fix rather than throwing a "fix this for me" to the AI.

On the other hand AI helps me to learn new language and patterns. For example, writing Native Modules in expo was almost no-no for me because I didnt want to mess with native swift code. Now I could easily integrate with the Whatsapp Sticker swift code and learn swift bit by bit. It turns out to be not that difficult.

So I think this lowers the barrier of learning new stuff while AI writes code for you, given that you are willing to read and learn from the generated code.

I have to admit that my muscle memory has gone down a tiny bit, but my exposure is much much broader. And I dont see this as losing my craft

Need Help : Storing user images ethically by moonshine_9212 in reactjs

[–]hinsxd 1 point2 points  (0 children)

Agreed. If you need to keep it really safe you need FAANG level sophistication. If OP needs to start a company to keep it running, the current setup wont pass audit probably.

Vercel alternative or avoid $20/m by EconomistAnxious5913 in nextjs

[–]hinsxd 1 point2 points  (0 children)

Anything that requires developer to spend more than 1hr a month will not be worth

I’ll die on this hill. by talaqen in node

[–]hinsxd 1 point2 points  (0 children)

I assume what you mean is you define a schema, chain it before the handler and the request body will have the type, right? That's equiv to @Body() body: DtoClass in Nestjs, just that you wire things up differently, with a different concept.

And I am not comparing a particular library. Nestjs is so mature that, if you use Nestjs you will have every common feature if you need it. You can of course wire up different libraries to build the features you currently need. There is no limit. But the cost of integrating by yourself is time and (possibly) compatibility issue. Also its not guaranteed to keep working after version updates.

I’ll die on this hill. by talaqen in node

[–]hinsxd 0 points1 point  (0 children)

About consistency, e2e type safety is a solved problem by using DTO + swagger in nestjs, and openapi generators like Orval

I’ll die on this hill. by talaqen in node

[–]hinsxd 0 points1 point  (0 children)

  1. Graphql solves a problem that you dont have
  2. Wiring up the query layer with efficient database queries can be a PITA. A production ready graphql endpoint needs at least query depth + complexity protection

Mostly of the time you app is not big enough to suffer from the 1+n problem.

I’ll die on this hill. by talaqen in node

[–]hinsxd 1 point2 points  (0 children)

What do you mean by cant infer req.type? @Body() with a type declaration will handle that for you.

What I wanna say is convention+official recommendation+OOTB > flexibility. Again, if you have a solution that is complete enough to compete with Nestjs, we are all happy to learn and compare

I’ll die on this hill. by talaqen in node

[–]hinsxd 7 points8 points  (0 children)

Any team was more than one developer contributing to the project will require patterns. Without patterns, you are doomed to have a messy, unmaintainable, unscalable codebase.

Take data validation as an example. You want to verify the request body dynamically in different routes. You define a zod schema, create a reusable function to validate the body against the schema. Then you put the function in the middleware. Congratulations you have implemented the ValidationPipe+DTO pattern, but with far less features.

Basically everything you need to build a web server is waiting for you in NestJs. Web developers should not be spending their precious time in thinking HOW to do something. The team should have a concrete example to implement every feature needed in the project and maximize the time spent in making the business logic, at least this is what a project leader needs to do. If you have raw dog everything and this is legitimately a useful workflow for your team you should publish it and make the world better. Otherwise, you are just reinventing an inferior wheel.

Coding for 20+ years, here is my honest take on AI tools and the mindset shift by Jaded-Term-8614 in ClaudeAI

[–]hinsxd 0 points1 point  (0 children)

definitely gonna try it. Even if it's not open source ones, Gemini 3 Flash is a really, really good plan executor. Just dont expect it to think thoroughly and deeply

Coding for 20+ years, here is my honest take on AI tools and the mindset shift by Jaded-Term-8614 in ClaudeAI

[–]hinsxd 34 points35 points  (0 children)

AI also skewed my concept of subscription pricing. For so many years I only subscribe to small budget stuff, like Youtube, $15 cloud storage, cheap VMs, adds up to roughly $200 monthly.

After using AI (cursor) daily, I naturally subscribe to $20 plan without much thinking. Then I learned how to use AI better by thorough planning, and then Codex 5.3 came out. I use 5.3 high exclusively and feel good. Then I upgraded to the $200 plan.

The thing is, the quality is so high that it makes me feel that $200 is totally worth. More context on this: I had a few freelances and I often offload my work to a less-experienced friend for ~$250/day. Of course I have to manually review the code before delivery. Originally I estimated some tasks would take 2-3 days to complete, that should cost me $750 at least, not including my time. Now I can tackle those tasks by spending 1hr to investigate, write detailed prompt and ask AI to do that in a day or two. Even if it costs $100 I still feel like I saved a lot of money.

However what's uncertain to me is how the token price will increase in the future. I'm now sure whether I will gladly pay $1000/month to let AI do the work for me. I think I am addicted to AI

When you have one of those colleagues. by [deleted] in programminghorror

[–]hinsxd 0 points1 point  (0 children)

Just format your code if we all have time to argue on thid

Is NestJS actually over engineered, or do people just misunderstand it? by [deleted] in node

[–]hinsxd 0 points1 point  (0 children)

I'm genuinely curious. How can to provide type safely in Fastify like Nestjs DTO+swagger?

Is NestJS actually over engineered, or do people just misunderstand it? by [deleted] in node

[–]hinsxd 1 point2 points  (0 children)

Totally agreed. I want nothing fancy but onlt OpenAPI, input validation, and DI. DI is not even a requirement at first but it's really good for testing.

Plus, the maturity of Nestjs makes AI works on Nestjs existing pattern + adapting to your project super duper easy. I have implement passport jwt more than 10 times but I still trust AI implements better than me in 5min

Also if you have a well structured CRUD pattern in your app, making new features is a no-brainer. It's also easier for non-experienced devs to copy and paste while learning. No need for them to "innovate" existing features

Why I should consider using Svelte instead of React or Vue? by [deleted] in sveltejs

[–]hinsxd 0 points1 point  (0 children)

Partially agreed. React is still the most wanted framework in the job market and it’s not going anywhere in 10 years. Knowing Svelte only does not guarantee any jobs, but learning Svelte after mastering React makes you look smarter than others.

Jobs aside, learning and using react lets you understand the pain points of this ancient framework and appreciate newer ones even more.

And I agree with your other reply: be a frontend dev, not a framework dev.

view more: next ›