Very few tech companies can say that. So, it doesn't really matter if they ditch k8s for their own solution. Really, it doesn't.
894 karma · joined September 10, 2020
Very few tech companies can say that. So, it doesn't really matter if they ditch k8s for their own solution. Really, it doesn't.
You mean, that to each their own right? I agree, but RTO is the opposite. RTO forces everyone to work from the office.
If you prefer to work from the office, go ahead be my guest. I prefer to work from home. It's a win-win, right? No. Just because you like to work from the office, I too must go to the office so that you are happy. I don't force you to work from the office or your home or wherever you want.
So, if I have 15 years of experience can I work from home? Hum. All the juniors in the office, all the seniors at home. That's it? Or just because some engineers do not know how to work remotely, then I too should be dragged to the office?
Nonsense.
Sure, but those things can be learned on the actual job. So after a few years, the CS student knows both the theory (because of uni) and the practice (because of work)... Whereas someone who only learnt the practical stuff, well, usually lacks the theoretical foundations.
And even if AI is able to do that... Well, then anyone out there could become a UberCycle CEO. Which means: customer requirements will be much more complex by then and coming up with an entire product in 1h won't be enough anymore.
REST = http
GraphQL = http + GQL + resolvers
Sure, one more layer of abstraction here and there may be justified. In the case of GraphQL, it's not.
That's the only reason why teams use GraphQL. Decoupling taken to the extreme.
And no: not all tech companies have over hired during the pandemic and they are not firing people these days. No one talks about them because that doesn't sell.
- buy a domain for 20 USD/year and create the corresponding hr@MyNiceAndSeriousLookingDomain.com
- do what the scammer did in the blog post but without grammatical errors (I could even use chatgpt for that) and alway using my custom email address
See. That's easy to fake. If people are willing to pay the scammers, then the grammar errors and proton emails do not matter
In the past, software engineers were dealing with punched cards (few engineers), later on they were dealing with assembler (more demand), then with low level programming languages like C (demand starts to increase), and nowadays engineers deal with high level prog. languages like Python, JS, etc. (high demand). As the technology makes software more ubiquitous and reachable to any aspect of life, the demand for people who know about software increases.
Maybe in the future software engineers will have to deal with even higher level languages (prompts?), but that would only mean that making software is easier than before and you'll see software even more ubiquitous than it is right now. Demand will go up for people who know about software even if the tooling seems like it requires less people with such knowledge.
Hell, I think I as a developer could do that... Gonna invent a new open source license.
Needless to say: Bootstrap didn't make designer nor frontend engineers jobless.
Because the bigger the company the more valuation it gets (although, with the latest layoffs and all, I think this won't be the case much more). Why would Twitter (or any tech company) would remain static in size (let's say at 500 engineers) when it can just grow and grow? As long as money comes in (funding) they company has to do something with it (hiring and invent new areas to explore that requires more hiring).
It's not a question of technical requirements, it's just all about money.