Skip to main content

Where's Greg?

It's been almost two years since I posted anything here. In late 2015, things got really busy for me at Recruitics and, to be totally candid, maybe I wasn't sure what this blog is for.

What happened since late 2015?

My department moved offices. Twice. We weathered a round of layoffs and rebuilt the teams that were affected. And we've made a ton of progress improving our applications and data processing. I joined Twitter. I became the solo developer of a new integrations platform that now handles over 30% of our data collection traffic and cost tracking. And in two months we launch a free analytics product that will change the competitive landscape in online job advertising.

So ... there's been a lot going on for me.

What's next for this blog?

My original purpose for this blog was to contribute something that other software engineers might find useful. I posted a few technical commentaries on topics not well-covered elsewhere, and I wrote somewhat haphazardly about my experiences as an engineering manager. The blog never really got much attention or traffic; in retrospect I realize I am better at writing software than blogging.

I believe my original goal was good, and I'm going to give it another go. This time I am going to try to be more consistent about topics and content. And I'm going to be more open-minded and less judgmental about what this blog becomes. Happy reading!

Comments

Post a Comment

Popular posts from this blog

ReactJS, NPM and Maven

I'm just starting to get into working with ReactJS, Facebook's open source rendering framework. My project uses SpringBoot for annotation-driven dependency injection and MVC. I thought it would be great if I could use a bit of ReactJS to enhance the application. If you're looking for a basic conceptual intro, I recommend ReactJS for Stupid People and of course the official documentation  is quite good. In full disclosure, I still have no idea how to do "flux" yet. As an experienced Java backend developer, I'm pretty decent at hacking Maven builds - which is precisely what this blog post is going to be about. First, a word about how React likes to be built. Like many front-end tools, there is a toolkit for the node package manager (NPM). From the command prompt, one might run npm install -g react-tools  which installs the jsx command. The  jsx  command provides the ability to transform JSX syntax into ordinary JavaScript, which is precisely what I want...
21 comments
Read more

Solved: Unable to Locate Spring Namespace Handler

I attempted to run a Spring WebMVC application, and when starting up the application complained that it didn't know how to handle the MVC namespace in my XML configuration. The project runs JDK 7 and Spring 4.0.6 using Maven as the build system. The following is my XML configuration file: <?xml version="1.0" encoding="UTF-8"?> <beans xmlns="http://www.springframework.org/schema/beans"        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"        xmlns:mvc="http://www.springframework.org/schema/mvc"        xsi:schemaLocation="         http://www.springframework.org/schema/beans         http://www.springframework.org/schema/beans/spring-beans.xsd         http://www.springframework.org/schema/mvc         http://www.springframework.org/schema/mvc/spring-mvc.xsd">          <mvc:annotation-driven/> ...
1 comment
Read more

Capture Everything

This week I've started planning for the next version of our data collection system. The key realization for me is that I do not know all the questions we will need to answer in the future. Our current focus is on specific sequences of click events, but in the future we might want to look at browser versions or behavioral patterns related to IP addresses. If we don't capture user-agent, for example, we won't be able to answer questions about browser versions. If we don't capture IP then we cannot look for patterns in IP addresses. We should store data in a way that maximizes the range of questions we can address in the future. In the past few years, the cost of storing data have continued to fall. We use AWS extensively.  Amazon S3 costs are very reasonable and guarantees a high level of availability. Also, lower compute costs and open source tools like Hadoop that process large data volumes have greatly increased our ability to extract valuable insights from data. So s...
Post a Comment
Read more