916 karma · joined January 24, 2016
I always ask myself (and the team at large) "how much time/effort will it take to reach parity using the new tool-set?". The answer usually settles the debate immediately.
Yep - we found a company in Florida that was importing formula from Germany at a reasonable premium. Keep in mind that this was 4 years ago, so I don't know the state of that pipeline today.
This is precisely why I think we will never be able to effectively treat healthcare as a "free market" with tools like HSAs, posted price sheet, etc. The end user can never know the true cost of their procedure until it's long over (sometimes years later) and often don't get to choose at all.
Here I was thinking you were in the Seattle area until I read the last bit.
I've given it a fair shake (probably in the hundreds of hours of video conferencing) and I still feel like I don't understand how I'm supposed to use it for anything but pure video conferencing.
- Many jobs require travel; often with little to no advance notice. And you sometimes don't get to go home until the job is done. You know how devs joke about how hard it is to accurately plan a project? The same applies here too, but except the cost could be you stuck on the other side of the world, unable to visit family, until you reconcile the gap.
- Even lower upward mobility. There are still manager and project manager tracks most places, but VERY few have technical tracks that match. Oh, and if you choose the manager/project-manager path, expect to do zero technical work AND travel significantly more!
- Lower flexibility in expertise/duties. Most disciplines under "physical engineering" are highly regulated/mature and thus do not change much these days. One not-entirely-contrived example could involve industrial-scale boilers - any engineer working in this world has almost zero room for creativity/innovation, you are entirely bound to 50+ year old industry codes that are insurmountable. And if this is what you do for 10 years, you're going to have a terribly difficult time convincing another company to hire you to design gears or PCBs, etc.
As a former mechanical engineer, I came to say exactly this. Engineers in the traditional realms (mechanical, electrical, chemical, etc.) operate in the business domain all the time, even the junior engineers. Conversely, software engineers are usually isolated from the business domain until they reach the most senior positions. This creates a serious skills gap when the time comes for software engineers to make business decisions.
Are we sure this is true? It's easy to put $0 on a balance sheet under the real estate column. But there are certainly other costs (including opportunity costs).
But consider what OpenAPI/Swagger actually changed - it made for a singular page to tell a user (or machine) all the possible ways to interact with the service and what the shape of the requests and responses would look like. AsyncAPI is meant to do the same, but it's much harder to grok with all the various protocols generalized into unnatural-looking fields/URIs/etc.
Running such a production is difficult.