depending on what language you use, for example Python is largely self-commenting on the low level but sure if you're
-
-
constantly calling libraries and using super high-level stuff then you're going to have both baked in.
1 reply 0 retweets 0 likes -
I wrote my whole PhD work in C, including graphs and a GUI. Big no-no if you don't have comments.
2 replies 0 retweets 0 likes -
Replying to @o_guest @elneurozorro
I try to avoid having to write "what" style comments by having clear code, so I can focus on "why" style comments
3 replies 1 retweet 2 likes -
But I find it hard to keep quality up when approaching a deadline and working 60+ h weeks.
1 reply 0 retweets 0 likes -
Replying to @kaiblin @elneurozorro
that sucks dude, but I usually find the time. I think not being a student helps.
2 replies 0 retweets 0 likes -
Replying to @o_guest @elneurozorro
I'm not a student. I still have unrealistic deadlines that are out of my control.
2 replies 0 retweets 0 likes -
I try to get back to code after the deadline crunch is over and fix up stuff, of course.
1 reply 0 retweets 1 like -
Replying to @kaiblin @elneurozorro
that's good enough especially if you share the code on github etc
1 reply 0 retweets 0 likes -
on that note... off to write some.... comments?
1 reply 0 retweets 1 like
hahaha I am because this legacy code is spaghetti
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.