Over the past decade, the headline of this entry, first published in October 2004, seemed less and less outlandish. By March 2014, Larry Page had made that a very explicit goal, echoing Bill Gates’ earlier promise of a computer on every desk and in every home. Here is how the idea that Google would get into the internet access business – as a fundamental enabler to bigger things, not in a Comcast incumbentish (hereby a word) way – turned into reality over the years: Read More
It seems everything is now being turned into an off-the-cloud service, and as a case in point StatusPage.io launched in 2013 to let companies outsource their availability dashboards. They already have lined up a nice customer roster, with a monthly runrate now above $30K. It is rewarding to see best practices becoming so obvious and prevalent that they turn into products in their own right, though it often takes a bit longer than you might first expect for things to bloom to full maturity.
This entry started with a 2004 post, and spans more than a decade since I started advocating for API and web service providers to provide transparency into their operations. Check out how things propagated, starting with the latest developments:
The explosion in the quantity and quality of both commercial APIs and open source projects is a huge enabler for digital start-ups and small businesses. Instead of painfully rolling your own version of, say, sending email newsletters or displaying a media gallery, in many cases “there’s an app for that.” However, behind the numbers, the very uneven quality of the documentation made available with said APIs, plugins, and packages, is a serious impediment to fully realizing the productivity gains promised by these vibrant ecosystems. (Wow this sounds way too much like an enterprise software whitepaper!)
Typically documentation takes shortcuts by implying bits of knowledge that the reader may not have, skipping necessary steps, leaving out important nuances, or providing incomplete and obtuse examples. These issues are compounded because of today’s development by integration more than pure coding. I’ve been thinking about how this could be alleviated. Read More
Like many people developing with WordPress, I used to use XAMPP to run a Linux/Apache/MySQL stack under Windows. This beats developing directly off a remote server by a long stretch (in case anybody still does that), but it turns out to be quite a hassle as you wrestle with / vs \ in paths and other discrepancies between the Unix and Windows worlds. Developing in an environment as close to production as possible ends up being a much better choice. Popular free tools to do so are:
- VirtualBox to run other operating systems within your own
- Vagrant to manage development environments within VirtualBox
- Puphpet, a wizard-like interface to help set up Vagrant through Puppet automation scripts. Phansible does the same but using Ansible.
Yes, these work somewhat like Russian dolls, as modern web development has a severe case of tools to set up tools to set up tools. It can get a little crazy at times, so you want to find the sweet spot where you gain efficiency without becoming a slave to your toolset (which is supposed to save you time in the first place). Getting this up and running is a big enabler for continuous integration, and why you would want to think and develop that way is the topic of a separate entry.
In this post I’ll share some practical details to contribute a little back to the open source community and not just consume its benefits passively. The end result is a fully functional Unix environment serving a WordPress website locally on a Windows PC, across a whole local network.
This entry is written from the perspective of “Unix as a foreign language” from a Windows native. It does assume that you have read the basics about VirtualBox and Vagrant, and focuses on common roadblocks that I’ve encountered along the way. As always, the key to learning a whole new way of doing things is to break it down in small digestible chunks. Read More
I’ve put together lists of teams and people working at the intersection of news publishing, data, visualization, and online/mobile/software development to get a better sense of who talks the talk and who walks the walk. There’s a strong UK presence, while some organizations are missing that you’d expect might want to show up.
This would deserve some analysis (anyone up to datamine Open Source Report Card?), maybe later.
1. Github repositories from news orgs Read More