In April I joined DataStax as a director of engineering on the DataStax Enterprise engineering team. I meant to post something here during my first week, but have been kind of busy since I started (understatement!). We sell an enterprise-class version of the open-source Cassandra database, along with service, support, and training. We also support the Cassandra community and the open-source project itself (the Apache Cassandra committee chair and many committers are all DataStax employees).
My first five week have been both busy and exciting. Here are some observations and highlights so far:
It’s great to work for a smaller company once again – everyone is very motivated and focused on the mission, and it’s a very small circle of decision-makers.
I’ve worked for companies with remote workers before (especially Citrix), but here we take it to a whole new level. We just call it a “distributed” workforce. In particular the engineering team is spread literally around the world. Many of our job postings list the location as “Anywhere, World” which is quite appropriate.
We really like using SaaS based products, and have hardly any “infrastructure” hardware/servers of our own (just a few systems for Engineering & QA). Everything else is “in the cloud”.
I’ve had a big learning curve on distributed NoSQL databases in general, Cassandra, and all of the DataStax products.
DataStax is really growing quickly and we’re looking for strong people in a variety of areas. Check out the DataStax Careers page for current openings and let me know if I can help make a referral for you.
In particular these are some key open positions in my group:
Driver & Tools Engineer
Software Engineer in Test
This Jobvite link will take you to the details page for those 3 positions.
This is a very useful service. While it was primarily designed for classrooms, it could also be used for sports teams or anywhere else you need a 1:Many text messaging system.
Remind101 designed their system to be very focused for this type of communication. By keeping with a narrow focus, they’ve got a strong set of features like:
Privacy – no one participating (teacher, student, parent) has anyone else’s phone numbers; this would be very important for younger kids in particular
Only Group Messaging – there is no support for 1:1 messages; instead everything is sent to the entire group/class
One-way Messaging – students and parents cannot reply to any teacher message; I would like to see the ability to reply as well, in order to make it a better communication channel for the students back to the teacher
Mobile Apps – for the teacher side, they have apps for both Android and iOS
Email – as an alternative to text messaging, students/parents can receive messages via email
As a sport coach or manager, you could set up individual teams (“classes”), and connect with each of your teams separately as needed. For example, “16U Red”, “16U White”, and so on. This app could be used for a whole season, or just for a tournement weekend. (Just delete the group when the weekend is over.)
Here’s a screenshot of the web interface for sending a message:
I successfully migrated this website from MovableType 4.35 to WordPress 3.8.1. These are my notes from the migration in case they are helpful for anyone else. The good news is this is pretty straightforward, and there are plenty of notes out there (just search the internet for “WordPress MovableType import”). The tricky parts are the custom or special areas of your MovableType installation, and mine was no exception.
First, why switch to WordPress? I wanted something more current with a stronger platform of plugins and themes. I’ve been happy with MovableType and stuck through it over many versions and changes. It just started to look and feel a bit dated and it was time for something new. WordPress isn’t exactly “new” (having just passed its 10-year anniversary), but it continues to evolve and improve. I’ve also used it for a couple of sports team websites which turned out well.
As part of any migration , you need to identify the aspects of your site which are customized, unique, or which will potentially cause problems. In my case I had the following to deal with: