The depth of a dive is always delightful! Does K8s have a solid use-case for the project or did you just sK8 for fun?
The depth of a dive is always delightful! Does K8s have a solid use-case for the project or did you just sK8 for fun?
Round two, hell yeah.
The aesthetica of a stack of notes, born from a “dead end”, is secretly an odd motivator. You look back and see
Here is the breadth of what we did wrong.
and then beyond you, the effort lays itself out in a pretty trusswork.
_or_maybe_i_just_think_well-used_notebooks_are_pretty
Hah, stochastic parrots.
Makes me wonder. Every laziness I’ve had with the vector guessers, I’ve seen an exact counterweight.
| matrix scrombulator | webpage (2007-2014) |
|---|---|
| Here’s random code. Pray it works | Free ancient code at man 3 getifaddrs. |
| How does this API work? (when the API has below 10 million sample lines of code) | Incredibly concise documentation worth spending 2 minutes on or HTML text without margin lines worth spending 20 minutes on |
| Maybe this is what’s causing your bug. Investigate a, b, and c. Conclusion sentence. | footnote in ArchWiki / archetypal 2009 StackOverflow duplicate |
| Here’s the main idea of X… you need to take into account a combination of facets to ensure safety. | Angry blog post about X that’s oddly technical (now you see both sides) |
One, you can invoke more often (throw ChatGPT configs against the wall until it doesn’t error); the other you can invoke more deeply. So I can’t help but wonder – when we cancel out all the terms – if the timesaving sum is positive or negative. ¯\_(ツ)_/¯
Oh I love the “walk me through what I’m about to do” concept. Dry runs should be more common – especially in shell scripts…
The world would be a better place if every
install.shhad a--help, some niceprintf’s saying “Moving this here” / “Overwrite? [Y/N]”, and perhaps even a shoehorned-inset -x.Hope your r/w wasn’t eaten up by the subfolder incident (that I presume happened) :P