2,196 karma · joined September 12, 2019
These days I mostly do r&d for custom sensors, custom hardware and firmware to drive them, data analysis, physics simulations, etc.
Mostly using c#, f#, python, fortran, c, verilog
But bonsai is basically trash on real agentic coding work. I've tried both bonsai models, all the quants, messed with the hyperparameters, tried to fine tune (didn't succeed), and it just kept looping or failing to finish tasks. Qwen3.6 35b-a3b is my current go to for agentic work for any systems under 24gb vram, although honestly I'm not sure the dense qwen3.8 27b is meaningfully better. The main difference I see is it does a lot more testing attempts and burns a ton of tokens + compactions, so every task it takes 1.2-2x as long as 35b-a3b does. But the quality of the results is comparable.
As for speed it's mainly tied to rpm and the market decided no one wants higher failure rates / lower mtbf for marginal speed gains.
If you need speed and capacity, throw an ssd or two in front of a raid disk array for caching with primocache or whatever.
PDFgear is free of charge, and we don’t generate income through any hidden means. We Do NOT misuse or sell user data and we Do Not display ads. Here’s how we keep operations running:
We’ve secured investment to cover operational costs, including team expenses and technology like the ChatGPT API. We’re also experienced in optimizing technology usage to manage costs more effectively.You are far from the embedded world if you think 1 minute here or there is long. I have been involved with many projects that take hours to build, usually caused by hardware generation (fpga hdl builds) or poor cross compiling support (custom/complex toolchain requirements). These days I can keep most of the custom shenanigans in the 1hr ballpark by throwing more compute at a very heavy emulator (to fully emulate the architecture) but that's still pretty painful. One day I'll find a way to use the zig toolchain for cross compiles but it gets thrown off by some of the c macro or custom resource embedding nonsense.
Edit: missed some context on lazy first read so ignore the snark above.
> to fix your busted drive, just nuke the boot sector and send it
> bash
> dd if=/dev/zero of=/dev/xxx bs=512 count=1 conv=notrunc
The tol palettes are the best looking colorblind friendly palettes to me. Most of the others get complaints from non colorblind users about looking bad/desaturated.
But truthfully 90% of work related programming is not problem solving, it's implementing business logic. And dealing with poor, ever changing customer specs. Which an llm will not help with.
Except maybe arithmetic gotos designed to minimize the number of functions. Those are straight evil and I'm glad no modern language supports them.
Flask/quart are painful to work with due to horrible documentation in my experience, but they're popular too. Quart is just an async rewrite of flask by the same owners.
Litestar has a half baked comparison chart here: https://docs.litestar.dev/latest/