30+ years of tech, retired from an identity intelligence company, now part-time with an insurance broker.
Dev community mod - mostly light gardening & weeding out spam :)
The challenge I often come up against is knowing what 'finished' is..
I have many half-baked things in github, none with any 'definition of done' (to steal some agile terminology), but various levels of usefulness (even some stars!)
I have friends & colleagues who simply can't publish until they run out of things to do to their codebase.. and nothing published of course :)
Starting something without a purpose or a means to measure when it has reached that purpose is doomed to never reach 1.0, and publishing something without knowing why you will unpublish/obsolete/withdraw, is equally troublesome (and even harder to solve - so many zombies still in production sapping everyone's energy and money!).
The challenge I often come up against is knowing what 'finished' is..
I have many half-baked things in github, none with any 'definition of done' (to steal some agile terminology), but various levels of usefulness (even some stars!)
I have friends & colleagues who simply can't publish until they run out of things to do to their codebase.. and nothing published of course :)
Starting something without a purpose or a means to measure when it has reached that purpose is doomed to never reach 1.0, and publishing something without knowing why you will unpublish/obsolete/withdraw, is equally troublesome (and even harder to solve - so many zombies still in production sapping everyone's energy and money!).
Thanks for reading and sharing your thoughts! And Yes, totally agree.