Readit Newsfellow co-founder here! One fun thing about this project is the entire frontend was vibe-coded using Bolt in a few days.
emgeee commented on Show HN: Obelisk – a WASM-based deterministic workflow engine obeli.sk/... · Posted by u/tomasol
This is a pretty cool idea but I'm trying to think of the advantage of WASM vs other execution engines.
It seems to me one of the main use-cases for WASM is to execute lambdas, which are often short-lived (like 500ms timeout limits). Maybe this could have a place in embedded systems?
emgeee commented on Has the decline of knowledge work begun? nytimes.com/2025/03/25/bu... · Posted by u/pseudolus
Starting in 2022, US companies could not deduct SWE salary expenses in the same year, only over 5 years like hardware CapEx. For big companies, this will roll over in 2027. Meanwhile, LLM expenses can be written off immediately as OpEx.
great point, thanks for sharing
emgeee commented on Switching from Pyenv to Uv bluesock.org/~willkg/blog... · Posted by u/harryvederci
has anybody doing complex projects achiever success with uv completely replacing pyenv, and had mostly pros and few or no cons?
I'm very comfortable with pyenv, but am extremely open to new stuff
I've used uv to work on the feast feature store project to great success
emgeee commented on Detecting AI agent use and abuse stytch.com/blog/detecting... · Posted by u/mattmarcus
I asked a manager about this, the policy is that we do not need to differentiate between bots and people who sound similar to bots: both are considered low quality content/engagement. Delete them.
Seems like wherever they delete bots, they will in the end, delete human beings.
I never really thought about this perspective but in some ways it makes sense. I think the ironic part is that LinkedIn now provides built-in AI tools that make you sound more like a bot.
Maybe they could fingerprint slop generated with they tools and allow it through to incentivize upgrading
Having a kafka compatible API and S3 storage would be something I would jump to, the savings over MSK would be huge.
If you had a (paid for) API that sat on top of an S3 API for on-prem, that would be fantastic as well.
Kafka is great, but the whole Java ecosystem and the lack of control of what is in the topics and the stuff about co-ordinating the cluster in zookeeper is a management PITA.
Checkout warpstream (recently acquired by confluent)
People get me a job when I look for one.