I found joy in switching from grep to silversearcher, which runs faster and finds patterns more reliably.įinding joy is about taking the time to assess what parts of your process and job don't bring joy, and why.
#Organization benefits and tidiness code#
Tools and code may be beautiful in the sense that they are usable, modular, and productive. It's also okay if what sparks joy isn't necessarily beautiful, but instead, is just plain useful. Does your team have an old script that no longer serves a purpose? As Kondo would say: Thank it for its service, and let it go. Unlike with Kondo's clients with their possessions, IT teams can't hold their Docker images and Terraform state files to their chests to see if they spark joy (though server huggers may disagree).įor many IT teams, joy may seem like a luxury, not a framework around which they are empowered to make business decisions.īut fear not! You can start by defining what joy means for your organization. The idea of sparking joy is a bit abstract, especially for IT teams that are pushed to find new ways to increase productivity and improve responsiveness, all while remaining compatible with existing internal applications. Tidying your infrastructure will do more than just lower your AWS bill it will break your team out of that rut and build new, better practices.
As IT teams, we tend to get comfortable in our workflows, even if they're inefficient or unstable. Clutter and possessions start to define your workspace. It's a process of considering where your infrastructure is and where you want it to be.
This assessment and cleaning aren't going to be easy, or happen overnight. Just as you wouldn’t leave a burrito wrapper on the counter, don't leave temp files lying around after your test suite runs. Tidiness is about investing in changing old, bad habits now that will pay dividends in the coming years, and creating practices around consistent tidying. Tidying your infrastructure isn’t about being perfect or doing one big clean and then forgetting about it. Are you still using Avery's user account to publish Docker images, even though that person left the company six months ago? Do you cross your fingers before each Jenkins run, hoping that the transient bug that's plagued your team for months doesn't show up? We've all been there. You’ll have more space-physical, emotional, on disk-for the resources you need to do your job. Keeping your work tidy has many of the same benefits as keeping your house tidy. It has the same descriptors as a tidy room-organized, labeled, uncluttered-but applied more abstractly to your codebase and data center.
#Organization benefits and tidiness free#
As satisfying as clean racks and bundled cables might be, tidy infrastructure means being free of unnecessary or unused resources (or clutter), organized so that everything has a place, and automated so that it's easy to interact with. When you hear "tidy," your brain might jump to images of sparse bookshelves, organized drawers, and sparkling countertops. While the idea of a tidy IT infrastructure is more abstract than a tidy home, you can apply Kondo's principles and philosophies to your organization for many of the same benefits: more space for the resources and tools you actually use, a unified and defined vision for the IT infrastructure you want, and a more enjoyable work life. For example, what would your infrastructure look like using the KonMari method? How could you empower your IT team to define and reach their goals? What impact would that have on your business and IT spending?
The Kondo craze got me wondering if this method of tidying up could also apply to IT. For many people, the process and results of the KonMari method have been life-changing. She asks participants to focus on the utility and joy of objects in order to remove possessions that aren't serving a purpose. Marie Kondo, the tidying expert and Netflix phenomenon, has people everywhere re-examining what in their lives sparks joy. If that doesn't describe your IT infrastructure, perhaps it's time to follow Kondo's KonMari method.
0 kommentar(er)
