Chouser

Co-author, Joy of Clojure.

[Chouser @chrishouser]

read ← type
↓ ↑
eval think
↓ ↑
print → read

[Cult.Repo @CultRepo]

Join Rich Hickey in the chat at the live premiere of Clojure: The Documentary at 8PM CEST tonight on YouTube! Sign-up to get notified: https://t.co/JLYyRu6UfM

[Chouser @chrishouser]

Early Clojure IRC logs online again, now with new formatting:
https://t.co/p11FqNhzQZ

There may be gaps due to my PC getting disconnected from the IRC server.

[Chouser @chrishouser]

@jaycost every Thursday evening the alarm goes off and I check to see if there's a new podcast episode, live or otherwise. Still looking forward to the next one!

[Cult.Repo @CultRepo]

In 2005, Rich Hickey stepped away from client work and spent two years on a problem most engineers had stopped asking: what would a truly simple programming language look like?

The result was Clojure. We are telling the story in a new documentary. The trailer is out today. https://t.co/dD907TRKbM

[Chouser @chrishouser]

Just used difftastic in anger for the first time today. Very nice!

[Chouser @chrishouser]

https://t.co/iBrIiBGMTD
Merry Christmas, everyone!

[Ryan Robitaille @ryrobes]

Recent "sleep thief"... Direct native Wayland GUI rendering from Clojure! 👀

DSL modeled after Reagent, Hiccup, Re-com. Sexy UI, declarative(ish) & reactive with atoms in a "normal(ish)" way. WIP!

[Chouser @chrishouser]

clojure-mcp by @bhauman is great! I'm still a coding-agent newbie user, but it was easy to set up with vscode and immediately improved the quality of the work the agent can do. Collapsed file reads, the grep tool, the editing tool, and of course eval--all very helpful.

[Star Simpson @starsandrobots]

Amusement parks are such a gift from the 1890s, and if they didn’t exist, would sound like such a fever dream. “We’re gonna make a bicycle wheel as big as a house and put little seats in the spokes” “imagine high tea, but the teacups are enormous, you sit inside and they spin”

[Chouser @chrishouser]

@potetm Express that in hiccup, and you might be on to something...

[Chouser @chrishouser]

@grok @freeeky3 @SterlingCooley @grok how many times has this process been observed by scientists? Or what percentage of the necessary steps have been observed?

[Chouser @chrishouser]

Sure you can get better, especially if you limit the number of variables you change over time. Same tools, similar project, good notes ->better estimate. Hot new framework, new domain, new kind of customer ->worse estimate.

[djwhitt @djwhitt]

Do not agree. It's a skill. You can get good at it. The real problem is that people do not want accurate estimates.

[djwhitt @djwhitt]

Do not agree. It's a skill. You can get good at it. The real problem is that people do not want accurate estimates.

[Chouser @chrishouser]

@msimoni That's NeXT?

[Chouser @chrishouser]

@jaycost Starting late, or skipping things?

[Chouser @chrishouser]

@djwhitt @potetm Maybe starting to split hairs now... Writing the schema of your busted design seems far less helpful than having a discussion about what the design should be. The discussion and it's resulting artifacts may very well include schemas or types.

[Joel Martin @bus_kanaka]

I posted a 6 step tutorial on creating an LLM coding agent.
* Uses LiteLLM
* About 140 lines of python when finished
* Can use the free plan of GitHub Copilot (no API sign-up/credit is needed to work through the steps)
* Step 5 of the agent is used to create Step 6
...

[Tim Pote @potetm]

just use a for loop they said. you don’t need a fancy map reduce they said. for loop is simpler they said.

[Chouser @chrishouser]

@jaycost thanks for the podcast, I'm really enjoying it. I'll try to catch it live next time. Thursday?