The Principal Developer - September 2019






Eduards Sizovs

October 2 · Issue #10 · View online

I write about programming, leadership, mentoring, and hiring.

Hi, there!
Here is my short September update:
πŸŽ“ September was a training season, where I ran lots of public and on-premises training classes – Effective Java Software Design and The Principal Developer. The most exciting part was visiting Izmir and Ankara in Turkey – the country of contrasts. High-tech business mixed with agriculture, sheeps and wild dogs is interesting. On my way to the training, followed by a pack of hungry wild dogs, my eyes were searching for escape – doors, cars, long trees. Certain level of stress helps the training, they say:

Eduards – the free lunch.
Eduards – the free lunch.
Books that I finished reading:
πŸ“š Grammar Girl’s Quick and Dirty Tips for Better Writing – a book full of tips and tricks how to improve your writing skills. I believe that learning how to write is a good time investment. It’s a portable skill that will always be with you. Writing is everywhere – blogging, emailing, chatting, marketing, documentation, coding. If you unsure about your writing skills, this book can boost your confidence, because there is no one right way.
πŸ“š Practical Object-Oriented Design: An Agile Primer Using Ruby – it’s a book about object-oriented programming. I read this book because I organize Java courses, where I teach DDD and OO design. Sometimes I use metaphors that Sandi Metz uses for explaining OO. This book is OK, but Sandi has a better book – 99 Bottles of OOP.
πŸ“š Implementation Patterns – I enjoy reading all of Kent Beck’s books. Kent is a remarkable developer and following his thoughts on software design is both enjoyable and rewarding.Β  Although this book is not groundbreaking, it contains some solid patterns, especially useful if you are writing Java code. If you’re looking for patterns, probably you’ll find this book boring. The biggest value of this book is not in the offered patterns. The value is in understanding what’s in Kent’s head, how Kent is reasoning about code, coding, and design compromises.
πŸ“š Test-Driven Development by Example – There are only two books you need to read to fall in love with TDD – this book and Growing Object-Oriented Software Guided by Tests. Whereas GOOS is more practical and showing how to test-drive real applications, Kent’s book makes you – the reader – feel the rhythm of TDD. It’s like pairing together with Kent. The book also covers non-technical aspects of TDD, such as developer’s happiness and productivity.
πŸ“š Do Not Harm – a memoire of a neurosurgeon Henri Marsh, where he discloses his struggles and thoughts about life and death. Really good book full of interesting stories.
Article that I recommend:
Some of my tweets:
Eduards Sizovs πŸ‘¨πŸ»β€πŸ’»
I often ask senior developers if they mentor colleagues, and only a few hands go up. But when I ask them if their colleagues need to improve, everyone says yes! Everyone is good at finding flaws in others. Be the one who eliminates flaws.
Eduards Sizovs πŸ‘¨πŸ»β€πŸ’»
Sometimes teams stop doing *put some good engineering practice here* because they don't like it, and then later discover that the engineering practice was actually pretty good and their problems had been exposed by the engineering practice, not caused by it.
Eduards Sizovs πŸ‘¨πŸ»β€πŸ’»
Developers need autonomy, mastery, and purpose, not pizzas, hugs, and ping-pong tables.
Eduards Sizovs πŸ‘¨πŸ»β€πŸ’»
To write communicative code, first you need to believe that other people are as important as you.
Eduards Sizovs πŸ‘¨πŸ»β€πŸ’»
The state of IT in 2019:
πŸ’© IT managers rarely have a solid development background.
πŸ’© Developers don't want to become managers and protect the good.
πŸ’© Juniors exponentially outnumber seniors.
πŸ’© Mentoring is rare.
πŸ’© Edu system doesn't teach craftsmanship, XP, best practices.
Eduards Sizovs πŸ‘¨πŸ»β€πŸ’»
"How do I convince my teammates to do X"?

Don't convince. Start doing. People will follow if you do something worth following.
Eduards Sizovs πŸ‘¨πŸ»β€πŸ’»
Every time an experienced developer is working alone on something that no other team member can replicate, he/she gets a little smarter, and the entire team gets dumber. We need more mentors and fewer I'll-do-everything-myself-developers.
Eduards Sizovs πŸ‘¨πŸ»β€πŸ’»
Talent is not a search problem. Talent is available. People just need the right environment to grow.
Eduards Sizovs πŸ‘¨πŸ»β€πŸ’»
Tsundoku(Japanese: 積んθͺ­) is acquiring reading materials but letting them pile up in one's home without reading them.
Eduards Sizovs πŸ‘¨πŸ»β€πŸ’»
The world needs more programmers. What if Parnas was right?

β€” "One bad programmer can easily create two new jobs a year. Hiring bad programmers will just increase our need for them. If we had more good programmers, and could easily identify them, we would need fewer, not more."
Eduards Sizovs πŸ‘¨πŸ»β€πŸ’»
πŸ™‰πŸ’₯ Chaos Engineering for Teams: every week, one randomly-selected person takes the whole day off regardless of their current work. Without informing others.
Thanks for your attention and stay in touch!
P.S. all DevTernity workshop have been sold out. Hurry up, if you want to attend the main day.
Did you enjoy this issue?
In order to unsubscribe, click here.
If you were forwarded this newsletter and you like it, you can subscribe here.
Powered by Revue