1. Observe a pattern
2. Establish a correlating rule
3. Make an exception to the rule
4. Pay the price
October, 2013
-
-
I wouldn’t be shocked to see MacBook Pros in “space gray” in the not so distant future.
-
Don’t underestimate the value of your team’s (collective) experience. When new folks come on board you can tell them how you do things and why you do things certain ways. You can share historical anecdotes about the reasons things are done these ways, but there is no way for those new hires to actually have…
-
-
Life lesson from running a digital agency: When asking for help, focus your efforts on defining the problem instead of suggesting a solution. The person you’re asking for help from may have solutions you’ve never considered. If my recent experience is any measure, it works equally well when asking a hotel concierge for help getting…
-
-
I don’t know that I could do this, but I sure admire Wil and Rand for giving it a go.
-
And here I am running RAID 5 like a chump.
-
Apparently things are so bad for the Jacksonville Jaguars that they don’t even have budget to finish painting their helmets. #broncos
-
14 minutes long and fascinating.
-
I learned about Code Club at this year’s Monktoberfest. I love it. Check out their video:
-
The entire republican party has shifted right and thrown people like me over the fantail into their wake. You’re either with us or against us. Conservatives who used to be the serious men in white shirts and buzzcuts, the men who got us to the moon and home safely again, the ones who once taught science and engineering and medicine in the colleges, are now the party of Creationism and Rapture and screw you I got mine.
[…]
My views have not changed. I’m still the same guy you used to know.
-
-
Being everything to everyone is hard. “Decisions, not options” works best for opinionated, specific software; not as well for open platforms. (thanks Matt)
-
Setting them up for the long troll.