HN user
If the days of software engineering are over, then there is very little we can do and other jobs will quickly follow suit. I contend that this will not be the case but corporations are operating under the assumption that workers will be replaced quickly and cheaply. We largely missed the opportunity to organize during the covid pandemic when the balance of power swung towards workers and now it's time to remedy that mistake.
There is no attempt to hide it, corporations are rapidly attempting to replace technology workers of all skill levels as soon as possible. We need to protect ourselves as well as we can to secure our futures. Join up and let's act together to better our work lives.
this is incredible, I have been thinking about this exact project for quite some time but a little wary of which approach I might take. Thanks for posting this.
what workflows do you implement in Nanoclaw that wouldn't be straightforward to build in Claude?
Also interested if this supports strudel REPL or tidalcycles. This would be a really awesome device to use for livecoding sets if it does.
Don't give money to amazon that is better spent on an amazingly efficient postal service. Amazon is subsidized by imaginary money until they put all their competition out of business(including USPS).
I really can't tell to be honest, so if it's satire it's very good. If it's not then I don't really know what it's saying, humans are bad at stuff too? Many humans are not well educated and are not great conversationalists? Does this somehow make LLMs better in our perspective somehow?
I cannot tell if this is satire, but if it is, bravo.
Why does air-gapped environment require rolling your own CI/CD solution? Plenty of examples of air-gapped Jenkins and/or Argo Workflows. Was this just an educational exercise?
The big issue with LLMs is that they’re usually right — like 90% of the time — but that last 10% is tough to fix. A 10% failure rate might sound small, but at scale, it's significant — especially when it includes false positives. You end up either having to live with some bad results, build something to automatically catch mistakes, or have a person double-check everything if you want to bring that error rate down.
I hate reading documentation too.