- Culture
- Design
- General
- Marketing
- Networking/Systems
- Open Source
- phpSprockets
- Productivity
- Security
- Software
- April 2011
- November 2010
- August 2010
- March 2010
- February 2010
- December 2009
- September 2009
- July 2009
- June 2009
- April 2009
- March 2009
- January 2009
- December 2008
- November 2008
- October 2008
- September 2008
- August 2008
- July 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- January 2008
- December 2007
- November 2007
- October 2007
- September 2007
- August 2007
- July 2007
- June 2007
- May 2007
- April 2007
- March 2007
- Coding Horror
- Innova @ Flickr
- Joel on Software
- Lifehacker
- phpSprockets on Google Code
- Smashing Magazine
General The Innova Team
We took pictures right before the annual holiday feast.
Chip, Eddie, Keith, Reva, Matt, Dan, Jon, Michelle, Scott, Amanda, Bruce, Mary, Kent, Brian, Robert, Chris. Chad, who holds court at the Oregon branch office not pictured.
Productivity Flickr and Versioning
We often maintain and deploy projects as a single HEAD version in a Subversion repository. We don’t, generally, tend to do a lot of forking. This is good, as forking can be undisciplined, but sometimes you might want to be able to add or change features and not have to worry about adding broken code to a project.
It turns out that Flickr does the same sort of thing. Their solution: flags and flippers. Interesting read.
General Visualizing CSS
Converting a Photoshop pitch to a static HTML/CSS layout is a fundamental part of client-oriented web development. It can be hard work, not least because it is difficult to simultaneously focus on the appearance of the site and its structural foundations.
The usual solution to this is to muddle through and keep tweaking a steadily expanding morass of CSS until the site resembles the original .psd. This way of working is unstructured, which makes it stressful and self-limiting.
Let’s look at a better way.
General More great opportunities at CoverMyMeds
CoverMyMeds is looking for entry level account managers.
Open Source, Software GitHub Saves The Day
In the dark times (a few years ago) if Innova decided to make use of a third-party library that had bugs, we essentially had three options:
- App-specific workarounds: sometimes feasible, sometimes not
- Local modifications: wherein we dork around with the library code on our end, fix the bugs, and then maintain our own separate branch of the library. These made merging in new changes from upstream fun (in that why was I programmed to feel pain kind of way).
- Find/Write a replacement: You’d be shocked at how often we didn’t do this. Or, alternatively, underestimated how difficult a particular issue is.
In the last few weeks alone, GitHub’s changed that. Now, the libraries I want are on GitHub as rubygems or PHP tarballs or what have you. And when we encounter issues, the process is smooth:
- Fork project. GitHub has a button for this.
- Get our fork, make local changes, commit and push up to GitHub.
- Send a “pull request” to the original author to let them know we have patches that they may want. GitHub has a button for this.
My contributions are available for whoever wants them.
Now, if the original project checks in a few bugfixes I want, I can cleanly merge them in and keep my local fixes. And if upstream wants my fixes for the “canonical” repository for a project, then they’re welcome to them whenever they like. Git makes the magic happen, and GitHub makes the magic ridiculously easy.
How the hell did we develop software before this?