No-Bullshit Guide into Building Software

Transcript

1. No-Bullshit Guide into Building Software
2. Don’t listen to JavaScript developers!
3. Questions?
4. /usr/bin/whoami • Software Engineer @ Leadfeeder I do R&D + Billing stuff Aldo Ziflaj @aziflaj
5. /usr/bin/whoami • Software Engineer @ Leadfeeder I do R&D + Billing stuff • Previously @ Publer Systems Architect & Backend Dude Aldo Ziflaj @aziflaj
6. /usr/bin/whoami • Software Engineer @ Leadfeeder I do R&D + Billing stuff • Previously @ Publer Systems Architect & Backend Dude • Opinionated Human Person Aldo Ziflaj @aziflaj
7. bullshit /ˈbʊlʃɪt/
8. bullshit /ˈbʊlʃɪt/ Unnecessary steps and practices which add little to no value to the overall process
9. The Software Process
10. The Software Process
11. The Software Process PM
12. The Software Process PM Dev
13. meetings
14. meetings • Sprint planning & Guesstimations
15. meetings • Sprint planning & Guesstimations • Daily standups
16. meetings • Sprint planning & Guesstimations • Daily standups • Review & Retrospection
17. meetings • Sprint planning & Guesstimations • Daily standups • Review & Retrospection • PM says: “We need devs on this call”
18. PM-ing the right way
19. PM-ing the right way • Write better specs
20. PM-ing the right way • Write better specs • Prioritize your features!
21. PM-ing the right way • Write better specs • Prioritize your features! • Buffer all comms for devs
22. PM-ing the right way • Write better specs • Prioritize your features! • Buffer all comms for devs • Prioritize your features!
23. PM-ing the right way • Write better specs • Prioritize your features! • Buffer all comms for devs • Prioritize your features! • Regard guesstimations as optimistic
24. PM-ing the right way • Write better specs • Prioritize your features! • Buffer all comms for devs • Prioritize your features! • Regard guesstimations as optimistic • Know your product better than devs
25. PM-ing the right way • Write better specs • Prioritize your features! • Buffer all comms for devs • Prioritize your features! • Regard guesstimations as optimistic • Know your product better than devs • Prioritize your features!
26. How devs build shit • We’ll do it later
27. How devs build shit • We’ll do it later (we wont)
28. How devs build shit • We’ll do it later (we wont) • We need this
29. How devs build shit • We’ll do it later (we wont) • We need this (YAGNI)
30. How devs build shit • We’ll do it later (we wont) • We need this (YAGNI) • We do functional programming, fuck SOLID
31. How devs build shit • We’ll do it later (we wont) • We need this (YAGNI) • We do functional programming, fuck SOLID • Better architecture
32. How devs build shit • We’ll do it later (we wont) • We need this (YAGNI) • We do functional programming, fuck SOLID • Better architecture (overengineering)
33. How devs build shit • We’ll do it later (we wont) • We need this (YAGNI) • We do functional programming, fuck SOLID • Better architecture (overengineering) • New tech is better than everything we ever had!
34. How devs build shit • We’ll do it later (we wont) • We need this (YAGNI) • We do functional programming, fuck SOLID • Better architecture (overengineering) • New tech is better than everything we ever had! (it’s not)
35. How devs build shit • We’ll do it later (we wont) • We need this (YAGNI) • We do functional programming, fuck SOLID • Better architecture (overengineering) • New tech is better than everything we ever had! (it’s not) • OMG Microservices!!1!
36. How devs build shit • We’ll do it later (we wont) • We need this (YAGNI) • We do functional programming, fuck SOLID • Better architecture (overengineering) • New tech is better than everything we ever had! (it’s not) • OMG Microservices!!1! (I read an article)
37. How devs build shit • We’ll do it later (we wont) • We need this (YAGNI) • We do functional programming, fuck SOLID • Better architecture (overengineering) • New tech is better than everything we ever had! (it’s not) • OMG Microservices!!1! (I read an article) • sCaLaBiLiTy
38. How devs build shit • We’ll do it later (we wont) • We need this (YAGNI) • We do functional programming, fuck SOLID • Better architecture (overengineering) • New tech is better than everything we ever had! (it’s not) • OMG Microservices!!1! (I read an article) • sCaLaBiLiTy (facebook meta does this)
39. Building shit the right way
40. Building shit the right way • Old tech is shark, not dinosaur
41. Building shit the right way • Old tech is shark, not dinosaur • Most problems are already solved
42. Building shit the right way • Old tech is shark, not dinosaur • Most problems are already solved, your framework just did it too late
43. Building shit the right way • Old tech is shark, not dinosaur • Most problems are already solved, your framework just did it too late • Patterns exist for a reason
44. Building shit the right way • Old tech is shark, not dinosaur • Most problems are already solved, your framework just did it too late • Patterns exist for a reason • You don’t have a scale problem
45. Building shit the right way • Old tech is shark, not dinosaur • Most problems are already solved, your framework just did it too late • Patterns exist for a reason • You don’t have a scale problem (until you do)
46. Building shit the right way • Old tech is shark, not dinosaur • Most problems are already solved, your framework just did it too late • Patterns exist for a reason • You don’t have a scale problem (until you do) • Monoliths > Microservices*
47. Building shit the right way • Old tech is shark, not dinosaur • Most problems are already solved, your framework just did it too late • Patterns exist for a reason • You don’t have a scale problem (until you do) • Monoliths > Microservices* * Unless you absolutely need microservices
48. Questions? (for real this time)