Avatar

NotAnonymousAtAll

NotAnonymousAtAll@feddit.de
Joined
9 posts • 127 comments
Direct message

Outlawing the dog meat industry is a step in the right direction.

Outlawing just the dog meat industry instead of all meat industry is hypocritical.

permalink
report
reply

It sure did have a big impact, comparable to what some people expect to happen soon with AI.

However, I think your framing misses the main point of why many artists today are wary about AI: They are not just being replaced, their own work is used as a building block for the tools that will replace them; and they were not asked for permission and don’t even get any compensation for that.

permalink
report
reply

In the SHED survey, the gravity of this situation becomes more evident. The survey equates the displeasure of shifting from a flexible work model to a traditional one to that of experiencing a 2% to 3% pay cut.

Those number seem way too low to me. Just picking some semi-random numbers, let’s assume a 40 hour work week and an average travel time to work and back of 1 hour per day, so 5 hours per week. Being forced to come to the office would then be equivalent to 12.5% more of your time spent to earn the same amount of money. Of course that scales depending on how far away from the workplace you live, but for 3% or 2% to be realistic you would basically have to live right next door.

permalink
report
reply

Auf wieviel Prozent schätzt du die Aufmerksamkeit?

permalink
report
parent
reply

There is nothing unhealthy about being annoyed when someone forces you to always come to them no matter what it is about again and again and again, instead of at least sometimes actively coming to you when they want to interact.

permalink
report
parent
reply

I had a very similar issue and absolutely do know what you are talking about. Those things can be very annoying, and it is hard to explain how bad it feels to people who did not experience it themselves.

My recommendation is to talk to your husband about it and explain to him that this behavior annoys you. You can also try to explain why, but in the end that should not matter. Might take several tries until he gets it, and then still a while to actually adjust his behavior. If that fails you can still look into counseling.

permalink
report
reply

About comments:

Please please please, do not always write comments. Try to write code that does not need comments whenever possible. Proper variable, class and method names go a long way. If you think a block of code needs a comment, turn it into a method and give it a proper name instead.

Comments should be a last resort for cases where making the code self explanatory is not possible, and those should be rare.

About optimization:

Optimal code is code that fulfills it’s purpose without observable issues.

If you try to make something faster without any prior complaints or measurements indicating that it being slow is an actual issue, you are not optimizing, you are just engaging in mental masturbation.

permalink
report
reply

To save you a click:

“No, there are no in-game purchases in our game. We believe in providing a complete and immersive gaming experience without the need for additional purchases. Enjoy the game to its fullest without any additional costs or microtransactions.”

permalink
report
reply

it’s really useful to comment functions/methods, because otherwise you never know if something’s a bug or a non-obvious feature. Comments act as a parity check to the code, since they tell you what the dev who wrote the code wanted the code to do.

Unit tests should be the parity check for other code. Those don’t get outdated with the next refactoring where someone didn’t remember to also adjust all the comments.

Also, everone thinks they write good, clean and obvious code. Hardly anyone purpously writes bad, hacky code. Yet if you look at code you wrote a year ago, or code someone else on your team wrote, it’s full of non-obvious hacks. That means, people constantly misjudge the obviousnes of their code. Comments should be put on anything that could maybe be non-obvious.

Why would people be better at judging if something needs a comment than at judging if something needs a better name or refactoring? Asking people to skip that judgement step and comment everything just gives you a bunch of useless boilerplate comments. That trains everyone reading that codebase to ignore comments because they are almost always useless anyway.

putting documentation of the code anywhere else than in a comment (e.g. Confluence) is a total waste of time

At least this we can 100 % agree on. Documentation should be as close as possible to the code. (I just think most of the time that place is in the name of things, not in an actual comment.)

permalink
report
parent
reply