#evolutionarydesign — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #evolutionarydesign, aggregated by home.social.
-
"The mistake is treating both kinds of code the same: Glue code gets over-engineered. Core domain logic stays hidden in long services or handlers. Good architecture starts with noticing the difference."
#softwareengineering #softwarearchitecture #yagni #evolutionarydesign
-
"The mistake is treating both kinds of code the same: Glue code gets over-engineered. Core domain logic stays hidden in long services or handlers. Good architecture starts with noticing the difference."
#softwareengineering #softwarearchitecture #yagni #evolutionarydesign
-
"The mistake is treating both kinds of code the same: Glue code gets over-engineered. Core domain logic stays hidden in long services or handlers. Good architecture starts with noticing the difference."
#softwareengineering #softwarearchitecture #yagni #evolutionarydesign
-
"The mistake is treating both kinds of code the same: Glue code gets over-engineered. Core domain logic stays hidden in long services or handlers. Good architecture starts with noticing the difference."
#softwareengineering #softwarearchitecture #yagni #evolutionarydesign
-
When one part of a function is not changing while you're repeatedly changing another part, this is a signal to consider breaking that function into two pieces: the stable part and the unstable part.
This isn't a law, but merely a helpful guideline.
-
When one part of a function is not changing while you're repeatedly changing another part, this is a signal to consider breaking that function into two pieces: the stable part and the unstable part.
This isn't a law, but merely a helpful guideline.
-
When I grow up, I (still) want to be like Theo! His creatures are becoming ever more complex, elegant & marvellous....
https://www.youtube.com/watch?v=iWGlbpEZkNA
🔥🔥🔥
-
When I grow up, I (still) want to be like Theo! His creatures are becoming ever more complex, elegant & marvellous....
https://www.youtube.com/watch?v=iWGlbpEZkNA
🔥🔥🔥
-
DevLog 009: Improve timeline scrubbing
... This passes the tests, and when I try it in the application, it works as intended.
Are we done?
http://rickardlindberg.me/writing/devlog-009-improve-timeline-scrubbing/
-
The "Test Helper to Production Code" pipeline: one pattern.
Custom assertions become comparison operators become summary values become domain concepts.
-
The "Test Helper to Production Code" pipeline: one pattern.
Custom assertions become comparison operators become summary values become domain concepts.
-
Key practice: #EvolutionaryDesign | by Jason Yip | May, 2023 | Medium
https://jchyip.medium.com/key-practice-evolutionary-design-40a1649174df #ExtremeProgramming #ProductDevelopment #Agile
-
Key practice: #EvolutionaryDesign | by Jason Yip | May, 2023 | Medium
https://jchyip.medium.com/key-practice-evolutionary-design-40a1649174df #ExtremeProgramming #ProductDevelopment #Agile
-
#EvolutionaryDesign means you trust your ability to respond to change more than you trust your ability to predict the future.
-
#EvolutionaryDesign means you trust your ability to respond to change more than you trust your ability to predict the future.
-
#EvolutionaryDesign is a "good strategy" approach to design. Focus on the core, and only the core, of the problem first and then iterate. Attempting to anticipate all design issues upfront is "bad strategy".
-
#EvolutionaryDesign is a "good strategy" approach to design. Focus on the core, and only the core, of the problem first and then iterate. Attempting to anticipate all design issues upfront is "bad strategy".
-
We needed to extend a component with new behavior. Rather than trying to _think_ our way forward by designing something clever, we created a copy and added the new behavior there.
Yes, copy and paste. Loads of duplication. Then we made the code work, with nested if-else blocks. Yucky, but it worked.
THEN we went to town, doing mostly mindless #Refactoring. It was like the Gilded Rose #CodeKata, but in real life! #EvolutionaryDesign
-
We needed to extend a component with new behavior. Rather than trying to _think_ our way forward by designing something clever, we created a copy and added the new behavior there.
Yes, copy and paste. Loads of duplication. Then we made the code work, with nested if-else blocks. Yucky, but it worked.
THEN we went to town, doing mostly mindless #Refactoring. It was like the Gilded Rose #CodeKata, but in real life! #EvolutionaryDesign
-
@tonybyrne @davetron5000 Indeed. Thinking in labels (such as that) causes a new class of problems, which I've spent decades trying to avoid. :)
One nice aspect of #EvolutionaryDesign involves growing increasingly comfortable with imperfection, such as unfamiliar code or two design approaches in the same code base.
-
@tonybyrne @davetron5000 Indeed. Thinking in labels (such as that) causes a new class of problems, which I've spent decades trying to avoid. :)
One nice aspect of #EvolutionaryDesign involves growing increasingly comfortable with imperfection, such as unfamiliar code or two design approaches in the same code base.
-
#EvolutionaryDesign or #DesignUpfront? I believe it’s a bit of both as I always bring in my past experience and have some design in mind before I start to #tdd. I also evolve the design as I learn more about the domain and listen to what my tests are telling me.
Here’s a 2007 discussion between Jim Coplien and Uncle Bob that prompted me to write this: https://youtu.be/KtHQGs3zFAM -
#EvolutionaryDesign or #DesignUpfront? I believe it’s a bit of both as I always bring in my past experience and have some design in mind before I start to #tdd. I also evolve the design as I learn more about the domain and listen to what my tests are telling me.
Here’s a 2007 discussion between Jim Coplien and Uncle Bob that prompted me to write this: https://youtu.be/KtHQGs3zFAM -
Further to my recent discussion about #TestDoubles/ #MockObjects in design, I remember asking this question at a SoCraTes event in Rochegude, France:
"Are method/function expectations an #OOP disease?"
(Or something similar.)
The short answer seemed to be this: it's quite OO, but maybe not a disease. In FP we sometimes contort ourselves to turn complicated custom workflows into straightforward function composition, and it's not always worth the effort.
-
Further to my recent discussion about #TestDoubles/ #MockObjects in design, I remember asking this question at a SoCraTes event in Rochegude, France:
"Are method/function expectations an #OOP disease?"
(Or something similar.)
The short answer seemed to be this: it's quite OO, but maybe not a disease. In FP we sometimes contort ourselves to turn complicated custom workflows into straightforward function composition, and it's not always worth the effort.
-
Further to this idea, whose videos on "evolutionary design without #TestDoubles / #MockObjects" would you endorse? I mean you really like them. You found them compelling and convincing. They don't have to be free.
-
Further to this idea, whose videos on "evolutionary design without #TestDoubles / #MockObjects" would you endorse? I mean you really like them. You found them compelling and convincing. They don't have to be free.