People adding documentation to their code.

Keep dreaming

Code shouldn't be documented. Code should be well-written so that documentation isn't needed.

In the form of comment packed code maybe.

Like 'literate programming'?

@benzammour what kind of documentation are you referring to?

@DefiniteGoose that is only needed in very severe cases

don't really think that'll change. we'll always have lazy devs (including me).

@fdgram either write the good code or put the fukin comments.

Since former is mostly not done so **put the fukin comments**.

@sauronjs or you move somewhere where people don't write shite code

@fdgram I have never seen a code good enough for the comments to be skipped, including my own.

@sauronjs time to learn software engineering then :)

@fdgram if you're working in a start up, you never get enough time to design carefully and code. You just design what works, readable to dumbs and scalable enough to work for few years.

In my current company, I sure get enough time and use it good. I document everything I come across. I believe, I get better when I document because it becomes easier to read my own code. Also, I spend less time type checking when I am writing JS code(yes we don't use typescript). Also, autocomplete looks super when you see whole description of functions in popup and don't need to `CTRL + CLICK` to check what the fuck it's actually doing.

@fdgram trust me, you can never learn enough software engineering to skip documentation. Remember the last time when you checked, what are all the parameters of concat do and what does it do in different conditions.