๐ฆ๐ป๐ --
Any conversation
How do you define slop in relation to ? For me, it is how quickly you get to an unmaintainable state- the acceleration into something that becomes difficult to work. I talk more about it here: hellodavid.dev/blog/slop
An interesting thought: historically, a major consideration for companies choosing what to use is how many engineers use it (because that will make hiring much easier/harder). Going forward, this becomes "how big of a corpus of this code is out there", because it impacts how proficient are likely to be at using it.
Vagyis attรณl mรฉg, hogy trehรกny vagyok, mรฉg mลฑkรถdhetne jobban is az anyagmegmaradรกs tรถrvรฉnye, mint รฉppen errefelรฉ, vagyis errefelรฉ plรกne mลฑkรถdnie kellene, mรฉgsem ezt teszi.
So even though I'm clumsy, the law of conservation of matter could still work better than it does here, or rather, it shouldn't work here, but it doesn't.
Iโm using textlog to explore the intersection of and tech, with the goal of building an app that solves a problem in this space. Named , it's word represented as a hex color.
Of all the words there, it is a cocoa-ish color and is an appropriate name for this idea.
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.

