Writing code by staring into space for approx. 6 days and then writing everything in an hour.
Conversation
Notices
-
Embed this notice
Nick Poole (north@chaos.social)'s status on Tuesday, 22-Aug-2023 08:21:38 JST Nick Poole - clacke@libranet.de is my main likes this.
-
Embed this notice
Nick Poole (north@chaos.social)'s status on Tuesday, 09-Jul-2024 19:30:12 JST Nick Poole Relieved to discover that this is relatable content.
clacke@libranet.de is my main likes this. -
Embed this notice
Geoff Coffey (gwcoffey@bookstodon.com)'s status on Wednesday, 10-Jul-2024 18:42:03 JST Geoff Coffey @North It *is* an irony that the best way to figure out a tricky bit of code is to stop working on it.
clacke@libranet.de is my main likes this. -
Embed this notice
Andrew Padilla (datacequia@techhub.social)'s status on Wednesday, 10-Jul-2024 18:42:25 JST Andrew Padilla @North 😝 I’ve never found writing code to be a linear progression activity
clacke@libranet.de is my main likes this. -
Embed this notice
Joyographic (joyographic@mstdn.social)'s status on Wednesday, 10-Jul-2024 19:10:45 JST Joyographic @North Don't forget the six days you spend staring at the code after that, figuring out why it did what you told it to and not what you wanted.
clacke@libranet.de is my main likes this. -
Embed this notice
aburka 🫣 (aburka@hachyderm.io)'s status on Wednesday, 10-Jul-2024 19:11:35 JST aburka 🫣 @North Feynman programming
clacke@libranet.de is my main likes this. -
Embed this notice
GerbilEngineer (gerbilengineer@makersocial.online)'s status on Wednesday, 10-Jul-2024 19:12:04 JST GerbilEngineer Isn't that how everyone works? 🤔
clacke@libranet.de is my main likes this.