Software is like gardening - one day I'll go behind the shed and clean up. But if nobody ever goes there, does it matter a lot?

Software is like gardening one
Software is like gardening one
Software is like gardening - one day I'll go behind the shed and clean up. But if nobody ever goes there, does it matter a lot?
Software is like gardening one
Software is like gardening - one day I'll go behind the shed and clean up. But if nobody ever goes there, does it matter a lot?
Software is like gardening one
Software is like gardening - one day I'll go behind the shed and clean up. But if nobody ever goes there, does it matter a lot?
Software is like gardening one
Software is like gardening - one day I'll go behind the shed and clean up. But if nobody ever goes there, does it matter a lot?
Software is like gardening one
Software is like gardening - one day I'll go behind the shed and clean up. But if nobody ever goes there, does it matter a lot?
Software is like gardening one
Software is like gardening one
Software is like gardening one
Software is like gardening one
Software is like gardening one
Software is like gardening one

Mike Krieger’s quote compares software development to gardening, suggesting that just as gardeners occasionally need to clean up behind the shed, software developers must sometimes tidy up or refactor their work. The metaphor implies that maintenance in both fields is an ongoing but often overlooked task. The idea of going "behind the shed" suggests that there are areas of software (or a garden) that might not be immediately visible or impactful but still require attention over time.

Krieger’s follow-up question, "But if nobody ever goes there, does it matter a lot?" touches on the importance of this maintenance. It suggests that some aspects of software may remain hidden or irrelevant to users, leading to the question of whether it is worth spending time on these less visible tasks. This reflects a pragmatic view of software development, where developers need to weigh the cost of maintenance against the impact on the overall system or user experience.

The comparison also reflects the balance between perfection and practicality in software development. Just as in gardening, some areas might not need constant attention, and cleaning up can sometimes be more about aesthetic or organization rather than addressing immediate, functional problems. The metaphor hints at the challenge of managing technical debt in software—deciding when and where to invest time in refactoring or tidying up code, especially when it doesn’t have a direct user impact.

The origin of this quote comes from Krieger’s experience as a software engineer and co-founder of Instagram. His perspective is grounded in the reality of building and maintaining a complex software system, where decisions often have to be made about when to prioritize visible features or improvements over less glamorous but necessary maintenance. The quote reflects his thoughtful, efficient approach to software development, balancing effort with impact.

Mike Krieger
Mike Krieger

Brazilian - Businessman Born: March 4, 1986

Have 0 Comment Software is like gardening one

AAdministratorAdministrator

Welcome, honored guests. Please leave a comment, we will respond soon

Reply.
Information sender
Leave the question
Click here to rate
Information sender
0.31941 sec| 2544.695 kb