Some of their earlier videos go into a lot of detail on the safety interlocks (including that the radiation near the device can be lower than ambient because it's basically a large chunk of shielding :-)
As for pricing, https://news.ycombinator.com/item?id=45392896 had some numbers from 5 months ago. It seems like the kind of thing that you'd want as a nearby service, unless you needed to do continuous inspection (they have some automated conveyor sampling products too, it looks like.) My last company had a few 3d-printed components that would have been interesting to spot check after wear testing, but for a lot of things, the competition for the scan is "open it up with a screwdriver" :-)
With Open Camera, my device (and seemingly many others) have phantom cameras with IDs that crash Android's camera server if accessed. When that happens I have to restart my phone. Open Camera does not have a way to blacklist those. There are several issues open about this on the issue tracker but they have been open since 2020.
The other two prominent open source camera apps are Fossify Camera and PhotonCamera. Fossify Camera does not support multiple lenses yet. PhotonCamera is nice because it does image processing and handles my camera lenses correctly but it's UX is janky (on my device, with default settings, taking a photo takes 7-8 seconds and quitting the app before the process is complete loses the image), it's not on F-Droid and it doesn't automatically switch between lenses with zoom changes. There's also FreeDcam but I'm not a professional photographer and I'm certainly not going to buy a color calibration reference card that costs more than a hundred dollars.
It sucks that on my phone with /e/OS, instead of using a FOSS camera app, I resort to using Pixel's camera app with internet permission disabled to be able to take advantage of my hardware.
what's truly incredible is that this person is selling bootcamps.
the things they "didn't realize" or "didn't know" are basics. they're things you would know if you spent any time at all with terraform or AWS.
all the remediations are table stakes. things you should at least know about before using terraform. things you would learn by skimming the docs (or at least asking Claude about best practices).
even ignoring the technical aspects, a tiny amount of consideration at any point in that process would have made it clear to any competent person that they should stop and question their assumptions.
I mean, shit happens. good engineers take down prod all the time. but damn man, to miss those basics entirely while selling courses on engineering is just astounding.
the grifter mentality is probably so deeply engrained that I'm willing to bet that they never once thought "I'm totally qualified to sell courses", let alone question the thought.
tl;dr The amount of fossil fuels it takes to make stuff is not nearly as big as the amount of fossil fuels we use to transport ourselves in cars.
Consumption-based accounting of CO2 emissions is harder than production-based accounting, but it allows us to see more clearly what the CO2 cost of our lifestyle is. It's been ~5 years since I looked at one of those in detail, but I don't think it's changed much since then. The big takeaway for me was that for the US, which has massive emissions compared to Europe countries, urban/suburban design and land use was by far the biggest determinant of CO2 consumption, followed by income/wealth. Despite their higher wealth and ability to spend more, residents of urban areas have for lower emissions than suburban residents.
Saw the edit: I think that clarification was important.
The core point resonates with me personally. The shift isn't about writing less code, it's about where the real judgment lives. Knowing what to build, how to decompose a problem, which patterns to reach for - and critically, when the model is confidently wrong. Without that foundation you're not moving faster, you're just making bad decisions faster.
The scope point resonates too. Small, well-defined tasks with verifiable output is where agents actually shine.
I recently co-authored an article [0] that attempts to explain the various engines and formats.
My personal recommendation would be to just always use "lualatex", or "pdflatex" if you have older documents that won't work with LuaLaTeX for some reason. I'm also a big fan of ConTeXt [2], but I realize that that isn't a practical option for most people.
Sounds lovely. Our kids enjoyed the local bikepacking trips we did this summer, perhaps our next will visit the area. (In the off chance you have personal recommendations for bike touring companies/routes, let me know.)
This site is underweighted on OLAP. Columnstores were invented for precisely this use case; nobody in the field wants to normalize everything.
Which brings me to the question, why a rowstore? Are Z-sets hard to manage otherwise?
Another aspect of wide tables is that they tend to have a lot of dependencies, ie different columns come from different aggregations, and the whole table gets held up if one of them is late. IVM seems like a good solution for that problem.
It's true, but most of the cultural innovation I'm aware of, from Bach to Coltrane to Hendrix, came from people who could make art their life, largely by paying the bills with it. I don't think we'll lose art entirely, but we might lose the greatest artists.
So I've actually been putting more effort into deliberate practice since I started using AI in programming.
I've been a fan of Zed Shaw's method for years, of typing out interesting programs by hand. But I've been appreciating it even more now, as a way to stave off the feeling of my brain melting :)
The gross feeling I have if I go for too long without doing cardio, is a similar feeling to when I go for too long without actually writing a substantial amount of code myself.
I think that the feeling of making a sustained effort is itself something necessary and healthy, and rapidly disappearing from the world.
Hey man, read your breakdown on the Moongate architecture. Using Source Generators for DI and Lua for behavior decoupling so you never have to recompile C# is a beautiful setup. Strict domain separation is the way to go.
I saw your 'What's missing' list includes NPC AI.
I build AI agent workflows. Instead of building traditional, boring finite-state machines for NPCs, what if we plugged an LLM microservice into your Lua scripts? We could give key NPCs actual contextual memory and dynamic dialogue. Players could physically type to a merchant, negotiate prices, or ask for rumors, and the NPC would generate a response strictly within the lore of Ultima, triggering the correct Lua events (like handing over an item or opening a door).
Since you have the packet layer and Lua environment solid, the integration would be incredibly clean. I'd love to contribute and map out the AI logic for this if you're open to exploring it.
A key thing in this graph is that it doesn't seem to correlate to the rise of code assistants. That is a (relatively) recent last year thing from my point of view. Yes, they were there before, but they hadn't really hit in a way that I think hiring decisions had shifted because of them. This is just tech laying off, not AI taking jobs.
Not what the article is talking about, but I think betting against x86 in terms of the investment of companies (not individuals buying PC parts) has been a pretty good bet!
Being long AAPL and NVDA has crushed AMD and INTC, and that's with AMD's gains which I would argue are mostly due to non-x86 chips. Even Broadcom + Qualcom + ARM has been a better basket to hold for most of the last 5 years.
While PCs still need x86 because of the standardization the article talks about, more appliance-like computers like mobile phones and even server hardware have stolen a lot of market share and I think are the dominant way people will do their computing in the future.
Love how simple this is! It would be great if there you were able to add siblings without having a parent added first. And being able to add a child with only one parent present as well--there's an error that states the parent needs a spouse before adding a child.
What's fascinating to me is it looks totally different for me when I turned off my adblocker. We are i guess targeted differently by these ad companies. https://files.catbox.moe/9einuv.png
The creator of this dashboard is Israeli - given some of the questions about the sword/shield icons, labelling of countries as belligerents/targets etc. I felt it was relevant to state this. Not to mention selective information bias.
> Oh and roughly 65M of sea level rise as the planet shifts to a snow/ice-free mode
65M seems a lot bigger than the 3.6mm/year rise we are seeing today (with +1.5C in warming already happening). Where did you read that we will get 65M of sea level rise with 1.5-2.5C more warming?
i feel like i misunderstand the UI - it seems to show coalition strikes mostly being intercepted? or does the bottom row refer to strikes against coalition forces?
A 2026 AI Engineer is a 1996 Software Architect. I don't need to be the one manually implementing the individual widgets of a system, I can delegate their implementation to developers (agents).
I'm being a little facetious, but I don't think it's far off the mark from what TFA is saying, and it matches my experience over the past few months. The worst architects we ever worked with were the ones who couldn't actually implement anything from scratch. Like TFA says, if you've got the fundamentals down and you want to see how far you can go with these new tools, play the role of architect for a change and let the agents fly.
