As the Agile philosophy picked up steam (and started generating consulting profits), us developers were introduced to the concept of "Technical Debt."
Technical Debt was intended as a way to present sub-optimal technical implementations in the business "friendly" concept of financial debt. The delta between the optimal solution and the sub-optimal solution is the debt you burden yourself with immediately. This debt gains interest as long as you do not pay it back by implementing the (now possibly different) optimal solution.
While this metaphor is somewhat useful when discussing the impact of a decision with management, since it never reaches the stakeholder report, there's (in my experience) very little traction to fully pay back the debt. You sometime make a "good faith" payment (interest only?), but you're usually just left with something "less bad."
We need to move past "Technical" Debt. The impact is just not there, and very few engineers (or managers) will champion the payment of something that "just works as it is." Paying customers pay for new things, or fixing their problems.
I propose we start teasing out the truth of the debt. One of these is "Design Debt." Design Debt is a high stakes debt that will crush your pace, and can make a seasoned engineer cry.
Design Debt is the sub-optimal design decision made because you are using an Agile Methodology: requirements firm up over multiple iterations, so the design decision you made in an earlier cycle (sprint, Epic, etc...) is already sub-optimal.
Take, for example, deciding that you should implement an Entity-Attribute-Value data model since you heard the customer make a high level request for a system that you can "dynamically add fields to."
If you start moving forward with that (because we're "sprinting"), prior to engaging the customer in a deeper discussion, Congratulations! You've got "Design Debt".
And 3 years later, after you're finally going to production, and find the system cannot show a significant portion of your data because it times out querying for the data, you now have to allocate a full time senior developers time for, oh, 8 months to completely tear it out and put in a normalized data model.
If you get just one thing from the above, make it that Entity-Attribute-Value is a last resort model!
Ramblings on various curiosities I stumble upon. Mainly tech-related items, but fitness and nutrition are high up there too. With any luck, a perplexing issue will be solved, and perhaps save another soul a long, frustrating trip back and forth around the world.
Showing posts with label Development. Show all posts
Showing posts with label Development. Show all posts
Friday, June 7, 2019
Sunday, January 29, 2017
The Benefit of Not Using the Team Development Environment
I'm not a "standard"-compliant type of developer. At least, not when it comes to my development environments.
App server integrated with my IDE? Nah. I'll spin up a new VM with a packaging-compliant version, secured as close as possible to the deployed instance.
There's just something about creating your own deployment instance that helps me settle in. Now I know why Tomcat and NGINX have trouble speaking SSL to each other.
And it also uncovers trivial, yet easily hidden, deployment errors early.
Not long ago, we had an intern code up a small metrics collection component. I was on a task that had me touching just about all parts of the code, which caused me to get quite a bit out of sync with the primary development branch. Other developers were happily chugging along, pulling the new code, finishing tasks from the backlog. Happy times.
I finally reached a stable point where I could start merging in the fast moving development line (trying to avoid really intense merges). It all merged in without much trouble. I had it building a new WAR, and felt pretty confident.
Then, I tried to run it in my (non-standard) environment. Hmmm, what's this "ERROR" message? Perhaps it can be ignored as an in-progress task?
"Can't create /metrics.tmp"
What? Why is it trying to create a file in the root directory? Time to dig!
Oh. The new metrics code did not specify a directory - or offer a property to specify one - when creating a temporary file for collecting the metrics.
How did it work? Well, he was fully setup with the standard environment, which ran Tomcat from his Eclipse IDE (no, I deviate here too and use IntelliJ). The file was created without issue since the default directory was his home directory, and Tomcat ran under his identity.
Even deploying it to a development test environment did not uncover the issue, as
The failure did not stop the overall startup process. Everything ran, and Metrics was not a priority for testing a pre-MVP product. It was still using a "development" environment setup, so the creation succeeded, though put the file alongside the application installation directory.
So, the next time you start following the "New Developer Environment Setup" docs, you may want to try a few deviations. It may save some troubleshooting down the line.
So, the next time you start following the "New Developer Environment Setup" docs, you may want to try a few deviations. It may save some troubleshooting down the line.
Subscribe to:
Posts (Atom)
Disney's Cloudy Vision - Part 1
Today's Disney has the idea backwards: Disney Parks should be imagined as places where a particular character/IP would live, not create ...
-
I really enjoy shows that guide me through various points of history, digging deeper into the day to day minutiae that your history classes ...
-
As the Agile philosophy picked up steam (and started generating consulting profits), us developers were introduced to the concept of "...
-
I was not surprised to learn that I was breathing wrong, but it still feels wrong that I find myself having to fix it. I'll say it up...