Those involved in IT and Software Development specifically the many projects that are being managed as Agile Projects with the Scrum as the main organizational tool, are especially susceptible the problem of "Technical Debt". It happens when deadlines can't be met by doing the needed work and so corners are cut and quick hacks are used just to get the job done with the hope of coming back later on and fixing up the code to make it more professional, robust, etc. This is really just a form of laziness and is totally unprofessional for a corporation that pays for and relies so much on professionally produced work. These are the groups that should be first to be layed-off with the lower level managers that practise this kind of operation being first to go.
4 replies (most recent on top)
@qdn you know you are addressing your boss right? 😂😂😂
This is great.
@inq, your manager should have you as #1 on the layoff list as totally incompetent and unprofessional - maybe you should read the main post again so that you can understand what is being said before making stupid comments. The post is about Laziness and the lack of professionalism that now exists on many of these Agile projects as these days it's all about "hack'ing a solution quickly." When maintainability, and robustness are important, Hacking becomes a real problem. This is when the Technical Debt really adds up. So call it elegant, but when you replacement arrives from India to re-do your code and work on the 20 projects that will be created to replace yours, he will have to re-write your Elegant hack(s).
Terrible concept. Company is now employing shortcuts, and creating long term business problems down the road.
That is BS
Shows amateur hour
Some hacks are actually pretty creative and elegant and meets the business needs and that is often just as important as feeding some coders overly inflated view of his place in the org and probably the world
Grow up