Policy officers are mis-using this powerful, hugely invasive massive surveillance tool? I am utterly shocked!

I would NOT get tattooed for a job interview. I WOULD get tattooed for a JOB. Yes I'm that desperate. YES This is highly unethical.

Interesting -- I thought OnePlus batteries were supposed to wear down LESS than other phones specifically because of their "High amp" charging technique versus "High voltage". After some quick research it seems this is mostly due to the heat generated during charging happens in the charger brick instead of the phone, keeping the heat away from the battery. But I suppose in real world situations it may not have a huge effect.

YES!!! I fucking hate all these stupid web-pages-as-Apps

I would say quantum computing. It's one area you can't just tell an LLM to solve for you (yet, until the material and solutions are out there of course).

This is why I always work at a new company at least 6-12 months before making any major changes. I use that time to get into the flow of how things are being done (even if I think they are not efficient). I may make some suggestions but that's it.

Of course, I'll probably never get hired again anywhere so it doesn't matter anymore.

In 6-12 months you could ship a new product or a large feature. This strategy might actually put you on a performance improvement plan instead.

A company/manager that would PIP you during onboarding doesn't understand the craft and does not deserve you.

That's why I said I'd suggest things. And of course I'd go along with strategic plans. Every company is different -- you'd be surprised at how many shitty [small] companies are out there that are actually profitable and want to keep things the same, refusing to do anything differently.

Much respect -- at first glance when I saw the animated gif I thought this was just a project making assets from scratch for an existing game engine (e.g. Doom or Wolf 3D) but then I realize it's creating all the game code from scratch too! (But using similar techniques from the old days). Amazing work.

that sounds awesome. sad that something like that probably would not work well in USA. don't have the culture for it. too many pieces would get lost.

> that sounds awesome. sad that something like that probably would not work well in USA. don't have the culture for it. too many pieces would get lost.

I think the idea of "Netflix for LEGOs" started where one might expect X but for Y services to start - California.

We used one of these services in the USA somewhere nearing 10 years ago. Looks like they're still around at https://netbricks.biz/ - but I also see https://brick-library.com/ and https://brickdrop.co and wouldn't be surprised if there's more. It worked great. I detected zero incompatibility with my being from the USA. I didn't eat or carelessly throw away a single brick.

From a search it look like Pleygo was the first such startup from 2012 and based in San Jose / Santa Clara, but is no longer around.

I would assume it'd be pretty easy to have a system to count pieces and replenish lost ones. Actually, I'd be surprised if the German scheme doesn't already work like that. I don't see why it couldn't work.

This can only work in Japan and Germany, I imagine. Maybe in Korea/China/Singapore with severe financial penalties and deposits.

This is a very good intro to systemd timers -- I think you convinced me to finally start using them. Love the "list-timers" thing as well. With cron, it never seemed easy to me to get a picture of all the cron jobs running on a box. I'd need to check crontab for all users, as well as /etc/cron.d/, as well as the daily/hourly/monthly directories.

And in fact I do have a use-case for needing to run something ~5 minutes after the system boots and then every ~12 hours onward from there. It's great that systemd timers has me covered!

Thanks for the kind words! Especially given how ubiquitous systemd is now, skilling up on the toolbox with commands like `systemd-analyze` and `systemctl list-timers` feels super valuable.

that's impressive -- nice work.