Latest Articles
Explore comprehensive articles about artificial intelligence, software development, and engineering practices. From AI breakthroughs to modern development techniques and best practices.
Error handling is not just about catching exceptions. In real-world applications, it is a full-stack design concern that affects user experience, backend reliability, security, debugging, and production resilience. This article explores how to handle errors from user input to backend failures, and how to design safer, clearer, and more maintainable error-handling flows.
If AI can solve logical problems, write code, and give answers quickly, what happens to human learning? A personal reflection on AI, coding, and the importance of still understanding the work.
Why does fortune-telling so often feel accurate? Perhaps not only because ancient people were good at observing patterns in life, but because the ancients were us, and we are the ancients: shaped by similar instincts, survival pressures, and the same desire to catch a piece of luck within a finite life.
Although game applications, Web2 applications, and Web3 applications all follow the same software development lifecycle, the engineering mindset behind each stage is very different. In this article, I use Web2 as the baseline, then walk through how games and Web3 change the priorities, constraints, risks, and trade-offs across requirements, design, development, testing, deployment, and monitoring.
AI can generate plans, code snippets, and polished roadmaps in seconds—but it doesn’t automatically carry the consequences: integration constraints, security, testing, deployment, and long-term maintenance. That’s how “AI confidence + 0 accountability” shows up in real projects: timelines that sound convincing, scope that quietly assumes away the hard parts, and prototypes that get mistaken for production. The antidote is simple: confirm features first, lock an MVP scope, write acceptance criteria, then design the system and implement.
Authentication and authorization aren’t “login features”—they’re a production system shaped by browser behavior, protocols, and real attack paths. This guide cuts through the misleading “sessions vs tokens” debate and instead explains what actually matters: stateful vs stateless validation, OAuth 2.0 vs OIDC, SSO and federation, and how to design permissions that don’t leak data across tenants. You’ll see practical patterns (BFF + API), common Auth0 integration pitfalls, a threat-driven defense checklist (XSS, CSRF, token replay, refresh rotation, key rotation)