Conversation

Notices

1. Embed this notice
   Dare Obasanjo (carnage4life@mas.to)'s status on Tuesday, 08-Aug-2023 10:05:00 JST Dare Obasanjo

   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.

   • cool_boy_mew, Haelwenn /элвэн/ :triskell: and Doughnut Lollipop 【記録係】:blobfoxgooglymlem: like this.
   • Embed this notice
     ?? Humpleupagus ?? (humpleupagus@eveningzoo.club)'s status on Tuesday, 08-Aug-2023 18:57:32 JST ?? Humpleupagus ??

     in reply to
     A black guy fixing things with duct tape. If only there was a term for this. 🤔
   • Embed this notice
     Ari Turetzky (arit93@mastodon.social)'s status on Tuesday, 08-Aug-2023 20:47:27 JST Ari Turetzky

     in reply to

     @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.

     clacke likes this.
   • Embed this notice
     Eric G. (ericg@sanjuans.life)'s status on Tuesday, 08-Aug-2023 20:47:45 JST Eric G.

     in reply to

     @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.

     clacke likes this.