draaglom
The ICC prosecutes individuals not states, so there's no contradiction here.
>Given Palestine is a signatory does it mean they have to take action to extradite the Hamas leadership to face trial?
Yes
>What consequences do they face if they fail to do that?
There's no penalties built into the statute. It tends to have diplomatic blowback. See [1] for a prior example.
As a forecaster: It's fun! It's an interesting way to learn about the world -- rather than gathering inert facts, you're forced to integrate them into a mental model, and then your model is tested for its validity empirically. It's also difficult and competitive, if you like that sort of thing.
As a consumer of forecasts: There's good research that prediction markets and other forecast aggregators are the best technology we have as a society for quantifying uncertainty. Not everyone will listen to them, just like not everyone eats their veggies, but c'est la vie.
I don't think there's too much risk of self-defeating forecasts (where a low forecast lulls decision makers into a false sense of security) - at least not yet. They're still pretty niche.
The sites which host these forecasting competitions correct for the bias against rare events through what's called "proper scoring" rules -- there's some specific maths to it, but the short version is that you're exponentially rewarded for being a correct contrarian and exponentially punished for being confidently wrong.
There are limits to that too, of course -- the folks in the article will "only" have made on the order of mid hundreds to low thousands of predictions, so roughly speaking, you can expect these people to be calibrated for 1% or 0.5% odds but probably not 0.1% odds.
This is mine on Metaculus (mentioned in the article):
There's still a bit of noise at 205 predictions but you can see a pattern emerging!
Your framing is "the marginal cost of any given request rounds to zero" which is probably true.
Another likely true framing is "there are substantial numbers of users on legacy plans who in aggregate cost more to serve than they pay".
This picture appears to be (presumably) the actual team doing a team building activity.
This is both a reasonable choice given the inferred instrumental goals of the blog, and a honest reflection of (one part of) the team life, assuming it's a photo of the real team.
and previous discussions on HN: https://news.ycombinator.com/item?id=15591190
https://www.lazard.com/media/2ozoovyg/lazards-lcoeplus-april...
It looks like utility solar is currently ~33% the LCOE price per kwh of nuclear or 85% of the price of gas (CCGT).
This is an increase relative to 2021 (20% of nuclear / 60% of gas)
(As I understand it, the cost increase between 2021 and 2023 is from cost of capital and shipping)
Naively projecting out the LCOE trajectory, it indeed does not look like it's going to get to be 'dirt cheap' soon - eyeballing, the LCOE curve over time appears to be flattening towards a 5% or smaller cost reduction year over year.
As a result, the majority of SaaS businesses aren't profitable, and people talk mostly about MRR.
As I understand it, Instagram is a python codebase and (guessing) may be the primary motivator here.
Probably the first, say, 100 person-years of effort poured into the Instagram codebase were done at a time when product development velocity, not performance, was the main priority.
- replace RSUs with cash payments on same vesting schedule @ equivalent of final sale price
- keep RSUs despite being private (apparently SpaceX issues RSUs just fine & has regular liquidity events)
Booting a serverless function with 100s of mbs of modules takes an appreciable time - to the point where some folks webpack bundle their serverless code
There are several providers - Okta, AWS, and more.
Fair warning: expect to pay enterprise tax on all your SaaS plans for the pleasure of allowing you to do SSO!
What do you think explains the difference?
* Are there ways you can explain yourself better that others are doing?
* Could the problem honestly be with your code being hard to understand? Could you simplify?
* Could you deliver in smaller chunks, that are each easier to understand?
* Is it about working on a tech or product area that they aren't so familiar with? Perhaps you can help bridge that gap with a lightning talk or some new documentation?
>I have not had a direct conversation as I'm not sure how to go about it or phrase it. We seem to have a good relationship and I don't want to potentially ruin it going about this in the wrong way.
You've got to place trust in your colleagues that you can have adult conversations about what's working well and what's not. It doesn't have to be a big deal!
It could be as simple as:
"Hey <name>, I feel like a few times lately PR reviews hasn't been smooth. Have you noticed that too? Is there anything you think I could do differently?"
>We have basic standards
One thing that could help here is improving your team standards for a PR author! E.g. at my company, we have a PR template which encourages you to add a screenshot/screencast of your feature working.
We also encourage adding test steps to our PR template, to make it easy for reviewers to try the thing themselves. Good test steps might look like:
* Run the app as normal
* Turn on feature flag XYZ
* Head to localhost:3000/new-page and click all the widgets
* You should see the widgets created in your db with this query:
It sounds like work, but it's probably the steps you did anyway before you put the PR up! so it's more of a mindset thing
* Are their code reviews _of you_ poor in particular, or are they poor in general when reviewing anyone's code?
* Are they reviewing your code in good faith (and are just finding it challenging) or in bad faith (and can't be arsed or don't like you / the project / etc)?
* Have you had a direct conversation with them about it? (Is your relationship with them strong enough to enable that?)
* Do your team have standards for a code review? Expectations for an author and for a reviewer?
* It suggests the person understands the bigger picture behind what they're doing (rather than just "punching tickets")
* If your code sits in a 'financial critical path', this usually implies stricter requirements in your engineering in some respects -- you'll probably have had to think harder about reliability, cover more edge cases & co-ordinate with others more around requirements
IEA claims datacenters account for 1% of electricity demand and data networks are another 1%:
IEA (2020), Data Centres and Data Transmission Networks, IEA, Paris https://www.iea.org/reports/data-centres-and-data-transmissi...
Now, those figures are _electricity_ not _carbon emissions_ - so perhaps the 3.8% figure includes e.g. datacenter construction emissions, or emissions related to producing servers and networking equipment?
"when was running invented"
"how many terashits does the ps5 have"
Without your app, it'd cost your clients $X in hours worked doing the book keeping, organisation and confirmations plus $Y in lost business due to mixups / confusion / etc from the alternatives.
What units you charge in to capture this fraction (billing for usage, per seat, whatever) is your second question, but you want to keep it as simple as possible while aligning to the value that the client is getting. Per successful booking probably makes sense here (I would imagine...)
>But what do I do with the cancelled bookings [...] I still pay for the sent SMS notifications :(
I'd suggest accepting these as a cost of doing business and pricing high enough that it doesn't matter.
Why commit to a tighter SLA than you legally have to?
e.g. this study[1] in the UK puts "IT" as <6% of household electricity use, which is itself a fraction of a person's total energy use.
edit: and this[2] indicates that datacenter usage is also not very significant.
Therefore, no amount of optimising web pages will make a meaningful difference to carbon output.
As web professionals, it's better if we direct our focus towards more productive areas around this goal -- by e.g. donating to relevant campaign groups, or using our tech skills to produce media on the topic.
[1]: https://assets.publishing.service.gov.uk/government/uploads/...
[2]: https://www.iea.org/reports/data-centres-and-data-transmissi...