sping

Great, cause we haven't been burning enough energy jetting around the globe up to now. Glad they found a way to burn a whole lot more.

floppy drive, hard drive, sechs drive — we got building blocks. Crowd sourcing a joke could work.

Excellent, the punchline is sorted, now we just need the rest of the joke.

Or they avoid the need for that solution by avoiding that problem in the first place?.

I don't even now how anyone keeps track of them and finds the ones they want. And how can you possibly do that quicker than just going to the page afresh.

Part of working on a project for me is assembling links to important pages. It may be days, weeks or months later that I want to come back and there are the links. And of course, anything generically or regularly useful is just a bookmark as you say.

It really seems like people keep tabs open just to keep a list of useful pages. There are much easier and more effective ways to do that.

it always entertains me when a vim aficionado regurgitates the "just missing a good editor" joke, given that one of the editors Emacs offers is a pretty comprehensive clone of vim.

(personally, I never had any problem with the default editor when I migrated to it from vi, though I was using a keyboard that already had ctrl next to a.)

I really f'ing love Emacs, and... this is true. I'm still constantly learning, 3 decades in.

But that's part of its appeal - it's a constantly evolving, you tweak and modify it for your needs, and you grow and change together.

Well on Reddit, programmerhumor was mostly populated by people weirdly proud of how bad they are at their job, so I don't see how Lemmy was going to be different.

I've worked in a few startups, and it always annoys me when people say they don't have time to do it right. You don't have time not to do it right - code structure and clarity is needed even as a solo dev, as you say, for future you. Barfing out code on the basis of "it works, so ship it" you'll be tied up in your own spaghetti in a few months. Hence the traditional clean-sheet rewrite that comes along after 18-24 months that really brings progress to its knees.

Ironically I just left the startup world for a larger more established company and the code is some of the worst I've seen in a decade. e.g. core interface definitions without even have a sentence explaining the purpose of required functions. Think "you're required to provide a function called "performControl()", but to work out its responsibilities you're going to have to reverse-engineer the codebase". Worst of all this unprofessional crap is part of that ground-up 2nd attempt rewrite.

What do you think comments are?

These are arguments talking past each other. Sure 1 useful comment and 9 redundant ones can be better than zero, but comments are not reliable and often get overlooked in code changes and become misleading, sometimes critically misleading. So often the choice is between not enough comments versus many comments that you cannot trust and will sometimes tell you flat-out lies and overall just add to the difficulty of reading the code.

There's no virtue in the number of comments, high or low. The virtue is in the presence of quality comments. If we try to argue about how many there should be we can talk past each other forever.