I'm not that worried about returning to the office. I think most office jobs will be some form of remote work forever.

We worked in offices because it's the way we always did it. But we now know we don't have to.

It reminds me of post World War 2, where women were expected to just return to their previous lives.

There will be a big push to get people back in the office. But companies that embrace remote work will be more profitable.

Off topic: The pandemic has been wonderful for my gi tract.

Constipation driven by office bathrooms problems where a regular concern. I would really try to time bowel movements so that they would happen at home. And would get constipated if I missed my window.

Not having to worry about this has been a huge quality of life improvement.

Seconded. In addition to a shy colon, I have a shy bladder. It was pure hell working in an office, physiologically speaking.

Ever since I started working from home regularly, my GI system has never been better. I went from having the worst GI issues in my household to having the best GI system. I'm sure having less stress in general from not having to go to the office is a huge help. It's also great that I can freely pass gas as needed instead of holding it in for hours which caused tremendous pain as the day went on.

My back is actually doing much better too. I designed (using that term loosely, more like jury-rigged) a wooden chair with a tailbone cushion, open back so my spine doesnt have any pressure on it, and a swivel keyboard/mouse tray aligned with my arm-rests so it puts almost no strain on my wrists. It's basically like this - https://imperatorworks.com/index.php/iw-r1 - but no monitor attachments, it's made out of an old wood rocking chair, and it's ugly as sin. Does wonders for my back though

I picture the peak when the moons of Jupiter are full with a thriving civilization. One trillion strong under one government. Building the ships that take humanity to other stars.

How small we will look to them.

I picture the peak when the entire universe is teeming with life, but looks empty to very simple creatures like us.

Seems awfully convenient that the universe would look identical to us in particular, as opposed to any other observer. Or being computronium.

I can't see the US ever adopting a single payer health care system. However I do think they could adopt a health care justice system.

The US cares a lot about justice, and free markets. Some kind of well funded, and empowered FBI system for ensuring citizens get fair value for the money spent.

The quote here is the main point. "But if you want to engage with 20+ exchanges, to go to market quickly, and implement continuous performance tuning, you'll choose Java."

The amount of changes you need to make due to customer preferences and regulations is continuous. If it's ok for your system to run in the 100 microsecond range then Java is a clear winner. If you are just focused on a single exchange, running in the same rack as the exchange then of course C or lower is what you will want.

I just wanted to add an another perspective. I had a great private office with a door that closed, and a quiet work environment. My home office is also a nice dedicated room and well equipped.

Even in the quietest office noises would get to me. I would always have to fight to focus on work. At the end of the day I was spent.

Working from home full time, even with my family here 24/7 has been incredibly relaxing. I really, really don't want to ever go back.

Frameworks make hiring a bit easier it's true.

I'm amazed at the number of developers who can't seem to cope with working with custom in house frameworks. I'm talking about fully working systems, with full source code and being walked through the code by the author / maintainer.

They fall apart, constantly complaining that the approach is non standard, deprecated, dangerous, unprofessional, untestable.

So we are trying more and more to use frameworks, just to be able to hire more easily.

Definitely agree, developers can get away with a lot of missing knowledge and not realise it, if they're using frameworks from the start of their career.

Ideally you could hire senior developers with the skills to work inside boutique software, but I have found "legacy" code turns a lot of people off a project, and most boutique software eventually gets called "legacy" even if it's well architected and running perfectly fine.

The skill which I think new devs could differentiate themselves with, is debugging. Familiarising yourself with software patterns definitely puts you ahead, but being able to use debuggers to understand code that has no pattern, that's when you become the kind of bug-squasher/problem-solver that projects like that require. If you have good debugging skills, you can work on any project, because you can find out all the information you need by stepping through the code.

This just displays the core incompetence in basics that many devs who are dependent on frameworks have.

I think I understand your point.

It's more back to the mainframe model of software development. I did this back in the 90s and I never had to think about scaling. Granted these were just simple crud / back-office apps.

But I can see how it would work for most modern software.

The mainframe model is viable (and legitimate) again because you can buy 128 core machines. That’ll have no problem running at people’s businesses

As a GenX in the 90's my money went to: - Going to the movies - Going out for fast food - Renting movies - Renting video games