The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
Oh absolutely. My experience at work from 2010-2015 was consecutively horrible. I too had a psychopathic boss. My previous career from 1978-2009 was pretty comfortable. Just the usual project death marches and stuff.
It was so bad it left me shellshocked. It interfered with my interviewing for new jobs, caused me to ask questions that probably disqualified me as a candidate. I ended up retiring to write geeky books on C++ and experiment with all the software I never had time to try out when I was employed.
unfortunately, due to reorganization (layoffs) in my previous company i have been assigned to two different bosses.
one of them, my older boss, was trying to prove to the director that this new "thing" is not going to work, albeit in a passive way. without telling him directly, but by sabotaging my daily work, giving me instant assignments that confronted my current assignments from the new boss.
the new boss on the other had was a totalitarian psychopath who used to phone us on 20 minute basis to ask for progress, status, etc. in one word micromanagement at it's worst. he was also at high stress by this reorganization. the director also, everybody was taking some king of stress reducing pills. the place was falling apart.
during that period i have developed insomnia and a nervous tick i still can't get rid off, even that now i work in a beautiful stress free company. 3 years have passed since then.
one morning, after spending a sleepless nigh, i went angry to the directors office and said to him "you will assign me to only one boss, i don't care which one, or i will come to work but i'll stop working". he was afraid being caught on the radar by upper management so he complied. either that or he used me to the maximum and had to loosen up a little.
a few months later a left that IT job for an unqualified workers job as a electric meter reader. in the past 3 years 5 of my colleagues have left that IT firm voluntarily and another 5 were forced to leave. the rest of them, some of my best friends, are still battling high pressure.
the motto "stress increases productivity" is like mass hysteria. it doesn't leave the company once it's in, unless something huge breaks.
"When you are dead, you won't even know that you are dead. It's a pain only felt by others; same thing when you are stupid."
Ignorant - An individual without knowledge, but is willing to learn. Stupid - An individual without knowledge and is incapable of learning. Idiot - An individual without knowledge and allows social media to do the thinking for them.
It has the same roots as NoSQL has. The concept and the naming convention is too contrary to each other, that sometimes it is unclear as to whether take this literally, or understand it first.
Serverless basically, the way I understand it, is, a NoOps. If you know DevOps, then you will know what a NoOps is. Basically serverless is not about Functions as a Service, rather it contains a total architectural redesign of the applications to leave the operational components on the runtime. It can be a function, can be an API, whatever. But you leave the operational stuff out of it. It contains the scalability, error-proofing, etc.
At the end of the day, I would be wrong, as someone else might have a different view of this component; provided Kubernetes also has a serverless runtime now, KNative. When provided by a vendor, it would be a service.
Conference a few years ago guy started his NoSQL talk clearing up to say Not Only SQL - which is a better training start to refer to most of those applications as Not Only SQL, especially if talking to SQL developers.
Perhaps an issue with people coming in to a conversation and use words which sound similar but are totatly different concepts.
Go back 12 years
Our app is Java right, so it it sounds it will be quick to port over.
When you deploy functions-as-a-service, how many servers do you personally have to spin up and manage?
Also, the cloud providers make no guarantee that your function will actually run on a server. Your AWS Lambda might function end up running on Jeff Bezos' laptop, or on a Raspberry Pi in the front closet of Amazon's Timbuktu sales office.
Or another way to look at it:
Functions-as-a-service are computing for serverless people, sort of like how Uber is transportation for carless people. In both cases, you can achieve your goal without having to deal with the headaches of owning and maintaining infrastructure. And also in both cases, they're awesome if they fit your use cases, and useless if they don't.
I'm going to be posting an article about all of this some time in the next week.