griffinmyers

4 ms·

1. 1.▲
   by griffinmyers 3y ago

   We're still waiting for our "react" moment on the backend; a fundamental shift in the abstractions we treat as the bedrock of our applications. I think the author does a good job here showing why the state machine might just
2. 2.▲
   by griffinmyers 3y ago

   These look super useful -- a great example of two powerful paradigms that together are greater than the sum of their parts.
3. 3.▲
   Show HN: Wirepig – Mock HTTP and TCP deps with real sockets in Node.js tests(github.com)

   1 points by griffinmyers 4y ago|0 comments
4. 4.▲
   by griffinmyers 5y ago

   This was a doozy.
5. 5.▲
   by griffinmyers 6y ago

   I hit this issue a year ago, in a slightly different setup. We were trying to expose an internal ECS Service to other services via an NLB. Things worked great, as long as the sending and receiving services didn't end up on the same EC2
6. 6.▲
   by griffinmyers 6y ago

   It's a wonderful tune -- I was an instant fan hearing it in the movie Inherent Vice.
7. 7.▲
   What to Expect When You're Expecting to Go Remote(wgm.cool)

   2 points by griffinmyers 7y ago|0 comments
8. 8.▲
   Designing an API Client(building.usebutton.com)

   1 points by griffinmyers 10y ago|0 comments