Why me:
• Strong experience with Node.js and TypeScript for backend and full stack development.
• Practical experience with React for modern frontend projects.
• Proficient with Golang for building reliable and efficient services.
• Focus on clean architecture, testing, and maintainable code.
• Consistent, self directed, and comfortable collaborating asynchronously.
Feel free to reach out. I am happy to talk about how I can help with your project or team.
José Valim nails it: Remix's concurrent submissions have a fundamental flaw. Without causal ordering, you're stuck with race conditions and stale data, leading to poor UX. They need to rethink their approach or embrace causal ordering to fix this.
If you just have a context, than your app cannot kill itself and the environment has to do it. That is better than nothing, but having the app do the killing is advantageous because: A) it can die faster (and so you can e.g. do your blue-green rollout faster) and B) you can write a log to say that your app is finished shutting down all its components, which can be useful for troubleshooting if your app was mid-transaction when it was killed.
Agreed, I learned the hard way that complicated constraints, those that are really good to keep data integrity, are really hard to test and might have unintended consequences.
Yeah I was afraid of that. Websockets are costly. Thankfully the approach doesn't completely depend on websockets so I have disabled it for now on the site.
Same here, I have a Pi 3 but I want to have this outside in the balcony, the question that always stops me is how to power it and what camera do I meed?
My plan was to stick the Pi inside, and power both it and the camera with Power over Ethernet (external-rated PoE cameras are a dime-a-dozen on Alibaba and friends).
I even got so far as to get it working with Zoneminder to dump out the clips that had motion, but didn't get further.
