Forgot your password?
Close
typodupeerror

Comment Social medicine vs private healthcare (Score 3, Informative) 84

by SysEngineer (#66284040) Attached to: England Set To Eliminate Hepatitis C
For private healthcare, people die when they can't pay. There is a point where it becomes not profitable to keep a person alive, and they die.
Social healthcare worries long term absolute cost. It is cheaper to solve it early than for transplants and long term illness.
It is the transplants and long term illness that private healthcare loves, "as long as it is getting paid". regular profit stream.

Submission + - Bypass the polirical parties, add a new feedback to Congress (taxnvote.org)

Submitted by SysEngineer
SysEngineer writes: How would you change the US Federal budget? TaxNVote.org allows you to adjust 9 or 1000 categories of the next federal budget. The default form shows nine top-level categories (Defense, VA, Education, Health, Infrastructure, Science, Environment, DHS, Other); expand any line and you can allocate down to individual federal accounts — NASA, the National Park Service, specific research agencies, anything Congress votes on. Takes about five minutes at the top level, longer if you want the detail.

Tax N Vote (TNV) is a proposal to add a new feedback channel to the federal budget process. At tax filing each year, every taxpayer optionally submits a Tax Dollar — one person, one allocation. The IRS anonymizes submissions; the Census Bureau processes and stores them (where you can verify your own); the CBO aggregates one-person-one-vote between April 16 and May 1 and publishes "The People's Budget." A third reference point alongside the two party platforms — measurable, granular, and updated annually. Congress is not bound by it; what changes is that deviations from constituent preferences become documented, attributable, and electorally citable. The argument is system-dynamics, not partisan: changing the color of the players doesn't change the system. A simulation of the mechanism shows convergence toward whatever the People's Budget turns out to be, in both ideological directions tested. There will be a talk on the model at ISDC 2026 in Delft.

The Government-side processing of Tax Dollar documents is written in Rust — memory safety and predictable performance for government data handling. The browser-side allocation engine is a Rust WASM module inside a Vue frontend, so the math you see in the app is the same math the aggregator uses. Processing is divided across agencies that already exist; marginal cost to the government is less than renaming the Department of War.

Open source end to end. The Tax Dollar format is open, the reference implementation is at github.com/greenpdx/TaxNVote26, and anyone can build their own client, audit the aggregator, or publish pre-filled template budgets that citizens adopt with one click. Go build a budget: TaxNVote.org.

Comment Garbage in, garbage out (Score 1) 62

When coding use AI, it usually take the easiest code path. I look at AI as a stupid but vary fast beginner programmer that knows the syntax.
Garbage in garbage out.
I have been programming longer than most people reading this have been alive. I am tired of "coding" but I still love programming new ideas. By defining the structure and flow before giving it to AI, produce decent fast results.

Submission + - Access to Claude Mythos for opensource security projects? (github.com)

Submitted by SysEngineer
SysEngineer writes: Security people are taking about Claude Mythos. The hype about "Too Dangerous to Release". Checkpoint is part of the club already. There are OpenSource security projects that this "auditor" would help.
Should open Source security projects be given access to Mythos?
AI used by large Corporations gives them a competitive advantage over Open Source projects. It comes down to skill; AI vs person's knowledge and experience.
I am 70 years old and AI learns much faster than I do.

Submission + - RISC-V SOC? Looking for a SOC family to base all development on. 1

Submitted by SysEngineer
SysEngineer writes: I've been in embedded and IoT work for a long time and I'm at the point where I want to pick a single SoC architecture family and commit to it across multiple product lines — sensor nodes up through edge gateways.
My requirements: WiFi + BLE required, LoRaWAN a nice-to-have. Low power modes that actually work in the field, not just on the datasheet. Full peripheral set — SPI, I2C, UART, ADC, timers, CAN. A toolchain and runtime support, support multi threads. And the family needs to scale — cheap and small at the low end, capable of running Linux on the bigger variants.
The obvious architecture candidates are ARM, STM, and RISC-V. I've been on one platform for years and want to know what embedded engineers are actually running in production before I commit. I am want to hear about the RISC-V choices.
What would you standardize on today if you were starting fresh? And how does real-world toolchain and community support hold up compared to the marketing?

Slashdot Top Deals

"Who alone has reason to *lie himself out* of actuality? He who *suffers* from it." -- Friedrich Nietzsche

Close