Why Open Source?

As members of the open source community, we have internalized the benefits of open source. Sometimes, knowing a topic so well can hinder us from explaining it to people who need to understand our work: Clients, customers, and employers. They need to understand us because they pay us. Understanding helps to build trust.

The topic What is Open Source is covered in earlier post by that title. This presentation covers some of the “whys” of open source in terms that matter to the people we serve: Clients, customers, and employers.

Flourish Open Source Conference at UIC

Flourish is an open source conference to be held at the University of Illinois at Chicago on Saturday, April 5, 2014. The conference is run by university students and tickets are free.

Why go to Flourish? Because…

How .gitignore Works

Earlier today I ran into a Git issue within a RubyMotion project. I added a directory to the project’s .gitignore file, but Git seemed to ignore my ignore. Expressed more clearly, Git continued to track a directory that I explicitly told it to ignore.

What?

Either there was a bug in Git, or my understanding of .gitignore was incomplete. It was time for me to dig in and learn more about .gitignore.

CocoaConf Chicago Recap

One purpose of a conference is to help you to spot trends while there’s still time to reap the benefits of being an early adopter.  
~Brian Marick at SCNA 2013

Early adopters on Apple’s Mac OS X and iOS platforms flock to CocoaConf, a multi-city conference for developers. Tickets are slightly easier to get than WWDC; CocoaConf consistently sells out.

CocoaConf’s presenters are practicing developers, actively building real software every day. They come to CocoaConf to share their experiences in a wonderful upward-spiral of technical learning. Here are a few highlights from the latest CocoaConf, held March 7-8 near Chicago.

Fixing MacVim on OS X Mavericks

Experience told me to delay upgrading to OS X Mavericks for as long as possible because the upgrade would likely break my dev environment. Sure enough, the upgrade broke MacVim.

~$ which mvim

~$ 

The ‘nix which command returned a null response when asked about MacVim. Not cool, Mavericks!