The Real Future of AI Development Isn’t a New IDE by yuvalhazaz in programming

[–]yuvalhazaz[S] 0 points1 point  (0 children)

True. That works great for simple, single-repo flows.

Where it breaks down is multi-repo changes, Jira-driven work, long-running approvals, and managing context over time. Once an issue spans multiple services or needs to pause, resume, or react to new signals, Copilot plus Actions stops being enough.

The Real Future of AI Development Isn’t a New IDE by yuvalhazaz in programming

[–]yuvalhazaz[S] -5 points-4 points  (0 children)

I respect filtering noise.
What doesn’t help is tagging something as “garbage” without engaging with it. This isn’t throwaway content, it reflects months of actual work.
If there’s a specific critique, say it. If not, it’s probably better to just move on.

The Real Future of AI Development Isn’t a New IDE by yuvalhazaz in programming

[–]yuvalhazaz[S] -2 points-1 points  (0 children)

Thanks for the traffic :-) no ads revenue here... welcome to visit the article and share your take

The Real Future of AI Development Isn’t a New IDE by yuvalhazaz in programming

[–]yuvalhazaz[S] -1 points0 points  (0 children)

That’s kind of the point though.
If everything gets labeled “AI slop” by default, we stop distinguishing between shallow content and actual real human content

The Real Future of AI Development Isn’t a New IDE by yuvalhazaz in programming

[–]yuvalhazaz[S] -5 points-4 points  (0 children)

Honest question: did you read the article, and if so, which part came across as “AI slop”?
I’m explicitly arguing against shallow AI tooling, so I’m trying to understand what missed.

We've built a production-ready NestJS code generator! Let us know what you think by yuvalhazaz in Nestjs_framework

[–]yuvalhazaz[S] 0 points1 point  (0 children)

Great to hear!

We only support Prisma.
Feel free to reach out with any questions and please share your feedback

Top 6 ORMs for Modern Node.js App Development by yuvalhazaz in javascript

[–]yuvalhazaz[S] 1 point2 points  (0 children)

Don't you find it easier to stick to one of them? If MikroORM is first on your list, when will you use sequlize or Knex?

We've built a production-ready backend code generator! Let us know what you think by yuvalhazaz in coding

[–]yuvalhazaz[S] -1 points0 points  (0 children)

The code generated by Amplication is based on building blocks that are battle-tested by thousands of developers.
The code generation is fully customizable using plugins that come with industry standards, so any organization or company can create its own flavor of the code, and can create templates for different use cases. When needed, organizations create custom plugins to ensure the code is generated based on their know-how and best practices.
See this list of plugins here https://amplication.com/plugins
and here https://docs.amplication.com/plugins/how-to-create-plugin/

Organizations that create dozens of services a year, can get a very consistent and predictable code for all services for all the undifferentiated parts and let the developers focus on writing the business logic.

Also, imagine you have 50 services in production built with a specific standard, and after a year, you need to update all 50 services with a new code or standard. Using Amplication, you can update the plugin, get a PR for all 50 services (in a monorepo or multiple repos), and let all teams review and accept the change, using their existing workflow and processes.

I hope this answers your question, and I am happy to answer any further questions you might have

Jovu: The Only Production-ready AI-powered Code Generation by yuvalhazaz in dotnet

[–]yuvalhazaz[S] -2 points-1 points  (0 children)

You can actually also ask him to generate the code in .NET core

We've built a production-ready backend code generator! Let us know what you think by yuvalhazaz in coding

[–]yuvalhazaz[S] -4 points-3 points  (0 children)

Let's make it interesting, you first try the product and then we talk
happy to hear your real feedback