bobfromhuddle
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.
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.
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.
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.
Nobody depends on 8chan. 8chan is not comparable to "air".
This point is so incredibly banal that I'm surprised to find myself making it.
If that's your honest reading of events, then you're the problem here, my dude.
* Chat - Weechat + WeeSlack (https://github.com/wee-slack/wee-slack)
* Pair Programming - tmate.io + neovim
* Google Play Music - tuijam(https://github.com/cfangmeier/tuijam)
I really like bat (https://github.com/sharkdp/bat) as a cat replacement, and I've been enjoying using entr (http://entrproject.org/) for running tests automatically when code changes.
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 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.
Send a CV to [email protected]
The vts module has been updated in recent months to support more granular reporting of request times, but it's had everything we need for a while.
It exposes metrics either as an html page or a json api.
Battery life is poor compared to a Mac, but it's really light given the compute power.
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.
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.
State is carried by the client, the client traverses links to find out what it can do, the responses are described by a published content type, and the content type defines the semantics of the protocol.
It's not hard, but people like to pretend that it is. Nothing says you can't stick to GET and POST, nothing requires weird headers.
"ReST in Practice" is a great introduction for engineers.
I'm an architect helping to move a a cluster of monoliths to a proper service-oriented setup; some of the teams work in PHP Symfony with MySQL, some work in Python 2.7 with Postgres, some in Python 3.4 with [insert hipster technology here]. We use Redis and Couchbase at various versions for different systems, Eventstore for messaging, and Elasticsearch.
That's a lot of moving parts to keep updated, but because we're deploying docker containers to production anyway, it's really simple to get up and running by just running `docker-compose up` from the root of a project.
tl;dr you're correct, unless you have to work in multiple systems that can version their infrastructure separately.
I'm not a fan of the spec, but overall it seems to strike a good balance between what is specified and what is left out. To compare this to SOAP is missing the point.
What killed SOAP was an insistence on treating HTTP as a dumb transport - thereby breaking the constraints of the interwebs, the inherent brittleness of RPC, and the lunacy of the WS-* stack.
None of that applies here, it's closer in spirit to AtomPub, which is still a pretty decent standard, but just happens to be in XML which everybody hates nowadays.
I think a lot of the commentators in this thread seriously believe that having a different data format and interaction style for every API on the internet is somehow "simpler" than adopting a loosely defined set of conventions and writing them down somewhere as a standard.
I had my first son when I was 22 (now 31), and my career has continued to go from strength to strength. There is adequate time in the evenings, or on commutes, to read and ponder, and I find time at work to investigate technologies that will have a positive effect on the business, because that's my job. Since then I've learned three or four new languages, taught myself a whole bunch of crypo-stuff, got down with the Agile crowd, implemented machine learning and search techniques, and become a software architect.
I think you'd be surprised at how many employers would rather employ happily married young men with children, because they know that they're less likely to be job hoppers; you might be right that early-stage startups are no longer a viable choice, though, unless you're sure they're going to be around for at least a couple of years.
Having said that, I joined my current company six years ago as employee number 5. It was founded by a mid-thirties guy with a wife and kids, who re-mortgaged his house to get the capital he needed.
Having children needn't prevent you from doing meaningful and interesting things with your career, you just need to distinguish between what's important, and what's recreational. After a few months, once you and your wife have started to get a handle on this whole parenthood thing, you'll find more time to do the things you love.
Of course, you might find that you'd rather spend the time playing with your kids :)
That's a fashionable notion in our post-modern world, but wrong. Young rhesus monkeys display gender-specific toy preferences in line with human behaviour: http://www.sciencedirect.com/science/article/pii/S0018506X08...
Boys and girls are different, though I'll agree with you that most of the pressure to look good is societal rather than innate. Worse: most of it comes from other women.
As you're doing so, move all those queries into one big fat DB class, and when you spot groups of related queries, split them out into their own classes.
The next priority should be to get rid of the PHP from the DB - if need be create another huge class with a zillion if-else statements.
You need to modify the code to simplify it. You don't need to improve the design, you just need to dumb it down until you can understand where all the parts are. Stabilise, simplify, then refactor.
Senior JQuery, CSS, HTML developer - London, UK
Huddle are hiring in London - we're a .Net shop with rapidly growing user base, and we're currently expanding our dev team to work on our online collaboration system.
We're funded by Matrix, are the leading small company in our space, and are shooting for world domination.
www.huddle.net - mail jobs at huddle.net and tell them Bob sent you ;)
IANAL, however, just a programmer.