100 karma · joined August 30, 2023
https://nizarmah.com
I’m not mitigating these risks. I literally gave models my old laptops to have fun with.
Jokes aside: Dad is a code reviewer skill that focuses on boring correct code. It's my co-worker's personal project, and I found myself using it on everything I do. My actual father remains unable to read code.
This was entirely vibe-coded, but man did it make my life easier. So I hope it helps you too.
I'd love to try this again with a simpler UI. If there's a place I can follow for updates, LMK.
It seems like your program is really capable, but I'm finding the UI extremely overwhelming.
I find myself comparing this to MIT's Scratch, and I know your tool is much more capable, but the user experience makes Scratch so intuitive.
Everything reads like a short sentence, and I can just dive in without understanding what I'm doing.
Any chance this can turn into something like "building legos"?
Blocks can be built exactly like Scratch. And, then, maybe you can map their input/output streams as a way to connect blocks (ideally inferred on the run).
And people can re-use blocks that others have built.
I know this is supposed to be a programming language, not a toy. But, selfishly, I want the UX to feel like it's a toy, so simple to discover it on my own. I can imagine prototyping stuff with it, especially if there's a library of stuff that I can use or contribute to while doing so...
Small request: When I have a document open, ask to prevent accidentally closing the tab.
Large request: Resizing pictures and signatures.
I didn't know I needed this, but now that you shared it—I NEEDED IT!
This is largely because it leaves chance for misinterpretation or miscommunication. Programming languages eliminated misinterpretation and made miscommunication easier to notice through errors.
Programming language enables micromanaging proactively, I specify the instructions before they run. I often find myself micromanaging retroactively with LLMs, until I reach the path I am looking for.
That's a really cool idea. Kudos!! A companion system should be relatively easy. It's also two single devices communicating with each other which makes things much simpler to build as well. This is worth looking closer into.
It's hard to find a one-size-fits-all solution. I don't know if satellite coverage would still be available under rubble. It's definitely valuable in other situations.
The country coverage is a huge part. My country will likely not get satellite coverage in the next 5 to 10 years. Such countries is where disaster response is worse and infrastructure is more prone to failure.
I find the "instruction app" a little limited because a person needs to be conscious, they need to be calm and collected to remember to open the app, and their phone needs to be accessible.
In its current state, providing instructions is better than just broadcasting BLE which will be weakened and lost by rubble.
In my country, a lot of first responders still rely on asking people to scream if they can hear them. Anyone unconscious would be discovered days later...
There has to be some way of providing an automated signal of life.
The comments about the physics limitations are pretty awesome. They make me wonder if we can assist it in any way... I learned about passive resonators recently. I know they have a short distance transmission, but maybe if they were part of the building material?
I need to start by learning more about the physics. I know I'm limited by it, but maybe there's window we can walk through instead of the door.
I will also try to create a monetized version for specific use. Maybe that can help fund building a solution that's publicly available.
Both of those will increase the chances of it being adopted by smartphones, like Google and Apple. That's why I switched from GPL-3.0 to MIT.
I appreciate the kind words and the awesome suggestion. Thank you!
Improvements are definitely needed with location, but the signal loss as you mentioned is higher priority and restricts what can be used for location.
I'm planning to do my homework about alternatives to help mitigate the signal loss. And from there, the options for location might be clearer.
Some of them might require you open the application the first time ever while on internet.
There are many out there (on the App/Play store) that support both use cases you mentioned, I just can't list any off the top of my head because it's been a while since I used one.
It'll be easy to find a collapsed building site. The person rescuing just needs to be close to the site with the app. Otherwise, the signal might not be noticed.
+1 regarding finding survivors for malicious purposes. I tried my best to lower the surface area of that happening. It's still possible in edge cases, like opposing soldiers finding the people transmitting SOS, but they need to be extremely close to do that.
Sadly today, money and connections are needed for r&d and distribution. And having a market that buys a tool like this in certain circumstances can seriously contribute to finding/building publicly available solutions.
I imagine such fancier tools would be less available among common folks, and more among first responders.
NASA already has the tech to detect heartbeats under rubble using radar [1]. No additional equipment is needed by the rescued. The problem is emergency response can get overwhelmed in large disasters.
If Rydberg sensors would be more common, and new tech is added to mobile devices, this can seriously shift the playing field.
I will look into this, because we need out of the box solutions. Thank you!
[1]: https://www.dhs.gov/archive/detecting-heartbeats-rubble-dhs-...