O’Reilly presents a cogent synthesis of many issues in the world of technology that keep me up at night. I’d call this essential reading: Tim O’Reilly’s argument against Reid Hoffman’s “Blitzscaling” — Quartz
Support The Right to Repair in New Hampshire (NH HB462)
For years, I have extended the life of the computers and smart phones in my family by upgrading memory and storage and replacing worn out batteries. I have even replaced a broken display or two on my own with a steady hand and a set of instructions prepared by other intrepid home repair enthusiasts. This practice saves us money and helps preserve the environment by extending the life of technology that would otherwise head to a landfill.
It is getting harder and harder for me to do this. I fear that in the near future it will become impossible. Some manufacturers are working very hard to make that future come true.
The people selling everything from electric toothbrushes to computers, printers, cars and trucks have been reaping the rewards of advances in technology for years. As these tools of daily living have become more advanced, the ability for a buyer to visit a local repair shop or fix it themselves when something goes wrong has slowly eroded away. We are rapidly reaching the point at which we no longer own what we buy anymore, but merely rent it from the manufacturer for the “privilege” of using it.
This consolidation of power in the hands of manufacturers is unprecedented. The process is also draining money and skills from states like New Hampshire and funneling it into the hands of a few wealthy corporations who turn around and demand outrageous sums for repair procedures.
Please support the Right to Repair Act for the State of New Hampshire. We cannot rely on California to lead the way on this issue. It would be fitting for the “live free or die” state to be among the first in our nation to preserve our liberty to repair our own technology.
For more information about how to take action, visit The Action Network.
Testing from Sunlit 2.3.2 beta (248)
Digging Deep
Yesterday I dug through the soil of my back yard, tracing the tendrils of poison ivy roots to turn back that pesky plant’s intrusion on our sandbox play area.
Today, I turned back time in my head, distilling my entire career into an NIH biographical sketch.
I am unsure which effort has left me more exhausted.
Open Sorcerer
I crystallize dreams
into a lattice of code;
their energy pulls me forward.
But dreams will not be restrained.
I set them free.
Their potential is confined
only by the imagination of others.
I ❤️ PEP8
Two weeks ago, I attended DjangoCon 2016 in Philadelphia. It was a great conference, and I’ll have more to say about that in a future post, but this post isn’t about DjangoCon.
Ben Lopatin gave a talk called “Working with legacy Django projects.” This post isn’t about that talk, either, though it was an excellent talk.
When he gave the talk, Ben was wearing a t-shirt that had “I ❤️ PEP8” on it. ‘That is a great shirt,’ I thought. ‘I have to have one,’ I continued. As you can see in the photo above, I now have one. It wasn’t really until after it arrived that I gave much thought as to why I liked it so much.
PEP8 is a style guide for writing Python code. We follow PEP8 in the GreeneLab for all of our Python code. I suppose my first impulse to buy the shirt came from being a programming nerd who wanted to proudly fly his freak flag, and nothing could be more obscure and wonky than declaring one’s love for a programming style guide on a t-shirt. That is reason enough to get the shirt, but that wasn’t really it.
If a t-shirt declares your membership on a team, then what is Team PEP8 all about? Programmers repeatedly tackle the challenge of getting the computer to understand what it should do in response to our commands. That is the nature of programming. But we have syntax for that. A style guide puts additional constraints on what you write in your programs. Why make it harder than it already is to get the computer to do the right thing? Because getting computers to follow along is the easy part. The real challenge of programming is writing code that not only gets the computer to jump through the right hoops in the right order, but does so in a clear and uncomplicated way that another programmer can also understand. That is what a style guide is for. Write readable code, make better software. That is why I ❤️ PEP8. Go, team!
Oh, yeah. If you want, you can join the team too. It takes more than a t-shirt, though that might help. It takes more than a style guide, too. You have to work on the craft of writing readable code. Are you up for that challenge?
Hello, world!
Q: Another blog? Does the world really need another blog?
A: A blog is a place for your voice to have a home online. I’ve had a voice on twitter for quite a while, but occasionally I’ve got more to say.
Q: Okay, fine, but why now?
A: It’s all about the donuts.
Q: How long are you going to continue with the fake FAQ?
A: Made-up FAQs are the worst, huh? I’m guessing you want me to write something more interesting.
Q: Yes.
A. That’s not a question. Gotcha!
Q: You call that an answer?
A: Touché.