The following is a guest post by Bill, a software developer here at Lijit who is leading the search engine team. I thought his post was a great follow-up to the one from our CEO on the company’s recent funding and appreciate Bill taking the time to share his thoughts on how we should spend that cash.
As you may know, Lijit recently received 7.1 million dollars in venture capital funding. This means different things to different people. To the investors, it means they see promise in the company and are willing to take a calculated risk. To the executives, it’s a significant milestone in building a successful company. To the employees, it means we still have jobs, and it keeps alive the stock-option dream. But to the engineering team, it signifies a new phase.
Prior to this, Lijit has been a true startup. Everybody has worn multiple hats: the VP of Engineering does systems administration, the senior architect does configuration management, and everybody doubles as the QA team. This early phase can be very exciting and very satisfying. You get to do a little bit of everything, and the urgency to ‘just get it done’ means that you’re rarely constrained by bureaucracy or red tape. But it’s also a difficult time. Everybody is overworked, you often have to do tasks outside of your comfort zone, priorities and direction can change daily, and progress is often constricted by a lack of resources.
I only joined Lijit a few months ago, so I missed a lot of the early pains. But I got here in time to experience some of it, and I worked with many of the Lijit staff at a previous gig where we went through all these phases.
With the funding, it all begins to change. From an engineering perspective, this can be a very exciting time. In the past couple of months we’ve hired a QA team, built a dedicated Test Environment which mirrors the production system, and instituted a bug tracking process. We’ve brought additional developers on board with specialized skillsets, and organized into teams dedicated to each of our primary products (website, search platform, adserving platform). Not only have we built a talented IT team, we’re hiring a configuration management engineer. We’re adopting agile development methods, and we’re building a product roadmap and release timeline that give us direction months into the future. Across the board, we’re transitioning from a small team with limited process to a larger, more specialized team, with greater resources, and naturally, more process.
If we do this right, we become a more productive and higher quality organization which can quickly respond to business needs. If we do it wrong, we can become mired in process and overhead.
And that, really, is the exciting part–we get to define ‘doing this right’. The trick is to integrate these processes and resources while still remaining nimble. We get to pick and choose the parts that make sense. If it doesn’t make sense, if it doesn’t make us faster and improve our quality, then we don’t do it. It’s easy to get bogged down in all this stuff. But we won’t because we’ve been here before.
Photo credit: noahwesley

















