I'm somewhat conflicted about this talk.
On one hand I found it (positively) thought provoking. It allowed me to consciously add some strategies for dealing with different kinds of people to my tool belt. Sound advice up until here.
On the other hand the three archetypes presented here are too much of a simplification, that is not rectified enough by shortly mentioning this in the beginning when it's the basis of your entire talk.
What I'm missing is the notion that people can actually adapt and evolve if given the proper support / tools. For me - both as a dev and having some experience with leading teams - this is a key aspect of providing solid leadership.
Also you quickly brush over the concept that as a leader you can take several approaches/stances. I would suggest making this more explicit, maybe even explaining the most common stances and when to adopt them as a leader within an IT context.
Comparing with the other feedback provided here, I guess this makes me a dissenter in this specific scenario ;-) I did enjoy the talk and it is clear how much time you spent in preparation, both in research and the visually stunning slides. I hope my feedback helps you improve this even further.
Great talk, worthy of the predicate 'advanced'. I liked how by comparing with real world stuff, you made your examples understandable. In the end it went a little bit over my head; would love the slides to re-read this at some later point in time.
Loved this talk. It's great hearing stories from the trenches, combined with every time what solution was chosen, what the reasoning behind the choices were and why ultimately another solution was chosen.
I think the real lesson is: when apps grow, stuff breaks - and will keep on breaking. What would make the talk even better for me is more emphasis on the first promised point (how to go about designing an application for growth) and staying a bit longer at the main takeaways.
For people who haven't seen this talk and are in dev or devops, would definitely recommend!
Thank you for sharing! I recognised the "Success is not final, failure is not fatal, it is the courage to continue that counts." Winston Churchill quote.
Loved learning of the questions/tools you've used. I don't journal or keep a diary but use (physical) cards and (physical & digital) notes in various places, checkbox/to-do lists, pro/con comparisons, and occasionally calendar notes (I have an app that lets me save any text to a calendar) to remember/remind me of things and help spot patterns.
Lots of useful pointers on interaction and communication skills.
Enjoyed the situations that described the weaknesses of each personality type, as well as the listed strengths (why a "bad" thing can be a good thing).
I've found helping colleagues understand there are different types of communication styles and skill levels (even if I'm not a leader) can improve cohesiveness in a team. And I'm a big believer in "teamwork is dreamwork".
Very insightful and enjoyable talk, really well researched and interesting. I definitely recognised myself and my colleagues in the personality types covered, it was great to hear some advice on how to effectively manage different types of team members.
Interesting talk! Well-prepared, with quite some humor and in-slide-jokes. I agree with Mike that the talk would be even better with a bit more focus on the testing part.
Thanks, great talk. I'm still on the monolith side, and sometimes consider to introduce a microservice. I pretty much agree on everything you say, be very thoughtful about why you would introduce a microservice and make very sure it fixes more problems than it creates new ones.
It was great to have a talk which had a balance between monoliths and microarchitecture. And why monoliths are not something to be ashamed of.