Hello, I'm Sergej Brazdeikis and I write about engineering management and web technology.
When switched from an engineer to a more managerial role, I had to think on a team level. The very definition of success changed - now it is team success. System thinking on the team level is a daily exercise.
One mistake I'm doing over and over again as the manager is - Me as, Engineering manager, need to spend at least 50% on the effort within the engineering managers team, not my team I'm the manager in.
Many engineering teams are doing the dailies. Often, the teams are doing it only because it is the best practice in the industry. We also all been there on questioning this daily meeting. What values does it bring? Why do not need it?
Recently I started reading my first book about writing. Currently, I've read eight chapters. And omg. I'm not sure if I get so much value because it is an excellent book or it is my first book about writing.
Java 8 language capabilities. The notes
Sharing the learnings after attending Coderetreat event for the first time
Java library list you can't miss in 2017
Assessment whether Kubernetes is fully usable on AWS
Personal notes about the book Browser Networking by Ilja Grigorik
Guide to setup static website on AWS S3 under 10 minutes
How to write tests for docker images
Cost analysis when scaling. Recommendations for cost optimizations