jeremyslade.com

Just watched “Another Go at Language Design” by Rob Pike from Google.  I had not heard of the Go language prior to this, and now I’m very intrigued.  The main points that I find interesting:

• It’s a compiled language for speed, yet flexible Interface mechanism supports a (type-safe) duck-typing style I really miss when doing C/C++/Java
• Goroutines + channels provide concurrency in the language
• It’s designed to be good a system-level programming tasks

Admittedly, I’m not enamored with the syntax.  I’ve grown very fond of the aesthetics of Ruby, and Go seems like a big step backward on first impression.

I’ll add that to stack of things to learn more about.  It may be a good fit for upcoming projects…

BTW — I highly recommend the EE380 Computer Systems Colloquium, a weekly lecture series held at Stanford during the academic year.  It’s been a while since I viewed any of the presentations, and this reminded me of the interesting topics they cover.  I hope to be a regular viewer again.

I’m down to one week left at Intel.  I’m looking forward to the next step in my career / personal development — I’ll be taking a position at IntelePeer starting in May.

This represents a big change in a number of ways.  It’s a small company of ~70 people, in a totally new industry for me (telecom).  I’ll be doing more focused software development than I’ve done for a while at Intel.  And while I will still be in Fort Collins, I’m going to be telecommuting primarily.

There’s plenty I will miss about Intel, but I think it’s time to move on.  I’ve been here (HP / Intel) since getting out of school (12 years), and the longer I stay, the harder it will be to look into other opportunities.  Besides, one of the core Intel values is supposed to be risk taking, right?