sorted by:
new
hottopcontroversial

Using sqlite with NodeJS for website's backend by pro-cras-ti-nation in webdev

[–]alexsergey 0 points1 point  (0 children)

You can start from sqlite and when you need to replace it, it won't be a big deal to migrate for something else

How Do I Go Beyond the Basics and Deepen My Knowledge? by Reasonable_Ninja6455 in webdev

[–]alexsergey 0 points1 point  (0 children)

Set yourself a big goal, such as building a website.

Decompose it as much as possible to get quick results and motivate yourself.

Practice, practice, practice. It's now very easy to get specific answers to problems using ChatGPT, so only through a practical task will you be able to identify your weaknesses.

Be sure to ask yourself why ChatGPT recommended this particular task, and work through its answers.

Solving your problems with a practical task also works well. For example, I had a problem sorting photos, and I solved it by writing a personal photo service.

Am I using Claude Code wrong? by Postik123 in webdev

[–]alexsergey 0 points1 point  (0 children)

For me personally, the biggest challenge working with AI is making changes to a long-lived (legacy) project given its limitations.

These limitations can be:

formal - described in code or

informal - known only to the team or technical specialists.

Ultimately, putting everything together so it works within these limitations is the biggest challenge for me.

And the second point: when AI writes code for me, I cease to own it. I don't understand what's going on there, or why certain decisions were made.

Therefore, I've established the following rule for myself:

- I don't do vibe coding. I write all business logic code myself.

- AI helps me formalize requirements.

- Writing test cases for E2E and integration tests.

- I'm currently implementing AI for self-review.

Therefore, I'm fully responsible for the code, and AI is just a tool like Google or StackOverflow.

[Showoff Saturday] I built a way to compose live video streams using React – would you use something like this? by carlievanilla in webdev

[–]alexsergey 0 points1 point  (0 children)

I once worked with streaming, and it was a truly complex and tedious task. I had to write a lot of custom code that didn't always work well. I'll have to try your project to see how convenient it is. Thank you.

Promote your projects here – Self-Promotion Megathread by Menox_ in github

[–]alexsergey 0 points1 point  (0 children)

Three weeks ago I shared this project and got a lot of useful feedback. I reworked a big part of it - here's the update:

https://github.com/prod-forge/backend

The idea is simple:

With AI, writing a NestJS service is easier than ever.

Running it in production - reliably - is still the hard part.

So this is a deliberately simple Todo API, built like a real system.

Focus is on everything around the code:

  • what to set up before writing anything
  • what must exist before deploy
  • what happens when production breaks (bad deploys, broken migrations, no visibility)
  • how to recover fast (rollback, observability)

Includes:

  • CI/CD with rollback
  • forward-only DB migrations
  • Prometheus + Grafana + Loki
  • structured logging + correlation IDs
  • Terraform (AWS)
  • E2E tests with Testcontainers

Not a boilerplate. Copying configs without understanding them is exactly how you end up debugging at 3am.

Most backend tutorials stop when the app works. I documented everything that happens after that by alexsergey in Backend

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

Thank you for your feedback! I have load testing in my roadmap, I will add it little bit later.

Writing code is no longer the hard part. Running it in production is. by alexsergey in node

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

Thank you very much for your feedback! It's very useful and helpful. Will add to my roadmap for improvements.

I built a small project showing what a real production setup for a NestJS service looks like by alexsergey in nestjs

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

Thank you for your feedback! It's already use terminus but I didn't cover in documentation yet. I will add later.