in what industry does your previous salary not matter? (Not a snarky ask btw.) I have never entertained an offer blow my current salary, so personally find them highly correlated (sw eng).
Higher salaries will get disclosed more, because if I get an offer below my current salary, then I can disclose and at the very least get a match or refuse the offer. At a lower salary, there is a higher probability that the offer is higher, and my current salary does not matter.
I believe that people more rarely accept a downgrade in salary, so the probably of acceptance is also conditioned on the current salary. What this means is that the effect is biased and probably non-linear, but I wouldn't qualify it as non effect.
in software, this is where "catastrophic" data leaks and security vulnerabilities come from, an engineer or team deciding to roll their own version of a security or cryptography library without having the proper experience to even know what they don't know.
I can't seem to find it, but I read a description for a game in development that seemed really similar to this, a farming/crafting simulator where you start in the basement of a house and can expand to the kitchen etc. You have to avoid the house cat etc.
Totally different game of course, but this reminded me of Katamari Damacy! In many levels you start tiny in a room somewhere, and have to roll up paper clips and thumb tacks in order to grow and roll up successively larger things, while avoiding gigantic pets, and so on. Apart from being hilarious and sometimes challenging, I also found it an interesting psychological effect to come back to the same place when you're 100 times larger, now able to roll up humans, cars, the entire house... :)
Katamari is a casual game (I prefer this genre) but now I wonder if there would be some way to make a more "simulationist" game that uses this scaling effect somehow.
wow, thank you for recommending this - the graphics are not quite what I'm after, but the concept definitely is - albeit the tiny humans seem a bit too large to live in mouseholes
this is an issue I have battled as well. Docker is great for normalizing the execution environment; which should be a huge boon for developer tooling but on MacOS having your laptop sound like a hovercraft just to have some files watched for hot rebuilds is no bueno.
Even if you don't change the interface, by doing fun things like writing types in go that accept strings or ints as ints to strangle a perl server binary and proxying unimplemented handlers, you can still end up with problems. We started having issues with our db getting knocked over by callbacks from our server fleet on an endpoint we hadn't even rewritten yet. Turns out the slowness of perl handling the tls connections had shielded the db and forced retries, switching to go meant the db was hammered with the concurrent requests from perl workers, unhindered by the tls handshake.