Showerthoughts

29612 readers

968 users here now

A "Showerthought" is a simple term used to describe the thoughts that pop into your head while you're doing everyday things like taking a shower, driving, or just daydreaming. The best ones are thoughts that many people can relate to and they find something funny or interesting in regular stuff.

Rules

All posts must be showerthoughts
The entire showerthought must be in the title
Avoid politics (NEW RULE as of 5 Nov 2024, trying it out)
Posts must be original/unique
Adhere to Lemmy's Code of Conduct

founded 1 year ago

MODERATORS

[email protected]

Can't be the only one right? (lemmy.world)

submitted 5 months ago by [email protected] to c/[email protected]

37 comments fedilink hide all child comments

So I created this blog from scratch, and after posting my first article I noticed something.

I suffer from post-Post clarity

I have noticied before when posting random bullshit online, but holy shit, now having to write longer stuff, it's clear as day.

As soon as I press the publish button even after re-reading the whole thing, everywhere I look is spelling/grammar mistakes and stupid takes.

How in hell does this happen?

Anyways as a proof of concept any edit will be in comment thread.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 8 points 5 months ago (1 children)

You can look at the git logs for any open-source project if you want to feel better about it: there's usually a regular pattern of:
do this for all the things.
Followed by either:
hang on, wait. Not *all* the things.
Or:
Missed these out of all the things

[–] [email protected] 2 points 5 months ago (2 children)

Yeah . . . many of my commits are just to fix typos.

[–] [email protected] 2 points 5 months ago

commits

[–] [email protected] 1 points 5 months ago* (last edited 5 months ago)

In case you don't know, you can do an interactive rebase and amend any past commit, not only the latest.

If the commits were already pushed to a remote, you can still do it but need to add --force or --force-with-lease to your next git push to make it overwrite the remote branch.