I think it's early to tell. But generally tariffs = more uncertainty = tighter capital. If a startup raised high before, it might have to do a down round in the future unless growth is real.
This looks great. I'm usually very much a DIY type of person when it comes to investing because of the typical fees mentioned, but excited to try this out!
This was particularly bad at Meta pre-efficiency push Zuck. There was huge bloat that was counterproductive. Empire builders were incentivized by promotions based on the size of their orgs.
One thing the article didn't mention is how crucial it is for a team to have focus and to ruthlessly prioritize. It's easier for bigger teams to fall into the trap of doing "busy work" and people fighting for scope on their performance reviews. This is the worst possible outcome for company and employee where you have work driven by optics vs value.
It depends on your reliability and performance constraints. I'd recommend just doing this via hooks on the application layer if it's a simple application. If you're building a production scalable application that required reliability guarantees - you can do this with https://github.com/BemiHQ/bemi too (I'm one of the maintainers from the article). I saw you mentioned you're using Node.js, check out the Bemi github there's a few Node.js compatible libraries too. Feel free to ping me any q's!
Thanks throwaway-blaze! And that's actually very interesting to hear that you've already covered something like this using Amplitude events. Do you remember what your initial motivation for doing this was? Were you trying to capture server-side state transitions for analytics or for troubleshooting purposes?
Thank you for the interest! We're too early stage to start hiring right now. Let's stay in touch for now, can you DM me?
For anyone else that's interested in getting involved - we have some open-source libraries that we'll work to make more accessible for contributions down the line. Stay tuned for updates, and appreciate the interest!