10 Modern Software Over-Engineering Mistakes

Few things are guaranteed to increase all the time: Distance between stars, Entropy in the visible universe, and Fucking business requirements. Many articles say Don’t over-engineer but don’t say why or how. Here are 10 clear examples.



Two other great articles linked in that one:

Refactoring — Not on the backlog!/

Write code that is easy to delete, not easy to extend.

Speeding up AngularJS apps with simple optimizations

  • Before diving into code, consider how to best architect your application to avoid performance challenges that dirty-checking faces in large quantities of Objects.

  • Be mindful of ng-repeats — how much data are you expecting back? How much weight is that going to add to Angular’s $digest cycle?

  • Not everything needs to be “Angular.” In Directives there are many cases we need to work with pure DOM.

  • Keep checking out the Angular project on GitHub, as there are often some great hidden features that can be found from upcoming releases. That’s how I came across the “bind once” functionality.

  • The more $$watchers there are, the slower your application will be, and with some of the performance enhancements above, even their simplicity can make a huge difference