I'm #bored. Let's have a #flamewar about #codecomments.
There are those "YOU SHOULD NEVER WRITE COMMENTS, IF YOU NEED COMMENTS YOUR CODE SUCKS AND NEED REWRITING"
and then we have "You should comment *ALL* code *ALL* the time"
And then we have "You should write comments, if it makes sense and the code is non trivial"
Which camp are you in, and why?
#bored #flamewar #codecomments #devlife #dev #code #codingstyle #comments
Oh, boy... in over 25 years of C and C++ programming I'm starting to consider and use `goto` for reducing the redundancy in some cleanup-on-error sequences.
I don't know if I should happy or depressed about it. :P
I might as well conform to the Linux kernel coding guidelines (that mostly match my honed-over-the-years style).
#codingstyle #programming #gamedev
Droid Sans Mono is my favorite font with 20 of font size.
I always followed linux kernel coding style because is without any doubt rational.
But on kotlin 80 row lenght is too short, like all bad languages that are based on multiple nested crap.
I raised row lenght to 120, this implies that you have atleast 2 monitor to work well, but for me is not a problem.
Coding style have just a task, make the code more readble, after read 24 hour, you know what I mean.
:blobheartcat:
I'm experimenting with a new #codingstyle: For every line of code there's a line blank following it.
Kind of looks like those Bills they bring before the US Congress.
Why do I like this #codingstyle so much?
https://www.reddit.com/r/ProgrammerHumor/comments/qhjthz/be_warned/
I've just discovered that ESLint's default is to *require* a space before the opening paren in a function definition. Admittedly I most recently came from C++ but this feels very backwards to me. Are there...reasons? As much as there ever are for style things?
I learned that spaces before paren in block statements in C++ was specifically to differentiate from function declarations/calls, so this default perplexes me.
#askmastodon #javascript #eslint #codingstyle #coding