8 ms·
Naming things: The most underrated skill in software development
- UnhappyMeaning 1y agoGood points, also I’ve just almost completely let AI handle this. I don’t use it to write code for me yet but I will be lazy and ask it this prompt, “what should I name this variable (or function) that describes this or does this?”
- az09mugen 1y agoJust remembering this famous quote : "There are only two hard things in Computer Science: cache invalidation and naming things. -- Phil Karlton"
- mock-possum 1y agoThat, and off-by-one errors ;]
- idiomat9000 1y agoWorld_street_car_tire_nut_object cause everything is a object..
- variadix 1y agoNames are also a good way to determine how to draw boundaries between data, between code, etc. If you can give something a concise, descriptive, and intuitive name you can usually pull it out into its own function, type, etc. and it will _improve_ readability, since the name adds information and abstracts the implementation well. Names are also a good heuristic for whether your abstractions and boundaries are good. If they require verbose, misleading, or unintuitive names you may need to redraw those boundaries and abstractions.
- IshKebab 1y agoTotally agree. Hardware engineers especially need to learn this. They can't stand using clear variable names; everything needs to be abbreviated to death. No_vwls_allwd. So infuriating.
- hulitu 1y agoSW engineers are better: they reuse already given names. /s