With one of my colleagues, we’ve been working a lot to create and foster a culture of learning, an environment where constant self-improvement and knowledge sharing is highly valued. Let’s say that we are part-time developer advocates. We’ve achieved some of our goals, but there is still a long way ahead of us. The “us” applies both to the developers and the management.
Code Ahead, what shall I call you? You are a novel. A fiction. Yet according to you, you’re semi-autobiographical. You are a rather exact picture of how things go in software development. Yet you’re also a manifesto of how things should go instead. You give lots of pieces of advice on “programming, debugging, releasing, testing, organizing, teamwork and management issues”.
It’s so easy to tell anyone that he shouldn’t care about this and that. He shouldn’t complain what the other does, shouldn’t care about the inhibitory conditions. But do you do your own job when you are doing this?
Have you, Sandor, really read that book? - you might ask if you know me or you simply know what path I’m following. A hint: the technical path. Yet, my answer would be, of course, I had and it was great!
What it is about?
I’ve already written quite a few articles about features introduced by C++ 11 and how much it changed how I look at the language. The feature I liked the most is probably the one of lambda expressions. I don’t like them for their sheer existence, it’s not l’art pour l’art, but it really helps using the different STL algorithms. If you want to get a quick introduction to all the 105, have a look at this video by the owner of fluentcpp.com.
After I attended a training on the subject of optimizing C++, I felt I’d be interested in going a bit deeper. At least to read a bit more about this topic. So I asked the trainer for some books he’d recommend about optimization. One was Kurt Guntheroth’s Optimized C++. As soon as I finished reading Essential Skills for the Agile Developer, I started to read this one.
I’ve worked in a couple of different scrum teams, one I even served as a scrum master. There was one common point among all these teams, the scrum master was always or at least used to be a software developer. Then I joined my latest scrum team last summer where our scrum master is a product analyst.