kawogi

AIded development?

In theory, air-gaps can be circumvented by bribing or blackmailing people, which is in reach for an LLM/agent.

I think the term "AI incest" would sum this up :)

While I'm waiting for my Kia EV3 to arrive, I'm desparately trying to figure out which wallbox I need to buy to make use of V2H/V2G. Everything claims to be "ready", but I still don't know whether V2H/V2L will be DC or AC. Which protocol do my smart meters have to provide? What about the PV-inverter? How many apps will I need? How many cloud accounts? What about island-operation? Will I be able to use Home-Assistant for everything? What about feeding in the flexible pricing of my power provider? Another App/API? Which node in this hairball will have which role? Will the car decide when to charge? Or the App? Or the Wallbox? Or its App?

I'm drowning in theoretical options and I'm left with the feeling that everything seems to be possible in theory, but I won't find a solution that works in practice. There are just too many protocols and regulations at play.

Would have loved to wait another year until the dust around these topics have settled a bit, but the old car broke too early :( (sorry for the rant)

IIUC that was meant as an intermediate step (which isn't uncommon), which IMO makes the translation way less exciting.

The interesting part will be whether they can transform that "mechanical Rust" into something idiomatic. I'm waiting ...

In my experience, it absolutely does (at least if you use it idiomatically). Using the type system (esp. enums, Result and newtypes) makes a good bunch of invalid states irrepresentable.

This also helps to focus on the remaining things that could go wrong.

The integration of unit tests also lowers the barrier to just sprinkle some tests in, if you're unsure that you got an edge case right. Anf clippy (not stricly the language, but still kind of a core component) greaty helps to stay on the idiomatic track.

No silver bullet of course, but I never had so few runtime issues with any other programming language so far.

What logic bugs did you encounter the most?

edit: mobile typos

I had no troubles targeting an ATTiny13A with Rust.

(had to disable debug symbols, though)

Why should that be any harder than C?

IIUC only 50k LoC are non-test code, which improves the metric. Whether that's enough tests still depends on the code. If most are getters and setters, the coverage might be ok.

I often wish this type existed, but didn't find a way to define the niche value for the compiler to optimize the None-case.

Do you know a solution to this?

Support for Firefox on Linux is still only in nightly (unless that changed "very" recently)

This blocks progress (and motivation) on some of my projects.

LineageOS was just the easiest for me personally (was already installed anyway). But aren't there parental tools to lock down phones for non-tech people?

Another middle ground would be to insert no SIM card (my kids only had access via WiFi at first) or to disable mobile data.

Maybe my kids are special, but so far it was enough agree upon rules about what they are allowed to do. As soon as they break the rules they will loose some of their benefits. No rule works for everyone, but simple "no" to a technology that has so many upsides for our family life is also nothing for me.

Edit: also "selling a locked-down phone" is exactly NOT a solution. Parents will have to learn the up and downs of this technology and apply an individual solution to their situation.

> Initial results from a groundbreaking study by the National Institute of Health reveal that MRI's found significant differences in the brains of children who use smartphones, tablets, and video games more than seven hours a day.

Reminds me of "Every single person who confuses correlation and causation ends up dying".

Jokes aside: "more than 7 hours a day" is a _quite little more_ than the 0 hours the site is asking for. Also I'd guess it might make a difference whether the kids are using a drawing app, tiktok, learning a foreign language, reading an eBook, playing a shooter, gambling, …

Who will teach them how to (not) use them once they have one? I mean things like privacy, phishing, social media risks, addiction, subscription fees, etc.?

I think the possession of a device isn't the risk itself.

So, no flexibility, spontaneity? So far we had:

- "I'd like to stay with a friend after school - they'll drive me home after dinner", "Sure, thanks for the info, have fun"

- "Fire alert, I'm fine but bored"

- "Had to help a friend with an accident, will be home 1h later approx"

- Bus didn't turn up, uses app to improvise an alternative connection

- asking teachers about details from the lessons

- getting a news-feed from school

- looking up the schedule if things change

- manage their calendar and todo-lists

- set an alarm/reminder

So basically "everything" an adult does with their phone to make their lives easier.

After that there's enough brain left to learn that social media is something that needs special attention