I know Safari 15.3 doesn’t support feature Y, but I also know the current version does. Now I want to know if I can just use the feature or if I need to program around Safari 15.3. It would be nice to just look at the server logs from last month and see if someone still uses it.

30 minutes before the show?

In my local theater you also have to ‘reserve’ a seat when you buy the ticket in person. Don’t ask me why.

maybe everyone here is just a rude little shit.

Or maybe you’re just a snowflake that can’t handle criticism.

constantly dropping calls, video quality is awful […], audio is terrible,

I have none of these issues with Teams. Maybe your internet connection sucks?

Just to provide some data on the radiation dose. It’s everyone’s own decision whether a ‘willy-nilly’ PET scan is worth it.

From the English Wikipedia:

FDG, which is now the standard radiotracer used for PET neuroimaging and cancer patient management, has an effective radiation dose of 14 mSv.

The amount of radiation in FDG is similar to the effective dose of spending one year in the American city of Denver, Colorado (12.4 mSv/year). […T]he whole body occupational dose limit for nuclear energy workers in the US is 50 mSv/year.

https://en.wikipedia.org/wiki/Positron_emission_tomography#Safety

From the German Wikipedia:

Es ist bei einer Strahlendosis von 1 Sievert (Sv), der 100 Menschen ausgesetzt sind, mit 5 Todesfällen durch Strahlenkrebs zu rechnen […]. Man müsste also 100.000 PET-Untersuchungen durchführen, um 35 Todesfälle an Strahlenkrebs (nach einer mittleren Latenzzeit von etwa 15 Jahren für Leukämie und etwa 40 Jahren für solide Tumoren) zu verursachen, das heißt etwa eine auf 3000 Untersuchungen

If 100 people received a radiation dose of 1 Sievert (Sv), one would expect 5 deaths due to radiation-induced cancer […]. One would need 100,000 PET scans in order to cause 35 cancer deaths (after a median wait duration of 15 years for leucemia and 40 years for solid tumors), which is about 1 in 3000 scans.

https://de.wikipedia.org/wiki/Positronen-Emissions-Tomographie#Strahlenexposition

Is this not rude:

I checked the code and I’m appalled. There are more BLOBs than source code

No. The commenter is voicing their own feelings and explains why they have them. There is neither blaming nor rudeness here.

And this:

I understand that removing BLOBs isn’t a priority over new and shiny features. But due to recent events, this should be rethought.

It would have been nice if you had explained why you think this is rude. The author expresses understanding that the maintainers’ priorities don’t align with the author’s. This seems to be an uncontroversial statement to me.

Then the author explains (I agree, it’s more a hint than an explanation) why they think the priorities should be changed. In my view their argument is sound. Again, there is no blaming or rudeness here.

They should have opened with a complement

I assume you mean “compliment”.

I’ve often heard of the “sandwich technique” – start with a compliment, then voice criticism, end with another positive thing. I find this is an appropriate procedure when voicing open feedback, that is, good things and bad things. However, this is a Github issue. Its whole point is to point out a perceived problem, not to give the maintainers a pat on the back or thank them.

I cannot fathom what in this issue description gives rise to your concern. It’s worded very calmly, clearly explaining why the author thinks these BLOBs shouldn’t be there, expressing an understanding that it’s not a top priority and even closing with a thank you.

My manager once accused me of overinflating my (granted, very conservative) estimates just to be able to pull off a Scotty and be early in 10% of the time.

Teach this to your manager: At the beginning of a task, uncertainty is highest. Under no circumstances should you give an estimate in ‘man-hours’. Even days is too precise. The first estimate should be in months or years (of course depending on the size of the project). Then, as your insight into the project grows, you refine that to months, then weeks, later days. A vague estimate with a lower and a higher bound is way more useful to your manager than a ridiculously ‘precise’ but highly speculative number.

This lesson was brought to you by either “Code Complete 2” or “Rapid Development” by Steve McConnel, and by my former manager who wanted projects estimated in minutes.

A text editor that doesn’t assume that the keys on my keyboard are in the same order as yours.

Honestly, I find it great that Linus still manages the Kernel after all this time.

Aww. I confused “communities” for “instances” when I read the title. Thanks for pointing it out.

Your data quality is questionable. You list only 2 communities for feddit.org. Lemmy Explorer has 148. I doubt that they’re all ‘suspicious’. And if they are, then that flag is itself suspicious.

Please avoid any and all situations in which you might have the chance of handling any kind of categorized data, for the sake of all of us.

While we’re giving advice on good reads, I foudn “Code Complete” to be much more useful than “The Pragmatic Programmer” (also about 10x the size).

At the end of my 20s I can feel that I’m becoming stupider. Reading texts or just thinking about a problem take more effort than they used to.

Firefox has a context menu entry “copy link without tracking” when you right-click in the address bar.

No, it does.

I’m sure that’s a study in psychology about how survey results are significantly better with dog pictures just waiting to be written.