Skip to main content

Switching to Mac from Windows: Getting Used to New Tools

I've been a Windows guy since 3.1--a long painful experience, but you get used to the tools and tech of the MSFT world, and it lulls you into thinking in the limits of that paradigm.

Over the summer I made the switch after repeated config issues with Rails gems on Windows vs Mac. My team is on Mac, so I was the outlier.

I got a Macbook Air--the new version with Lion OS--because I plan to travel a ton and I wanted the latest and greatest. I got the 11" screen so I could work on a plane in the cheap seats without worrying too much about the guy in front of me leaning back.

I'm not what you would call a professional developer--I am not. I can teach myself anything, but I'm slower than the average bear, and it's better to have smarter people than I working on my projects.

Last year we chose Rails instead of--wait for it--Classic ASP, which shows you just how adventurous I was at the time. Rails scales nicely, especially on the Heroku platform.

I use Sublime as a text editor, simply on a recommendation, but I'm going to try something else, hopefully with code completion.

Ryan pushed me onto Ubuntu running on Oracle's vBox virtual machine, so we have a consistent environment, because...hh, right: there was that config issue with a Ruby gem on Lion OS. The compatibility issues weren't fixed because the team is on OSX 10.6. That's why we went to the VM.

Since then I've had to learn a few things (gasp) like command line stuff (gasp gasp...feels like DOS). After logging into the VM, I need to be able to execute commands that inherently write to the file system outside the VM, so you have to use "sudo". Sudo is basically a proxy that acts on behalf of the VM to execute commands outside the sandbox.

So instead of git pull origin master, if you're in the VM you have to write sudo git pull origin master. Doing it without sudo throws a permissions error.

So what's git? For the non-programmer it's gittin' too technical. Git's basically a utility for accessing and modifying the contents of a shared code repository. We use as our repository, and it's fantastic--one of the best dev startups, it seems.

Next there's Ruby on Rails. I'm not a Rails programmer and don't aspire to be. I'd prefer working in Javascript from server to browser: up and down the stack JS. With node.js--an all JS http server--you can do that. Node, Express for MVC (model, view, control) framework, MongoDB (JSON document db), PhoneGap for mobile (just learning about PhoneGap) using HTML5 and JS, jQuery for lots of handy stuff, etc.

But we're in Rails. So I have to know a bit of it. Ruby is really quite elegant and doesn't require quite the syntax of other languages.

Rails as a framework is cool because of the amazing number of free objects out there (ruby gems) that install instantly from their remote locations--a very, very nice feature of rails.

I tend to forget the next one: rake sunspot:solr:start. We use Solr as our interface to the Lucene indexing server, which indexes everything we store to make it highly searchable. Fun stuff that we haven't dug into enough yet, but I'm looking forward to the time when it's possible.

For the db, Rails uses SQLite, and I use SQlite Manager to inspect the db and perform test queries.

Post-funding I doubt I'll be coding much; some may argue I shouldn't be coding at all. But there's nothing like really getting in there and learning along the way. What we're doing isn't terribly complex yet; once we've nailed down the concept and made choices about how to deliver it.

I find it incredibly refreshing and fun. But I think I'd have more fun if I really, really new Rails, or had 3 or 4 Rails developers working with me in the same room. It's time to expand the toolset a bit--time to add some cash to it and get moving.


Popular posts from this blog

Beta Signup

I've been working for quite a while on a new search concept, though the further in I get, the closer the rest of the world gets to what we're doing. So today I'm inviting you to sign up for the rather modest beta, which will be ready soon if we can nail down a few difficult  details. Jawaya is a way of navigating the web and getting better results. And that's as much as I can say right now, because we're not a funded startup, and things are moving really fast in this space--it's going to be very competitive. I predict there will be about 10 funded startups in the next 6 months doing something similar. One of them will be mine, and we aim to make it the best. We're raising a round of capital to fund the team, and are shooting for early sustainability. This is my fifth company; my fourth in the tech space, and my third software company. I think it will be the biggest and can possibly have a positive impact on the world by reducing the amount of time it takes

Where Innovation Happens

As I get closer to a go/no-go decision on a project, I've been thinking about the difference about my vision for the project and the supportive innovations to enable the core innovations The vision combines (in unequal parts) product, core innovation as I imagine it, the application of that core innovation, design, marketing,  developer ecosystem, and business development. The core innovation enables everything else, but it's the application of the innovation that makes it meaningful, useful, and in this case, fun. This week we're testing initial approaches to the implementation for our specific application, and that's where we'll develop the enabling innovations, which is basically where the rubber meets the road. The difference is that the enabling innovation happens at the source of real problems only encountered in the making of something, and in a project like this just getting the essence of it right isn't enough; it also has to be safe, the compone

The Real Jobs Problem

It's the economy, stupid.  Well, yes, it always has been, if you're in the distortion field of politics.  But whose economy? The pundits, the White House, the Republican candidates all miss the mark. They keep talking about debt, taxes, and monetary policy. None of those things tell the real story behind today's economy.  The Old Economy Keynes was right--in the old economy. Economy gets weak, pump some money into the economy through public works projects, which  1) puts people to work, which  2) boosts the economy and  3) generates new tax revenue, while  4) leaving us with another generation of reliable infrastructure to support  5) more growth (for growth's sake, which is another post).  The Beach Ball Imagine a beach ball, partially deflated to represent a recession. Got it? Now imagine the govt pumping that beach ball back up through sensible public investment (which we haven't seen for decades). The New Economy Same beach ball, same pum