Doxin

Different variable in a different scope referring to the same thing. Normally I'd agree with giving it a different name, but both scanner variables refer to the same object in memory, so it doesn't actually matter that they are different variables in the code as shown.

I've got qwen3.6-something-or-other (also around 20GB) in 12GB VRAM with a 64k context, and I'm decently sure I could go to a 128k context without losing too much speed. it's doing around 40 tokens per second, though the initial prompt processing is a bit of a bottleneck.

MoE models are kind of bonkers.

A well designed set of buttons is much faster to open than a zipper, and about as fast to close. I've got a number of jeans with button flies where opening them is a single handed smooth motion. I've unfortunately also got a number where it's a real fight for each individual button.

Python doesn't try especially hard to stop you from doing stupid things in general. It's kind of core to the language that it doesn't. Hence no access modifiers. I think it's usually phrased as "we're all consenting adults".

As the famous idiom goes, sticks and stones may break my bones but words can leave permanent psychological scars that may never heal.

Physical violence is definitely going to leave lasting effects, but words can still do the same.

You can return data for multiple page elements with HTMX too using the "OOB" mechanism.

"legitimate interest" was supposed to be for things like remember-login cookies and the like. Not for advertisers going "my interest is legitimate because it's how I make money".

You can even get carbon fiber reinforced TPU for if you want shear strength but don't need the flexibility. From what I hear it's kind of bonkers how tough that stuff is.

There's a video of the prototype printing: https://www.youtube.com/watch?v=XB7iAFXCJQM

You can still share pre-DRM copyrighted work without running afoul of any laws. Stuff like lending out or selling VHS tapes. Copyright is concerned about copying, not about moving. Digital media just makes the line between copying and moving sufficiently blurry that companies get away with making moving impossible under the guise of making copying impossible.

Work on your reading comprehension. I never said anything was illegal. Spying means the act of keeping a secret watch for intelligence purposes. This is what they are doing. And just because it's legal does not mean it isn't wrong.

Increasing prices at busy times (i.e. surge pricing) is... to some degree defensible. Spying on people and charging different prices to different people for the same thing (i.e. surveillance pricing) is not. Can you imagine the mayhem if companies just straight up knew salary information for all of their customers?

Reduced test cases make it way easier to figure out what the actual bug is. E.g. a real world example is when I tested a "slugify" function with hypothesis. It almost immediately spat out this failing test case:

aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaẞ

Boy I sure do wonder what character could possibly be causing issues there. whereas without shrinking it might instead spit out something like

ЁЂЃЄЅІЇЈЉЊЋЌЍЎЏАБВГДẞЕЖЗИЙКЛМНОПРСТУФХЦЧШЩЪЫЬЭЮЯабвгдежзийклмноп

Which makes finding the offending character a lot harder.

It's automatic. If you post and the title gets mangled you can go back and edit the title and it won't get re-mangled, but you kinda have to be paying attention and be aware of that.

It's also just sort of generally used as easily spotted value in a hex editor. similar to DEADBEEF, ABADBABE, CAFED00D, and probably a bunch more variations on the concept. CAFEBABE seems especially prolific, getting used for -- among other things -- poison value for memory pools in plan9 and MACH-O universal object files magic number[0]

[0] https://en.wikipedia.org/wiki/Hexspeak

There's playing the game as intended and playing to the rules. People who insist on doing the latter even after being asked not to are infuriating. I've got one friend who got himself permanently uninvited from board game night for these sorts of shenanigans.

Except trams have, as far as I know without exception, specific traffic rules around them. A tram simply does not and cannot stop as quickly as a car (or indeed a bus) can. The reason that that's largely accepted is because the tradeoff is also that a tram can't really make any sudden unexpected motions at all.

If you get hit by a tram it is because you are in a place where you should have known the tram would hit you. The things are on tracks.

I find this also heavily depends on which LLM you're using. I've found chatGPT is completely awful at getting corrected, it'll double down until the cows come home. Meanwhile claude will generally adjust its behavior without too much nagging.

A linear ramp would work, but you can probably get to the end-point quicker if you're not going linearly. Something like

