There is significant support for the initiative. Initiatives tend to lose steam as time go by, so it might not be enough in the end, but like Brexit, don't underestimate it.

Also because, at least on our side, the account was in an inconsistent state: we were correctly enrolled/validated, but could not access the signing interface.

So it looks like even if no one actually updates, the vast majority of the cases will be caught by automated tools. You just need to give them a bit of time.

You don't even have to be as organised as in the example, LLMs are pretty good at making something out of ramblings.

I agree it's best if working in isolation, but if you need to synchronise then estimations make sense.

If you need 3 months to implement something, and another team 1 week, and both need to be ready at the same time; then if you actually know those estimations the second team can wait until then and do something immediately useful in between.

That's just too slow for business in my experience though. Rightly or wrongly, they want it now, not in a couple of sprints.

So what we do is we put both the investigation and the implementation in the same sprint, use the top of the range for the implementation, and re-evaluate things mid-sprint once the investigation is done. Of course this messes up predictability and agile people don't like it, but they don't have better ideas either on how to handle it.

Not sure if we're not enough agile or too agile for scrum.

Not at all, it has one of the lowest rate in Europe along with the UK. It's very hard to get the building permit required to install one. Portable AC has had a boom those past few years though (because it doesn't require a permit).

I tried various combos of weight* reps, and in the end the optimum was somewhere in the middle because no matter how light the weight there was a limit for me at about ~150 reps.

In my case, the curve would be: total volume increases quickly initially at you go from max weight/1 rep to something like 20/30 reps, then something of a plateau as things equalise, then it goes down again as you reach the max reps threshold.

With good naming it should be pretty obvious it's a Foo, and then either you know the type by heart, or will need to look up the definition anyway.

With standard containers, you can have the assumption that everyone knows the type, at least high level. So knowing whether it's a list, a vector, a stack, a map or a multimap, ... is pretty useful and avoid a lookup.

And if you add the value to the customers, then it's through the roof.

Maybe the reverse is more clear: if air travel didn't exist, it would have a huge economic impact; a clear proof of the value creation. Airlines just happen to capture essentially 0% of it.

We're having troubles with memory usage when using SQLite in-memory DBs with "a lot" of inserts and deletes. Like maybe inserting up to a 100k rows in 5 minutes, deleting them all after 5 minutes, and doing this for days on end. We see memory usage slowly creeping up over hours/days when doing that.

Any settings that would help with that? It's particularly bad on macOS, we've had instances where we reached 1GB of memory usage according to Activity Monitor after a week or so.

There's probably generally a bit of correlation. But just because someone can be very focused and go to extreme lengths in one aspect of their life doesn't mean they can consistently do it in every aspect of their life.