I don’t like to blog about blogging, but there’s an opinion regularly put forth by fortysomething developers that gets me worked up. The gist runs as follows: the writer no longer likes being a software developer and based on their own anecdotal evidence wonders why so many other similarly disillusioned old hands flock to management positions. Disappointed that real progress in the art of programming is stagnant, they complain that people – not them! – keep making the same stupid mistakes. As if history doesn’t repeat itself everywhere all the time.Continue reading “You’re no rockstar, but you have more Yoda appeal than you think”
There is a consistent thread in my career, other than not having been fired from a project since 2001. It is the repeated failure to carry an Open-Source project that deserves to be called more than an amateur attempt. I throw in the towel. I’m not going to breathe new life into my Hibernate-killing polyglot ORM framework for the JVM. And if I do, I won’t share it with the world. I have given up and given in, and I know exactly why it happened – or rather didn’t happen.
We’ve all heard and probably repeat the claim that any serious developer should boast an impressive portfolio of Open-Source work. I’m not talking about being a core contributor to the likes of Spring or the Apache foundation. If that were a prerequisite to landing a job, I think few of us would work at all. I mean the thousands of one-man-band projects out there on github in varying stages of abandonment. Merely showing your job is also your hobby doesn’t make you special.Continue reading “Don’t share your hobby projects for the wrong reasons”
In some of my recent posts on Agile I voiced my excitement and support for the Agile 2 movement. Indeed, after many years in software a breath of fresh air can still get me motivated. Agile 2 has given a renewed incentive to everyone’s favorite waste of time: quarreling in comment threads about the True interpretation of the Agile Path. “Folks, can we please stop going around in circles. Agile is perfectly straightforward if you do it our way. Just come back from the Dark Side and get certified with us”.
Forgive my tongue in cheek. Disagreement is not a waste of time. It’s the foundation of any democratic process. Software projects are still being scrapped midway or delivered with huge overruns, and Agile has notbrought us the magic bullet. Have you not been involved in those projects, or been partly responsible? We still haven’t found what we’re looking for, as Bono sang. Every proposal to improve out methods, from modest to maverick, deserves to be heard.Continue reading “Agile is never a recipe for creativity”
In a previous post I wrote about the uncompromising artistry of Stanley Kubrick, who produced film classics at the cost of wildly unpredictable schedules and budgets. You can reach for similar brilliance in programming, but you had better do it on your own time or with a generous CFO. There is a different, more workable, and healthier attitude towards our craft. Just keep at it, enjoy it, and don’t worry about making a dent in the universe. Reading Woody Allen’s autobiography over the holidays, indulge me to draw another cinematic parallel with this veteran New York writer/director. Don’t worry, it will also be about coding.
Woody Allen (1935) is one of the most consistently prolific cinematographers in the business. He has written and directed over fifty films over an equal number of years, almost like clockwork and at 85 shows no intention of stopping. He doesn’t approach his oeuvre as a project with a culmination. His business is about keeping busy. He is in it for the long run, if only to act as an antidote to the unavoidable spectre of death and oblivion. But let’s not get into his glum outlook on life here.Continue reading “The Woody Allen way of coding”
Today I want to talk about the widespread Scrum practice of demoing new user-facing features to key stakeholders after every Sprint. I consider it a dubious practice because it can prevent and degrade a culture of quality. Neither the Scrum guide nor common sense demands that you should strive to hold such a demo at regular intervals. The Agile 2 movement understands that turning teams into feature factories kills quiet reflection, adaptation and true agility.
There’s a lot that people think the Scrum guide dictates which is in fact not in it. There are no story points, no poker planning sessions, and no Fibonacci ranges. Like religions accrue articles of faith that are in no holy book, so Scrum has given rise to received practices based on wrong assumptions. One belief is that you must hold a demo at the end of the Sprint. There is no such mandatory demo. There is a review, during which you inspect the outcome of the Sprint and determine future adaptations. [..] The Sprint Review is a working session and the Scrum Team should avoid limiting it to a presentation. There you have it, straight from the horse’s mouth.Continue reading “How Mandatory Demos Can Degrade Quality Culture”