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?
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.
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 [email protected]
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.
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 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:
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.
It doesn't need to care whether someone else is handling it. It should just do what it needs to do according to its contract. The caller that receives the promise as a result has its own contract that may or may not involve handling the error as well (and so on up the chain).
You generally have to have an end-of-the-chain catch as a safety precaution. If you don't have one and the promise fails you may get no feedback that an error happened at all. All methods that return promises should be able to expect the caller to handle them appropriately whether they pass or fail - it's not their responsibility to try and figure out how to handle an error in the context of the wider application.
The way I handle situations like this is to only put the catches where I need them to serve some purpose. Generally, I don't catch errors at the start of the chain because I can't know what to do with them at that point. If I do catch them, it's only for logging or similar purposes and I still let the error propagate further.
Another pattern I use is to split the promise chain so that I let my main results flow be the result that gets passed on, but I can do other things in a parallel manner internally:
It's similar to the naming convention used by other long, hard-to-spell words for projects. First letter of word, number of letters in the middle, last letter of word.
Something similar has been standardized as well with the JSON API specification (although it adds its own weight to the message as well, it does address this problem): http://jsonapi.org/format/#document-compound-documents
They can be pretty crazy to figure out how to navigate on larger intersections (which have the double diamond plus other intersections in the same area). I can't tell you how many times I've missed my turn and had to take a long way around trying to get through this intersection in Austin: http://www.openstreetmap.org/#map=17/30.23595/-97.82471
Edit: On second thought I'm not entirely sure that is a double-diamond, although I've heard people refer to it as one. It doesn't seem to match up with the wikipedia article, however.
I would love the ability to easily spin up multiple profiles at one time. Having the separate profile for Dev Edition should help, but sometimes I want a few others as well (depending on the task at hand).
Ideally, It'd be best to be able to open a new tab inside of a different profile and just be able to tab back and forth between the different profiles.
I personally believe this is somewhere something like fig comes into play nicely. You can still have the isolated services, but with super simple setup: download the fig.yml and run fig up.
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.