Tyranny is forcing concepts or actions at the wrong hierarchy of dependencies in a complex system. We have seen this over and over again in complex social systems, but this also takes place in complex software systems. Tyranny should be avoided in any system if that system is to endure the test of time.
Within a fractal system, there is an inherited conflict between higher and lower level nodes: higher level nodes wants lower level nodes to solve specific problems and the lower level nodes want higher level nodes to solve general problems. This conflict is central to a developers growth in creating modular code that is of high quality.
Spaghetti code is something that all developers know is bad and have an idea on how to not create it. Looking at your system as a fractal system will help prevent spaghetti code.
A couple years ago I had to agonize over which version of Angular to use for my front end development of a brand new project: AngularJs with all my currently built up knowledge, or the new framework that's the future. In deciding which technology to use in a project, we definitely need to be thinking … Continue reading AngularJs 1.x and the Lindy Effect
All developers have been told to write reusable code. I remember having that drilled into my head in college by my professors daily. The main reason we have to write reusable code: so we don't have to write the same code twice. That is a perfectly valid reason and I can't argue with that. But, what … Continue reading Optionality and Reusable Coding
When I'm trying to be a good developer and apply SOLID principles to my coding practice, I usually get a little frustrated with applying something so abstract. One issue that has frustrated me a lot is with the Open/Closed principle: when to say that a piece of code/entity is now closed to change. After many … Continue reading Open/Closed and Expected Outcomes
UI automation testing can be a nightmare: tests break all the time when developers are changing behaviors for new features or bug fixes. Here I'd like to propose why UI automation tests constantly break and a hypothetical solution to the nightmare.
LongLoft - Code Writer 