proof:
left -> left -> left = right

It is amazing how George Orwell predicted all these half-a-century or so ago.
Even Yes Minister has one episode on a similar issue, that was three decades back.

Are we ignoring warnings from the past? or decided to be selective in terms of learning from the past?

trying to define where earth's atmosphere ends and space starts.

Interpreting the actual intent of a person, from a sentence he/she wrote, is quite challenging.
Especially if you are using a language like English. Not convinced? read this one -> "Is the duck ready to eat?"

On the other end, things can be taken out of context. Salman Rushdie's Satanic Verses is a prime example, where all book burners read only certain passages, not the entire novel.

I watch YouTube a lot, on average about 2-3 hours a day. As of late, I live in a country where there is a bandwidth cap of 40 GB/month. And I have no option but to YouTube at 144p to avoid extra bandwidth charges.

I applaud all efforts by tech companies to reduce bandwidth usage (and not to forget, making inter-webs more exciting). Then again, none of those efforts matter, if bandwidth caps are forcing consumers to use internet like back in 90s.

skills that are practically useful in life, such as

1. Self reliance (how to cook, how to do minor repair works around house, etc)
2. Think broadly (do projects that encompasses everything from planning, prototyping, executing, teamwork etc.)
3. Financial management
4. Driving (it is better to start young, see Finland)
5. Surviving outdoors (you never know when you gonna need it)
6. Interacting face-to-face
7. Objective thinking (so that they won't fall into sound-bites of politicians)

I do not foresee "coding" will help anyone in the broader spectrum. Perhaps, it can liberate few talented coders who would've gone to another field. Other than you enter into an STEM career; quite unlikely "coding" will help you survive.

Something peripheral: "coding" projects will only succeed because of other skills i.e planning, team work, communication etc; not because of your "coding" skills it self.

I worked as a developer, and I was one of the rare ones who took QA feedback positively.

By and large, I got along well with QA. Simply because I acknowledged the fact that they helped me a lot in understanding better about developing quality software (at least UX wise). I was always driven to write code that pass QA, which I took as part of my work and pride.

However, not every developer shares the same sentiment as me. They went on to complain and remove QA, and take all that responsibility to them. Great, that's as good as you are the judge for your own court case. Since then, my employer fired all QAs, and ever since, quality reaching new "lows" every quarter.

Sith lord is not behind it !

"Elementary, My Dear Watson!"

From the article: "Above all, devops is a cultural philosophy".

Looks like it is another buzz word like Agile. Based on my experience, Agile can be "Fragile" when the team is not committed on it. Beyond that, Agile can NOT be applied to a) large projects b) projects with lot of groundwork and c) dev stack that require long compilation/building process. Most Agile/Scrum projects I worked end up falling back to a semi "Waterfall" workflow while still doing some Agile stuff (which I happily coined "ScrumFall" after the penultimate James Bond movie.)

Having said all that, jury is still out there as to whether there is something called DevOps. Only time can tell I suppose. Just my $0.02.

Vodka ?

Languages wise

1. Hopefully the death of Java and similar GC knock-off languages like C#. World would be a really nice place without them.
2. Expect demise/marginalising of dynamic languages like Ruby, Python, etc (Python may survive for a bit, as some of the NLP libraries are written in it).
3. Expect JavaScript to be the de-facto language. In fact, it has become on the web. But yet to see it getting closer to OS and general hardware.
4. C/C++ will remain there as long as there are hardware and peripherals. Fortran because of research and stuff.
5. Maybe the second coming of Functional Languages. I expected languages like F# to take off rapidly, but still haven't seen any momentum. Likely, they will have its day when more and more cores are squeezed into the CPU.

Work wise

1. Nothing will change... still there will be incompetent managers, unrealistic timelines and unworkable workflows (agile, scrum, waterfall)

At least for me, the killer feature of PostgreSQL is its procedure language PL/pgSQL. By a fortunate accident, I had the opportunity to write some complicated features (read "calculation heavy") for a web app using PL/pgSQL. Once coupled with triggers, you can just leave everything to the DB to the point, controller has to do nothing except query and return JSON objects to the front. It is so expressive, powerful, efficient and reliable.

I have worked with MySQL, Oracle, MSSQL and as of late MongoDB.
Given a choice, I will always settle for PostgreSQL... it is just so natural to work with.

Why do people keep deferring their journey to pearly gates to meet their maker ?

On a serious note, we have a population crisis!
That's the root cause for every socio-political problems in our time.

I'd rather be excited if academics, medical practitioners, politicians and alike embark on an project to legalize "ethical euthanasia".

I was a dev in a firm that pledged to do things agile/scrum way. However, nobody knew how to do it in the "text book" sense. As you can imagine, it went horribly wrong, especially for large web projects. Same firm, then tried waterfall, similar disaster.

So I conclude, workflow doesn't really matter. If the team you are working is not properly functioning as a team, likely no workflow can help you.

What I call a properly functioning team is a team with members who has a common goal, willing to sacrifice and work hard to achieve it, and willing to help other team members. Unfortunately, most organizations are driven by appraisal systems, which by design down play team work.