HN user
I have a ~200 line file of style rules that I copy and paste between all my projects(There's got to be a better way to manage files like that!) but I can never quite tell if it's helping anything....
I usually prompt with very specific architectures, defining classes, functions, and JSON schemas, plus what libraries I want to use, and that seems to work, most of the time.
I generally use AiderDesk with MiniMax M2.5
They made the laser drill from The Core IRL?
I have my own personal formal debrief process for larger projects: https://github.com/EternityForest/THUNDERWARS
Usually if I notice anything of interest to others, it just winds up in a group chat.
There are two other solutions, make the automation so reliable that the human skill is not needed, or make the consequences of failure low enough that you can just accept failure.
As far as I know, Places that actually care about safety apply all of them at once.
They add layers of failsafes that don't rely on humans, they make the automation better and better, and for the most critical stuff, they continue training for things that will almost certainly not happen.
And for the rare(depending on personality) cases where we care about the pilot's ability more than the result, just don't automate at all.
This inventory tracker app that runs entirely in the browser with yjs, and syncs over peer.js, that I have not been very good about using lately
https://eternityforest.github.io/Stuffer/
Not an app, but a productivity system, partially refined by telling AI every time I forgot anything and asking for research references on human error that are relevant to that specific mistake:
I've been doing LARP and tabletop most of my life, that's exactly the feel I was going for.
Most of the actual functional "backend" parts come from computer science and various research used in safety critical industries (Like Crew Resource Management), but the general aesthetic is heavily tabletop influenced.
I haven't done much with most of the explicit "gamification" elements like habit trackers use, because those usually don't actually feel like games, they're mostly just performance metrics without any story or gameplay mechanics.
I think it would be cool in theory to have some sort of XP system, but mostly everything I've seen seems too much like bookkeeping overhead.
In real TTRPGs, the points actually represent something, but with habit trackers, they're representing results that already exist automatically in the real world as a consequence of the habit.
I can't imagine that mics are going to be affected by anything that doesn't also seriously bother at least some animals, definitely not something I'd use outside of some ultra secure conference room or something.
A web based inventory management app. I've wanted to try something like this for a long time, but it always seemed completely impractical to spend a few weeks on before AI, without knowing if the entire idea is actually practical.
So far, I think it is in fact worth it, but only in specific use cases, like very rarely accessed items with no obvious place, and making sure your AV gear you bring to events comes back with you.
* Every item is a container, unlimited nesting
* Everything stored in the browser with YJS, very clunky peer.js or manual file sync available
* Select an object, click add items, scan QR codes to add those items
* There's also NFC support on Chrome mobile
* Generate random printable QR sheets(Still need to fix sticker alignment issues)
* Tracks where an item was last scanned with GPS
* Save container contents as a loadout, check contents against loadout
* Can mark a container as needing re-inventory, contents that haven't been re-added after that show a warning
Local hubs solve that pretty well, aside from still needing to update the hub.
I remember doing my own backups with rsync a super long time ago! It worked pretty well, but it didn't have compression, encryption, desktop integration, or deduplication, and adding anything would be one more script to maintain.
Now I use Kopia, no real complaints there. I used to use Borg but until recently it needed some fussy extra community package to work on Synology.
I'd love to see a new battery standard.
Something future proof for new chemistries, consumer friendly and self protected, able to be series-es and paralleled if needed, etc.
Maybe even designed to be an external part of the case like 2 way radio and tool batteries, with the option of a retaining screw for toys and tamper resistance.
A few different sizes, from keychain up to power tool, and paralleling adapters to go bigger.
The electronics would probably cost pennies in volume, just like the tech that goes into those lithium AAs with built-in chargers and buck converters that are almost really awesome.
I've been using one folder per client, one folder per project for years, with no issues, although I don't tend to work on small pieces very often, I rarely do anything that seems too small to make its own project folder.
I used to do the FHS style organizing things by category, but now I'm pretty strongly against non-isolated project environments.
Sodium ion showed up a year or two ago and you can buy them on Amazon as 12v lead acid replacements, 18650s are also available but the voltage range is different from normal lithium.
Debugging rarely works correctly between languages, and features like "find all references" usually break too. Maybe that's not an issue with Prolog because a C logic solver would also be hard to debug, but it's a problem with many template languages.
Is there an online demo? How does it compare to Opus?
Tests freeze behavior in place, and manual end to end testing can confirm that the most common paths are at least kind of correct ish.
Obviously that's not good enough, but I'd much rather have AI tests than poor test coverage.
I'm surprised there's not a lot more work on "backend free" systems.
A lot of apps seem like they could literally all use the same exact backend, if there was a service that just gave you the 20 or so features these kinds of things need.
Pocketbase is pretty close, but not all the way there yet, you still have to handle billing and security yourself, you're not just creating a client that has access to whatever resources the end user paid for and assigned to the app via the host's UI.
Mostly still just working on my KaithemAutomation project, that I maintain for creating interactive props and puzzles, plus a few trivial not yet released projects.
Right now, I'm experimenting with adding the ability to create DMX lighting effects plugins in WebAssembly, which I'm excited about.
https://github.com/EternityForest/KaithemAutomation/tree/mas...
With off the shelf options, preferring FOSS if possible, I still enjoy using and contributing to open source.
Some of the substitutions wound up being a step down in features, or required rethinking parts of workflows, but the time savings is such a benefit.
Custom notetaking tool with p2p sync-> Google keep
Custom batteries included Linux distro for SD protection, Kiosk browsers, offline docs, creative commons content packs -> a few scripts built into my control server on vanilla RasPi OS
Rsync-> Borg -> Kopia(to avoid fussing with Borg's community NAS package)
I did a similar thing a few years back, but rather than simplifying, I focused on getting rid of hacky DIY things that needed maintenance.
I got rid of almost all the customized software in my life, and the few projects I decided to keep, I aggressively modernized, getting rid of thousands of lines of original code and adding many times more tests than I'd ever had before.
It very significantly improved my life and career to not have a second part time job maintaining a note taking app.
Bookmarked!
I wonder if cloth simulation could be integrated as a CAD primitive that somehow outputs reasonable BRep geometry?
Could you take an AI 3D scan of someone's face, virtually lay a heavy cloth over it, then add whatever you wanted to make a mask?
Could you make the deformed cloth surface into one side of a cube, where the other side was flat for easily working with it, and use that to make custom pseudo-vacumformed cases for things?
Or just stack up boxes and simple shapes, and use the cloth simulation to build organic looking industrial design within a more traditional CAD workflow?
There's always going to be some maintenance, at the very least the API changes for providers you mentioned, and then there's still the reviews and testing of the C.
A mempool seems very much like a DIY implementation of malloc, unless you have fixed size allocations or something else that would make things different, not sure why I'd want that in the general case.
For "non hacker style" production code it just seems like a lot of extra steps.
Isn't PERC in chlorinated brakleen similarly dangerous?
I'm working with Extism at the moment, It's pretty nice at handling the memory allocations.
I'm not sure how well it carries over to embedded platforms though, but I'm really interested in trying.
Why would I want to have an extra thing to maintain, on top of having to manually review, debug, and write tests for a language I don't like that much?
Why is it that CI tools don't make warnings visible? Why are they ignored by default in the first place? Seems like that should be a rather high priority.
UV is taking over really fast, it seems to be much more popular any other option.
I suspect conda still has some market share too but I've never needed it.
What can you do with bash that isn't in the stdlib of python?
Generally the only nontrivial scripting I ever do is associated with a larger project, so I often already have a pyproject.toml and a UV environment, and I just add the dependencies to the dev group.
I really like the idea of a project oriented community with fishbowls and jams, and the focus on efficiency.
I wonder if there's any similar communities focused on more typical modern dev practices? It seems like the interesting tech communities are often hacker ethos focused.