We are cloud FinOps experts, helping our customers to reduce cloud spend using innovative commitment trading techniques. We have several internal products, and a customer-facing web portal.
We are proud of our culture of openness and transparency, with an emphasis on learning. We operate autonomous self-organised teams, and we value everyone’s ideas and opinions. We do a lot of pair programming to share knowledge and experience. We currently work fully remote, with occasional visits to our London office for collaborative work that helps us get to know each other better.
We seek enthusiastic developers who either know or would like to learn Clojure. We currently have a diverse team of nine full-stack devs, but we have plenty of front-end and back-end work, so we can accommodate people who have a preference.
Hi I live in france and I have some experience in the fintech sector as backend java dev. Would you take people part-time or with hourly contract or something like that?
I really want to learn Clojure and deploy to prod, and I'm looking for something extra to support my family. But I also cannot leave France.
Burning the propane takes you back to CO2, which you then turn back into propane again and repeat? If your napkin maths is correct, and the process is net energy positive, doesn't this violate the principle of conservation of energy?
It must take at least as much energy to turn carbon dioxide into propane as you generate when you burn that propane to generate carbon dioxide.
> If your napkin maths is correct, and the process is net energy positive, doesn't this violate the principle of conservation of energy?
In theory, yes, but you need to take into account all the energy that goes into the process, which includes the catalyst, and also the actual capture of the CO2.
The way i read it, this is "just" a way of turning already captured CO2 into fuel again in an efficient way.
Still, it does seem a little bit too good that you can obtain 3 kWh of energy by spending 1.6 kWh, but i guess time will tell.
Burning propane produces CO2 AND water. I think the missing bit is the energy required to split the water into hydrogen and oxygen before the hydrogen is used as an input to produce the propane.
Heat pumps do not create heat, they simply move heat from one place to another, which is an entirely different beast.
Using a traditional resistive heater, you're roughly creating 1 kWh of heat by spending 1 kWh of electricity (there is some loss), but with a heat pump you're moving heat, which is also why heat pumps become much less efficient the colder the temperature as there is less heat to move, and many residential heat pumps include a regular resistive heating element as a backup.
Isn't the input electrical energy and the output of burning the propane heat? If you convert the heat back to electrical energy, you get much less than you input into the reaction.
You are correct, you cannot sell Convertible RIs on the RI Marketplace.
I think it is going too far to say that RIs are a trap: the rules are pretty transparent. I agree with you that if your infra is elastic or evolving then you need to be very cautious about making large or long-term commitments.
I think the convertibles are a bit of a trap, though - even though the rules are transparent. You might overprovision to begin with (which you may not realise), then you can't even sell them.
That used to be true, when AWS only sold AZ-specific RIs, but for a long time now AWS have (by default) sold region-level RIs instead, and these do not include a capacity reservation. You can now purchase Capacity Reservations [0] on their own.
It is great to see articles like this, as Reserved Instances are a fantastic way to save some money, and they are widely misunderstood.
I work for a company [0] that specialises in Cloud FinOps, and I helped write our in-house billing system, which has to deal with _all_ of the intricacies of Reserved Instances, so I know very well how deep this rabbit hole goes.
This article opens by categorising RIs as "one of the most complex but crucial AWS offerings", but I think it perhaps glosses over some of that complexity, which might cause people to get burnt. For example, it suggests that you can safely sell your way out of trouble on the RI Marketplace, but in many cases you can't: there are 5 products you can buy RIs for (EC2, RDS, ElastiCache, OpenSearch, and Redshift), but the RI Marketplace only lets you sell EC2 RIs, and only Standard EC2 RIs at that, not Convertible.
I don't want to take anything away from this article, nor do I want to frighten people away from buying RIs, but please take care. If you aren't sure, I encourage you to use one of the many companies operating in this space to help you out (and you certainly don't have to give away 20% of your savings to do that).
We are cloud FinOps experts, helping our customers to reduce cloud spend using innovative commitment trading techniques. We have several internal products, and we are currently building a new customer-facing portal.
We are proud of our culture of openness and transparency with an emphasis on learning. We operate autonomous self-organised teams, and we value everyone’s ideas and opinions. We do a lot of pair programming to share knowledge and experience. We currently work fully remote, with occasional visits to our London office for collaborative work that helps us get to know each other better.
We seek enthusiastic developers who either know or would like to learn Clojure. We currently have a diverse team of nine full-stack devs, but we have plenty of front-end and back-end work, so we can accommodate people who have a preference.
