« swipe left for tags/categories
swipe right to go back »
Yesterday when we were having Comcast issues in downtown Boulder, I thought about how slow the Internet speed at my office was. For several hours, it was 0 Mbps down and 0 Mbps up (0/0) until I gave up and tethered my iPhone to my computer and used Verizon LTE for the rest of the afternoon.
When I got home, Pandora had trouble starting up on my CenturyLink connection, which Speedtest showed was 2/0.5. So I switched over to my other ISP at home, Skybeam, and got 9.5/2.5. This morning CenturyLink is showing up as 8.5/0.75. Recognize that this is my actual speed, not what I’m paying for and could theoretically get. For example, on Skybeam I’m paying for “up to 15/3.”
At my office, on Comcast, I usually get 75/25. But even that feels slow after hanging out at my Google fiberhouse in Kansas City and getting 800/? (I don’t remember what the upload speed was.)
And yes – as a consumer, I’m spending a ton of money for all of this Internet connectivity.
Fred’s post from yesterday - The Fast Lane, The Slow Lane, and The No Lane - got me thinking. When the SOPA/PIPA issue came to a head, the most effective way to help people understand the potential implications was to blackout the Internet for a day.
What if we did the same by Demoing the Slow Lane for a day. Algorithmically, all sites could slow themselves down dramatically, demonstrating what performance might look like over a 1/1 pipe. Or even a 0.5/0.5 pipe. I’m no server expert, but it looks like Apache has a setting called mod_ratelimit that does bandwidth throttling for client connections. And I’m sure some intrepid readers could quickly come up with elegant solutions to this.
Let the world see “Waiting for”, “Connecting”, and “Buffering” show up in their browser continuously throughout the day. Explain what is going on. Then click a button to bypass the Slow Lane and get normal connectivity.
Instead of everyone getting tangled up in the legal question of what “net neutrality” means, consumers can see what could happen if / when ISPs can decide which companies get to use their fast lanes by paying extra and who is relegated to the slow lane.
I’m totally sick and exhausted with our federal government. Boehner’s statement yesterday on immigration, where he said “We have no intention of ever going to conference on the Senate bill” was the last straw for me. Idiotic and totally broken.
I could rant for a while, but I won’t. Instead, I’ll encourage you to watch this amazing video that Jennifer Bradley just showed at the Startup Phenomenon conference. She totally nails it – people at the top, then metros, then states, and then federal government following their leads.
I just bought Jennifer’s book The Metropolitan Revolution: How Cities and Metros Are Fixing Our Broken Politics and Fragile Economy and plan to read it this weekend.
Now that our federal government is back at work and the short term debt ceiling thing is resolved, it should be no surprise that the news cycle is now obsessed with Obamacare and its flawed implementation. Over the weekend I must have seen a dozen articles about this online and in the NY Times, and then I woke up this morning to a bunch of new things about the Healthcare.gov site underlying tech, how screwed up it is, and what / how the Health and Human Services agency is going to do to fix it.
The punch line – a tech surge.
To ensure that we make swift progress, and that the consumer experience continues to improve, our team has called in additional help to solve some of the more complex technical issues we are encountering.
Our team is bringing in some of the best and brightest from both inside and outside government to scrub in with the team and help improve HealthCare.gov. We’re also putting in place tools and processes to aggressively monitor and identify parts of HealthCare.gov where individuals are encountering errors or having difficulty using the site, so we can prioritize and fix them. We are also defining new test processes to prevent new issues from cropping up as we improve the overall service and deploying fixes to the site during off-peak hours on a regular basis.
From my perspective, this is exactly the wrong thing to do. Many years ago I read Fredrick Brooks iconic book on software engineering – The Mythical Man-Month. One of his key messages is that adding additional software engineers to an already late project will just delay things more. I like to take a different approach – if a project is late, take people off the project, shrink the scope, and ship it faster.
I think rather than a tech surge, we should have a “tech retreat and reset.” There are four easy steps.
- 1. Shut down everything including taking all the existing sites offline.
- 2. Set a new launch date of July 14, 2014.
- 3. Fire all of the contractors.
- 4. Hire Harper Reed as CTO of Healthcare.gov, give him the ball and 100% of the budget, and let him run with it.
If Harper isn’t available, ask him for three names of people he’d put in charge of this. But put one person – a CTO – in charge. And let them hire a team – using all the budget for individual hires, not government contractors or consulting firms.
Hopefully the government owns all the software even though Healthcare.gov apparently violates open source licenses. Given that, the new CTO and his team can quickly triage what is useful and what isn’t. By taking the whole thing offline for nine months, you aren’t in the hell of trying to fix something while it’s completely broken. It’s still a fire drill, but you are no longer inside the building that is burning to the ground.
It’s 2013. We know a lot more about building complex software than we did in 1980. So we should stop using approaches from the 1980s, admit failure when it happens, and hit reset. Doing a “tech surge” will only end in more tears.
The open data movement is great for business, but is also great for us as citizens. To accelerate that program, President Obama and US CTO Todd Park have created a national event to leverage technology and open data to strengthen our democracy in the United States.
On June 1st and 2nd the largest hackathon in the world is forming. Over 5000 people in 87 locations will be joining up to use their talents to make their communities a better place. The National Day of Civic Hacking is the first of a yearly event created by the White House to gather Citizen Engineers and have them use newly accessible government data to improve their communities and our entire society. The multitude of data that is being released as part of the Open Data Initiatives.
A company I’ve been involved for a long time with – Rally Software – is taking a leadership role in this. Rally’s product development team is devoting their talent and energy to participate and host the Boulder, Denver, Seattle, and Raleigh event (join up at these locations.) Through their corporate social responsibility initiative, Rally for Impact they are offering an exclusive and complimentary one-year subscription to AgileZen and Flowdock to all participants of the National Day of Civic Hacking.
Specifically for Coloradans, there are sites in Denver and Boulder. In Denver, the site is focused on open data from the State of Colorado and called Hack4Colorado. In Boulder, the Boulder Civic Hackfest, is focused on local data, the Census Bureau and the National Renewable Energy Lab’s Open Energy Info project. On Saturday, NREL engineers will join the local civic hackers too. Hacking isn’t just about writing code, it’s about exploring the boundaries of what’s doable and what’s desirable.
Rally is also donating three seats to their Enterprise Lean Startup training course to this effort. This highly interactive workshop, on June 5 & 6 in Boulder, teaches you how to systematically discover what’s desirable for users and customers. To claim the training seats be the first three people to send email to firstname.lastname@example.org if you are attending the event in Boulder or Denver. Awards will be given at the closing of each event in Boulder and Denver by Rally staff.
I’m proud of my long time friends at Rally for providing leadership here!