StudioLE

You must mean ie7, surely?

I was developing for ie6 back in 2010 and I considered those to be dark, dark times. I can't believe it hung on for another 3 years?

The author pronounces it [aɡe̞] with a hard g, like GIF, and is always spelled lowercase.

I can't be the only one to think GIF is a terrible example for pronunciation?

It sounds like your process isn't working because you're treating Tuesday's deadline as just a feature freeze rather than a full freeze.

If you want to go ahead with the full freeze then if it fails QA the feature should simply be rejected. Revert the change make the fixes and wait for the next Tuesday deadline to resubmit it.

If you're keen to continue the feature freeze then you need to move forward the freeze deadline and agree very specific timings with QA. For example: Feature freeze at 9 am Tuesday morning - so devs must submit all features before end of the day Monday. QA have all Tuesday to review for a deadline 9 am Wednesday.

That gives the dev at a minimum some time on Wednesday to address any issues, but more likely QA can come back quicker so they'll have some time on Tuesday as well.

Dev must submit fixes before a 2 pm deadline on Wednesday. QA do a second review and have all feedback by 9 am Thursday at which point it's simple commit/revert.

If the DuckDuckGo result for your search doesn't yield anything then just append it with g! and it'll take you straight to the Google results.

It's a useful trick but very rarely do I find I need it. Only really when researching a very specific error.

Proton Mail and Tutanota always rank high on lists of privacy friendly email providers.

You don't have to look at reducing your Google use as a monumental effort. You can slowly transfer, minimise the number of services you use.

Simple - Switch your default search provider to Duck Duck Go.

Easy - Switch to Firefox

Mid - export your documents from Google Drive

Complex - Transfer your primary email to another provider.

Has GitHub actually done anything negative? Your comments really just sound like fear mongering, I can't see any actual issues.

What is the bloat you're referring to? The UI is clean and simple. Navigating and searching code is intuitive. The issue tracker is basic but reliable. Releases are clear. GitHub Actions are complex but featureful and incredibly useful. GitHub Packages are basic but useful. GitHub Copilot is damn impressive.

Brand guidelines almost always state not to stylise the logo, so this would be the correct way of doing things.

You should consider who your audience is, are they all CLI experts familiar with the difference in syntax? That seems unlikely.

I'd always write documentation in a way that's accessible to most users. The difference between $ and # syntax is highly esoteric.

sudo on the other hand is familiar to almost everyone. It's one of the first things mentioned in beginners guides.

I wouldn't even prefix your commands with $ as an experienced user is quite likely to include that when copying the command.

A lot of people are citing the arch wiki as a standard that uses # but isn't the entire meme around arch that its a notably complex system?

Can't you just select the text without the sudo prefix..?

Aren't you enjoying everyone listing their favourite text editors and the fact they use ssh?

Damn. Even the website documenting their design is ugly as sin.