673 karma · joined May 31, 2017
The OG of DB table designers is the SQL Server database diagrams feature, and before that MS Access, and there is still room for improvement in this tool. Obviously saving changes back to your db (and migration scripts) is the most important feature, git tracking of schema changes would be good.
If the development work went into debating, specifying and expressing required behavior as a written spec more exactly (beyond w3c specs and towards the more pragmatic reality of what current browsers actually do) then very long term we can probably have engines that are AI built [or just more easily developed by humans] from a combination of the written specs and the set of tests they need to pass.
Using AI for adversarial development (e.g. one group tries to break and hack it, the other group defends and refines) could get interesting and wasn't really an option before. Anything that's now available to reduce the human resource cost of development could make a big difference.
In reality all big business become software companies eventually, but the really big ones tend to lean towards customizing a vendor product (e.g. SAP) to replace their collection of built-from-scratch tools. I'm not in the logistics business but if that's not SAP then I'm not sure what is.
Agree all the hooks and infrastructure you need to put in place are a pain and it's also difficult to debug if someone has an issue (one guy couldn't cancel for an unknown reason).
That way they can just go to azure and subscribe to the license that way, without needing any azure resources etc, it's just a billing mechanism.
They can then bundle that into their usual Azure spend and even do manual POs etc that I never have to deal with.
The key points are:
- offer email support, but don't offer phone, video calls or remote support. This works for most people and forces them to properly phrase questions instead of just "jumping on a call" (so you can then effectively train them over the phone, which doesn't scale).
- offer as much self-service as possible
- work at your own pace and it's ok to just not work some days.
- finding a niche is hard, but they can be surprisingly basic. You're just saving someone time, effort, worry etc.
- lean on global cloud services for reliability. Let them do that.
She said, "I installed it before for my cybersecurity course but I think it was just a trial"
Assumptions eh.
Spare capacity will depend on the planning in place at the time of sizing the power distribution, e.g. if it was going to be a growing industrial area or not, otherwise they have to either fund the upgrade or wait for distribution kit to get old and be replaced.
I once demonstrated this when a telecoms giant ran a very similar music popularity contest (around 24 yrs ago) and they were not amused. Everyone else was most bemused at my mid-paced metal instrumental No.1.
Systems and requirements go hand in hand but the reality is requirements are eventually codified, and after a point only the system matters because the system is the reality and the requirements were just the formal inspiration.
I would love to see automated requirement analysis and verification from code.
If your app does something on the users local machine (or a server) and cannot just exist in a browser then there is room for a desktop app.
You can run a local web server on a high port and connect to that as the web UI but not that many apps get away with that approach.