satyrnein

If the dev environments are on AWS with real S3 buckets (etc), and everything runs as an auto scaling group, is it not possible to use the same exact docker images (and terraform) in dev and prod?

We haven't achieved it (yet?) but that's the direction I was aspiring to!

Anyone have any recommendations for a product that implements a referral program with reasonable defaults on top of Stripe subscriptions?

In that case, we might only be differing on terminology. In my understanding, scrum's defining feature was the fixed time box. What you described sounds like kanban to me!

On day 1 of the sprint, aren't they all in the same stage?

I just checked and seems like IE was down to around 60% and Firefox up to a third when Chrome launched (not sure how long before that the project was greenlight). So it probably still played a role.

At time it was a defense against Microsoft embrace-extend-extinguishing the web through their dominance with IE. Remember ActiveX, VBscript in the browser, etc?

Interesting, what I like about kanban is that (in my opinion) it explicitly recognizes that work proceeds through specific stages, and therefore tickets go through a mini-waterfall. Waterfall is great with a small enough batch size. In contrast, scrum seems to pretend that design, development, code review, QA, etc, all happen at once throughout the sprint.

Libertarians would argue that wealth inequality is the natural outcome of consumers exercising their agency. I recall one asking why progressives are obsessed with income equality but not trying to address inequality in number of sex partners.

I wonder what is at the end of this road. Hopefully it's not just that some junior artists get fired and everything else stays the same.

Does the line between novel and graphic novel blur, as more authors "direct" AIs to depict what's in their brains?

Is this how we get to infinite generated worlds in the metaverse?

At least it's fast to try again!

What strawman? This time I actually am confused.

The comment I replied (and the article itself) seem to imply that, if you monetize via advertising, that your business isn't really about whatever you say it is. I was replying that I fail to see how that's different from non-advertising-fueled businesses.

For example, Facebook isn't really about connecting people, but a hypothetical competitor with the exact same feature set that charged a subscription fee instead of running ads would be about connecting people?

Only semi related, but i wanted to install a USB jack in my belly button so i could charge my phone off my visceral fat, which seemed like a win-win. Probably best I didn't, though, because this predated usb-c...

Most companies exist for motive X, which they do by providing value Y, then monetizing it via method Z. X is almost always "profit" and Z is something boring like selling physical items, subscriptions, ads, etc, so the mission statement is about Y.

The following statements are true but not very interesting:

Microsoft was never about computers on every desk and in every home, it was really about selling software licenses to make money!

The Super Bowl was never about football, it was really about selling ads to makes money!

Wal-Mart was never about saving people money so they could live better, it was really about selling physical items at retail to make money!

Facebook was never about connecting people, it was really about selling ads to make money!

Is the Facebook one any more insightful because the monetization strategy is advertising?

Since you are not confused, what policy would you propose?

So clear up my confusion: what should we do about it? Are we supposed to commit their human rights abuses for them, by denying entry to their best and brightest?

AWS offers instances with RHEL for a higher rate.

Sure it is, unless they have passed laws against emigration, like North Korea. (Of course, those laws would rightly be seen as totalitarian.)

Immigration was compared to "colonial appropriation" which doesn't exactly sound voluntary.

In contrast, it would be a terrible thing to forcibly lock people into their birth countries to stop brain drain.

Accepting immigrants who desperately want to come is nothing like taking resources by force.

I'm kind of unclear how the device part is supposed to work. Let's assume the work laptop is fully locked down, and employees' personal laptops are completely compromised with each keystroke sent directly to ransomware rings. Are you supposed to block your employees from logging into your SaaS apps and internal web apps from their personal devices? What's the mechanism for that?

At a previous company I declined the "perk" of the company paying for my phone plan, because it required giving them control over it. I was mostly worried about losing my phone number accidentally upon parting ways.

Nowadays, Android can have a Work profile that your company can control (and wipe, for example) that doesn't affect your personal stuff. It's actually convenient because you have a separate instance of Chrome, which is a good workaround for mobile Chrome not supporting multiple profiles inside the app like the desktop version does.

The question was about finding a similar developer experience, not how to create similar user experiences.

From a management perspective, the fiction of the full stack developer that is equally skilled at everything is the easiest. You stick with that until you complicate your architecture (wisely or not) to the point where having specialists outweighs having to manage multiples queues of work and dependencies.

I think the causality runs the other way. Once the frontend had gotten so complex that it required a specialized team, solutions arose to reduce the back and forth necessary between frontend and backend teams.

Thanks, so is this a drop-in replacement for paid Cypress, but better? Pricing seems similar with $6/1000 tests.

A few questions on dependencies: do you need to be using the paid Cypress dashboard? do you need to be using Github for your repo?

The video says it's 20 minutes end to end, somehow.

If you want to do rolling/canary deployments without downtime, or gradual rollouts to subsets of users, or a/b testing, you will have multiple versions running in parallel against the same database. Plenty of "serious work" happens that way.

You still need story point estimates on the previous items, or some reason to believe that previous stories were of similar size (which is also a form of estimate).