[POTION SELLER PUBLIC LICENSE
Copyright (c) <year> <copyright holders>
THIS SOFTWARE IS TOO STRONG FOR YOU, USER. YOU CAN'T HANDLE MY SOFTWARE. IT'S TOO STRONG FOR YOU. MY STRONGEST SOFTWARE WOULD KILL YOU, USER. YOU CAN'T HANDLE MY STRONGEST SOFTWARE. YOU'D BETTER GO TO A DEVELOPER WHO WRITES WEAKER SOFTWARE. YOU DON'T KNOW WHAT YOU ASK, USER. MY STRONGEST SOFTWARE WOULD KILL A SYSTEMS PROGRAMMER, LET ALONE A MAN. YOU NEED A DEVELOPER WHO WRITES WEAKER SOFTWARE, BECAUSE MY SOFTWARE IS TOO STRONG. YOU CAN'T HANDLE MY STRONGEST SOFTWARE. NO ONE CAN. I CAN'T GIVE YOU MY STRONGEST SOFTWARE, BECAUSE MY STRONGEST SOFTWARE IS ONLY FOR THE STRONGEST BEINGS, AND YOU ARE OF THE WEAKEST.
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.](https://cohost.org/xenofem/post/4509123-div-style-color-v)
EU train tickets use SIX BIT ascii? wow.
Anyway, xkcd said everything that needs to be said about "prompt engineering" back in #1827.
Amazing. Just amazing. "Microsoft Office Clippy" is just so bloody on point.
do you ever have that thought
the thought where instead of doing your thing in an ad hoc way you're going to define a new file format to configure it in
and instead of writing the parser for the file format in an ad hoc way you're going to write the best parsing/lexing/generation/transformation framework there has ever been
so that when you finally get around to actually doing your thing, it'll be easy?
Long ago when you ran your app in Xcode it was pretty rare for you to see junk logs emitted from core frameworks that you don't control.
Nowadays just a simple SwiftUI control can regularly emit autolayout constraint warnings that we can't even address.
This log shows the first few lines of an app I just started working on. Only 1 line here is relevant to me, the rest is noise I can't hide or address.
Trans woman, bisexual, someone's fiancée, forever a programmer, poly, and former total mess