I have a calendar from a vendor we use that has some of the classic coding and design principles – one for each month. I was rubbing my chin staring at it this morning and I wanted to share what popped into my head…
While I am sure that the KISS principle has been written about (perhaps to death) I had another instance of this today as it applies to operations and infrastructure.
Quick background – I recently inherited an Operational group. Operations is the clean up crew of development here. While I understand the rationale of separating them, I think I like the idea of developers supporting their own code so that they better understand the impact of what they do. What a great teaching tool – you want to not get up in the middle of the night – fix the code, do a better job in the first place, write a utility to help you out. We have a bunch of applications that have been around for years and over time the developers who maintain many of these have moved on. So today I asked the question of someone about two AD groups and what they are used for. In both cases the answer was initially I don’t know – and later the answer became these are not used anymore.
Part of keeping systems simple is getting rid of the things that are not used anymore. We have all these extraneous moving parts that we don’t need. This just creates system bloat that should be easy to remove.
Granted you cannot get to everything – right now. But this stuff has to get cleaned up over time. Putting it into some sort of maintenance, wish list or Kaizen log seems like an easy thing to do.
All it takes is discipline.