magic_lobster_party @ magic_lobster_party @kbin.social

Posts

2

Comments

580

Joined

2 yr. ago

In software that’s already badly engineered. Either you do the work and refactor everything, or accept it’s probably not worth all the effort.

Not necessarily a bad practice if the singleton is immutable, and it’s provided via dependency injection for example.

That make sense. Most industry best practices are there to prevent problems that arises when code is evolving over a long period of time.

Lecturers at universities tend to have little to no industry experience at all.

For me most of the people who have written our most annoying tech debt left the company long time ago.

// TODO: Fix later

The definition of a variable is that it’s mutable. If it’s immutable it’s constant.

No amount of oppression justifies raping civilians.

Bad analogy. Death Star is not a civilian target.

Sadly it won’t. Peaceful options were already slim before this. It likely won’t end until Israel has destroyed Hamas.

Armored Core 6 as well

I think “15 hours ago” is fine. That one is quite precise. Showing date as “1 year ago” is not helpful. It could be anything between 2021-10-06 and 2022-10-05. It’s a huge span. In that time Ukraine got invaded and the Queen died.

I love it. That means I will hate Instagram more and use it less. Please, no quality of life improvements to that app.

Saying “1 week ago” or “1 month ago” instead of just saying the date. Dude, I want to know if this happened in August or September.

I usually use the GUI in IntelliJ for those kind of purposes, but any other GUI might do. Then I perform a manual binary search to find the commit I want.

I think comments should be a last resort when all other methods are inadequate. Proper git commit logs have helped me many times to understand why a certain thing is needed.

Git logs don’t need maintenance either. They always tell what was true when the code was written. Comments need maintenance, and are often difficult to keep updated.

You can write a detailed comment about the whys of a particular function, only for it to become outdated in weeks when the functionality has changed.

According to who? If I have access to the source code, which I often do, I’d rather just read the code. Chances are that if documentation exists, it’s no longer up to date.

You can find them by reading the code. It’s not difficult if they’re placed at proper locations.

Often you can find the “why” in the file’s Git history. If done properly, you should be able to find which commit introduced this change, and which issue is attached to this commit.