The sump pumps in my french drain
Of my existence are the bane,
The cause of too much pain,
But only when it rains.
It’s time for John Szeder‘s year-in-review Christmas poem!
‘Twas the night before christmas, and before it all ended,
Half of the internet found itself unfriended.
We are still waiting for the year of VR.
It’s stuck in traffic, in a self-driving car.
Blogging is out–all that writing is tedium,
Unless, of course, it was posted on medium.
Or else it was twittered, or if you like, tweeted:
140 characters, invariably deleted.
The buyers keep buying; the sellers keep selling.
Amazon has less of us leaving our dwelling.
People are talking about new services and toys.
The signal is indistinguishable from all of the noise.
So what could all of this possibly mean?
What is the statement for 2016?
What is this “The Year Of”, What is new? What is trending?
What thing do we humblebrag in tones condescending?
Is IoT enabling your elf on the shelf?
Did you run all the numbers on your quantifiable self?
Can you control your video games with a gesture or thought?
Are your interactions meaningful with your conversational bot?
I watch it all crawling forward, I sigh and I shrug.
2016 is The Year Of We All Need A Hug.
So go wrap some arms around whoever is near,
And have a merry Christmas and happy New Year!
— John Szeder 2016
Long, long ago, I wrote a book about PHP. Actually, it was the first book about PHP. And it was a success. It lead to two more editions and another book about MySQL. Zeev, Andi and Monte each graciously helped with reviews, writing and endorsements. Being a best-selling author of the first PHP book has been great for landing gigs. Facing a range of criticism, especially in Amazon reviews, was a valuable learning experience.
Having last published a book in 2003, you might guess that sales have dropped off. The royalty checks are small. Even though the effort to write the books was immense, the rewards more than made up for it, especially for the first edition Core PHP. Despite diminishing returns, I might have continued the pattern of writing a new edition for each major version of PHP, but better books came out and PHP 6 never did.
As a perspective-setter, I offer all-time sales totals for the four books I wrote.
Last September, ZeroTurnaround released analysis of a survey focussed on tools and practices of developers. They reported on how these affected the quality of code and how predictable delivery dates were. The Developer Productivity Report 2013 is a long read with lots of details. In the end, the data support what most developers already know. If you’re a programmer like me, does any of this surprise you?
I accept all of this with the except that I have not found IDEs to be a significant improvement to my productivity. Sometimes I wonder if exposing all the prototypes through popups doesn’t prevent developers from mastering a system and internalizing it. On the other hand, having memorized all the random parameters to PHP’s function might have been a waste of brain space. I’ll probably be fine for now with Geany and grep.
There’s a remarkable nugget about testing (slide 7):
Automated tests showed the largest overall improvements both in the predictability and quality of software deliveries. Quality goes up most when Developers are testing the code (also discussed in Sven Peter’s talk “How to do Kickass Software Development” at GeekOut 2013), which means that you shouldn’t just leave testing to QA team, but bake it into the development process as well. The rest of the measurements were more or less insignificant, although we don’t recommend letting yourcustomers/users test your software for you.
If you can convince your developers to do testing, there’s a big advantage for quality.
Seems like you’d need to be drunk or young or both to play this, but it does illustrate a game mechanic I like. That is the hidden wager mechanic. In games played around a table, it keeps everyone engaged and prevents those lulls where one player is deep in thought while the other players might get bored.
Earlier this evening, @danfuzz told me that some of his friends were playing a game called “Tweet or Twenty” in which everyone around a table selects a Cards Against Humanity white card and either must post the content to their Twitter account or pay $20 into a pot. The idea is that if the card is too embarrassing, you’d rather pay than have to post it.
I thought this was a fun idea until I realized that since (a) the posts all contained “#TweetOrTwenty”, and (b) a more-or-less complete list of Cards Against Humanity cards is readily available, embarrassment is limited because it’s easy to tell when someone is playing and therefore when their post is not to be taken at face value. So I started thinking of ways to remove this limitation.