The document outlines an upcoming professional development event over 3 days that will cover various development topics including clean code, SOLID principles, testing, architecture, and infrastructure. The talks will be given by developers from ulabox, a 6 year old PHP and Javascript startup. Additionally, the document provides advice for transitioning from student to professional developer such as taking responsibility for code, learning constantly, and automating processes. It emphasizes the importance of quality, working as a team using agile practices, and finding solutions rather than excuses.

1. Professional development
University -> Business

2. ● Developers at ulabox
● 6-years-old startup
● 12 developers
● old code and new services
○ PHP + Javascript
○ Solr, MySQL, PostgreSQL, Redis, ELK, RabbitMQ...
● We are hiring and also offering internships too!
Professional development
About us

3. ● Professional development: university meets business
○ by Julio Martínez
● Source code version control with git
○ by Juanma Orta
● Continuous integration & continuous delivery
○ by Rubén Sospedra
(50min talks)
Professional development
Schedule: 1st day

4. ● Clean code
○ by Julio Martínez
● SOLID principles
○ by Julio Martínez
● Testing Driven Development
○ by Manel Sellés
Professional development
Schedule: 2nd day

5. ● Hexagonal architecture
○ by Manel Sellés
● Infrastructure with Docker
○ by Julio Martínez
● Final words and questions
○ by Julio Martínez and Manel Sellés
Professional development
Schedule: 3rd day

6. ● Could you tell me differences between them?
● Do they program in a different way?
● Which one is more responsible?
● Which one is prouder of his code?
Professional development
From student to professional developer

7. ● It’s a difficult job!
● Take responsibility
○ Be proud of your code, sign it
○ Do not program by coincidence
● Need to learn everyday, eager to
○ Fast adapter
○ Books, videos, seminars, meetups, conferences
Professional development
Looking for professionalism

8. ● It’s all about trade-offs
○ Look for good enough software
○ Old code to maintain vs. new code
● However, try to be professional
○ Boy-scout rule
○ Make quality a requirement
○ Try to exceed user’s expectations
Professional development
Professionalism in a business world

9. ● Provide solutions
○ Make it easy for your boss
● No excuses, but options
○ Explain trade-offs
● Think about your users
● Work as a team
Professional development
Your role in the company

10. ● Code quality and care
○ Code versioning
○ Code paradigms’ alignment
○ Testing
● Automate everything
○ Continuous integration (& delivery)
○ “A developer should be replaceable”
Professional development
Development as a team

11. ● Short time increments
○ Kanban, sprints
● Code quality
○ Code reviews, pair programming
● Every single developer is doing his/her best!
○ Everybody learns from others
Professional development
Agile software development

12. ● Books:
○ The Pragmatic Programmer (Hunt & Thomas)
○ The Software Craftsman (Mancuso)
● Meetings/seminars/conferences:
○ Meetup.com: Software Craftsmanship
● Internet (but be critic):
○ A good source: Codely.tv
Professional development
References