The board of directors should now fire the management over such as gross mismanagement. Then, the board of directors should be fired for not proactively requiring backups.
Regardless how you edit/compile your code, you still need to debug/troubleshoot problems in production, and that is very likely to use Kubernetes. So the more reasonable approach seems to be: first, figure out how do you troubleshoot/identify/mitigate a problem in production, then reproduce it in development environment and work to fix it at daytime. When you have instrumented your app for reasonable debugging experience then using these tools on development machine becomes much easier problem, K8s or not.
I did designs that overstayed their intended lifespan by 15 years. I did designs that were cancelled even before being fully implemented. Most however had their predictable lifespan of 3-6 years.
It seems to me that the key is to make useful product based on sound technical decisions; entropy (a thing you can't control) will handle the rest.
DIY is good if this is part of your life plan. Otherwise it's a distraction.
We live in civilization for a reason; different people specialize in different tasks so that overall, we all can enjoy our lives more.
In other words, except for simple little things, don't make me fix my bathroom: there are people who do this faster and better than me, but NO ONE is going to fix bugs in my software for me. To each his own.
The flip side of minimum wage is often overlooked: people on the bottom end of the spectrum, who struggle to compete with other minimum-wagers, are cut out of the workforce. At $15 or $20/hour, the job requirements are higher than at $10/hour, and these folks stand no chance.
Likewise, the low-end employers are priced out of the market.
It's the same survival of fittest, except the weakest constituance is hurt most. They are very sparse so their voice is never heard.
In a few states you are allowed to pay people with 'severe' disabilities under minimum wage.
The idea is to incentivize companies to hire these people for otherwise unprofitable work and mostly to get the disabled out of the house and earning some money that they otherwise would not.
For example, most of the prescription glasses made in the US are made by blind people under such a scheme.
Honestly, it sounds terribly exploitative. But, from what I understand, these schemes are mostly successful in that the disabled are happy with it along with the employers.
> It's the same survival of fittest, except the weakest constituance is hurt most. They are very sparse so their voice is never heard.
their voice is heard to a disproportionate extent because there are entire companies like Walmart and really entire industries like food service that built a business model around being able to pay sub-living wages (usually with the difference made up by tax dollars or tips).
iPad: probably not. Windows 2-in-1's (for example, Surface Pro) _somewhat_ fit the bill: heavier than a tablet but still a full-blown computer when you need it.
People are focusing on verbage and precision, but are missing the point.
Having a well-maintained Python tooling is essential for _any_ company who does AI. While smaller companies can get away with open source solutions, for bigger companies it is unavoidable to have teams dedicated to maintaining and supporting Python tooling.
This announcement is troubling, and may indicate one of the two: 1) Google is in dire situation, and there is no more fat to cut, so they are starting to cut muscle. 2) Google management is clueless and cannot discriminate between fat and muscle.
