codebase

The codebase is written in Coffeescript, Jade, and Stylus.

Last position was Project Lead on a medium sized Rails codebase.

Tasks will include developing, integrating, and maintaining software modules for new instruments, as well as understanding the existing codebase to enable efficient support of existing instruments.

Our codebase is well organized, documented, and tested.

Projects like resque_scheduler, robut, resque_unit, and json_api_client were all extracted from our codebase, and we’ve contributed several patches back to Rails.

Look at even a modest node.js project, and dig into your node_modules tree, it's amazing how many different modules wind up in your codebase to do the exact same thing(s).

- Do you have a codebase that has become a nightmare to maintain, and could use a refactoring in the worst way?

* You have opinions on how to structure code, and you're excited about taking ownership of the architecture of our entire frontend codebase.

Your first two answers would be obvious if we assume that we're working with modern codebase written by adequate developers, but that's a very strong assumption to make, so I wanted to be specific.

Position 1: Software Developer We're looking for a developer to help with creating public-facing Android/iOS APIs for 3rd party developers, internal APIs for our engineers, and cleaning our codebase/developing the style guide that we'll be using for years to come.

> if we assume that we're working with modern codebase written by adequate developers Yeah, come to think of it if there's a chance this function came from a pre-C++11 codebase I wouldn't be so sure that the caller wasn't supposed to delete those nodes.

A very well tested codebase with resilient systems and tooling takes time to learn, it will take time for a person to become productive within it - and that time is a lot longer than the 4 or so hours you get on your first day after the legal paperwork is done;) So pushing on day one - regardless of dangers it poses to the system - seems like pushing to production for the sake of pushing to production.

They saw what the Epic guys were doing, probably even trolled their codebase for ideas, said "Hey, we can do the same thing but make it proprietary and cost a shit ton, just like all our other stuff, and make tons of bank!