Sure, but it's also paved with bad intentions, and neutral intentions. I would say that intentions have very little effect on the overall outcome of actions in general. Also good and bad are relative.
I would say that the road to outcomes are paved with actions. Not as pithy as the original though.
On a side note, they (Google included) really should drop the "accessibility" naming.
I don't know how much it made sense when it was to allow blind UI navigation (could have been a "navigation" or "interactions" setting).
But nowadays with the amount of stuff in there, including permissions for password managers, animation reduction, audio EQ etc., it just makes less and less sense.
proxmox is using KVM for virtualization and Linux Containers (LXC) for the containers. I agree that something like terraform and/or ansible would make more sense for an IAC (infrastructure as code) deployment. Most of the people I talk to that use proxmox for a homelab prefer to do things manually and don't bother with any IAC implementation.
For work I'm a firm believer in reproducible environments and IAC. We actually a combination of vagrant, libvirt, and KVM to spin up local clusters for quick testing and development. It works out pretty well, but in my homelab I don't have anything complicated enough to bother setting up terraform/ansible for. Although I imagine if my server crashed I probably wouldn't think that way anymore.
Given enough appetite and love from me, I've got a pretty robust Ansible script for building a Proxmox host with $i++ LxC's.
It's not suitable for open sourcing yet (embedded secrets and the like), but if the community wants it, it's pretty solid.
Only issue I see is the Ansible script currently always expects to be building a cluster of Proxmox hosts. I'd need to make some change to customise it so it can build out just one node though.
I've been using it or ~3 years now for my Proxmox cluster home lab which predominantly hosts LLAMA, *Arr stack, deluge, Nginx, Tailscale and a few other services.
It's not quite a one click deployment, but it can build our an entire cluster in 30 minutes after an initial Proxmox install is completed.
If you want to manage VMs, then you're probably using terraform + provider. However, SDN (Software Defined Networking) is not yet supported [1], which makes any kind of deployment with network separation not feasible (using IAC only).
I've seen this more and more in recent memory. I feel like the standard used to be define an acronym the first time you use it, then you can use it without explanation.
That's an interesting thought. I've done quite a bit of work in the medical/healthcare space in tech in the past. I think part of your issue is that doctors are notoriously hard to get a hold of. Also they don't make any of the decisions for tech.
If you're just generally trying to get an idea of pain points in the industry I think you should get more specific. Here are some for instances:
- Are you trying to make the interface between the doctor and the patient easier?
- Are you going to look at the way the doctors interact with the EHR (electronic health records) vendors?
- Are you trying to make the check-in process easier for patients?
- Are you trying to provide analytics for long term quality of care metrics on hospitals?
- Are you targeting small clinics, hospitals, or ER/minor emergency rooms?
Also for cold calling doctors on Linkedin, I am not surprised that you aren't getting much feedback. Most of the doctors I've known tend not to be into online stuff. You might have more luck reaching out to a local professional organization.
Also you might think about trying to contact nurses, nurse practitioners, or physician's assistants. There might be a local nurses professional organization that you could reach out to who could ask their members if anybody is interested. Just frame it as you're trying to figure out a way to make their jobs easier.
This ended up being a little rambly, but I hope it's useful. Cheers.
For what it's worth it does require a meta account, but not a Facebook one. I refused to buy one while it required a Facebook account since I deleted a couple of years ago. Once they made the change I figured that was an OK compromise. I just found out today during the outage that my headset won't work if I get signed out of my Meta account. That was an unpleasant realization, although I suppose it's partially my fault for trusting Meta not to hamstring the hardware their selling.
It's the equivalent of finding out that if Microsoft's auth servers go down no one with a Windows PC can use it since they can't authenticate. I'm fairly displeased.
I agree that people value different things but I wouldn’t say information about brand reliability is widely available. I have a consumer reports membership for checking that kind of thing simply because all of the info out there is mostly blogspam and fake review sites.
Information from reputable sources on large appliance purchases is incredibly hard to find since most people don’t buy appliances often, so even consumers used to doing online research will be hard pressed to know which sites to trust. I know that I wouldn’t have a clue.
If there is a place besides consumer reports, which is a paid service, where you can. Heck these things I would be very interested in hearing about it.
I loved looking for jobs on SO. I found some of the coolest companies and was seriously bummed when it went under. It’s how I heard about my current job I’ve happily been at for a couple of years.
If you use the windows boot record as the parent boot instead of grub you can mostly get around this issue. It’s what I did on my gaming rig. I mostly use that as a development machine these days, but occasionally boot into windows for games.
I would say that the road to outcomes are paved with actions. Not as pithy as the original though.