Doesn’t it flip around for small scale? Paying 100x the cost for something, all in, it’s cheaper to rent for small workloads like 10m/day.

At 10x you have to be at hours per day and 5x you’re at 4h.

Is latency of the network that noticeable? Aren’t we talking low hundreds of ms at worst here? Much lower for something close regionally.

The cost of sharing recordings of video you collect anyway is near 0, and this provides videos of public places.

What's the value of a recording inside my house to the police? That requires paying a human to go around recording it?

Even if my neighborhood is a public place, I don't agree that most public places should have 24hr video surveillance.

The cost of sharing recordings of video you collect anyway is near 0. If not police, many stalkers would definitely appreciate this information.

Almost, but not entirely, quite unlike the truth.

This gives you a distribution unrelated to active use, puts users in the same bucket (with the same number you’re going to have the same users in the first 10%) and links combinations together.

Often problems are more complex than they seem at first sight and I have found it’s a good approach to think “what am I missing” rather than “lots of people must be making very obviously bad decisions” and reach the latter conclusion only after more work. Usually I’ve missed something.

> Is that a problem?

Yes! Are you totally missing some countries, did you set it to try and hit 20% but it’s actually 60% of traffic, does it happen to include some VIP type users, how does it impact the thing you’re trying to measure while you do this?

Do you give qa user ids in the right ranges to get applied and non applied views?

Even then you’re not able to get specific combinations.

> Are you trying to do a bunch of separate staged rollouts at the same time?

That would be very common yes, otherwise a staged rollout can be a big blocker.

But more than that it means there’s one user who always gets the beta testing of everything for example.

I think it’s a lot below 80%, really.

> No developer or SaaS should be needed to make them understand tasks are checked out when you start work and contain instructions and when you are done you move the ticket to DONE.

However jira, trello, linear and basecamp are all SaaS. Then when you create a ticket, what starts the agent? Linear has integrations however that either needs codex/github running things (another SaaS) or you need to do your own agent setup.

This is a replacement for jira/etc for a project, rather than an addon.

A few scattered thoughts but a board with decoration or art of a similar size could be a nice cover, the other (more building required) would be to look if there’s a way you can fold down/away the monitor when not in use.

Link doesn't work - maybe not public?

Also things like improving devx - nicer log analysis, speeding up test suites, auto handing some CI failures, improving scripting, tooling etc.

I wouldn’t discount the value of moving small tasks away from developers, nor the value of fast cheap prototypes.

Product owners can very quickly get, for many problems, an interactive demo without coding. For lots of problems this can be somewhere from a static html page which shows the interactions to a hacked in feature that lets them actually test if it solves the customer need and try several variations before handing over much more concrete specs of what they want to happen. So much time is lost between getting an idea from someone’s head to code to use to then find out it wasn’t communicated well and then finally that the idea didn’t help anyway and we want it in a different way.

Yes yes I know someone is about to say that now there’s pressure to push the prototype out but that’s an organisational level problem that existed anyway.

And small problems can much faster to solve as well, or even move away from devs. Often people just need some text changed somewhere or html putting together, or some basic code for analysis. They could understand the logic, but the task of writing it from scratch and how to run things may be too much - now you don’t need to prioritise work for a dev to get some sql written and they can spend their time on the larger more software engineering level problems.

"that’s an organisational level problem that existed anyway"

That's very true to many organizations. One cannot just slap an AI tool on it when you are dealing with fundamental organizational problems in the first place.

"they can spend their time on the larger more software engineering level problems"

For sure, devs still needs to focus on the right type of work and maintain the balance. I built a tool to just do that: https://worktypefocus.com/