Using deep research for trip planning and visualising it with coding agent is fun.
Any conversation
mandelbrot
for y in range(10):
s=''
for x in range(25):
a=[]
for q in range(2):
z=c=x/25*3-2+1j*((y*2+q)/10-1);n=40
while n and abs(z)<2:z=z*z+c;n-=1
a+=[n<5]
s+=" โโโ"[a[0]+2*a[1]]
print(s)
โโ
โโโโโโโโ
โ โโโโโโโโโ
โโโโโโโโโโโโโ
โโโโโโโโโโโโโโโโโโโ
โโโ โโโโโโโโโ
โโโโโโโโ
โ โโโโ
โโโฆ
NIH syndrome? I am guilty of it too. I love implementing things from scratch, you learn a lot by doing so and you get to own the codebase end-to-end, so no surprises and fighting around othersโ choices. It can get exhausting too though, in the end I succumb to using off-the-shelf components because my primary goals move at a higher level.
I've been building a Markdown variant called Zd that's focused on extensibility and simplicity. I'm curious what you would change about Markdown if you were designing it from scratch, what challenges you face as a user, or what you wish were easier to do when incorporating Markdown into your own projects.
Really glad to be using Haskell for work - especially in today's climate with agentic coding.
Our team uses containers to keep our development environment consistent across team members, though, and most agent sandbox approaches want to either offload your work fully to the cloud or they want to sandbox the agent harness process itself.
We're not ready for full cloud based development (yet?) and sandboxing just the agent doesn't work for us when the agent needs to run docker.

