Habits for Debugging Faster
Practical debugging habits that save time: reproduce first, read the error, test one hypothesis at a time, bisect, log with context, and write a failing test.
I am Perdi, a software engineer. I write about programming, Linux, and the craft of building software, for developers who like clear explanations and working examples.
First engineering role out of university. Built internal tooling with Vue.js and learned how to ship production code as part of a small, fast-moving team.
First engineering role out of university. Built internal tooling with Vue.js and learned how to ship production code as part of a small, fast-moving team.
First engineering role out of university. Built internal tooling with Vue.js and learned how to ship production code as part of a small, fast-moving team.
Leading a team of 4 frontend engineers. Rebuilt the core dashboard in React and TypeScript, cutting load time by 40%, and introduced component-level testing and code review standards the rest of the org went on to adopt.
Leading a team of 4 frontend engineers. Rebuilt the core dashboard in React and TypeScript, cutting load time by 40%, and introduced component-level testing and code review standards the rest of the org went on to adopt.
First engineering role out of university. Built internal tooling with Vue.js and learned how to ship production code as part of a small, fast-moving team.
First engineering role out of university. Built internal tooling with Vue.js and learned how to ship production code as part of a small, fast-moving team.
Android App for optimized the pltd works by seeing the supply from ptls.
Status:Live
AI apps that help parents for having conversetion with adhd children, record the conversetion and get the summary for analyse by profesional.
Status:Live
AI apps that help parents for having conversetion with adhd children, record the conversetion and get the summary for analyse by profesional.
Status:Archived
Samsung Electronics Indonesia
Fakultas Teknologi Informasi dan HMPTI Universitas Kristen Satya Wacana (UKSW)
Telkom University
Practical debugging habits that save time: reproduce first, read the error, test one hypothesis at a time, bisect, log with context, and write a failing test.
A practical guide to code review from both sides: what authors should prepare, how reviewers should comment, and how to tell if your process is healthy.
A calm, practical tour of Big-O: the few complexity classes you actually meet, JavaScript examples, a Set optimisation, and when to just measure.