Extreme Professionalism - Software Craftsmanship
•
2 likes•324 views
Decades ago, IT started as a single engineering practice, but as time passed by it got increasingly fragmented. Conflicts broke out between testers vs developers vs sysadmins vs DBAs vs many other roles. Recently, developers themselves split into many subspecialties like backend/frontend/iOS/Android/microservices/functions/etc. The overspecialization we face today is a rich source of communication overhead, a low bus factor, lack of responsibility, blaming, repeated isolated patching and fulminating costs. More than a ‘full-stack’ developer, a software craftsperson distinguishes oneself by acting professionally and taking responsibility for as many aspects of one’s work. Jump on this never-ending journey of continuous improvement and decide what’s the next level for your own case. For a company/individual training, check out my website: victorrentea.ro
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Extreme Professionalism - Software Craftsmanship
Similar to Extreme Professionalism - Software Craftsmanship (20)
More from Victor Rentea
More from Victor Rentea (17)
Recently uploaded
Recently uploaded (20)
Extreme Professionalism - Software Craftsmanship
- 1. Extreme Professionalism: Software Craftsmanship victor.rentea@gmail.com ♦ ♦ @victorrentea ♦ VictorRentea.ro
- 2. Victor Rentea Clean Code Evangelist VictorRentea.ro/#playlist 100% Independent Trainer & Consultant Founder of Bucharest Software Craftsmanship Community Simple Design, Refactoring, TDD Java Champion C# 14 of Java Join for free monthly webinars
- 3. Technical Training Hibernate/JPASpring Func Prog in Java & more 300+ days2000 devs8 years VictorRentea.rovictorrentea.teachable.com 40 companies Follow me: 30K 4K 3K Java PerformanceReactive-X Design Patterns DDD Clean Code Refactoring Unit Testing TDD any lang
- 4. VictorRentea.ro4 A bit of history
- 5. VictorRentea.ro5 At the beginning there were only Craftspersons
- 6. VictorRentea.ro6 They had to do everything Most were women But then, it all changed…
- 7. VictorRentea.ro7 A Gentle Introduction to Conflicts and Toxicity in IT
- 11. VictorRentea.ro11 Admins vs Devs Admins hate change Dev’s job is to change things Developers with no admin rights on their VMs Restricted software, email scanning Zip>Encrypt>Base64encode>Email
- 13. VictorRentea.ro13 DBA vs Dev DBA = profession invented in 2000s by Oracle “Keep all logic IN” “DB is a detail” Conservative A (worse) Extreme: Let's reimplement it all in noSQL
- 15. VictorRentea.ro15 Isolated Communities Open vs Proprietary Languages Static vs Dynamic Game devs locked-up in “studios” NodeJS devs reinventing a lot
- 16. VictorRentea.ro16 Frontend vs Backend Single-Page-Apps tech are complex Young devs → UI → reinventing stuff Rediscovering Best Practices Backend devs -> “API developers” Since 2010s:
- 20. VictorRentea.ro22 The Triad of Waste Android vs iOS vs Web Companies implement the same UI 3 times Boy, in 2020, any business gotta' have an app Different teams 3x more bugs
- 21. VictorRentea.ro23 Sometimes, even in the same language…
- 24. VictorRentea.ro26 Overspecialization Slow projects Large teams Low truck factor But sometimes even worse…
- 27. VictorRentea.ro29 Collective Code Ownership You learn all aspects of your project You can help in any area You don’t delegate You control Power Responsibility
- 29. VictorRentea.ro31 Becoming Fuller-Stack Of your stack, not all Polyglot Reuse the essence simple design, auto-testing, security, logging, Deeper in critical areas
- 30. VictorRentea.ro32 Don’t Claim to be a Full-Stack Guru ∄
- 32. VictorRentea.ro34 Why Full-Stack? Technologies change Learning keeps you flexible Better welded teams More useful, adaptable, thus earn more
- 33. VictorRentea.ro35 “What Should I Learn?” Master technologies of your project Fully understand the true cause of a bug Seek design flaws, refactoring ideas
- 34. VictorRentea.ro36 What Happens Then? You fix the problem, not work around it You can Keep It Simple (KISS) and Maintainable You pick the right tools for the job You become pragmatic
- 35. VictorRentea.ro37 Other walls to tear down?
- 37. VictorRentea.ro39 No Ambiguity Can Pass Through Us Humans – Developers – Machine
- 42. VictorRentea.ro48 … we still have a job!! well-payed Despite delivering expensive bugs, slowly
- 45. VictorRentea.ro51 Are you Agile? Yeah, but, you know… A kind of.. Agileish Transitioning...
- 46. What is Agile ? The Developer
- 48. VictorRentea.ro54 Scrum Pushed upon us Management Buzzword
- 53. 59 © VictorRentea.ro a training by I will NOT commit SH*T I will push with reliable tests I will not harm a colleague
- 54. 60 © VictorRentea.ro a training by Okay, So what should I do?
- 55. VictorRentea.ro61 Skills of a Craftsperson ● Talk to customers directly ● Understand the real underlying problem ● Propose solutions ● Break the problem into small user-centric stories ● Design UI flow ● Write working code ● Write automated tests to avoid regressions ● Evolve the system architecture by refactoring ● Deploy the system to the end users (“DevOps”) Old-fashioned software developer My Trainings
- 56. VictorRentea.ro62 Back in the 1990s debugging skills were a major point of discussion in any job interview. Seniority could be measured by your ability and experience in debugging code. Those days are gone. Although debugging skills are important, we should be unpleasantly surprised whenever we need to resort to that, and when it occurs, we should write tests and refactor our code so we never need to do that again. read "breakpoint" (n.r.)
- 60. VictorRentea.ro66 Underdesign Emerging Architecture that never emerges Lack of Knowledge Lack of Skills ➔ Missing Practices
- 62. VictorRentea.ro69 This is NOT Extreme Programming
- 64. VictorRentea.ro71 1. I will not produce harmful code 2. The code that I produce will always be my best work 3. I will make frequent and small releases 4. I will provide with a quick and repeatable proof that it works 5. I will fearlessly and relentlessly improve code at any occasion. I will not make the code worse The Software Craftsperson’s Oath -slightly simplified- https://blog.cleancoder.com/uncle-bob/2015/11/18/TheProgrammersOath.html
- 65. VictorRentea.ro72 5. I will fearlessly and relentlessly improve code at any occasion. I will not make the code worse 6. I will keep productivity high for me and my team. 7. I will continuously ensure that others can cover for me and that I can cover for them 8. I will produce estimates that are sharp. I will not make promises without certainty 9. I will never stop learning and improving my craft https://blog.cleancoder.com/uncle-bob/2015/11/18/TheProgrammersOath.html The Software Craftsperson’s Oath -slightly simplified-
- 66. VictorRentea.ro73 Problem The performance of your daily programming activities does not give you room to learn by making mistakes. It’s as if you’re always on stage.
- 67. VictorRentea.ro74 Challenge Your... Design: Testable Code, Language: TypeScript, Java, SQL, C#, Closure, Swift, R, ... Communication: Explain your stuff to others (+non-technical!) Reasoning: Start a pet project, contribute to Open-Source Economics: Think about starting a business
- 70. VictorRentea.ro77 Practice Pair Programming Refactoring TDD Don’t Rush Fear Compete Do Play Challenge Yourself (restrictions) Try new ideas Coding Dojo 1-2h 4-10
- 71. VictorRentea.ro78 First Half Chapter 3 + links
- 78. VictorRentea.ro85 2 34 5 7 77777 7899777 "Grape" Programming aka ad-hoc mobbing
- 79. VictorRentea.ro86 Craftsmanship does not mean just loving to code But it usually starts with that
- 80. VictorRentea.ro87 Juniors are eager to write more code Seniors can’t wait to delete it
- 82. VictorRentea.ro89 We don’t just write code We solve problems Training for you: victorrentea.teachable.com ♦ For your company: VictorRentea.ro ♦ Community: VictorRentea.ro/community victorrentea@gmail.com ♦ @victorrentea Talk inspired by "The World Needs Full-Stack Craftsmen" talk by Anton Keks