And massively increased again in the last five years…

The main thrust of the argument seems to be two fold - it‘s not 100% is (almost nothing is) and it costs a lot upfront (so do fossil-fuel plants). Smells like like some serious astroturfing to me

The rest of your argument? The only thing I see missing is transport. It needs to scale to global levels and be free with respect to both carbon and cash

I would recommend reading Kim Stanley Robinson for better ideas than I could ever give - The Ministry for the Future and New York 2140 spring to mind.

From the angle, it also looks she only has a single boob - right in the middle.

Did Christian say he didn’t want to sell to them? I read that as “didn’t offer enough money”

The same position is open in multiple job markets, including here in Toronto. It’s possible that they need multiple code engineers, but the most likely read is they really need this person.

Possibly to tick a few boxes in the IPO prospectus…

I just realized something…

At some point, Valve will release a Steam Deck 2 - It will be slimmer and even better than the first. Maybe in a couple of years I am guessing

Then that will be it because other companies will be releasing cheaper devices with their Steam OS. Steam simply cannot compete with them on price, and the feature set (other than faster chips) will mostly be locked in.

In short, there will be now Steam Deck 3 - Gaben strikes again

Isn’t this guy supposed to be a lawyer? He can’t string two sentences together coherently.

He obviously gained a lot of weight by the time he ended up playing the nightclub boss in John Wick 4

The tests help you discover what needs to be written, too. Honestly, I can’t imagine starting to write code unless I have at least a rough concept of what to write.

Maybe I’m being judgemental (I don’t mean to be) but what I am trying to say is that, in my experience, writing tests as you code has usually lead to the best outcomes and often the fastest delivery times.

This is why you write the test before the code. You write the test to make sure something fails, then you write the code to make it pass. Then you repeat this until all your behaviors are captured in code. It’s called TDD

But, full marks for writing tests in the first place

That’s positively early on trains around Toronto where I live… The schedule is merely a guideline