- Published on
AI heeft niet de kwaliteit van code veranderd, maar de snelheid waarmee slechte beslissingen je systeem in glippen. Een reactie op het stuk van Florian Herrengt, plus het punt waarop ik het niet met hem eens ben.
Code-review
All Posts
- nextjs (8)
- frontend (6)
- github-actions (3)
- javascript (3)
- framework (3)
- react (3)
code-review (2)
- promises (2)
- nestjs (2)
- backend (2)
- docker (2)
- react19 (2)
- react-hooks (2)
- icon-libraries (1)
- web-design (1)
- ai (1)
- software-engineering (1)
- axios (1)
- fetch (1)
- azure-esb (1)
- best-practices (1)
- docker-compose (1)
- getserversideprops (1)
- ssr (1)
- server-side-rendering (1)
- css (1)
- converstations (1)
- settimeout (1)
- setinterval (1)
- langchain (1)
- langchain-agents (1)
- llm (1)
- ublock-origin (1)
- tech-interview (1)
- mysql (1)
- postgresql (1)
- database (1)
- nestjs-vs-express (1)
- express (1)
- nextjs-15 (1)
- app-router (1)
- navigation (1)
- otel (1)
- opentelemetry (1)
- honeycomb (1)
- playwright (1)
- react-server-components (1)
- redwoodjs (1)
- graphql (1)
- vercel (1)
- cicd (1)
- ssh (1)
- stripe-webhook (1)
- webhook (1)
- terraform (1)
- useactionstate (1)
- useoptimistic (1)
- usepathname (1)
- Published on
Code review is one of the most effective ways to ensure that the code we write is not only correct but also maintainable and scalable. In this article, I will be sharing some of the best practices that I have learned over the years when it comes to code review.