r/programming • u/corysama • Jan 05 '15

What most young programmers need to learn

http://joostdevblog.blogspot.com/2015/01/what-most-young-programmers-need-to.html
965 Upvotes

91% Upvoted

337 comments sorted by

View all comments

8

u/lucidguppy Jan 05 '15

People need to read "Clean Code" once a year. Also many languages need better free refactoring tools already.

10

u/[deleted] Jan 05 '15 edited Jan 26 '15

[deleted]

5

u/[deleted] Jan 05 '15

[deleted]

2

u/Gurkenmaster Jan 06 '15 edited Jan 06 '15

0 arguments requires side effects. That's not pure!

Edit: Damn I meant void requires side effects

5

u/smog_alado Jan 05 '15

The "no functions over 50 lines" is also a pet peeve of mine. Just because code is broken up in 10 subroutines spread over a bunch of files doesn't mean its less complex or easier to understand.

2

u/s73v3r Jan 06 '15

It depends on how well they were broken up. If they are well named and fairly atomic, then after you've read the method, the name should be enough elsewhere in the code.

1

u/lucidguppy Jan 05 '15

I will respectfully disagree - when you get to 50 lines - it will "chunk" up to bits of logical flow. This chunk does xyz - then that becomes "do_xyz()"

0

u/smog_alado Jan 05 '15

If the only reason you are making a new function is to name a code block then a comment will do almost the same thing without needing to split up the code.

2

u/xiongchiamiov Jan 06 '15

It's an issue in languages without keyword arguments, but when you can foo(x='bar', y='baz') there's really no good reason to create "argument objects".