this post was submitted on 20 Jun 2025
210 points (91.0% liked)
Showerthoughts
35300 readers
1503 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 most popular seem to be lighthearted clever little truths, hidden in daily life.
Here are some examples to inspire your own showerthoughts:
- Both “200” and “160” are 2 minutes in microwave math
- When you’re a kid, you don’t realize you’re also watching your mom and dad grow up.
- More dreams have been destroyed by alarm clocks than anything else
Rules
- All posts must be showerthoughts
- The entire showerthought must be in the title
- No politics
- If your topic is in a grey area, please phrase it to emphasize the fascinating aspects, not the dramatic aspects. You can do this by avoiding overly politicized terms such as "capitalism" and "communism". If you must make comparisons, you can say something is different without saying something is better/worse.
- A good place for politics is c/politicaldiscussion
- Posts must be original/unique
- Adhere to Lemmy's Code of Conduct and the TOS
If you made it this far, showerthoughts is accepting new mods. This community is generally tame so its not a lot of work, but having a few more mods would help reports get addressed a little sooner.
Whats it like to be a mod? Reports just show up as messages in your Lemmy inbox, and if a different mod has already addressed the report, the message goes away and you never worry about it.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
One of my co-workers, maybe oversold his capabilities and experience. That or whoever told me what he was capable of oversold him. Doesn't matter at this point. Not that long ago, he basically was never submitting any merge requests, and when he did there were a ton of issues. Then one week, everything changed. He was writing code and a style that didn't match what he had done the week before, there was an excessive amount of documentation where before there was none. It was co-pilot. He had gotten access to copilot, which we all have. But it was obvious that he's been leaning heavily into it.
And a short-term yeah it looks like he's doing really well. But I fear he's not actually learning anything by doing this. Which means if there's a mistake, for a major change that needs a happen, He's not going to get there on his own. One time he tried to submit a merge request and I was like, there's an obvious flaw here because this could be null and you're not handling that. If the company ever decides that we're not going to use co-pilot anymore, cuz I think we're still on a trial run, He's going to find himself right back where he started. And that's going to hurt his career in the end.