A broken clock fixed by taping a working clock over it is a metaphor for every codebase youβll encounter in your professional career as a software developer.
Conversation
Notices
-
Dare Obasanjo (carnage4life@mas.to)'s status on Tuesday, 08-Aug-2023 12:21:24 UTC Dare Obasanjo -
Ari Turetzky (arit93@mastodon.social)'s status on Tuesday, 08-Aug-2023 12:21:23 UTC Ari Turetzky @carnage4life all that's missing is the post it note telling you to talk to someone who left 10 years ago about how to change the batteries in the working clock.
Santa Claes πΈπͺππ°π likes this. -
Ari Turetzky (arit93@mastodon.social)'s status on Tuesday, 08-Aug-2023 12:21:27 UTC Ari Turetzky @fugueish @carnage4life 6 months later there would just be a solar powered digital clock duct taped over the second clock, and we'd have pretty awards hanging on our cubes. (what me cynical!? unpossible)
Santa Claes πΈπͺππ°π likes this. -
Chris Palmer :donor: (fugueish@infosec.exchange)'s status on Tuesday, 08-Aug-2023 12:21:32 UTC Chris Palmer :donor: @AriT93 @carnage4life And this is why we all dream of a greenfield project to implement a sundial
Santa Claes πΈπͺππ°π likes this. -
Eric G. (ericg@sanjuans.life)'s status on Tuesday, 08-Aug-2023 12:21:39 UTC Eric G. @carnage4life I have been occasionally scolded for my 'messy' PRs that muck out disfunction, realign ancillary internal methods & data structures and/or otherwise embrace my inner Fowler. The PR diffs are ugly AF but some of them are things I am most proud of.
To the topic: lately I feel sometimes our PR/user story approach encourages the employment of duck tape by encouraging change that fully satisfies stated requirements, makes for easy-to-read PRs, but loses the plot along the way.
Santa Claes πΈπͺππ°π likes this.
-