blah blah...

1. Lior Bar-On, 2017
“Were we doing it wrong all these years?”
http://evolutionaryhomebuilders.com
Evolutionary
Software Design

2. Who is this Guy? - Lior Bar-On
‫תוכנה‬ ‫ארכיטקטורת‬ ‫בלוג‬
Developer
Architect
Chief Architect
Blogger ?

3. Does Software Design
pays off?
firstcovers.com

4. Ingredients:
● Hours of thinking
● Hours of Putting thoughts on paper
● Time making the thoughts communicable
● “The Review Meeting” -- a ceremony
● [Optional] Hours arguing about some points
● Tax: making some changes
● [Optional] Post work (update doc, more meetings)
● => Happiness for doing “the right thing”
http://www.seriouseats.com/

5. ASTMe
A structure that makes sense
DSS
It’s the Database Schema, Stupid
PID / DSS-PID
Polishing implementation details
http://www.seriouseats.com/

6. ●

7. https://www.safaribooksonline.com/library/view/user-experience-mapping

8. “Start up Design”
“Balanced Design”
Too much Design
“No Design”

9. http://safetytoolboxtopics.com/Behavioral-Safety/shortcuts-part-1.html
=> Less “design practices”Small / expected Feature
=> Less “design practices”“Did it Before”
=> Less “design practices”“No Clue”
=> More “design practices”
“Got a direction, but path
is unclear”

10. Design Practices vs. Exploration

11. ● Aim for breakthroughs
● The leverage is in the assumptions - not
implementation details
● Keep decisions open

12. Understanding
of “right” design
Breakthroughs
Viable Learning

13. while(true) {
if (clarity < OK) {
do(explore) // “Map”
} else {
do(design.practices) // “Reduce”
}
}

14. E2E Flow
MVC / di
DB Access B.Logic
(skinny)
Max-learning min-time
Complex
Cozy
CozyGood
Good

15. ™
● ++ “Routine” work
● ++ Large work

16. Amount of given functionality
Adaptability to changes
“A Caravan over a Palace”

17. Design Practices
(probably won’t get there)
http://www.talentism.com/new-business-playbook/what-is-a-playbook/

18. design.practices
○ Understand the context properly
○ Review Main Decisions (aim: assumptions)
○ Iterate the Model & Flow
○ Activate your own checklist

19. ● Alternative #1:
○ Pros: ….
○ Cons: …
● Alternative #2: SELECTED
○ Pros: ….
○ Cons: …
● Alternative #3:
○ Pros: ….
○ Cons: ...

20. ● Alternative #1: RabbitMQ
○ Pros: simple, efficient,..
○ Cons: how to recover if messages lost?
● Alternative #2: Service polls the source
○ Pros: ability to recover, smaller per-message overhead
○ Cons: new dependency between services
Alternative #2 selected

21. and
Brainstorm Database Schema, but:
Eliminate the f**&!*n types:
“Number”, “text”, “bool” are
enough
Drop technical fields
(“created_at”)
Drop FKs, Nullability etc.
Assure Good Business ⇔ Software Mapping
Walkthrough the code+model - for verification

22. http://www.lifehack.org
Special Thanks to Erez Lotan
http://www.softwarearchiblog.com/2017/06/effective-software-design-sed.html