Uploaded byEveryware Technologies
The Professional Software Engineer
This document discusses the role and responsibilities of a professional software engineer. It covers topics like agile methodologies, software craftsmanship principles, test-driven development, architecture, design patterns, and resources for further learning. The document is presented by Everyware Technologies, a consulting, training and development company focused on helping engineers improve their skills and practices.
More Related Content
Similar to The Professional Software Engineer
The Professional Software Engineer
- 1. The Professional Software Engineer CarlosRodríguez Domínguez Everyware Technologies S.L. Tomás Ruiz López /everywaretech @everywaretech {tomas, carlos}@everywaretech.es
- 2.
- 3.
- 4.
- 5. Kent Beck RobertC. Martin Martin Fowler Agile Manifesto
- 6.
- 7. Individuals & Interactions overProcesses and Tools
- 8. Working Software over ComprehensiveDocumentation
- 9. Customer Collaboration over ContractNegotiation
- 10. Responding to Change overFollowing a Plan
- 11.
- 12. Well-crafted Software not onlyworking software
- 13. Steadily Adding Value notonly responding to change
- 14. Community of Professionals not onlyindividuals and interactions
- 15. Productive Partnerships not onlycustomer collaboration
- 16.
- 17. Do No Harm TheHippocratic Oath
- 18. Perpetual Inexperience Quality, Ethicsand Chickens
- 19. Continuous Learning Respond toIndustrial Change
- 20. Practicing Kata, Wasa &Randori
- 21. Mentoring Teaching as aLearning Process
- 22. Saying NO Discuss andnegotiate
- 23.
- 24.
- 25. Working Week Avoid workingovertime
- 26. Leadership Don’t confuse withdespotism
- 27.
- 28. 4 Variables Quality, Time,Money & Scope
- 29. Planning The Backlog ofUser Stories
- 30.
- 31. #NoEstimates Because we arereally bad at estimating
- 32. The 20-80 Rule Beable to manage your resources
- 33.
- 34. Meetings 200 € /(person-hour)
- 35.
- 36.
- 37. IDE Some help isalways appreciated
- 38. Source Code Control Alwayshave a fallback
- 39. Clean Code Commit toCoding Standards
- 40. Architecture Clean, Hexagonal, Screaming,Onion, Ring…
- 41. S Singleton Invasion TTight Coupling U Untestability P Premature Optimization I Indescriptive Naming D Duplication
- 42. S Single Responsibility OOpen-Closed L Liskov Substitution I Interface Segregation D Dependency Inversion
- 43. Refactoring Eliminate Code Smellsand Design Mistakes
- 44. Test-Driven Development Making sureit works? NO
- 45.
- 46.
- 47.
- 48.
- 49.
- 50. About Professionalism The CleanCoder: A Code of Conduct for Professional Programmers by Robert C. Martin The Software Craftsman: Professionalism, Pragmatism, Pride by Sandro Mancuso Quality, Ethics and Chickens by Wendy Closson (podcast interviewing Robert C. Martin)
- 51. About Agile Methodologies ExtremeProgramming Explained: Embrace Change by Kent Beck Agile Software Development: Principles, Patterns and Practices by Robert C. Martin Test-Driven Development by Example by Kent Beck
- 52. About Architecture Microservices byMartin Fowler (video) The Clean Architecture by Robert C. Martin (video)
- 53. About Design andDevelopment Refactoring: Improving the Design of Existing Code by Martin Fowler Object Thinking by David West Clean Code: A Handbook of Agile Software Craftmanship by Robert C. Martin Design Patterns: Elements of Reusable Object- Oriented Software by Erich Gamma, Ralph Johnson, Richard Helm & John Vlissides
- 54. About Test-Driven Development IntegratedTests are a Scam by J. B. Rainsberger (video) 467 tests, 0 failures, 0 confidence by Katrina Owen (video) The Deep Synergy between Testability and Good Design by Tim Yann (video) Making Making CoffeeScript by Kent Beck (video) JUnit Recipes: Practical Methods for Programmer Testing by J. B. Rainsberger
- 55.
- 56.