cupofjoakim

I'm not just talking about the post though. In many places it IS legal to remove someone zero notice with or without a severance package.

i'm tired man. AI this, AI that, here's how we productmaxxed our deliveries, here's how many people we could remove, etc etc. Everyone is going crazy about ai, but no one is remembering the people affected.

Corpo culture is disgusting around layoffs. Zero notice terminations should not be legal, anywhere. Have some fucking heart guys.

I tried it out, but with kev instead of this python script. The issue is that mid session swapping invalidates the cache, which drives cost quite a lot. Ended up loosing money when comparing prompts in most of my transcripts.

If you're not behind a walled garden like i am (vertex), you could probably experiment with routing on effort level instead. Anthropic supports it, but vertex has not added that feature yet.

I wonder if this could be a good stepping stone to write a local prompt router to optimise what model get what prompt. I.e. if the prompt is just a lookup, send it to haiku, if it's reasoning, send it to opus and if it's implementation send it to sonnet.

The issues are global and they are correct. The landscape is not the same in US as in other countries, but this is a global problem and should be handled as such.

I'm not against a tax on AI or robots, but I think this may be the big chance we have to look at universal income with new eyes. If jobs are to disappear, why not soften the blow and get rid of some of the inefficiencies many government processes mean in terms of other citizen benefits?

What I worry about more however is the malevolent actors across the AI space. I'd argue that most companies mean well, but chasing profit at all costs can very easily turn into malevolence. Both these and actors being malevolent on purpose needs to have a control function.

Well, nesting is not the only option.

``` thing.doThis() thing.thenDoThat() thing.andFinallyThis()

// or

doThis(thing) thenDoThat(thing) andFinallyThis(thing) ```

Fair! That'd depend on the operations right? For example, AFAIK typescript can't do much about multiple chained `map` calls, and i've seen quite a few `.filter(...).map(...).filter(Boolean).map(...)` :/

Interesting. there are some parts i like a lot here, but two things that I really dislike syntax wise. One is the lean towards a chainable syntax - this has proven to a big footgun for many devs in both java streams and typescript, making it very easy to go from O(n) to O(2n). The other part i really dislike is the first argument principle noted. If i myself define `string_and_reverse` and I can call it both through `string_and_reverse(42)` and `42.string_and_reverse()` i could definitely see this leading to some very funky looking chaining.

Perhaps it's just one point from me - not liking chaining :D

This is great. I wish however there was some sandbox support, perhaps running the whole hive inside a vm for example

The US being stuck in imperial is such a meme nowadays with "freedum units" and the like. It's yet another odd thing that makes it easy for the rest of the world to laugh at the US. In these isolationist times I doubt this will change soon though, but it'd definitely help international collaboration.

That's great if you need everything. If you need one of them, not so much.

I find your comment a bit funny on multiple levels. "Linux" does not force anything on you right? It's the community that has by and large decided to move to maintaining other solutions. If you still want to use fvwm you can still run it on arch with x11 until x11 is not maintained and the kernel breaks it somehow