nubs

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?

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 [email protected]

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

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 [email protected].

Location: Austin, TX

Remote: No

Willing to relocate: No

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

Resume: http://overthemonkey.com/resume

Email: [email protected]

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...

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 */});

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.

One pattern I use is to rethrow the error:

return service.fetchData().then((data) => {}).catch((err) => {console.log(err); throw err;});

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:

let results = service.fetchData().then((data) => {}); results.catch((err) => {console.log(err);}); return results;

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.

e10s = electrolysis

i18n = internationalization

l10n = localization

k8s = kubernetes

Here's some other ports of Scientist I've come across as well:

PHP

https://github.com/LartTyler/Analyst

Javascript

https://github.com/trello/scientist

https://github.com/Runnable/scientist

https://github.com/jirwin/labrat

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 don't think you read this properly. This isn't about working with the X clipboard - it's about copying/moving files on the filesystem.

In general, the data isn't there for most locations, but it has been added for some locations. For example, Saint Basil's Cathedral: http://www.openstreetmap.org/#map=19/55.75252/37.62300&layer...

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: Chesapeake, VA, US

Remote: Willing to work remotely

Willing to relocate: Yes

Technologies: PHP, Linux, Docker, JavaScript, ...

Resume: http://www.overthemonkey.com/resume

Email: [email protected]

I am a full-stack engineer with over ten years of PHP experience. I have extensive experience with Linux as a development machine and as the base of a production software stack. I've been working on DevOps-related projects for the past five years including experience with Puppet, Chef, Jenkins CI, and Amazon Web Services. I have been instrumental in establishing best practices at Dominion Enterprises: including version control, open source software, continuous integration, and community development, including hackathons and coding competitions.

Docker provides more flexibility. So while you can have developers managing security updates that is definitely not the only way of handling things.

I see a process where ops are responsible for the base images (base os images, and layers for different software stacks) and can handle security updates at will. Developers can maintain small dockerfiles that just install their application on top of the ops-managed image. ops can then be in charge of building (and re-building) the images and deploying them. Of course, that can all be fine-tuned to your liking.

How does this compare to vfsStream[1]? I've used that in the past for mocking in unit tests. Does this offer anything more than vfsStream?

[1]: https://github.com/mikey179/vfsStream

Very interesting how you can definitely see 3 distinct groups emerge in recent years. I'm guessing linesmen are the majority of the group that really shifts over to the right.

I once did something similar in PHP.[1] View the semi-useful writeup[2] as well.

[1]: https://gist.githubusercontent.com/nubs/5849633/raw/78bae58f...

[2]: https://gist.github.com/nubs/5849633

This list is missing https://github.com/nikic/FastRoute which is definitely worth looking at.

The claim of "fast" definitely looks inaccurate in comparison to nikic's router[0]. I'd recommend reading through his blog[1] on the matter.

[0]: https://github.com/nikic/FastRoute

[1]: http://nikic.github.io/2014/02/18/Fast-request-routing-using...