Hello, reddit ๐
Any conversation
เถ
เถฏ เถดเทเทเทเถบ เถฏเทเท. เทเทโเถปเท เถฝเถเถเทเทเท เทเทเถธ เถธเทเทเถบเถเถธ เถดเทเถฑเท เทเถณ เถดเทเถบเถฑ เถฏเทเท เถดเทเถฏเท เถฑเทเทเทเถฉเท เถฏเทเถฑเถบเถเท. เทเทเทเถเท เถดเทเทเทเถบ (เถธเทเถบเท เถธเท) เถฝเทเถเถบเถงเถธ เถฑเทเทเทเถฉเท เถฏเทเถฑเถบเถเท.
Today is Poya Day. The full moon day of every month in Sri Lanka is a public holiday. Vesak Poya (May) is a holiday for the whole world.
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.
code quality is about coupling.
coupling is not a technical property of the code bytes.
code acquires its meaning in contact with the cultural environment, and coupling is about meaning.
two constants with no semantic relationship are nonetheless coupled in pragmatics if they refer to the same domain concept.
if your goal is to minimise the time integral of future work, you must understand your domain: it decides which lines will need changing.
to carve up a codebase is to carve up the world.
Any users around?
I have been customizing it to the way I work, as it is meant to be. Bent it in a way that I enjoy holding it, so to say.
Maybe someone will find those useful, so I took the time to get it published.
Gruntfooot is a footer customization, where you can try new colors/glyphs in real time and also has theme support.
