3 ms·

It's just my opinion, but as I always see during the years of work if you only focus on "getting things done" you have an illusion that you ship faster.. This w

It's just my opinion, but as I always see during the years of work if you only focus on "getting things done" you have an illusion that you ship faster.. This way you will have more bugs, regressions, technical debt etc. and fixing them will take much more time than doing things the right way.

scarface74 9y ago
Why does gettings things done preclude quality code if you know in advance that you took shortcuts? For instance, write now to "get things done" I might keep all of my passwords for a system I'm trying to get through QA and UAT in a plain text configuration file. Knowing that's a "bad thing", I'm going to abstract how I get credentials in a method/class that everyone uses. Then once I decide how we want to store credentials securely, we can rip it out, change one method and everyone is updated through the shared library. Another real world example for us is logging. I knew in advance that we ultimately wanted a better logging framework for searching than just a straight text log like you get with log4net/log4j. We wanted structured searchable logging and to eventually use Elastic Search and Kibanna. I didn't have the bandwidth to do that at the time, but I still insisted on Serilog that would give us structured logging and just used a text file sink, later I added a Mongo sink for searchability just by making a configuration change, when I get around to it, I'll add an ElasticSearch sink. We then get easily searchable logs with applications specific properties to search with a nice front end without any code changes. Even if I skip unit testing, I'm still going to insist code be structured in a way that separates business code from persistence so when we get a chance to write unit tests (if ever) it makes it a lot easier. Yes it takes years of experience to know when you are taking shortcuts (getting money on credit - technical debt), and knowing how to get the loan at the lowest interest rate to make the loan less onerous (paying back the technical debt)

scarface74 9y ago

Why does gettings things done preclude quality code if you know in advance that you took shortcuts? For instance, write now to "get things done" I might keep all of my passwords for a system I'm trying to get through QA and UAT in a plain text configuration file. Knowing that's a "bad thing", I'm going to abstract how I get credentials in a method/class that everyone uses. Then once I decide how we want to store credentials securely, we can rip it out, change one method and everyone is updated through the shared library. Another real world example for us is logging. I knew in advance that we ultimately wanted a better logging framework for searching than just a straight text log like you get with log4net/log4j. We wanted structured searchable logging and to eventually use Elastic Search and Kibanna. I didn't have the bandwidth to do that at the time, but I still insisted on Serilog that would give us structured logging and just used a text file sink, later I added a Mongo sink for searchability just by making a configuration change, when I get around to it, I'll add an ElasticSearch sink. We then get easily searchable logs with applications specific properties to search with a nice front end without any code changes. Even if I skip unit testing, I'm still going to insist code be structured in a way that separates business code from persistence so when we get a chance to write unit tests (if ever) it makes it a lot easier. Yes it takes years of experience to know when you are taking shortcuts (getting money on credit - technical debt), and knowing how to get the loan at the lowest interest rate to make the loan less onerous (paying back the technical debt)