@dUcKtYpEd I get you, not everything is programming. We need to learn management and leading too :)

@svgPhoenix I hope you don't :P

I develop in Javascript on daily basis and i have never seen such edge cases in real-life projects or big packages.

Undefined is what we are afraid of / take advantage of. To avoid such weird stuff, we just optimize stuff better.

@dUcKtYpEd So is it a good opportunity to improve for the junior ? Interesting.

I haven't thought of it like that. I thought he has more responsibility on his shoulder than he could carry. But when you put it like that, it makes a lot sense

Ok.

@svgPhoenix Avoiding language because it has weird quirks on edge cases, yeah truly legit.

Happened today. Tweaking around with my distro or trying out a new one is way more satisfying :)

@dUcKtYpEd Project lead is busy with backend stuff, since the other company can't provide services properly. So that junior leads the project...

@dUcKtYpEd That is how it should be. Here at my side : Every pull/merge request is checked by only a Junior developer and that Junior has to test the app briefly to not let any defects go in. That junior also codes and merges his own requests...

@dUcKtYpEd What i hate the most is the project manager that wants things to be merged quickly without reviewing and testing fully.

Nobody can attack your server if you block every incoming request :)

It is nice when customers know what they want and appreciate effort. Kinda rare :(

What is the deal with it ? If the junior did not do that, you would rant on it too.

🙄

Instantly liked. Configuring nvm on fish was very painful.

We worked in Christmas too

I love it. Almost had an orgasm :)

You can ignore lateinit warnings, they keep your code more organized, but not mandatory to use.

??variable is your friend. Use it. Refactor your logic if needed. It will be worth it.

Refactor your shitty workarounds caused by Java being such a jerk with nulls.

Use foreach returns, they are weird to use but absolutely a work of art if you are used to it.

Keep your static variables at the bottom, inside of a union class ( i name it like that, i forgot the whole thing ), for tidying purposes.

If you use something like Android Studio, it will recommend you that anyways.

Some code snippets are not easily converted to Kotlin, expect some hardships and a learning curve.

@gnulinuxer4fun @duckWit @mt3o @Fast-Nop

I have come to end this nice debate. Comments are often used to explain the train of thought the coder goes through, which is kinda wrong. We don't explain what we write in English further, do we ?

1. If you create a new framework, or tweaked your c/c++ standart operations etc, you should comment. Anything ONLY you know should be commented. The normal usage of languages are already documented at the official docs, no need to comment those.

2. The most important part is, commenting the weird parts. For example, if you declare an empty function on c#, empty alert on javascript etc, you better comment what is going on briefly, to save time of the developer who needs to change something there.

If you don't, they will say "why do we need that, let's remove this and see what we got". After minutes of compiling and tweaking, they will get what is going on.

@retard I do that sometimes, yes.

I don't think it is relevant. It is like leaving the desk and sitting again, when a computer does not work. Whenever i see this, i get irritated.

More relevant answer could be : Let's remove the motor and put it back together again.

@Jifuna Yes it is ridiculous, also not ethical. I am not talking about the context, i am talking about blaming the employee.

@linuxxx Which is what i am doing, but unfortunately, another developer made the changes on them. I am responsible to merging it to master branch and polish it before it goes into main release, and guess what ?

He not-surpisingly hardcoded the duration value everywhere, so i need to change 100+ different places. Not a good day.

@klekih @endor No, both of you are wrong. An employee has to do what he/she is told to do, decision making is not his/her job and he/she is absolutely not to blame.

If he/she declined, the boss would still find someone else anyways, plus negative consequences for rejecting the boss.

Well you are not to blame, but i think it is really time to slowly pack up your stuff and leave.

Having a 1/2 less salary with a shitty job is probably better than being monitored and not being able to have fun.

I have educated and taught a couple of men and women how to code and basic concepts, my conclusion is that women are better programmers.

Change my mind.

@jonii Ahhh a man of culture...

Just open a PR and let it stay there. If anybody asks you about it, just tell them it is ready for review. Nobody can blame you if your work is ready.

Merging your own requests is worse than it seems. We are humans, we can make mistakes.

No.

Production kills perfection.

Node.js