DEV Community

Discussion on: Architectural decisions that you regret...

Collapse
 
ben profile image
Ben Halpern

Perhaps not "architecture" per se, but one regret that comes to mind about a previous project is getting too domain-specific with some of the model names. It became really hard to communicate, or even justify why something was called something. Domain-specification is nice on some level, but conventions are really practical and powerful.

Collapse
 
eljayadobe profile image
Eljay-Adobe

Robert Martin's Clean Code has a really good section on naming advice.

Because the 2 hard problems in computer science are:

  • cache invalidation
  • naming things
  • off-by-one errors

Oh, and also...

  • exception handling
  • race conditions
  • asynchronous operations
  • multi-threading
  • floating point number algorithms to minimize units-in-last-place fidelity loss
  • Wirth's law