needle_position = needle_position * 0.9 + desired_needle_position * 0.1

is very easy to implement, easier than linear if you ask me, and should give it a nice damped movement. The constants can be tuned to go as quick or as slow as you like of course.

except if := was the default then accidentally typing ":=" instead of "==" would be the easy bug to make.

:= was bolted on after of course, and I think that was a mistake, but no one asked me, nor do I expect anyone to ;P

Maybe not. I don't know. I'm not a scientist. I have to err on the side of caution with these things because I don't know.

not really? I have a habit of using the wrongest solder for my projects. The stuff I use currently was formulated for wave soldering, no clue why it comes in spools but it was cheap.

In general the formulation is more important than the brand, and the formulation isn't /that/ important either. If it's lead free, has a rosin core, and comes on a spool, you can probably use it.

Splitting = and := in python is very intentional though, It makes writing bugs like this impossible:

    if is_logged_in=True:
        allow_access()

I've got... opinions on the way python separates statements and expressions, but there's some real benefits to it too.

> Leaded solder is easier to work with for personal projects

it really isn't if you use a nice modern lead-free solder. you'll need your iron to be about 20c hotter, but it's not like the early days of lead-free where it'd flow all weird.

A glass fiber pen is my go-to for cleaning groddy pads and pins and the like. Works a treat.

I can make no claims as to the brands mentioned in the parent post, but a 3 second heating time isn't all that fast for a real nice soldering iron. Previous job had an iron that'd heat between you picking it up and moving it over to the PCB. That one was stupendously expensive from what I heard, but I can only imagine that tech has gotten a lot cheaper since then.

Important to note that these days you really should use lead-free solder. You'll find all sorts of people going around claiming that leaded is better, but it's really not, and it's not worth the health risk. Your iron needs to be about 20c hotter than for leaded and your solder joints will look dull instead of shiny. If you find lead-free solder to not flow properly to be grainy your iron isn't hot enough.

Still wash your hands after using lead-free solder by the way. You don't want to be eating rosin or copper either.

For this example, perhaps not much, but a similar query also works. given this image[0] I queried qwen3.5-35b-a3b "where is waldo", and after thinking some got this back:

---

Waldo is located in the *center* of the image.

Here is how to spot him:

1. Look towards the middle of the beach scene.

2. Find the *red and white striped lifeguard stand/booth* on the right side of the center area.

3. Just to the left of that booth, there is a man standing up wearing his signature *red and white striped shirt*, blue jeans, and red hat with a pom-pom. He also has a camera around his neck.

---

Which is not generally something OCR can do. If you instead ask "how many horses are in this image?" you get this response:

---

Based on a careful look at the image, there are *3* equine animals (which appear to be donkeys or ponies used for beach rides).

1. One is near the top left, being ridden by someone in yellow shorts.

2. Right next to it is another one, being ridden by someone in blue and yellow.

3. On the far right edge of the image (near the water), there is a third grey animal being ridden by someone wearing a hat.

--

Now is this all anything you can't do with more boring machine learning? sure, but there's something incredibly convenient about how generic LLMs are. You don't need to train anything, just point the LLM at an image and ask.

[0] https://i.pinimg.com/originals/18/64/44/1864444c819a7adae742...

I'd recommend you'd give D a try. It manages to have a bunch of the cool features C++ has, while still largely feeling like working in C with some of the cruft fixed.

D's equivalent to "constexpr" is "compile time function evaluation". i.e. in any context where it only makes sense to run code at compile time, it will do so. This makes it trivial to do some pretty complex things at compile time. I put together an example that shows creating static arrays, dynamic arrays, and a dynamic array with a partial fibbonaci sequence all at compile time[0].

[0] https://gist.github.com/SuperDoxin/d9fcc68b73c035cbde7f0bd08...

ah I guess I sort of elided actually... saying the point I was trying to make. If it's just about showing games off to your friends (which with a course like this is pretty likely) you can point them to the emulator.

yeah if you're aiming to make a proper professional game with aims of making profit... the playdate probably isn't the way to go. But then I recon that's part of what makes it an awesome platform. It hasn't been captured by capitalism yet.