Like any other occupation, the longer you do software development, the more you learn. Often, much of the wisdom one accumulates over time comes from learning the hard way, through trial and error. Other times, though, those who’ve come before you will save you some time (and pain) by imparting the lessons they themselves have learned over the years. One of the good ways to do that is through proverbs, that is, simple sayings that convey a truth, usually based on experience. A Github (https://github.com/AntJanus/programmers-proverbs) repository created last year called Programmer’s Proverbs has been collecting these short sayings from developers.

1.One thing should never do more than one thing.

2.What happens in Git stays in Git

3. Don't commit on master when drunk.

4.Debugging becomes significantly easier if you first admit that you are the problem.

5.Simpler code has less bugs

6.Give a programmer the correct code and he can do his work for a day. Teach a programmer to debug and he can do his work for a life time.

7.A foreach loop avoided is a CPU cycle earned.

8.Absence is beauty, in error logs.

9.Testing is easier than debugging.

10. The best code is no code at all.

11. Figure out your data structures, and the code will follow.

hmmmmmmmmm!!!! quite interesting.

danvery2k6:
Like any other occupation, the longer you do software development, the more you learn. Often, much of the wisdom one accumulates over time comes from learning the hard way, through trial and error. Other times, though, those who’ve come before you will save you some time (and pain) by imparting the lessons they themselves have learned over the years. One of the good ways to do that is through proverbs, that is, simple sayings that convey a truth, usually based on experience. A Github (https://github.com/AntJanus/programmers-proverbs) repository created last year called Programmer’s Proverbs has been collecting these short sayings from developers.

1.One thing should never do more than one thing.

2.What happens in Git stays in Git

3. Don't commit on master when drunk.

4.Debugging becomes significantly easier if you first admit that you are the problem.

5.Simpler code has less bugs

6.Give a programmer the correct code and he can do his work for a day. Teach a programmer to debug and he can do his work for a life time.

7.A foreach loop avoided is a CPU cycle earned.

8.Absence is beauty, in error logs.

9.Testing is easier than debugging.

10. The best code is no code at all.

11. Figure out your data structures, and the code will follow.

Nice.

Thanks op.
My tips:
Never repeat code, if subsequently needed package it
Control implementation (public modifiers!), don't get lazy
The world doesn't revolve around software dev only; your server, network, your client, and maybe support needs assurance devs aren't haphazardly throwing code together, especially for frameworks
Avoid Stack overflow code, unless you're 100% sure of what you're doing.

FIND A TEAM YOU CAN WORK WITH!!! stop all this "ill be the next sole, spot lighted Mark Zuckerburg or Steve Jobs", flying solo bullsh.it. Great deliverables requires a team.

Nice thread op

AAinEqGuinea:
Thanks op.
My tips:
Never repeat code, if subsequently needed package it
Control implementation (public modifiers!), don't get lazy
The world doesn't revolve around software dev only; your server, network, your client, and maybe support needs assurance devs aren't haphazardly throwing code together, especially for frameworks
Avoid Stack overflow code, unless you're 100% sure of what you're doing.

FIND A TEAM YOU CAN WORK WITH!!! stop all this "ill be the next sole, spot lighted Mark Zuckerburg or Steve Jobs", flying solo bullsh.it. Great deliverables requires a team.

Nice thread op

i Love this piece

Interesting...