Ask HN: What jobs can a software engineer take to tackle climate change?
I'm a software engineer with a diverse background in backend, frontend development.
How do I find jobs related to tackling global warming and climate change in Europe for an English speaker?
Open to ideas and thoughts.
76 comments
[ 2.9 ms ] story [ 149 ms ] threadThose tree planting drone companies probably require software engineering.
I'm not sure if that's just an asterisk indicating that the short-run effect may be a wash, or if it's clear enough to rule out some environments/tree species in favor of other choices.
Luckily some competitors still exist: https://www.cloudandheat.com/ https://www.qarnot.com/fr/home-fr/
I wish people would go for the big guns, fully renewable energy, nuclear, electric transport, green concrete and steel - the major issues instead of wasting time and money recovering 10% of what some coal power plant supplied to their data centre.
It's better than nothing but very close to nothing. It's a pervasive way of thinking in green engineering, every bit helps but what we need is BIG help: https://www.withouthotair.com/c19/page_114.shtml
Trees are the cheapest most efficient way to remove carbon from the atmosphere. No other solution comes even remotely close.
You can drive a Prius, become a vegan, and buy solar panels but a person who plants a single acre of trees will have offset an entire lifetime of greenhouse gas production and then some.
Nearest I've found is <https://greenismything.com/2015/06/23/howmanytrees/> which suggests ~2 acres per head for the US.
So to a zero approximation, I need to plant 1000 trees to offset my lifetime's carbon footprint. Without too much math, looking at my backyard, it's not possible to squeeze that into an acre (an order of magnitude off).
If there's a higher payoff available than that, I don't know where it is.
Absolutely vital tip from extremely painful experience; your physical and more vitally mental health come first. You must not forget that as if you burn yourself out you're no good for anything.
I don't think anyone should feel bad about not coming up with the solutions to global problems. You not knowing any higher payoff doesn't make you a bad person. But every incredible transformation of the world started with a person, and many incredible people only became incredible through the work they tried to do.
Borlaug saved a Billion people from starvation. He started out as a basically normal man. Find something, fight for it, wrestle with the world and hope to hold on to something, mostly because we all lose in the end. If you lose early, enjoy a happy and normal life with your family, but you don't have to lose before you start.
I don’t know anything else about them other than I think they are based in Europe. Might be worth a look.
[1] https://www.ecosia.org/
As for cows, the biggest source of methane emission in livestock comes from belching rather than farts. https://en.wikipedia.org/wiki/Environmental_impact_of_meat_p...
Software has the possibility to change behavior but it's probably not the biggest lever available for this particular problem.
As for finding those organizations, that's a different question and may be better asked without reference to software engineering so as to receive the widest spectrum of orgs.
Recently the web has evolved with CSS Grid and this means that you no longer need to have web pages made of 'div soup' with every 'div' using half a dozen non-semantic class attributes.
It is extremely rare for a web page to be 10% or higher in actual content, if you look at the actual document and don't even consider the images/scripts/stylesheets. Most of the web could be at the 33% mark if you strip the presentational markup away and just use HTML5 elements, styling them with CSS Grid. The benefits of writing this way are many, apart from being green, such a page is accessible because useful elements are used for the page, e.g. 'nav' instead of 'div', and easier to maintain, because the content is kept simple. There is also SEO benefit from having a quicker to download page that is a fraction of the size.
Now you may scoff at saving a few bytes from a few web pages but the savings add up, get one template right for a website that gets used by a few million people on a daily basis and you are suddenly saving gigabytes. People's phone batteries last longer, cell towers don't have to do as much work, server rooms can run cooler, it is a bigger win than people think.
Once upon a time we thought nothing of single use food containers or excess packaging, the humble 'div' with its framework class attributes double-wrapping every block of content on the page with a few 'span' elements thrown in for good measure is possibly more wasteful, at least you can reuse plastic bags, you can't reuse a 'div' that has been beamed across the airwaves from the far side of the globe.
There are laws coming along meaning that web pages have to be accessible. You can make them accessible in a lip service way or re-write them with maintainable, CSS-Grid styled HTML5 to deliver a first class accessible experience. In the EU there is a two year period for the public sector to get their act together on this.
Writing HTML without the div where you focus on document structure and use the right elements is very easy, as is using CSS Grid. But we are in an industry where the mindset is to work from a visual mockup and to then paint by numbers gormlessly using the dreadful div element that has no place in modern HTML and very much goes against the 'separation of concerns'.
The world needs someone to teach a new intake of web developers how to write actual HTML, leaving the build tools and hacks far behind, more of a focus on the written word rather than the overly complex tech.
We have had revolutions in web design, for instance 'responsive' was a thing. If we can have actual HTML instead of bloated presentational markup then there will be some old timers who won't get it, but this easier way should be well received. Right now though dev teams are very much geared up for over complicating projects and not even thinking to use just the HTML5 elements in a content first type of way. Hierarchies of teams are built around anachronistic 'agile' processes that are doomed to result in bloated div websites.
Unless there is nuclear war then we are not going back on the web, it is here to stay and be improved on. Be that improvement. Teach people how to write web pages the easy way, enable others to think differently and not be using tired Stack Overflow 'div' solutions that were okay a decade ago.
The maths of the CO2 saving is not easy to work out. But then it is. HTML is the language of the web and web pages are what we read. This page you are reading right now is HTML and not some JSON stringified thing. Coding the lean HTML5 way does get your HTML document size halved, plus the lights don't have to be on as long to write it in the first place.
You can do all of this stuff a lot easier than the stuff you have done thus far. I don't think your skill set is in 'pl...
But half the world spends half their time on their phone. Halve the bytes and bandwidth needed for that and make things accessible - what is not to like? I bet that changing the way we do web pages to remove old fashioned bloat saves more penguins than your suggestion.
My suggestion was written specifically for the questioner based on their skillset. Not a one size fits all solution for everyone.
Please do the maths for me after refactoring a web page of your choosing so you have an idea of the gains. Don't be a blocker, present some sums.
Very nascent, researching and blue-sky-ing, but I'm just putting it out there for anyone who might like to discuss this.
have slack, too.
jason.[lastname-from-username] at gmail
1. Innovation (e.g. find new and better sources of energy) 2. Mitigation (e.g. reduce energy consumption)
For example the Tesla Solar Roof is an innovation strategy whereas planting trees is a mitigation strategy.
Although we really need a combination of both most companies tend to focus on a single approach, so I'd suggest thinking about which type of approach you'd like to work on.