Man, I sure wish cybertrucks had been around to deflect when I spent 7 years driving a Fiat Panda.
This is the dumbest bet you can make and more or less the definition of lose/lose- if we fail to move off greenhouse gasses, what kind of mad max style future are you hoping to be rich in?
By the power invested in me by, well, nobody whatsoever, can I just take a minute to say, let's all cool down a little in the comments!
There's a lot of arguing against:
- The idea that acknowledging the tragic reality of climate change makes you defeatist
- The idea that because we have had some great advantages in green tech we can sit back and let climate change fix itself
I don't see anyone making those arguments here though! Just lots of people concerned about climate change with different skews of how positive/negative we should feel.
Personally, I swing between powerful optimism and waking in terror at 3:00am for the future we're hurtling towards. I'm sure other people are the same, so let's just be friendly to the fact that other people are in different vibes to us.
There are some people working together very well right now to dismantle the climate, so let's all remember that when we're talking with each other.
Peace and love!
It doesn't split, but I'd guess 99.9% of those online meets are dating apps (rather than other ways of meeting online).
That's kind of sad, not because there's any one way people should meet, but because meeting people is now mostly mediated through for profit companies.
AI: "Have you tried funding public transport and regulating the carbon industry?"
Ok, now we need to make a new AI so that AI can solve global warming but without using an existing solution that might marginally inconvenience the mega rich.
Public transport would be a much more effective and cheaper solution, but we're all looking at EVs because it means not having to change anything about the status quo.
Short answer is no, I think because what tools you need for programming change so much based on the development you're doing. C++ developers need compiler toolchain stuff that Javascript developers would never need to look at and vice versa.
Curveball answer is that modern extensible IDEs with the power of language servers and plugins have kind of become this. I'd massively recommend properly getting into one of the following and learning how to configure new languages and plugins:
- VScode
- Neovim
- Emacs
- Helix
(Sure I've probably missed some great options, feel free to flame me on why notepad++ should be OPs first choice)
I wish I'd read this years ago! I've nearly bankrupted myself buying a new machine each time, thanks!
So, putting aside the questionable morals of this person. I'm not sure alt right reddit threads are the election swing spot they seem to think.
Well not for the people taking them, but you can make heaps of cash doling then out! (sarcasm)
I'm a data engineer, and have seen an ungodly ammount of 200-but-actually-no-stuff-is-broken errors and it's the bane of my life!
We have generic code to handle pulling in api data, and transforming it. It's obviously check the status code, but any time an API implements this we have to choose between:
- having code fail wierdly further down the line because can't parse the status
- adding in some kind of insane
if not response.ok or "actually no there's an error really" in response.content
logic
Every time you ignore protocols and invent your own, you are making everyone sad.
Will take recommendations of support groups I can join for victims of terrible apis.
Here's my hot tip! (ok maybe luke warm)
Write as much of your CICD in a scripting language like bash/python/whatever. You'll be able to test it locally and then the testing phase of your CICD will just be setting up the environment so it has the right git branches coined, permissions, etc.
You won't need to do 30 commits now, only like 7! And you'll cry for only like 20 minutes instead of a whole afternoon!