The first day of #devcamp17 was packed with lot of great talks, here comes the second day.
Table of Contents
Optimizing PhpStorm IDE
The most valuable session so far. Christopher of Mayflower showed us how he optimized his PhpStorm IDE. After working almost two years with PyCharm (which is based on the same core like all other Jetbrains IDEs) I figured out almost a dozen of tricks which will definitely increase my productivity!
You can read the full session as a blog post here:
Fighting fear driven development
Perhaps You have already worked in company where fear is the leading factor for everything. Did You encounter one or more of the following symptoms?
- Unrealistic Deadlines
- Debris Code
- Non-existent error culture
- Suboptimal knowledge
- Fear of job loss
- Fear of bankruptcy
- Blaming and finger pointing
How can we fight such a culture?
- We have to see failures as systematic or at least team failures not individual ones.
- Problems should be documented
- Favor small changes
- Be a role model
- Be open for questions
- Create psychological safety in your team
But sometimes it is fight not flight, then you need an exit strategy.
Great things happen when you leave your comfort zone. I’ve never done a coding dojo before left alone a pair programming session. The idea of this dojo is simple: take a project which you want to refactor, team up as a pair with driver and navigator and do a time boxed refactoring session.
From school to professional Developer
An interesting talk about the difference between education and work life. Everyone agreed that companies have to rethink their hiring process because degrees are no guarantee for coding skills while lateral entrants who lack the formal qualification can indeed be good software craftsman. Another trend in education seems to be problem based learning.
MVP – minimum releasable crap?
A good walkthrough of the dos and don’ts of an MVP – a minmum viable product. The Session was heavily influenced by Erik Kniberg’s blog article “Making sense of MVP (Minimum Viable Product) – and why I prefer Earliest Testable/Usable/Lovable”
Main takeaway: better call it “earliest testable release” 🙂
Bug handling across several teams
A little knowledge exchange how the participant’s companies handle bug tracking and issue management in general. I was very happy that my company e.solutions GmbH has a quite nice approach where almost everyone os allowed to give feedback of our products. Leave no bug behind(TM) 🙂
As I already said: I had a blast! The organisation was perfect, the location fitted the purpose / the idea of a barcamp very well. Coffee was great, food was delicious. Big thanks to the folks from Mayflower! I hope there will be a #devcamp18.