Not exactly. Specific events are required by law to be reported by medical professionals. Anecdata says this gets missed fairly often as there's no real enforcement.
I ran a BBS in the 90s, nothing big but it had a small local community, some of them just users (lusers) and some of the sysops of other boards. I only had one phone line but call waiting would just kick the user off if I got a call. It was really easy to one up, I was running Renegade but there were quite a few different systems that you just basically turn on and you're up. I spent way too much time customizing each menu with ANSI art for each menu and trying to pimp out the UX. There were multiplayer games and file boards and message boards and you could live-chat with the sysop or other users if the board had multiple phone lines. My buddy called long distance to Kansas to some warez board to download a paint program and ran up a huge phone bill. It was magical and so much fun. Internet still has not achieved that kind of decentralized p2p in the mainstream. Plug a Raspberry Pi into your cable modem and build your own little board, give access to whoever you want. Would be pretty cool to me, but I don't know if I'm just old and nostalgic or if anybody else would actually want to do it. But yeah, wild wild west was the best.
I ran a small board. Was fun but tried to do too much on 1541 (mods (games), and messages). I miss the 800 backdoors people put on party lines on. Hitting a newspaper box in a certain spot so it would open free. BBS meetups. War dialing. Local zines that were really cool programs
There were private FTP and IRC bots, DC++, etc. Private Minecraft and other game servers are still pretty common.
> Internet still has not achieved that kind of decentralized p2p in the mainstream.
BBSes were never mainstream. Personal computing in the 80s and early 90s was not mainstream. This is the insurmountable problem in trying to recapture that experience.
There's a ton down this rabbit hole. One of the great anomalies of our industry is that we've used the database to bring coherence to countless "user domains", but never applied the same principles to our own stack. The benefits of doing so compound exponentially.
So basically Oracle Apex, oracle html db before that, and end of the 90s we were generating this from Oracle Designer 2000: low-code tools to generate web applications from the database...
When I hear "low code" I get a little skeptical. Often such tools make the first 80% of the project simpler but the last 20% a bear, unless you live with clunky defaults. There's a difference between managing code better and removing code. Generally I find the best path to "low code" is to write small simplification wrappers that fit your shop's conventions, because a big vendor probably won't fit your shop's conventions out of the box.
Thus, you can code like "currentForm.AddButton("clickMe", destination: screenY); and all the styling etc. is done by your shop's wrapper to fit your shop's preference. The wrapper won't fit all needs, but if fits 90% of buttons, then you only have to specialize 10% of them. I don't know why people tolerate copy and paste of verbose snippets for such. Wrap the repetitive clutter away to make it easier to grok your primary work.
I like optional named parameters such that customization is incremimental:
I worked on Oracle Developer/Designer in the 90s. Was pretty good. I also went to the Oracle course at Reading for MOD PL/SQL which Htmldb and Apex were based on. There is still quite a bit of Apex work around, and all the oracle "applications" of course as well.
Oh the Eric Hanson I guess? I remeber watching an interview with you where you said something to the effect "back then I had time and money on my hands so I went and tried to build this thing. Four years later, and none of that is true anymore". That stuck with me.
