Matt Parsons @mattoflambda

Haskell jock. Backend Developer UX at @mercury. I wrote @prodhaskell so you can get a Haskell job! parsonsmatt.org Denver Joined February 2013

Tweets

18K
Followers

5K
Following

597
Likes

43K

Matt Parsons @mattoflambda

a day ago

Spotify is really good for obscure classical music and really awful for mainstream classical. Funny juxtaposition- my IDAGIO subscription is mostly useful for really popular composers

0 0 1 182 0

View Details

Matt Parsons @mattoflambda

a week ago

@h_thoreson “Hey do you want to cut your salary in half and move to a shithole? Why aren’t you responding? This is my last attempt…”

0 0 2 14 0

View Details

Matt Parsons @mattoflambda

2 weeks ago

managing autonomous AI agents is probably like managing lazy and disinterested human engineers (i've only managed awesome and good engineers so i don't know for sure)

1 0 3 258 0

View Details

Codex est'd token spend is $113 (API rates). Claude is $31 (from `/cost`). I think Claude is the winner in this. Or at least the best loser? Clearly more aligned with my intent than Codex. Cheaper. Failed fast.

1 0 0 133 0

View Details

Matt Parsons @mattoflambda

2 weeks ago

ok now that I've had coffee and can evaluate/review myself: Codex was Goodharting- 2.43x improvement is actually "20s constant cached" and the memory use was actually higher, but a config change masked it. Claude's 10% gain was honest but also behavior changing and failed tests

1 0 0 135 0

View Details

Matt Parsons @mattoflambda

2 weeks ago

evaluating Claude and GPT-5.5 by giving them the same tasks in separate subtrees and seeing which one does better

1 0 2 705 0

View Details

Matt Parsons @mattoflambda

2 weeks ago

@h_thoreson prices are sorta starting to correct in Denver but it's still a "weak seller's market" - just so burned by the insanity of the last few years that "house is available for more than a few days" feels like a treat

0 0 1 17 0

View Details

Matt Parsons @mattoflambda

3 weeks ago

@theodorvaryag i have yet to try a different cli for this, though experimenting is on my todo list

0 0 0 22 0

View Details

Matt Parsons @mattoflambda

3 weeks ago

Author: Matt Parsons Co-Author: GHC

0 0 4 257 0

View Details

Mitchell Hashimoto @mitchellh

4 weeks ago

I strongly believe there are entire companies right now under heavy AI psychosis and its impossible to have rational conversations about it with them. I can't name any specific people because they include personal friends I deeply respect, but I worry about how this plays out. I lived through the great MTBF vs MTTR (mean-time-between-failure vs. mean-time-to-recovery) reckoning of infrastructure during the transition to cloud and cloud automation. All those arguments are rearing their ugly heads again but now its... the whole software development industry (maybe the whole world, really). It's frightening, because the psychosis folks operate under an almost absolute "MTTR is all you need" mentality: "its fine to ship bugs because the agents will fix them so quickly and at a scale humans can't do!" We learned in infrastructure that MTTR is great but you can't yeet resilient systems entirely. The main issue is I don't even know how to bring this up to people I know personally, because bringing this topic up leads to immediately dismissals like "no no, it has full test coverage" or "bug reports are going down" or something, which just don't paint the whole picture. We already learned this lesson once in infrastructure: you can automate yourself into a very resilient catastrophe machine. Systems can appear healthy by local metrics while globally becoming incomprehensible. Bug reports can go down while latent risk explodes. Test coverage can rise while semantic understanding falls. Changes happens so fast that nobody notices the underlying architecture decaying. I worry.