The truth, in a way that isn’t overly critical of my current employer and emphasizes what I hope to get from a new opportunity. I take it less as “what’s wrong with the company you’re leaving” and more “what are you looking for from a company you’re interested in jumping to”, which has very similar answers but focuses on the positive and also gives them actually relevant information that they can use to help you. They can connect the dots that the reason you’re looking for that is because you’re not finding it there, without you having to trash a company yourself.

Yeah, the benefit of the new technology doesn’t outweigh the slew of minor annoyances associated with making it work in a world designed for regular sized monitors.

Yeah people do that, until you’re sharing a code window and then need to see if it works on a browser and then your dev tools are popped out so you have three windows…or you don’t want to just have one meeting and one window visible, you also want slack or a window for googling or something similar…

It’s all workaround-able, it’s just minor annoyance after minor annoyance lol.

Everyone at my work who has this runs into issues whenever they need to share their screens, apologizing for low resolution or painstakingly resizing every window to mimic multiple screens anyway.

What do you mean by “established” though? Is a community with 80 people from my instance and 500 more across all other instances less established than one with 250 people from my instance and 30 more across all other instances? If so, how? Legitimate question - I’m new here and it’s possible there’s a good reason to care, but I can’t see one.

Is “how many people from your own instance subscribe” even a useful metric? I don’t see what value it brings, I don’t care how many people on there happen to also come from my instance, I just want to know which instance has the most active version of this community.

It’s not like all those subreddits existed at 0.1 though.

The problem is, loading things takes different amounts of time. I once tried to implement a real loading bar for an app because it took long enough to load that clients needed some indication that the app hadn’t crashed. There were seven steps, so I naively made each step take about 14% of the bar. Then I tested it, and it just jumped to step 4, sat there for the entire loading process, and then jumped to 100%. Because loading isn’t linear.

The only way for loading bars to work is for them to be fake.

“Just give us a point value, we don’t need a time estimate.”

“Okay, so 2 points is roughly equal to 12 hours…”