Ubuntu because it requires the least amount of hack fixes to get working.

And snap has vastly simplified software installation.

That’s rather optimistic. I’m pretty sure it’s daily. Although, perhaps it’s only once a month that it gets upvoted

What phrasing are you saying is dishonest? A quick search of proton student discount doesn’t even bring up any results from them

My mantra has always been to bring solutions not problems. Applying that to code reviews makes for a far more productive experience.

Rather than just pointing out errors in code help the developer with prompts towards the solution.

Or, if you’re too lazy to explain why something shouldn’t be done then why should another developer have to act on your criticism?

I wish this had been my experience. I pushed for so long in my last company for standards to be written, code formatters implemented and objectivity to be brought to reviews but it was always ignored.

Instead I had to endure every employee who claimed seniority (in a non hierarchical company) subjecting their opinion on style in reviews. It came up the point that I dreaded having to work with specific people because they kept triggering my PTSD with their moving target of micro management.

Only afterwards did I truly appreciate how poor a lot of their opinions were. Now one of my first questions when approaching a new project is what standards we’re following. If they look at me blank faced that’s a pretty solid red flag.

This was my experience too. At first I found code reviews to be an invaluable resource for improving my code. But I then reached a point where I’d learned everything I could from a particular reviewer.

I’d submit code that met every criteria, but the reviewer would still nit pick on tiny details that were entirely subjectective. It was no longer about the quality of code it became about the reviewer trying to put their mark on my work.

The only solution was to either ignore their nits or adopt the hairy arm technique whereby you include intentional errors for the reviewer to comment on so they feel their time had been valuable and you get away without yours being wasted.

jQuery was an essential stepping stone back when JS was lacking a ton of features that people take for granted these days.

Sure everything could have been done with Vanilla JS but it was verbose and difficult to follow. jQuery made it possible for any developer to quickly make a page dynamic

Yep. And three functions is better than one for legibility even if one would be fewer lines of code

Do you mean rel="nofollow"?

I’ll occasionally

1. stash my changes
2. unstash them.
3. Revise the file in my editor so only the chunk I want to commit is present
4. Commit
5. Unstash the changes again to get back the uncommitted change

It’s clunky but it’s robust and safe. It does sound a lot cleaner to just use commit -p though

-p –patch

Interactively choose hunks of patch between the index and the work tree and add them to the index. This gives the user a chance to review the difference before adding modified contents to the index.

This effectively runs add --interactive, but bypasses the initial command menu and directly jumps to the patch subcommand. See “Interactive mode” for details.

The documentation is entirely meaningless? What does it do?

You’ve never used a graphical git client?!

I’m comfortable on the command line but a decent git UI is a way better experience.

git diff is so basic using a GUI makes it far easier to compare changes.

Same for merge conflicts. I’m not sure you can even resolve them on the CLI?

Any form of rebase: I think I used the CLI to do an interactive rebase a few times in the early days but I’d never do so without a GUI now.

Managing branches: perhaps I’m a little too ott but I keep a lot of branches preserved locally, a GUI provides a decent tree structure for them whereas I assume on the command line I’d just get a long list.

Managing stashes: unless you just want to apply latest stash (which admittedly is almost always the case) then I’d much rather check what I’m applying through a GUI first.

There are some things I still use the CLI for though:

git remote add git remote set-url because I’m just too lazy to figure out how to do that in a GUI. It’s usually hidden away somewhere.

git push --force because every GUI makes it such an effort. C’mon! I know what I’m doing - it’s /probably/ not going to mess things up…

Perfect!

deleted by creator

That’s what I was questioning. Why do do the work but then not make it accessible?

It’s a similar thought to this topic: https://lemmy.world/post/3179113

My main issue with this is it requires a cheat sheet just to view a cheat sheet.

I’ll rephrase. Why require an editor? The most common viewers of SVG do not support layers.

I’ll rephrase. Why require an editor? The most common viewers of SVG do not support layers

Why not export them rather than requiring people to install Inkscape just to view the files?

I imagine most single developer projects lack any design or UX so the screenshot would do little to encourage users to download.