Reminds me of the viral video where a dad asks him children to instruct him on how to make a peanut butter sandwich. If they were vague, he would exploit any ambiguity in the instructions against them - like "rub the knife on the bread" before it had any peanut butter on it :)
The military knows how to do this - and has a strong reason to. If your documentation cannot survive the death or resignation of the man, team or department that wrote it, you can't build generational knowledge. Look up the mil spec for chocolate cake (skips my mind where it is in my library) for example.
5G will not make this better. The problem for your (our) part of the world is coverage, and that needs to be dealt with using more cell towers. A 5g transition will possibly compound this problem, by needing more towers for the same coverage area, and by making those towers and the infrastructure for data transport to them more expensive.
IMHO 5G is a great idea for cities, ideally mini building-as-a-city size projects, where you can provide coverage to a lot of people really fast. But for penetrating and providing reliable coverage for wider areas, 5g isn't the right thing. Hopefully the next iteration works towards that.
It's also been interesting to see Kerala change over the last decade - I see things change as snapshots everytime I'm there, so I feel it more keenly. Speeds are a lot faster when they're available, but tower-to-tower and carrier-to-carrier handover is still a massive problem. Part of it's hardware, with the signal just not reaching you. The other part is still software, where some towers just won't let you go, or refuse to upgrade you. I've sat next to people who were getting 4g on the same carrier, same phone, while I was getting 3g and had to restart.
Scrolled to the article, finished reading, looked at the URL and wondered if insurers had gotten a lot more serious with their tech writing :)
Honestly though, thanks for this. I had wandered into Firebase a number of times, and always found hydrant not ball. After reading through and using it for a bit, the same problems you mentioned (why is 1MB the limit? Why isn't that abstracted away with gracefully degrading performance?) ran fast and ran far.
Did not know there was a better one. Would you say it's worth building on, still? Or is it at risk of cancellation by the Cube?
K6 is my usual go-to, since it can import Postman request files (which makes it easier to simulate more complex requests with file uploads and such), and is highly configurable.
Postico is amazing. I recently moved out of MacOS, and I can honestly say that it's the only tool that keeps making me want to move back. pgAdmin is a right pain.
Thank you! I was halfway to building JSON escaping as a tool for myself. I'm working with AWS SES templates at the moment, and the manual steps to - validate handlebars, inline CSS, escape JSON, upload and then see what failed is killing me.
Honestly the first and sometimes last step is to just not be afraid to break things.
If the author had been as afraid as me of reverse biasing the circuit, he might not have gotten started. Try things, and if something breaks there's still something you can learn from that behavior.
I was just about to comment with the suggestion of adding a low pass filter for nyquist transformation, but reddit beat me to it!
Still amazing that it's a self-contained audio device, no actual addressing or protocol needed. It would be interesting if (as the author thinks) these were custom ASICs with built in songs from the factory, or some combination of EEPROM and decoder/driver chip. Does anyone remember what they sold for way back?
I'm glad that logic programming isn't completely dead. I think once gradient descent has filled it's niches well and the AI summer quietens a little, we might see a return to knowledge engines and decision trees as a useful complement (if not a supplement) to solving the class of problems not well served by neural nets.
Unfortunately I ended up shelving the project once it became clear that I couldn't go far without rebuilding the browser, and I think things have only gotten worse in terms of what extensions can do.
It's not much - and I remember getting a little further, but I must've lost the file - but hopefully it eases the discovery of prior art if you end up going down this path.
If you do, would love to hear from you to help or share thoughts!
The one I'm trying to do most recently is to compile bitcoin's bx[1] to wasm, so it can be run in the browser. It's not a crypto-related project, I primarily need the mnemonic generation code so I can generate mnemonics from passphrases for more general-purpose reasons.
Two reasons I'm thinking of getting it done in WASM: First is of course, not to roll my own crypto. Second is that if you're asking someone to generate a private key to use themselves, sending ANY information to a server is a big no.
Honestly I'd appreciate any thoughts or advice anyone has, I'm open!
The military knows how to do this - and has a strong reason to. If your documentation cannot survive the death or resignation of the man, team or department that wrote it, you can't build generational knowledge. Look up the mil spec for chocolate cake (skips my mind where it is in my library) for example.