Spencer Rinehart

Location: Austin, TX

Remote: Remote, Hybrid, On-site

Willing to relocate: No

Technologies: Node.js, React, AWS, PHP, Typescript, Docker, Linux, PostgreSQL, MongoDB, GraphQL, HTML/CSS/JavaScript, Git

Resume: https://www.overthemonkey.com/resume.pdf

Email: anubis [at] overthemonkey.com

I am looking for a company that drives ownership amongst its team and provides a healthy environment for collaboration. I am a full-stack Principal Software Engineer with 18+ years of experience, predominantly in web develop (Database, API layer, web layer and everything in between), DevOps, and architecture. I have 10+ years of start-up experience and 6+ years of leadership experience. I am passionate about engineering and scaling as far as they align with business needs.

Our organization recently looked into AWS Session Manager for tunneling but couldn't find documentation on how to make it work for our usecase. We were trying to tunnel into our VPC in order to be able to connect to an Amazon DocumentDB cluster. We don't have any EC2 instances which seems to be the only thing Session Manager has support for. Despite the callouts that Session Manager replaces bastion servers, that didn't seem to be the case for us. Did we miss something in our research?

Last I checked the "tunneling" only works to redirect traffic to a different port on the same SSM managed instance. The tunnel cannot be established with another box in the same VPC. So I don't think you can call it tunneling until they add that feature. Here's the GitHub issue where they discuss the limitation and a workaround: https://github.com/aws/amazon-ssm-agent/issues/208

KEY Concierge | Austin, TX | ONSITE | Full Time | Software Engineer

KEY is a hospitality marketplace for travelers, vacation rental properties, and vendors. We are transforming the industry through our technology platform, which vets properties and provides curated services to make guests’ stays seamless and homeowners’ lives easier.

Our Stack: Node.js, React, PostgreSQL, MongoDB, AWS, GraphQL

We are looking for an experienced engineer to provide technical leadership and build a technology platform that connects vendors, property managers/aviation partners, and travelers, enabling the travelers to effortlessly plan curated experiences. You will be a key member of the team to develop the platform for concierge service.

Are you ready to join us as KEY expands into the hottest travel destinations, and usher in the next big wave in the travel industry? Contact us at careers-engineering@key.co

I think the National Association of Pastoral Musicians will be fine. I assume you meant npmjs.com. :)

meanwhile the International Brotherhood of Magicians has faded into obscurity.

It still proves your point, but the gallery is interactive via clicking to the sides of the image. Interactive but not intuitive.

Twyla | Frontend Engineer (React), Backend Engineer (Node.js), Full Stack | Austin, TX | Full Time | ONSITE | https://www.twyla.com

At Twyla, we make it possible for everyone to shop exclusive limited-edition prints from the most talked-about artists in the game. We're dedicated to making great art accessible and we're backed by Google Ventures and other top VC funds.

We work in a bright industrial loft in downtown Austin that doubles as our art gallery. Our culture is fast-paced, creative and cool. We offer great benefits, including unlimited vacation and competitive compensation to qualified candidates. If you think you are a good fit we'd love to speak with you about joining our vibrant and talented team.

As a member of our technical team you will play a critical role in guiding our technical decisions. We are looking for highly motivated individuals with a passion for bleeding-edge software development and creating delightful customer experiences. We are currently hiring for a few different positions:

Frontend Engineer: We love React and are looking for an additional developer to join the team and work with us on building a unique and creative website. Experience with GraphQL a big plus.

Backend Engineer: Our modern Node.js GraphQL API backend and manufacturing system provides an interesting challenge to empower the development of our application and print-on-demand manufacturing pipeline.

Get in touch with us or apply for a position at it@twyla.com.

Location: Austin, TX

Remote: No

Willing to relocate: No

Technologies: Node.js, PHP, Docker, AWS, HTML/CSS/JS

Resume: http://overthemonkey.com/resume

Email: anubis@overthemonkey.com

I'm interested in working for a small team of engineers passionate about technology.

I've done something similar with PHP, by casting an array to a string (The string "Array") and using "variable variables". If only there was a way to call functions in PHP without using letters in the code... https://gist.github.com/nubs/5849633#file-nodigitsorquotesei...

You can call a function by name:

    $foo = "file_get_contents";
    $bar = "http://example.com/";
    $baz = $foo($bar);

In PHP 7 this doesn't even require you to give the function name its own variable:

    ("file_get_contents")("http://example.com/");

I dunno, raise the T-Rex up and have it be able to protect you. Classic Lion King type story there with Timon & Pumbaa using Simba. ;)

You should only ever be squashing an error into a success response if that's what someone would be expecting but that's rarely the case. Normally you should be allowing the error to bubble up and be decided by the caller.

I can think of a couple cases where catching an error down low with the purpose of squashing it makes sense. One would be for a service that you know may not have data and you don't care if it doesn't. For instance, trying to get geolocation data for a user in order to improve their experience but if it fails you don't need to show an error:

return geolocationService.fetch().catch((err) { /* log error /; return {}; / empty result/ });

Another case is when you might have multiple ways of handling the request where one is prioritized over the other. In this case, you can catch errors from the first attempt and try a second method. If they both error out, then the result promise will be an error as well.

return primary.fetch().catch((err) => { return secondary.fetch(); }).then((data) => { / manipulate data */});