slow_donkey

Location: Boston, MA

Remote: Yes

Willing to relocate: No

Technologies: TypeScript, Node, Kubernetes, AWS, React/React Native

Résumé/CV: email

Email: hn@raindeer.io

Looking for backend jobs remote or in Boston. Early engineer at current startup and helping lead a team which is recognized as the top performing engineering team in the company.

Interested in mid/senior positions preferably with a statically typed language stack. Would love to transition into golang.

Strongly agree - as someone much more comfortable within the node ecosystem, there's several libraries I'd rather use in place of Nest's choices. However it makes a great starting point for people not aware of the other options and who need an opinionated bootstrap.

If anyone's wondering my current template is routing-controllers, class-validator, tssyringe, and sequelize-typescript.

Separate issue, but if anyone can suggest a different query builder / orm in typescript that'd be truly appreciated. Imo typeorm is too much of an abstraction and sequelize works but requires custom types ever since v5

You could shoehorn hasura for this usecase but those tools are primarily intended for frontend clients to subscribe to a schema you expose.

Change data capture allows you to stream database changes to a message bus or stream which has much better support for backend service requirements. Example: if a downstream service goes down, how would it retrieve the missed events from Hasura? Using Kafka or a buffered message bus, you'd be able to replay events to the service.

Nevermind having to support websockets in all your services :/

Unfortunately that's the easiest way to build a real business around recruiting. Same with car sales. If you do your job well, the user won't come back for a few years. Therefore the user has to be the recruiting companies which guarantee repeat business

This looks great - I've been looking into debezium for a similar idea but they don't natively support views which makes sense from a technical pov but is rather limiting. There's a few blog posts on attaching metadata/creating an aggregate table but it involves the application creating that data which seems backwards.

Would be huge if materialize supports this out the box. I believe it's a very useful middle ground between CRUD overwriting data and eventsourcing. I still want my source of truth to be a rdbms, but downstream services could use data stream instead

The goal is to push the limits of the game's physics not real life. Quake based games allow you to retain speed when jumping at the same 'frame' as landing (bunny hopping) and slide up slopes with enough speed.

These physics create a high skill ceiling for speed runs and in normal play because of how powerful movement becomes during play.

I work at a place with mobile apps. You can't continuously release a new app update every day so a release cycle is useful for structuring when we're going to ship, when qa starts to test, and having deliverable dates in anticipation of app store/play store approvers (couple days)

Definitely agree in regards to sourdough starter vs yeast. Although I thought most Neapolitan pizzerias didn't use sourdough anyways - would love to be wrong about this.

Why would instant yeast have an effect on slow rising? You'd just use a smaller amount than AD or cake yeast? I can't think of any significant difference especially compared to AD.

>How are images built with Paketo Buildpacks different from Docker images? Unlike Docker images, images built from Paketo Buildpacks are OCI compliant.

Can someone explain why this is significant - I'm struggling to wrap my head around the why

I believe the emphasis was on "full stack engineer" which is why the justification was experience with both frontend and backend engineering.

Depending on which circles you run with, full stack is usually seen as misnomer because it colloquially refers to frontend engineers with the bare knowledge of backend in Node.

Ooh details please. I've looked at the docs but haven't used actions yet. What makes it worse than circle?

The initial capabilities look similar and circle really needs a competitor with how flaky their service has recently been.

Unfortunately you've already established your site as a lemon market by posting jobs at absurdly low rates.

I'm not sure what demographic you're targeting but $100 for 3 iOS screens is well below market rate

You could easily export your passwords if needed and leave bitwarden in that case.

Now I think there is a scenario where the maintainer gets bussed and bitwarden later goes down after some months resulting in lost passwords.

Your link blasts a song on click

Laptop model: Thinkpad T440p

CPU: Intel® Core™ i7-4710MQ CPU @ 2.50GHz × 8

RAM: 12GB

Screen: 14" Matte

Personal comments: Debian works well. Wish I upgraded the screen. Battery life is meh ~4hrs and drains while sleeping. Bit thick and takes a lot of space in backpack.

Intermittently, the fan will sound like it's hitting something and make a terrible whirring noise. Gets taken care of by a few spurts of compressed air.

Used as my 'desktop' at home.

---

Laptop model: Mackbook Pro 2015

CPU: i5 - 2.7ghz

RAM: 8GB

Screen: 13"

Personal comments: Decent battery life and works well for travel. Good keyboard like T440p. Not a fan of the OS but hardware-wise works very well.

Used as my personal travel laptop.

---

Laptop model: Mackbook Pro 2018

CPU: i7?

RAM: 16GB

Screen: 15"

Personal comments: Very good battery life. 15" is bigger than I'm used to, but I've started to appreciate the screen real estate without external monitor. Probably my least favorite laptop to use simply because the keys consistently double tap and I can't feel for fn keys (fn, volume, brightness). Work-provided laptop.

In summary, I'd lean towards a Thinkpad carbon for the ideal combination of portability, keyboard, and ability to run Linux. Never appreciated quality screens until using Macs - will definitely be upgrading future laptop screens.

Not sure about Kong specifically, but monetization is a common feature API gateways support (Apigee)

They absolutely are the victims but it's also a students responsibility to do due diligence on the bootcamps just like you would (should?) research an employer before signing the job offer.

IMO the problem is that Dart is pretty much JS and really not challenging the status quo - My light experience with Dart is JS < Dart < TS. So if there's an opportunity to simply use TS, I don't see the benefits of Dart.

I hate such problems as a job seeker but you can't deny their effectiveness in finding viable candidates. We typically don't whiteboard and it's easy to find candidates who can pass the basic build/consume an API test. But once you throw a different type of problem, they fall apart. I hope someone can counter that whiteboarding also has the same fallacy.

Don't know about BOA, but I've never had a problem receiving verification codes on my voice number which is my daily driver.

Would love to see your current setup - I also have the same issue with TypeORM and am sticking with sequelize.

I'm wondering this too, our company has relatively small and has done a great job at reducing meetings for engineers. But peeking at any other department calendars shows significant meeting creep with weekly syncs that seem important. Arguably some of their jobs (eng manager) inevitably has tons of meetings but as we grow I only see more and more meetings accumulating.

UICollectionView would map to RecylerView on Android. But because RV gets used in 90% of screens and has annoying boilerplate, companies commonly make abstractions over rv like Bento.

If they're investing in kubernetes it makes complete sense to switch to GKE over AKS. We used AKS and it gave us tons of trouble while GKE seemed a lot more polished.

Honestly it looks fine to me - they do seem jarring individually but casually browsing the sites is pleasant.

I'm very appreciative that each component is very clear and pages won't draw my attention in 10 different places.

I'm curious why this is OKR specific. Shouldn't you be tracking those metrics anyways?

I have a cheap $25 Walmart backpack I got from another HN thread and it's worked surprisingly well - no signs of wear after ~2 years of daily use.

Found a link: https://www.walmart.com/ip/Outdoor-Products-Quest-Backpack-D...

Seems like poor design - we used drift and it definitely persisted chat sessions. Agreed on sounds and face being extremely annoying.

I would suggest using Vue progressively at that point. Refactoring our endpoints after using intercooler was not fun and using Vue/react without going full SPA let's you move on way easier