1) It will take you longer than you think
2) It will be harder than you imagined
3) It’s harder to find people who know it and non-trivial to get good at it (this should have been closer to the top) your project can be done in six months by five k8s experts but you only found one dude who knows it and he’s more a’ight than pro.
It’s probably still worth it, just go in with your eyes open.
Be prepared for this unfortunate pattern: “this thing I want just doesn’t work and probably never will.
Deploying k8s on a small, self-contained project that you just want to set up and go forever is probably a good place to begin.
If you try to move your whole production workflow in one go...
You’re going to have a bad time.
> 1) It will take you longer than you think 2) It will be harder than you imagined 3) It’s harder to find people who know it
Just so people have an idea of how hard it is to find people. I've got just about 1 year of experience getting kubernetes into production at a very large (multi-billion dollar) company. I have so many job offers coming in that I'm not even talking to companies offering less than 350k total comp. I don't have a college degree and 5 years ago I was making $50k a year. That might be just the generally bubble-ish nature of the tech industry right now, but if they're throwing around that kind of money for someone like me, I imagine that small shops have no way to compete.
Any chance you'd be happy to elaborate on what your role is? Are you primarily part of a dev-ops team, or tackling Kubernetes as part of developing the product? Did you obtain CNCF certification / think there's much value in those?
Also, if _all_ you want to deploy is a small, self-contained project, you don't need k8s. Most small companies/startups just don't need it. Stick with what is simple.
I’ve worked in data centers. The constant air circulation causes dust to accumulate in visible places. I assure you, computers are not as sealed up and tidy as you’d think. We used to jokingly call the hard, thick, black dust “cancer”. It’s hard to know what’s in it without study, but when you manufacture something with dangerous materials some amount of that material makes it onto and into the finished product. I’m not advocating for alarm, but your po-pi-ing comment was designed to minimize and it demands counterpoint.
Chips in all computers are highly encased, either in ceramic, hard plastic, metal, or some combination. They're never, ever, exposed to the air circulating through a computer, because the dust would destroy the delicate circuitry.
If you're regularly cracking open chips to snack on them, you have bigger problems...
Also every American who dies of cancer or other major medical condition will have his or her lifetime savings wiped out by medical bills. So measure average net income minus expenses at time of death and I’d be surprised if we beat Bangladesh. They probably have a higher gross national happiness in life as well.
There’s an active project to make good trackpad drivers for Linux. I suspect I could get better performance from the x1 given some work. I’ll focus on that one. The dell latitude 7250 I suspect just has a crap trackpad.
I’m glad this came out. It’s easy to forget that weed causes harm. Just from my own experience, when I’m on it I can’t think straight, can’t track a sentence from beginning to end. I can’t imagine where I’d be if those effects had applied long term as my brain was developing. Actually I can imagine. I’d be incapable of doing the high-paid, satisfying work I do now. I’d be stuck doing toilsome work with nowhere to go and a feeling that there’s more but I can’t quite grasp it.
I sometimes I have a feeling this is the case, as a regular user. But to clarify, I'm struggling with understanding differential geometry, and work as an se. Not trying to humblebrag but just trying to establish context. Should I be worried? I ask because I experience some of the same symptoms you do.
Much of the vision may have been his, but what he is accused of stealing is the work of 100s (1000s?) of engineers who worked to make those ideas a reality.
It really depends on interest. What does your target audience care about?
I’d recommend Sapiens to anyone, but it’s more of a thinking book than an escaping book.
1) It will take you longer than you think 2) It will be harder than you imagined 3) It’s harder to find people who know it and non-trivial to get good at it (this should have been closer to the top) your project can be done in six months by five k8s experts but you only found one dude who knows it and he’s more a’ight than pro.
It’s probably still worth it, just go in with your eyes open.
Be prepared for this unfortunate pattern: “this thing I want just doesn’t work and probably never will.
Deploying k8s on a small, self-contained project that you just want to set up and go forever is probably a good place to begin. If you try to move your whole production workflow in one go... You’re going to have a bad time.