As a Mac user, I like Time Machine for backups. It’s not perfect, but it gets the job done. There is a Linux version.

Nb. I’ve not used this particular software, so YMMV.

I felt that way about binary.

~/Dev/Project/file.ext~2025-03-20-Backup-6

Is that what we’re calling coke these days?

I imagine he’s looking at a payments table where there is a non-unique key to relate a citizen to each payment.

Using pivot tables.

You just describe half of my career. 😅

Yes. Thankfully in my experience I’ve only dealt with this once or twice. But it’s a pita every time.

I’ve tried switching macOS to a case sensitive file system, but not all programs can handle it (at the time it was Photoshop).

That’s called a workaround. No end user should have to rely on a workaround as a solution to a bug; and make no mistake, it’s a bug.

I’m probably going to get downvoted to Hell and back, but someone’s gotta say it: that’s a git problem, not Windows.

First of all, I agree that case-insensitive file systems suck. It makes things inconsistent, especially from a development standpoint.

But, everyone has known that Windows (and macOS) use case insensitive file systems. At least for Windows, it always has been that way.

Git was written in Linux, which uses a case sensitive file system. So it’s no surprise that its internals use case insensitive storage. Someone ported it over to Windows, and I’m sure they knew about the file system differences. They could’ve taken that into account for file systems that are case insensitive, but chose not to do anything to safe guard Windows users.

But until the day that somebody fixes Git, everybody who is not using case sensitive file systems needs to care more about how they name things (and make sure their team does too). Because fuck everyone else, right?

$goddamnitJeffStopChangingMyFuckingVariableNames = 1;

Does anybody know what tool this is?

Those commit messages though 🤣

bottombottominate

FTFY

👆 This. In my experience, I’ve seen a lot of developers get upset about “their code” not being used, time wasted, or someone else changing the code after the fact. Who cares? Once you commit that code, it’s no longer your code. It’s the company’s code. Your paycheck will reflect the same amount of money regardless — and if it doesn’t, you may want to find a better employer. 😅

I found this site which might help you in your search.

https://selfh.st/apps/

Food for thought (no pun intended), but unless you’re willing to build an app (could be a great app; I doubt you’re the only person who could use this), you might be over engineering this quite a bit. A spreadsheet could be made to do what you’re looking for, with much less effort.

Well for one, it encrypts all communications so that people can’t snoop on what you’re doing.

Ssh! 🫢 You’ll ruin the joke!

According to the PMBOK (7th edition) by the Project Management Institute (PMI), daily standup is a “brief, daily collaboration meeting in which the team review progress from the previous day, declares intentions for the current day, and highlights any obstacles encountered or anticipated.” Source

To be fair, daily standups are defined however your group collectively decide to define it.

For those who decide to report the work from previous day, it’s expected that you would have made your list before the meeting, not during. It’s a practice I too struggle with. 😊

Hm. Might not be standup that’s the problem. Might be a company culture thing. But only you know that for sure. Good luck op! Disassociation can be a life saver.