Third Iron

Third Iron

2 Followers
We create technology for academic and research libraries, including our flagship product, BrowZine

Decisions 5

Karl Becker

CTO, Co-Founder, & Developer at Third Iron, LLC

We use Node.js because it allows our full-stack developers to have less context-switching when working on different areas of our systems. Whether it's frontend or backend, there's no major syntax changes. Every single member of our team is experienced with a variety of languages, but reducing the cognitive overhead that comes with switching languages lets us more smoothly switch between front-end and back-end development.

It was a pretty hot new technology when we adopted it at the company's inception in 2011, and we're glad it's progressed and matured so much since then... and of course, still has more maturing to go, but we'll keep adopting new versions and features and fixes as they come!

12 3K

Karl Becker

CTO, Co-Founder, & Developer at Third Iron, LLC

We use TypeScript because type safety in JavaScript seems to be kind of a game changer, providing feedback on certain changes and classes of bugs that doesn't even require a single automated test run to discover.

How nice is it to simply add an element to an existing interface, and then instantly be shown in an IDE all the places that need to be updated to have the new element? 🎉

3 1.3K

Karl Becker

CTO, Co-Founder, & Developer at Third Iron, LLC

Legacy code that, although maintained slightly, will be phased out as we migrate the 2 backend tools that rely on it to other, more robust languages. See: http://bjorn.tipling.com/if-programming-languages-were-weapons PHP

1 955

Karl Becker

CTO, Co-Founder, & Developer at Third Iron, LLC

We use Ember.js because its convention over configuration helps our team stick with the Ember way of doing things and not have to bike shed or otherwise think about how to structure our app or do certain things. There is indeed a learning curve with Ember, but the amount of tech that Ember pioneered, and that is part of the framework, allowed us to quickly adopt patterns and practices from people who were more focused on web front-end development than our team was when we began our front-end web adventures.

More of our effort still goes to backend work than front-end, so being able to do things "the Ember way" has shrunk some of the decision making time.

1 838

Followers 2

Karl Becker
alicecameron517