Procurios, The Netherlands
Pim Elshoff works as a Developer at Procurios. He has over 10 years of experience as a developer with over 5 years in Agile and Scrum. Technology will always be a passion of him, but with more experience his main focus has shifted to people.
— TOPIC #1 —
You might have heard of Domain Driven Design. You may have heard DDD is a tool to write readable and change-ready code. You may have even heard DDD comes with a lot of talking, and modelling, and customers…
Starting with DDD sounds big, and scary, doesn’t it?
But getting started is not scary! Come find out what DDD can do for your code, tomorrow. We’ll use value objects, entities and services to bring order to our mind and code. We’ll see how naming things can guide us, but also trick us. We’ll rework a piece of code together and improve what it means. And tomorrow you can tell your peers that, technically, you’re doing DDD.
— TOPIC #2 —
From Conversation to Software
We all have coworkers, managers and customers demanding work from us. Feature here, bugfix there, just do what you’re told. But don’t you want to build stuff that matters? Are you not the expert here? What if Pim told you there is another way? You are *the* person to take the outcome of the project seriously. So help people solve their problems and grasp their opportunities!
In this soft skill talk, we’ll take a look at how you can do just that. We will write user stories that help you understand their problems. We will use story mapping to create meaningful and insightful choices for your clients. Finally we’ll use release planning to predict and plan, together, where the project will end up.
Join the talk and find out how you can turn conversation into software.
— WORKSHOP —
(Di|Con)vergent Mob Refactoring
Programmers come in all kinds and sizes. But we’ve found that there is one major distinction that keeps us from working together: attitude. Optimistic programmers tend to come up with solutions quickly, while not always respecting the problem. Pessimistic programmers tend to come up with questions quickly, while not always respecting simpler solutions.
Working together can be difficult. But by explicitly diverging and converging we can find respect for each other and what we have to bring to the table. By working together we find better solutions than we could working alone. We will group up in teams of four or five, in so called mobs, and work on a case study in pomodoro’s. We will first diverge, to give the optimists their moment in the spotlight, where they can create tempo and get some things done. Then we will converge and give the pessimists the power, where they can refine and get things done well. If you’re not sure what your attitude is, then we will help you discover it.
We will be helping MeetInc. Their current implementation of what a meetup is, is sorely lacking. And the business has come with new rules. We will use this opportunity to make the code reflect the domain of meetups better. Your exact mission, should you choose to accept it, will be presented to you on GitHub shortly. And fear not, you are not alone. Your team is there with you, as are the business experts, who can answers all of your questions.
* Refactoring anemic models to useful domain concepts
* Divergence and convergence