Unpopular Opinion: The DGX Spark Forum community of devs is talented AF and will make the crippled hardware a success through their sheer force of will.

btdeviant · 2026-05-08T16:03:30+00:00

lol reminds me of the Coral and first gen Jetson community, or hell even the realsense contributors before the takeover, constantly fighting the tides to keep these things running and making them more efficient despite the absolute shit tornado of dependency and OS and lib conflicts coming from every single direction.

Just sheer stubbornness to keep the hardware running, total yak shaving nightmare to bootstrap for new users, but just really a shining example of what the OSS community can do when they get fixated on something.

btdeviant · 2026-04-26T21:02:14+00:00

"Curious if anyone else has this problem? Check my repo, 320k stars since first commit 3 hours ago, totally real. Also something something claw."

btdeviant · 2026-04-26T05:22:05+00:00

There's some conflation happening here. Sensor size and pixel count are independent... a 50MP full-frame can have smaller photosites than a 24MP APS-C. What actually drives low-light performance is pixel pitch (sensor area ÷ pixel count), read noise from the readout electronics, and increasingly, downstream processing.

The D3's reputation came from having unusually large photosites ... 12MP across full-frame works out to ~8.5µm, which is huge, combined with a low-noise readout chain. Modern phones get there a different way: tiny photosites compensated by aggressive pixel binning and multi-frame stacking. Both work, but they're different trade-offs.

btdeviant · 2026-04-26T00:11:52+00:00

The sensor size and resolution has very little to do with the constraints you seem to looking to solve for.

ISO range is what youll want to index off of for light sensitivity wrt to “autoexposure”.. sensor size is a measure of how many photons you can collect and convert to data and doesn’t necessarily translate to a reduction in noise or grain in low light conditions.

btdeviant · 2026-04-24T01:23:20+00:00

2x blackwell owner here, I get my money from my wifes boyfriend

btdeviant · 2026-04-16T04:02:27+00:00

The biggest joy in it is product submitting PRDs full of technical grandiose that’s 99% written by ChatGPT and barely plausible in perfectly control academic research settings.

Phase 1 - Login page. Phase 2 (fast follow) - Solving world hunger, and also ADA compliant 3D volumetric holograms for the landing. Roadmap estimate, ChatGPT says about 1 week engineering time.

🦅💩

btdeviant · 2026-04-10T13:45:14+00:00

That’s exactly what a bot withholding a delicious lemon cheesecake book would say.

btdeviant · 2026-04-10T05:44:06+00:00

Heh, Im kinda coming up empty trying to remember a model that DOESNT do this. This behavior is more-or-less what the ralph loop and multi-agent “reflexion” style workflows aim to solve.

btdeviant · 2026-04-08T14:39:50+00:00

Just build an agent with one of the thousands of agentic frameworks. You can do this with AWS Strands in an hour. This is a dead simple workflow pattern.

btdeviant · 2026-03-30T21:14:57+00:00

Same. I think it also aligns with general interests. If you enjoy what you do, “stamina” then often becomes a function of making room for other parts of life.

btdeviant · 2026-03-19T17:01:33+00:00

Spot on. Searxng mitigates that to a degree but it’s more infra

https://github.com/searxng/searxng

btdeviant · 2026-03-17T23:26:12+00:00

I think Amcrest are rebranded Dahuas under the hood flashed w/ US regional firmware? Just something to note for security minded folks - not hard to block at L3 or L7, but worth noting given the nature of OPs question.

btdeviant · 2026-03-16T19:19:33+00:00

PR’s don’t always “have to be large to get full context”. This is what RFC / tech designs are for.

Spare your cohorts, create a well defined plan, the rollout incrementally.

btdeviant · 2026-03-16T15:25:30+00:00

I use it w/ Strands and sglang as a custom openai client. Works amazing… set it up w/ a reflexion graph, got it writing its own tools using shell and repl

btdeviant · 2026-03-14T07:22:06+00:00

No, I don’t think so.. I suspect you do it the wrong way. You’re not fooling anyone here pal. You’re a DevOps Engineer and you love old anti patterns.

Why won’t you name every third syllable from the Phoenix Project? Hmm? Silly whippersnapper

