ishbits

My effort to becoming a polyglot programmer was to learn different languages for different jobs. For instance, my chosen languages are C, Python, Java, Javascript and more recently Go. I believe that each language is better suited for some jobs than others, and it comprises a full stack as far as languages are concerned.

But I may be working on a device driver in the morning (C) and the prototyping some UI ideas in the afternoon (javascript).

My cheaper VPS option doesn't allow you to spin up servers on demand or offer prorated billing. So while there may be cheaper, DO seems the cheapest for the flexibility it has.

C, custom drivers.

For storage, PostgreSQL and some custom stuff, also playing with Cassandra. If a web interface is required, SpringMVC - it's not cool but works.

Just going through the same thing with my wife and 2 kids. We thought California might be good for a lifestyle change, but I'm not sure of the valley is the place.

My employer has offices in Sunnyvale and Costs Mesa. But I'm finding the real estate a little crazy.

Aaaq

Tornado. But maybe that's because I come from an event driven background.

I sniff packets and write analytic/metric applications on the data, as well as protocol analysis.

Hows the Rackspace web mail interface?

My problem with most frameworks is that they come with an ORM.

I used hstore in an existing database for metrics. It allowed me to add different metrics in the code, rather than having to update the database for new metrics, then a metrics to hstore layer that more or less "streamed" them into the database. I find it quite awesome for that case.

Sometimes there is a need to unstructured data, and if you are already using Postgres, hstore is a great alternative to adding another database backend to your stack.

Tornado when using Python. SpringMVC/Jetty when using Java.

I currently use mbsync to backup my all mail folder on gmail. There is a way to set it to never delete on your local side, turning it more into a backup than a sync.

I run that daily, and Crashplan takes care of the rest. Sure it doesn't save the folder structure and what not, but I'm ok with that.

Many of us did similar in the 90s. I might go this route again but would use Postfix and Dovecot. I'd do this for my wife and kids as well - but if I get hit by a bus, email eventually not working is not something I should burden my wife with.

I've recently been thinking I need to learn Chef or Puppet. This thread has convinced me to pick up and try Ansible first.

A few years back it was common practice NOT to expose ZeroMQ to the wide open internet as it was built for that. I think they says it OK now, but its left a bitter sense for some of us.

At some point, to gain any form of remote access you have to put your trust in one piece of software. Being it VPN, ssh, or something.

For many people ssh is considered secure enough. And any secure issues get immediate attention so you can be updated pretty quickly.

Now any software could have unpublished zero days, which is why I also do some other host based security.

I'm not sure if I'm correct or not, but I see 2 types of big data guys. First there are the guys who know the tools - perhaps this is the "data engineer" referenced by rdouble. This guy would know all the tools, how to map data in and out of say something like Cassandra or HBase?

Then there are the guys who can properly analyze the data and turn that into something that can save an enterprise money. This is probably where the big bucks come in.

At my weekly codeandcoffee gathering we are discussing some problems we think can be solved by big data analysis. The actual underlying technology is merely an implementation detail, the value will come from the results. Our goal is to save a target enterprise 1% a year, and given our target customer is a $40 billion company, that is a lot of money we can charge. We're just discussing what ifs at this point.

Is #python not the official channel?

Hover or 10dollar.ca.

Forced myself to NewsBlur, deleting all my feeds in Google Reader. I mostly use the iOS app. While not as good as Reeder, its not bad.

So what are my real options for avoiding the JVM on new projects? Go? I'm not into functional save a bit if Scala. But not willing to invest time in something like Haskell.

I also don't feel like Python is an option. Seeking more performance from a single node is what he me move to Java from Python for many of the the things I work on.

A friend of my fathers. He's been fixing startups who started out wrong for the last 10 years.

Get references for people that are near you.

Thanks. I had not considered ElasticSearch but already ruled out Logstash for various reasons. ElasticSearch looks like the perfect starting point, gives me 90% of what I need.

3x24" screens at 1920x1200 each.

More and more thinking I may be better served by a single 27" or 30".

DI will defer the injection to runtime instead of compile time, so you don't get the benefit of type checking during the compile.

I've been bitten by this in the past with SpringMVC. It usually ripples up quickly and has never been an issue in a released app.

I've also found Tornado to be quite readable. But my norm is corporate closed source code which is pretty unreadable.

Right.

I think Java does suffer from a little too much boilerplate, but that is solved by becoming proficient in an IDE which doesn't actually take too long. Even for this old hacker who only picked up an IDE 2 years ago after nearly 20 years of emacs.

Oops. I meant to say Backbone not Bootstrap!! It was Backbone on my todo list, but Angular seems to be getting all the attention now.

So I was finally freeing up sometime to learn some frontend dev. Was going to focus on bootstrap. But would angular be better?

I'm trying to build up a toolset to rapidly build admin sections for services I work on which don't typically have users in the traditional sense.

Funny.. Just a few weeks I was wondering if Marco was bored of Instapaper and tried out Pocket in case he was going to dump it.

Doesn't matter, I ended up liking Pocket better after having been a long time Instapaper user.