Conversation

Notices

1. Embed this notice
   Ivan Sagalaev :flag_wbw: (isagalaev@mastodon.social)'s status on Thursday, 01-Feb-2024 08:36:58 JST Ivan Sagalaev :flag_wbw:

   • Josh Justice

   I never heard the term "evolutionary design", although this is apparently the way I design software (and try to teach others to do it). Here's a perfect, short and to the point, explanation of the concept by @CodingItWrong: https://codingitwrong.com/2024/01/29/brief-summary-of-evolutionary-design

   Also a good reminder of what the word "refactoring" actually means, despite it being widely used to refer to any arbitrary reshuffling of code.

   • Embed this notice
     phiofx (phiofx@hachyderm.io)'s status on Thursday, 01-Feb-2024 08:36:58 JST phiofx

     in reply to

     • Josh Justice

     @isagalaev @CodingItWrong evolutionary design makes a lot of sense, except when it doesnt and it needs to become... revolutionary? :-)

     I mean this dreadful moment when after many incremental changes that worked okayish you realise you have been under-engineering things and you must make major and costly revisions.

   • Embed this notice
     phiofx (phiofx@hachyderm.io)'s status on Thursday, 01-Feb-2024 08:54:30 JST phiofx

     in reply to

     • Josh Justice

     @isagalaev @CodingItWrong but thats just ex-post semantics. You only know that it was a shortcut rather than the simplest future proof solution when a requirement comes in that reveals that this is the case.

   • Embed this notice
     Ivan Sagalaev :flag_wbw: (isagalaev@mastodon.social)'s status on Thursday, 01-Feb-2024 08:54:31 JST Ivan Sagalaev :flag_wbw:

     in reply to

     • Josh Justice
     • phiofx

     @phiofx @CodingItWrong it feels like you're talking more about "making easy shortcuts" rather than "designing a most simple solution".