Matheus Wilberstaedt’s Post

Most of my “productive” days don’t start with writing code — they start with naming things. A small routine that saves me hours: - Before I touch implementation, I write 3 names on paper: the problem, the input, the output. - If I can’t name them clearly, the code will be unclear too. - If I *can* name them, the code almost writes itself (and PR reviews get way faster). Tiny example: “handleData()” → “normalizeBillingAddress()” One name tells a story. The other hides it. What’s one naming rule you swear by? #javascript #nodejs #react #softwareengineering #cleanCode #webdevelopment #programming #devlife

To view or add a comment, sign in

Explore content categories