> If AWS denies you, you go sign up at any of their competitors or buy your own servers and plug them into the internet

And then your ISP kick you out.

All of them? It's a website, the servers don't have to be in the same place as your bedroom. They don't even have to be in the same country.

And then what happens when CloudFare de platforms you? It doesn’t take much to DDOS most websites that aren’t protected by something like CloudFare.

So now you just have to get deplatformed by Cloudflare, AWS, Fastly, Azure, Radware, Google, Akamai, F5, Imperva and every other DDoS protection company in the world all at the same time while simultaneously suffering from a DDoS attack that never lets up or your site immediately comes back.

Meanwhile a DDoS attack is a crime, so Apple doing something with the equivalent effect is now something you're equating with the commission of a crime.

No the Supreme Court said a long time ago that a company has “no duty to deal”. Meaning it doesn’t have to do business with anyone it doesn’t want to.

But you don't want to do business with Apple, you only want to do business with your own customers who have iPhones.

Opened the article and decided to try out the "Listen to this story" section.

After reading the article name and author, it proceeds to state "This is an AI generated narration".

Well, well, well.

How the turntables...

I doubt that author Guthrie Scrimgeour is the one deciding to add AI narration to the Wired articles.

Story points are in fact time, and I'm tired of pretending they're not.

You can sugar coat it all you want and say they represent complexity, but at the end of the day(or sprint), the higher the complexity, the more time it takes to complete.

I don't think anyone is really saying that story points aren't time. It's just that you don't know what the story point <-> time conversion factor is until your team is calibrated.

Fixing the machine at the factory can be quite complex, but you might have a technician in and out in a day or two to get it done.

Assembling 5,000 identical widgets is not complex, but it might takes you weeks or months.

Complexity and wall time occasionally move the same way on the graph (generally with wall time climbing much faster than our view of complexity), but they’re not necessarily or always so.

I tend to explain “complexity” more in terms of “at what skill level of employee would we stop seeing substantial gains in quality/speed/maintainability/etc when we assign this work out”.

Something that a senior could do substantially better/faster than an intermediate is “high” complexity. Something that the intermediate could do substantially better/faster than the junior is “medium” complexity.

Adding some fields to a form is low complexity—an intermediate or senior won’t do a substantially different job than the junior—but doing 10 fields versus 100 fields will change the amount of time it takes quite a bit. Architecting a new service will see gains to senior and beyond and is high complexity but may not actually take all that long.

Ultimately, this boils down to “how many decisions remain to be made”. Most tasks can be made lower complexity by making those decisions in detail. “Rearchitect this module” becomes medium complexity when someone turns that into “rearchitect this module following X pattern” and low when someone turns it into “move methods A, B, C into new class X and split method D into E and F along this line”.

This view of complexity doesn’t directly drive wall time, but _does_ very directly impact the variability of that estimate. The more decisions remaining and the more unknowns up front, the wider the range of possible outcomes. Reducing the complexity will reduce the range of estimates.

The problem therein is that that time depends on who is given the story. Perhaps that should be part of the estimation itself? (Who is working on it.)

Does not work on Firefox/Windows 10.

Or maybe people just have different experiences?

I ran teams on a fairly powerful i9-equipped MacBook Pro and it was unbearable. Couldn't even scroll up to older messages without it freezing up, the integrations with Office 365 were also really slow.

I wonder if airports would accept an Instagram verification badge as proof that he's not a terrorist.

Hold on, no one dare steal my new business idea.

They did participate in a fraudulent scheme to obtain the badges. If they had been verified for their real accomplishments they would still have it.

Consider the following lame analogy:

A man who has been working as a programmer for 30 years has no diploma because he is self taught. He is having trouble finding a new position because for some reason companies are asking for a degree in a related field. He decides to buy one from a sketchy random university. People find out about the scheme and the diploma is invalidated. Should he be able to keep it because he probably knows everything he would be taught at university?

This article is the equivalent of gossip magazines saying some random celebrity died because they haven't been seen in a week.

But shouldn't the cost go down for the company as well? Now they no longer need to use office space to accommodate you or provide you with a space to eat/bathroom/take breaks. Rent in the valley is a nightmare and companies could save a lot by not needing a physical space for the entire workforce.

Been working from home since march and never had a problem to switch off from work. Some days I would be working on something I consider fun and stay a bit later than usual, but most days I just move my chair 1 meter to the left to my gaming computer and go play something.