A set of guidelines and practices to become a professional software engineer

1. The Professional
Software Engineer
Carlos Rodríguez Domínguez
Everyware Technologies S.L.
Tomás Ruiz López
/everywaretech @everywaretech
{tomas, carlos}@everywaretech.es

2. Everyware Technologies
Consulting

3. Everyware Technologies
Training

4. Everyware Technologies
Development

5. Kent Beck Robert C. Martin
Martin Fowler
Agile
Manifesto

6. The Agile
Manifesto

7. Individuals & Interactions
over Processes and Tools

8. Working Software
over Comprehensive Documentation

9. Customer Collaboration
over Contract Negotiation

10. Responding to Change
over Following a Plan

11. Software
Craftmanship

12. Well-crafted Software
not only working software

13. Steadily Adding Value
not only responding to change

14. Community of
Professionals
not only individuals and interactions

15. Productive Partnerships
not only customer collaboration

16. Professionalism

17. Do No Harm
The Hippocratic Oath

18. Perpetual Inexperience
Quality, Ethics and Chickens

19. Continuous Learning
Respond to Industrial Change

20. Practicing
Kata, Wasa & Randori

21. Mentoring
Teaching as a Learning Process

22. Saying NO
Discuss and negotiate

23. Saying YES
Say. Mean. Do.

24. Productivity
Pomodoro Technique

25. Working Week
Avoid working overtime

26. Leadership
Don’t confuse with despotism

27. Management

28. 4 Variables
Quality, Time, Money & Scope

29. Planning
The Backlog of User Stories

30. Estimation
T-Shirts & Poker cards

31. #NoEstimates
Because we are really bad at estimating

32. The 20-80 Rule
Be able to manage your resources

33. Task Assignment
Accepted Responsibility

34. Meetings
200 € / (person-hour)

35. Engineering

36. Tools
Bigger doesn’t mean Better

37. IDE
Some help is always appreciated

38. Source Code Control
Always have a fallback

39. Clean Code
Commit to Coding Standards

40. Architecture
Clean, Hexagonal, Screaming, Onion, Ring…

41. S Singleton Invasion
T Tight Coupling
U Untestability
P Premature Optimization
I Indescriptive Naming
D Duplication

42. S Single Responsibility
O Open-Closed
L Liskov Substitution
I Interface Segregation
D Dependency Inversion

43. Refactoring
Eliminate Code Smells and Design Mistakes

44. Test-Driven Development
Making sure it works? NO

45. Test-Driven Development
Finding bugs? Well…

46. Test-Driven Development
Guiding the Design!

47. Pair Programming
Collective Ownership

48. Continuous Integration
Release quickly

49. Further
Reading

50. About Professionalism
The Clean Coder: 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
Extreme Programming 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 by Martin Fowler (video)
The Clean Architecture by Robert C. Martin (video)

53. About Design and Development
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
Integrated Tests 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. About Practicing
www.codingdojo.org
code.google.com/codejam
www.exercism.io

56. Thanks!
Questions?
{tomas, carlos}@everywaretech.es
/everywaretech @everywaretech