At the beginning of this year Matt Gagne, Adam Jarret, and I finally decided to follow through with our idea to record a podcast together; it’s called Rubber Ducking and we try to record twice a month. We started out by making sure everyone was setup to properly record vocals and did a few riff sessions to determine the overall tone and content. Given that we’re three loudmouths from New England, this was the easy part.
- Just as with my 10 Commandments of Working From Home post, I wrote this as a way to explore my thoughts and hold myself accountable. I don’t know if anything here will resonate with anyone else. I plan to do a retrospective on this post at a later time and evaluate how I’m doing. Those interested but unfamiliar with the concept of the maker’s and manager’s schedule, should checkout Paul Graham’s post on the topic:Maker’s Schedule, Manager’s Schedule
- Pass The Tinfoil I grew up using Apple computers, and even though my chosen career path has thoroughly exposed me to Windows and Linux, my daily driver has always been some form of mac. But for the last several years as their mobile devices have taken over; I’ve become disenchanted. Personally, I don’t much care for the cellphone or tablet form factor and am not a user of iOS. As a result I feel I’m drifting further and further from Apple’s target market.
- There is a dirty little secret waiting to be discovered by anyone with a great idea: Deployment. Regardless of how amazing your functional prototype is it doesn’t amount to anything if it can’t be deployed and successfully scaled. It’s not difficult these days to find some entrepreneurial type who has a great idea and only needs “a programmer to build it for them” (for a flat fee of course) and they’ll take it from there.
- Building web apps is totally awesome, especially when they work great in our multiscreen world. But behind the scenes to all kinds of amazing consistent functionality is a developer banging their head against the wall trying to figure out how to test things across all these different mobile devices locally, because the simulators aren’t always good enough and pushing code for every little tweak and test is ridiculous. That used to be me banging my head against the wall trying to solve this problem.
- I’ve got the power Though technically it’s on loan from the sun. My wife and I used to live in a small cabin on a farm at the edge of the woods a little more than a quarter of a mile from the road. We had a dedicated power line running from the street to the house and lots of trees along the road and driveway. More than once while we were living there, large trees came down and knocked out our power.
- It has been almost two years since I wrote myself 10 commandments for working from home; I think it’s time for a retrospective. #1: Google Voice Number A dedicated work line is something I’m still a very firm believer in. But because the development team I’m a part of is “hyper-communicative” (we’re in a chat all day and frequently working collaboratively on GoTo Meeting or via Google Hangouts) I don’t use the actual “phone” very much.
- Performance At Scale WordPress is an incredible blogging platform and the strategy for deploying WordPress at moderate scale is pretty straightforward: a horizontally scaling web array and a vertically scaling database. The problem is that I (and I imagine the majority of people with industry blogs) don’t need constant scale. A “scaling event” might occur once every few months. I refuse to sacrifice ability to scale for convenience or cost.
- What is Confirmation Bias Confirmation bias is the tendency to favor information that supports one’s views or hypothesis. Every time you’re troubleshooting a problem and think, “I know it can’t be ________” you might be guilty of it. As a web developer I know that feeling all too well. Think about your last debugging experience. Did you solve the problem as quickly as you expected? How familiar with the codebase were you?