"200K lines is not 10 times as much as 20K lines - from the mission perspective it's just irrelevant. And yet it's the easiest thing to measure. And so we look for the keys under the lamp post." ~Kent Beck
www.youtube.com/watch?v=F8fBgDCf2Y4&t=2753s
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)
โโ
โโโโโโโโ
โ โโโโโโโโโ
โโโโโโโโโโโโโ
โโโโโโโโโโโโโโโโโโโ
โโโ โโโโโโโโโ
โโโโโโโโ
โ โโโโ
โโ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.
I find myself building bespoke tooling for my own and workflows these days, not only because of the obvious reason of software being so much cheaper to build, but also because there are SO MANY options for solving any given problem that it feels impossible to evaluate all of them.
If it's not a crucial piece of tech for a work problem then it often feels like paving my own way is both cheaper mentally (kind of amazing that's true these days) and probably a better fit.


