Introduction Code reviews. For many developers, they are a necessary evil — a box to check in the development process. However, I have come to appreciate them as a powerful tool for elevating code quality, fostering collaboration, and improving team dynamics. Today, I want to share my journey from viewing code reviews as a mundane task to recognizing their critical role in successful projects. L
Realistic Ragdoll Physics in Three.js Matthias von Bargen May 5 #threejs #javascript #webdev #gamedev 5 reactions Add Comment 3 min read
Building a Translation Pipeline for International Contract Bidding If your company bids on international contracts, you've probably dealt with the translation bottleneck. Technical proposals need precise translation, certified documents have strict formatting requirements, and procurement deadlines don't wait for anyone. After seeing how UK public procurement translation requirements can make or
Implementing Realistic Ragdoll Physics with Three.js and Rapier.js Have you ever wondered how to transition a character from a fluid animation to a limp, realistic heap upon impact? Whether it's for a game-over sequence or a chaotic physics sandbox, ragdoll physics is a staple of immersive 3D experiences. Today, we’re diving into a implementation of Three.js ragdoll physics using the high-perfor
I was doing a code review for a colleague when I found it. The component had five useEffect hooks. No errors. No warnings in the console. The PM had signed off on it. It had been in production for three months. But there was a subtle bug that only showed up when the user navigated quickly between pages. Data would flash. State would reset. Sometimes the old user's name would appear for a split sec
Handling emails in modern applications often feels like choosing between two evils: either you pay a fortune to SaaS providers as your user base grows, or you fight with ancient SMTP servers that have terrible Developer Experience (DX). I wanted something with a modern, clean API (think Resend or Stripe), that could handle both transactional emails and marketing campaigns, but with the freedom to
Jack had finally stepped into the world of Docker. It felt like magic, but Jack was never one to just believe in "magic spells." He was curious. He wanted to look under the hood and see what actually made Docker so powerful. He had one big question: How could 50 different people live in the same "apartment building" (the Host OS) without accidentally reading each other's mail or eating each other'
Last week I had a problem. I'd built an internal documentation site in Trilium Notes — about 30 notes covering product, marketing, and operations stuff. It was for non-technical teammates who needed to answer questions from developers about the platform. The docs were good. Structured, searchable, complete. But reading 30 notes to find one answer is not great UX, especially for someone who's been