123 reputation
4
bio website None
location Melbourne, Australia
age 23
visits member for 1 year, 8 months
seen May 14 at 17:23
stats profile views 1

I'm a Robotics Engineering and Computer Science student from Melbourne.

I'm most proficient in C, C++ and Python, and have basic knowledge of several others. Python is my language of choice.

In my spare time I enjoy coding (mostly games), sport, and good food and drink.


Sep
15
comment If the purpose of a single complicated LOC is clear, would you bother to split it on to multiple lines to make its method clear as well?
Yeah, this is essentially what I ended up doing.
Sep
15
awarded  Scholar
Sep
15
accepted If the purpose of a single complicated LOC is clear, would you bother to split it on to multiple lines to make its method clear as well?
Sep
14
comment If the purpose of a single complicated LOC is clear, would you bother to split it on to multiple lines to make its method clear as well?
Good point and good point. I think I'll change it.
Sep
14
comment If the purpose of a single complicated LOC is clear, would you bother to split it on to multiple lines to make its method clear as well?
I definitely see your point about the readability, and agree that it is more readable when it's split up, but I guess my question was more: this is a 2 line function that's not going to change, with a nice descriptive name and doc. It's obvious what it does, so is there any reason to break it up to show how it does it? Probably the important question I'm ignoring is: why the hell wouldn't you split it up? If I'm honest with myself, I think I'm just hesitating because I felt kind of clever when my 5-nested-bracket LOC worked first try, and now I don't want to disassemble it :P
Sep
14
awarded  Student
Sep
14
asked If the purpose of a single complicated LOC is clear, would you bother to split it on to multiple lines to make its method clear as well?
Sep
12
awarded  Supporter
Sep
12
awarded  Autobiographer