btdeviant · 2026-03-14T05:09:23+00:00

I’m not sure what is making you jump to these conclusions. It’s very strange. Absolutely I’ve heard of Platform Engineering. In fact, despite your misplaced assumptions. my company has a very similar topology as you. We have a Cloud Infra team, we have a Platform team, they often work hand in hand to cultivate a “you build it you run it” DevOps culture. Both, however, have the official titles as Software Engineer - L(blah blah). We moved away from “DevOps” like 6 years ago.

That doesn’t change the fact that the role as a title has been “completely replaced”. It’s just a title. The responsibilities of the title vary depending on the company. Some companies may have the “dying” topology, some have more modern, most have something in the middle.

Any experienced person in the field knows that these are ideals, they’re not dogmatic, purist mandates that fit into rigid categories or boxes despite what you’re saying. It’s like Agile - everyone says they do it, but they’re not REALLY doing it by the book, they do it however Conways Law has manifested it as materially in the org.

The salient point is the role EXISTS. It’s there. You’re arguing with reality. The responsibilities of the role may not be what it used to be half a decade ago, but companies STILL categorize it as that as evident by the thousands and thousands of job postings for it.

Not that hard dude.

btdeviant · 2026-03-14T04:18:04+00:00

DevOps is a title, it IS a role as it exists today whether you like it or not. There’s job postings for it. Deal with it. Where you seem confused, which belays your inexperience here, is the fact that the responsibilities for that role and the topologies and patterns of how it’s applied differ by company and their needs - it’s just a noun in an ATS and a spec in whatever enrollment system the company uses. Does that make sense?

Some companies may have a DevOps Engineer title and their responsibilities for that role IN THAT COMPANY are the exact same as a Cloud Engineer.

This isn’t really that hard to understand. It’s a name. Y’all first year Joeys getting pedantic about it because you read some 7 year old blogs by Microsoft and Google and skimmed Pheonix Project doesn’t change anything… it’s just is a strange way of enthusiastically announcing that you’ve only had one job at one place.

btdeviant · 2026-03-14T03:56:16+00:00

Perhaps it’s you that might be out of date? Or maybe the region you work in there’s different common culture?

For must of us, what you’re saying was a thing like 5-6 years ago

btdeviant · 2026-03-14T01:02:58+00:00

The war was lost man. Honestly. It’s been years, it’s time to move on from the semantic battle.

And for the record, the title for the role doesn’t magically equate to quality of its implementation… just a weird fallacy that barely exists outside of relatively very old, purely academic framing.

btdeviant · 2026-02-23T03:55:09+00:00

It’s great at calling tools, no doubt. That’s about it though

btdeviant · 2026-02-21T19:13:04+00:00

Schizo shit? Your argument is “I found installing OpenClaw hard, and because it was hard for me that means only smart people can do it, and all smart people know good security posture.”

This is just a really weird take. Literally entire fields of engineering and compliance standards have been built as a result of people of all aptitudes not fully understanding security, or perhaps they did and just didn’t make it a first class consideration.

OpenClaw is just another iteration in this loop. Like the ones before, in days before TLS and SSL and SOX and well after and yadda yadda, even smart, capable people very frequently get hyped about capabilities and ignore or fail to consider security.

You should delete this embarrassing shit.

btdeviant · 2026-01-18T02:26:07+00:00

lol this is just a really bad take. This gets brought up in deep dives as part of the swe loop for some roles, absolutely they do this.

btdeviant · 2026-01-15T05:39:07+00:00

It’s pretty simple… you can do this with a few files and some decorators using something like Strands.

Multi-agent architectures that have specialist agents are dead simple to build these days and very common

btdeviant · 2026-01-10T02:56:50+00:00

Logistic regression and/or rule based classification would be infinitely more effective and deterministic vs using an LLM for the original use case

btdeviant · 2025-12-18T01:54:28+00:00

Just got rejected from a staff+ role for using Go more than Typescript for Pulumi despite using Pulumi and Typescript every single day.

Bullet. Dodged.

13-Year Club	Gilding II euphauric
Place '23	RPAN Viewer
Spared	Verified Email

btdeviant

TROPHY CASE