hoshi sato, multipass!

this is based on the Album art of “Lateralus” an album from the band “Tool”.

https://standardebooks.org/ for public domain works.

and other ebooks i own are most likely from https://www.humblebundle.com/

subscribers and something called bits of which i dont know the purpose.

• avoid automated documenting tools

the output of tools like sphinx, javadoc and so forth is a good starting point, especially if you feed them properly commented code.

the rule “garbage in, garbage out” definitely applirs here.

I’ve seen enough programmers blindly copypasting code from stackoverflow and other forums without thinking and never understanding the thing they just “wrote”, to know that tools like copilot won’t make programmers worse, they will allow more people to be bad programmers.

people need to read more code, play around with it, break it and fix it to become better programmers.

the touchpads atleast feel like the ones on the steam controller.

flickstick is a control scheme where your stick only controls the camera horizontaly, so if you push the stick down you’ll spin 180° if you push it to the right you’ll turn until your character faces to the right and so forth.

deck is mostly more input options (right stick, d-pad, 4 back buttons instead of 2).

the biggest difference is the placement of the touchpads imho, as i cant use both shoulder buttons and the touchpad on a side without adjusting my grip, but that only mattered in shooters for which i use flickstick on the deck and not the right touchpad.

parquet is cloesely tied to the apache foundation, because it was designed as a storage format for hadoop.

But many data processing libraries offer interfaces to handle parquet files so you can use it outside of the hadoop eco system.

It’s really good for archiving data, because the format can store a lot of data with relatively low disk space, while still providing ok read performance because often times you won’t need to read the whole file due to how they are structured, where csv files would be a lot of plaintext taking up more diskspace.

since none of your examples add anything of value in the body: a plain old 403 is enough.

response bodies for 400 responses are more interesting, since you can often tell why a request was bad and the client can use that information to communicate to the user what went wrong.

best error code remains 418, though.

Tender is the Flesh by Agustina Bazterrica

Just started, premise is interesting, i hope Marcos becomes a bit more than our depressed tour guide for this bleak world.

Berserk by Kentarō Miura Mangas count, don’t they?

Just got the second volume of the english deluxe edition, and so far the drawings alone where worth the price.

The first Volume was basically an action packed rush through a grim dark world fighting demons, but the second volume seems to be a flashback to Guts youth and seems to focus more on Guts inner demons and how growing up as part of a mercenary band shaped and damaged the black swordsman we got to know in volume 1.

and maybe don’t butcher every shot of the movie thats based on a franchise known for somewhat krass humour and mowing through countless hordes of enemies by trying to make it pg-13.

for receipts and such paperless ngx is good. that won’t track your repairs or inform of you of likely maintenance problems, but that and a spread sheet sounds like a good start.

various communities on feddit.de have a pinned post on it

e.g.: c/dach

germany has an official repeating two week long meal plan which allways ends with pizza day. not adhering to the official plan is considered a crime and could be punished with two years in jail, a fine of 200 000 € or in especially bad cases with the revocation of ones drivers license.

nah, apparently the user works on sundays and get pizza at their workplace, but not today.

pizza day was canceled so they made those memes.

look into local dns servers if you want multiple machines to use your local domains if you only want a single windows or linux (and probably mac) computer to use the domain to access a specific local ip an entry in your etc/hosts file would be enough

sounds like you want a MultiKeyMap and a way to store the data from which you build the map, so i’d suggest to look up that data structure. incremental search could than be implemented by filtering on the key sets or subsets of it.

https://github.com/docker-mailserver/docker-mailserver should be able to do it.

if i remember this in 6 weeks i’ll check the setup at work.