Glue Languages

Glue languages are used everywhere. While you may identify as a Python, Java, Haskell or C/C++ developer, we all eventually end up congregating in some common spaces. On the web side of things of all these languages is JavaScript. On the server, this means shell/bash. These are our glue languages: languages that bring our ever so divided programming communities together.

JavaScript, shell scripting, SQL, and other glue languages like them are ubiquitous. Grab and Unix based computer and box and dive right in with a shell script. JavaScript, is allowing people to push the envelope both on the client as well as the server. No matter what language you primarily develop in, improving your skills in these common-ground scripting languages is one of the best things you can do for yourself.

Read More

OSX is not the only great development platform

Stack Overflow reports that that more developers now use OS X than Linux or Windows as their primary OS, and that trend is slowly increasing as less than fewer developers will be using Windows next year and the year after that.

Personally, I think there is a slew of reasons, including its growth, but a larger part being the migration of developers from Windows to OSX who drink, breath, and live Starbucks for a living and deem themselves to be hipsters. Attracted by the UNIX subsystem under the hood, beautiful aesthetics, and straightforward usability approach, more and more coders, adopted OSX as their primary machine.

This migration wasn’t just for Objective-C coders, the language that OSX was primarily was written in. Languages such as Java, C/C++, Python, Ruby and other communities were slowly implemented into the OSX. Apple in newer builds, installed most of the languages, as default with the OSX and lowered the barriers for the technically inclined to code.

Read More

Staying Productive in a Startup Of Two

Having a team behind your back is pretty nice.

You’ve got one of those software engineers that, well, is probably one of those people who sleeps with a copy of CLRS (The Infamous Algorithms Textbook) under a pillow. Or you can chat with your designer whom can visualize a layout in his head like Picasso visualized and created the Mona Lisa. Or you can ping your favorite pal in QA to help you decipher a bug that you can’t even begin to hunt down. Or, without even being asked, that one odd pedantic generalist on your team will probably be the first to proactively nudge you and volunteer that no, you made a mistake, you were actually thinking about Leonardo Da Vinci making the Mona Lisa, not Picasso.

The TLDR, is teams are nice. But when you’re building a startup, you have to start somewhere. And with half of the successful exits run by solo-founder companies, many of those startups start out pretty lonely.

I’ve been working with one other person for a while on Communote, with a varying amount of success and productivity, in between times of fewer productive stretches. Startups are very hard, small startups are harder, and staying productive in a startup is even harder. Here are a few things I’ve learned as I continue to chunk away at Communote.

Read More

Interviewing Is Hard

Today’s industry is so full of companies and startups who imagine a perfect world where a nervous candidate comes into the interview, answers a few clever coding challenges and then ultimately ends up the award-winning hire that will surely implement the high-class and exclusive algorithm that will bring the company into a new era of probability.

Most startups or winding projects have zero users and are a glimmer of the successful business they might wind up being some day. But we’re still romanticizing the idea that programming riddles will magically be the best benchmark for hiring, even though using a magic algorithm is very rarely the cause for any given startup’s success.

Read More