- Typescript
  - Node
  - React/Redux
  - Docker
  - PostgreSQL
  - Unit / integration testing patterns
  - AWS, especially Lambda

Hey all, I’m an engineer at Gather in Atlanta and we’re looking to add a senior-level engineer to our team. Gather is a restaurant-tech SaaS startup focused on helping restaurants and event venues manage their events business, drive demand, and interact with their guests. We’re looking for developers with interest in team leadership and experience in some or all of:

  - Typescript
  - Node
  - React/Redux
  - Docker
  - PostgreSQL
  - Unit / integration testing patterns
  - AWS, especially Lambda

https://www.gatherhere.com/careers/

At Gather, we believe that planning life's special events should be a seamless, fun experience for everyone involved. That's why we set out to empower events teams and their customers with user-friendly tools to simplify the event booking process — from initial inquiry to day-of execution.

We're a small team looking to expand and tackle some interesting challenges in the restaurant tech space. PM me for more info!

Stack: Typescript/Js/Node/React/RethinkDB/Postgres/ElasticSearch/AWS

If you'd still like to dress "better" in general, the /r/malefashionadvice subreddit has some solid resources on the sidebar that you should check out.

The use case I like most about typescript is it makes refactoring and making changes really painless. For example, in an angular app, you may have a service that several components rely on. When changing a method signature in the service, you'll get compile-time info about any other usages of that service, and you feel a lot more confident about making changes without something dumb slipping through the cracks and causing bugs in production.

This confidence generally lends itself to less fear of change and more willingness to refactor, which leads to a better/cleaner codebase.

Aside from that, I love the JSDoc comments showing up as you type, especially if you're working on a team in which you may not know 100% what everyone has worked on.

Other features I use every day and love:

-automatic/generated import statements

-type definitions for libraries (most have solid documentation)

-control-flow logic checking (you'll find more bugs than you think with this and it encourages more defensive programming)

-transpiling down to support older browsers (babel does this too but it's nice to have it built in)

Edit: I forgot to go into the "cons" list here.

-there's some finagling you'll have to do with some of the more poorly-written npm packages that strap themselves onto globals

-there's a slight learning curve

-you'll require a build step (with es6 if you're targeting es6-only browsers you can deploy just static files, but most people use webpack/babel anyway for older browser support and other things webpack gives you like bundling/minification/etc)

In more relevant news, the CEO (Jonathan Bush) just wrote a book ("wrote", he joked) that's a semi-right-wing take on the problem posed in this article (lack of EHR interoperability). Solid read though regardless of politics.

Also, the MDP program (the API you're referring to) is more designed to allow third party developers to build functionality onto athenanet that we don't have the specialization or capacity to build. It's not really a means of sharing health data (to my knowledge). However! We have been making the sharing of EHR data a priority, or at least seeming to, with the formation of the CommonWell Health Alliance (members including most major EHR creators... except Epic, because they're Epic). Additionally, we're working on some stuff with athenaCommunicator to help hospitals talk to labs, and stuff with Coordinator that I think involves the Austin crew too... but I don't know what of Coordinator we're allowed to talk about yet so I'll probably shut up on that matter.