It was about four or five years ago that I had an intrinsic need to be “right” all the time.
I couldn’t let it go when someone made a mistake, or slighted me, or disputed the quality / direction of my work. Everyone else was wrong. I wasn’t alone in this regard either: a number of the people around me did the same thing.
Being right made me feel superior; it made me feel better than the idiot who did that thing wrong; it made me feel moral; it made me feel righteous.
When someone made a mistake, I felt compelled to point it out – even if it meant interrupting a speaker’s presentation during a team meeting. People started spending a lot more time perfecting their talking points and PowerPoints – time that should have probably been spent on something that actually impacted the bottom line for...
Our engineering team has been neck-deep in configuration hell lately. Editing 2000-line Solr configuration files, trying to get Apache Oozie integrated into DataStax Enterprise, Cassandra 1.2 upgrades, and more – and the one thing in common with all of these tasks is the prevalence of enormous XML configuration files.
Having wasted countless hours trying to use tools like SCP and various Sublime Text plugins to try to edit (or hell, even view) the configuration files on our dozens of Linux machines, I finally had a “fuck this shit” moment this week and wrote instant-fileserver, a stand-alone file server that you can start using a single command on any directory on any operating system.
instant-fileserver (ifs) allows you to:
I spoke at the Cassandra Summit this year about how we use Cassandra, Hive, and Solr in production at MarkedUp Analytics.
Planet Cassandra recently made all of the videos and slides available and I thought I would share. Enjoy!
This post is about stress.
It's been nearly a year since I started MarkedUp Analytics, and we've come a long way - I've raised money, won the business of some amazing customers, built the nucleus of a really talented team, and developed a product that people rave about. At the previous //BUILD conference, no one had ever heard of us - this time our logo was shown onstage during a keynote. Feels like progress; none of it was easy.
I took my first vacation in two years last week and had a chance to put some distance between myself and MarkedUp for the first time since inception, and I thought a lot about some of the assumptions I had about starting a company when I was just getting started, in particular this section from "The Seven Unproductive Habits of Startup Founders:"
MarkedUp Analytics’s customers are developers and so are most of the people who work at the company, so I spend a lot of time thinking about and refining my answers to the following two questions:
- What are the lowest common denominator skills and programming knowledge that my customers have?
- What are the lowest common denominator skills and traits that the developers on my team need to have in order to best serve our customers?
- As I’ve been exposed to more customers and as I’ve turned over members of our team[footnote: developer turnover is a natural and expected byproduct of growth in a technology company, I’ve come to learn. Don’t let anyone tell you otherwise.] I’ve started refining my answers to these questions.
- Turns out that most of our customers are fairly sophisticated and thus I expect the developers on our team to be...
I was really surprised with the positive reception 10 Reasons Why You’re Failing to Realize Your Potential as a Developer received after it got picked up on Hacker News and a few other places. One theme that became immediately clear to me in some of the feedback in the comments and in much of the feedback that was emailed to me privately was that there are a decent number of developers out there who recognize that they can do better, but don't know how to do anything about it.
As an autodidactic learner, I probably take the ability to teach myself things for granted - but I recognize that's not the case for every developer.
It can be really difficult to wrap your arms around a new programming skill when you have to learn it on your own without any outside help from an instructor or teacher, and my goal...
I came across a blog post by Michael Halligan on Hacker News last week entitled “Benefits matter, or why I won’t work for your YCombinator start-up.” As a fledging entrepreneur trying to attract senior engineering talent to my startup, his post bothered me immensely. I spent about a week mulling it over before I decided to write this.
Michael’s attitude in the post is abrasive, needlessly cynical, and mercenary, but well-argued on its pure economic merits. He describes himself on his own blog thusly:
I'm just this guy who used to enjoy tech, now I would rather build bicycles. I still work in the tech industry, for the money, but I no longer call myself a "technologist".
And he ends his blog post with this call to action for other senior technologists like himself:
To all of my colleagues with whom I have been in...
Today on the MarkedUp Analytics Blog I authored a post entitled “Cassandra, Hive, and Hadoop: How We Picked Our Analytics Stack.”
In it I explain MarkedUp’s evaluation process for choosing a new database, how we selected Cassandra, and some benchmarks from our test. If you want to learn more, go read it.
I’ve written about RavenDB in the past on and I’ve spoken about it at code camp before. I think it’s a great technology for prototyping and it has some really interesting concepts not found in any other database that make Raven really simple and elegant to operate.
So I wanted to copy over a section from our blog post about building MarkedUp on Cassandra which explains why we ultimately needed to move away from RavenDB:
Looking back to what went wrong with RavenDB, we determined that it was fundamentally flawed in...
Since going full-time on my own startup 6 months ago, I’ve spent a lot of my time recruiting, evaluating, and working with a lot of different developers. My startup, MarkedUp, is an analytics provider for Windows 8 apps (and eventually, other platforms.)
Our technology is sophisticated and difficult even for large companies to master, so the bar is pretty high for developers who join our team. We’re selective about who we work with, but even with careful recruiting practices it’s still difficult to find developers talented enough to pull their own weight on a complex product like ours.
So I want to help average developers who want to improve by calling out 10 performance-killing behaviors that stagnate the careers of most developers.
Most developers stagnate both intellectually and productively after 4-5 years in industry; they adopt some tools, pick up some patterns, learn a language or two, and...
Today was one of those days when it was nearly 1pm before I was free to sit down and make my daily to-do list. There was water damage in my apartment, one of our awesome engineering candidates took an amazing job offer with a top video game studio instead of us, and I was way behind on all of the PR / marketing stuff I’m doing because we haven’t hired someone for the position yet. Typical, stressful day in the daily life of an early stage startup CEO.
So I sat down at the counter of a diner near our accelerator and started writing down my daily to-dos in the nearly-full, leather-bound Moleskine notebook I’ve used to keep myself and my thoughts organized for the past couple of years.
I just happened to open my notebook to an entry from 11/12/2011 (about a year ago) entitled “Skills I Want to...