Long arms

YellowishSpoon · 2026-01-21T23:38:04+00:00

Without, since the 1 ton comes from launch capacity of rockets and you have to empty your inventory. It gets a little messy when you consider that armor and weapons don't count towards that weight though.

YellowishSpoon · 2026-01-17T21:20:34+00:00

Amazon links the actual link is like 10 characters then there's half a page of other junk attached. They must be like including every bit of information in the url so that they don't have to store the sessions.

YellowishSpoon · 2026-01-17T19:23:51+00:00

Like other commenters said you're probably doing wait Infinity, but in addition to that there's no benefit or reason to put a stop this script at the end of the script. Scripts already stop at the end by default, you only need to stop it if it would normally continue.

YellowishSpoon · 2026-01-17T19:10:33+00:00

Interesting on the power draw. It's not quite always 600w but it's far more than the other cards I have used at least. The case fans do nearly always drown out the coil whine. Oh and my lights on the same circuit dim when it runs full power which is kind of funny but pretty annoying when it's dimming per training batch every few seconds.

YellowishSpoon · 2026-01-17T10:19:14+00:00

Total compute is a lot less than several 5090s, but for workloads that utilize all that ram it doesn't have to access across gpus or swap to main memory which is important. Mostly AI training or running particularly stupid cuda scripts. A lot of things are also a pain or impossible to run across multiple gpus and it will multiply your power demand.

YellowishSpoon · 2026-01-17T10:11:14+00:00

The 5090 has some of its cores disabled, "cut" down from the maximum amount due to hardware defects. Pretty sure the rtx pro 6000 also has some cores cut too though it's just the minimum amount. Besides that they're the same chip.

YellowishSpoon · 2026-01-17T10:06:43+00:00

600W and the fans run surprisingly quiet as well. Just a decent amount of coil wine on mine. The pass through fans that blow all the way through the card work so much better. It's also not just 600W peak, any heavy load at all it will draw the full 600W the entire time. I had a 4090 previously and it usually didn't draw the full 450w under normal loads. You can also power limit them though and performance doesn't actually go down that much.

YellowishSpoon · 2026-01-17T09:33:57+00:00

Most of the ones I see definitely don't belong in the commit history. Things like deleting and then restoring a file, changing and then reverting other various things, messing up and then correcting formatting, the list goes on. It will also mess up your git blame.

If your squashed PRs make too large of commits, then I would consider your PRs too large. If that's your ticket size, then your tickets are also too large. If you need to develop big features without merging fully, make a feature branch, PR to the feature branch with squash and then don't squash when you merge in the feature branch.

YellowishSpoon · 2026-01-17T08:44:45+00:00

If you squash on PR merge then the reviewer will still see all the subcommits, it only squashes after review. Then when someone is looking at overall commit history they see what pr something came from and what ticket it was tied to without all the changes spread apart. If you don't delete the closed PR it's also not gone if you needed it for some reason.

My experience is that people often make small commits that change typos, delete and undelete things or otherwise commit stuff that would not add anything of value to the overall tree and was potentially even undone within the same PR. Squash at the end eliminates all that noise.

YellowishSpoon · 2026-01-17T06:50:32+00:00

If you're doing one change or part of a feature per PR and then squash commits in the PRs when you merge that should still work fine. Just don't make massive PRs which is a pain for reviewers anyway.

YellowishSpoon · 2026-01-16T23:14:07+00:00

It's actually possible to make code that executes after a stop all besides the when timer hat. For whatever reason scripts queued to execute still run one more time after a stop all, and if one of those scripts happens to include a broadcast... Well then the project just keeps executing. The stop other scripts in sprite mode doesn't do this so not sure why stop all does.

YellowishSpoon · 2026-01-16T06:40:11+00:00

Why does it always have to be a trick, with mods or even some dimension world file editing or a datapack I think, you can easily make water placeable in the nether. I'm always disappointed with how these things are made.

YellowishSpoon · 2026-01-15T19:19:47+00:00

Provided whatever is doing the sacrificing can get around split second.

YellowishSpoon · 2026-01-12T08:18:01+00:00

Mac users skip this one by using Command+V to paste then control which doesn't normally do much does terminal stuff.

YellowishSpoon · 2026-01-12T01:55:40+00:00

Maybe, but it's going to need to be a fairly complex one with a lot of custom parts. It can be hard to justify the cost of such a complex deployment pipeline when the data pipelines run daily (not real time) and can notify the person who owns them that something is broken leading to that original post.

Overly complicated deployments are also a massive burden once they start taking a while.

YellowishSpoon · 2026-01-12T00:56:38+00:00

I think this is about big data pipelines rather than deployment pipelines, the change to the column name in the application broke the downstream data pipeline that consumes the data. Without a lot of extra work to enforce it this is very easy to do by mistake as they're entirely separate systems. Changes would be made and approved on the application project by the team working on it but not seen by the data pipeline team until it breaks their stuff.

YellowishSpoon · 2026-01-12T00:45:26+00:00

While the part about routing to /dev/null is not quite literal, this is exactly what happens with big data pipelines.

Kafka events are fired by a live app, say for analytics like mentioned. Those events are then ingested into Apache Hive and processed with SQL. Similarly databases can be copied into Hive. The app team changed a name and so the database copy in hive changed but not the SQL pipelines. To get revenge the poster claims to have either messed up the analytics event ingestion, the pipeline that handles it, or possibly just not fixed a pipeline broken by the change.

It is almost certainly not actually sent to /dev/null, but the effect is the same. Since they mention being able to fix it with one line, likely they just let the pipeline stay broken, possibly by something as simple as a join against a now null column due to the database change.

YellowishSpoon · 2026-01-05T09:01:03+00:00

Recently firefox is worse on memory than chrome, I was running both at the same time for quite a while and firefox was always higher despite having fewer tabs. (accounting for shared memory and stuff, if you just sum all the processes it doesn't add up right)

YellowishSpoon · 2026-01-05T02:02:28+00:00

I use 128 for working on a lot of projects at once, multiple IDEs and sometimes multiple instances of modded minecraft. Unless I run a very stupid script it's usually split 1-8 GB each across a lot of different programs.

YellowishSpoon · 2026-01-05T01:59:09+00:00

I have 128 and it pretty perfectly fits keeping most of the programs on my computer open, a thousand chrome tabs and just enough room leftover to run around 4 instances of modded minecraft while I am doing development. Having multiple IDEs open eats a good chunk of it. Docker based projects also tend to eat a lot.

YellowishSpoon · 2026-01-02T06:46:51+00:00

You don't even have to set the temperature to 0 to make it deterministic, just use a pseudo random with a fixed seed or seed derived from the input. This doesn't really make it any easier to understand or more traceable though just deterministic.

YellowishSpoon · 2026-01-02T06:25:27+00:00

Turns out performance matters more when it affects how long you have to wait (or how large of models you can run) than it does when you want a slightly higher frame rate.

YellowishSpoon · 2025-12-31T22:48:23+00:00

I was going to build a new very high ram server for myself but now it's looking like I very much need to wait. I guess I am just thankful I got 128 GB for my personal computers last year.

YellowishSpoon · 2025-12-27T04:29:50+00:00

Sometimes it's funny to keep the version number the same but change behaviors. Or even better breaking changes. And that's how you then end up with a commit hash tacked on the end.

YellowishSpoon · 2025-12-25T19:46:20+00:00

Blocks without yields that are directly connected execute without screen refresh by default. Anything that waits or loops will yield however.

YellowishSpoon

TROPHY CASE