Not at any scale that counts. There are a whole bunch of companies _trying_ to make zero carbon cement, but it's all very early stuff.
The lifetime of a cement plant is 30-50 years, and they cost 100-200M Euros to build, so even if there were a process that was ready to scale today, producing a cement that passed regulatory standards, we'd still be making some Portland cement into the 2070s.
Ergo, producers would like to stick a carbon-capture plant onto their kilns.
Yes! Likewise for grinding: offload excess power to industrial plants so they can grind rocks when it's windy. If you look at the problem in the right way, a silo full of ground rock is just a battery.
I work on decarbonising cement production, and the cement producers are betting _heavily_ on carbon capture as their "get out of jail free card".
I think they're likely wrong, but - again - it's not like we can just stop making concrete: all the solar farms, wind farms, dams, and assorted infrastructure that we need to combat climate change will be made with concrete, and there is currently no viable zero carbon alternative.
The grid is the easy bit, and will happen as a result of market forces, but those hard-to-abate sectors are really fricking hard.
Concrete absorbs co2 while curing. It's the calcination process, where we heat limestone up until the co2 burns off, that has unavoidable emissions. Since this concrete is recycled, that's already happened.
The emissions trend is slowing. We have the technology we need in order to change course, we're just not deploying it fast enough.
The worst projections, at least, are off the table: we're not headed for 6 degrees of warming, we're on track for 3, and I strongly suspect we'll end up closer to 2 degrees of warming.
That is going to be terrible. People will die, wars will be fought, and we'll see the largest migrations in human history with all the attendant political upheaval and barbarity, but we'll still be here. Humans as a species are going to make it.
For me, I found it helpful to go and work in climate. So long as I wasn't actively working to solve the problem, I was driven mad by the knowledge that we were heading for disaster.
If you're new to programming, steer clear of design patterns. If you're a working python programmer who's curious about how other ecosystems use design patterns, try https://www.cosmicpython.com/
I'm starting a new job doing exactly these things in order to reduce the carbon intensiveness of heavy industry, specifically cement production. I'm hyped because I think the technical challenges aren't too daunting, and the prize is huge.
And they're free to continue their speech elsewhere. Cloudflare and Voxility are within their rights to refuse service to a client on the basis that the client is persistently associated with terrorism and kiddy porn.
Why is that a remotely controversial statement? Nobody is suggesting that chan-tards should be rounded up for unamerican activities, and I'd be the first to speak against that, but CF don't need to tarnish their brand with 8chans bullshit.
They're free to withhold their support and so express an opinion.
I had issues with depression when I was younger. Self-harm, severe depression, suicide attempts, the whole gamut. Wasn't hospitalised, but that was the next step.
Looking back on it from my thirties, I've come to the conclusion that most of my problem was disturbed sleep patterns, and the rest was unhealthy thought patterns that became self-perpetuating.
Medication didn't help me in the slightest, just made me worse. Getting some sleep and engaging with the world around me is what made all the difference. I'm skeptical of the value of anti-depressants, and some of the side-effects are deeply troubling.
The problem is that when I was in the midst of a depressive episode, I wasn't capable of fixing those things. Telling a depressed person that they just need to think happier thoughts, get some sleep, take a bath, go for a walk is utterly pointless.
Made.com | Backend engineers and Architects | Soho London | http://www.made.com | Fulltime, ONSITE
Made.com is a rapidly growing online platform for bringing high-end design to the mass-market.
We apply ideas from DDD and event-driven architectures in a Python context, and we're looking for talented devs with exposure to event-sourcing, CQRS or DDD in any language.
Top-notch TDD skills are a must; experience with Ansible, Docker, and AWS would be welcomed.
I'm running Arch on a Dell M3800, most of my colleagues are running various Ubuntu flavours on the same hardware. Works well, up to and including the touchscreen.
Battery life is poor compared to a Mac, but it's really light given the compute power.
Heuristics. Really complex heuristics that defy simple codification: the feeling that a particular group of stones just isn't quite safe yet, the feeling that there is weakness in a structure on the other side of the board that can be exploited, the feeling that this corner is too hot right now, so you should definitely extend instead of the hane.
If you're not already a go player, and want to get started, come sign up on online-go.com and ping me, I'm pathogenix.
The same arguments were made about object orientation: I've never needed it, it's useless baggage with no real world benefits, it sounds great in theory but has no practical use...
I've built hypertext APIs, and they worked really well.
We had a(n overly) complex domain model where most of the complexity was around managing a permissions model for access to resources. We tried a whole bunch of ways to represent the actions available to end users, but the only one that worked really well was to advertise a URI when you could do something, and to omit it when you couldn't.
All the nightmarish logic was safely hidden behind the uniform interface. Clients only needed to know that they should follow links, and that the absence of a link meant that a resource wasn't available to them because reasons. It was a beautifully natural mapping of a difficult problem domain into a simple consumption model.
As a bonus, we could change URI structures around when we felt like it, and our clients never missed a beat, because they always followed links from a well-known entry point.
It's not always the right choice, there is plenty of room for simple RPC, but for workflows, and dynamic discovery of resources ReST works a treat.