9. Disclaimer
๏ง Itโs not scientific
๏ง Itโs not well-structured
๏ง Itโs my own opinion
10. 1. Log everything.
โข Log pageviews
including GET and
POST variables
โข Log every activity of
background tasks in
log files
๏ Debugging is much easier
11. 2. Start simple.
โข Keep the system
simple.
โข Simple = easy to
understand
โข You can always
refactor later
๏ Make your code friendly
to refactoring (Unit Tests,
Method Names)
If your kid wants a
helicopter, he will be
happy with this :-)
12. 3. Involve your team.
Let the team decide
about technology,
architecture AND
features
Benefits:
The team is more
engaged
More people -> better
solutions
Team discussions M&P Style
13. 4. Don't follow trends too quickly.
Before you choose a
technology, make sure
that it will still exist in 5
years
Tests:
How many books are in
Amazon about the
technology?
How many commits does
a project have?
8-Track players were once top
technology.
14. 5. Keep your code clean an tidy.
โข Remove unused code
โข Rename methods if the
function of the method
does not correspond
anymore to what the
method does
Cleaning is Fun!
15. 6. Defensive programming!
โข Think of everything
that can go wrong and
be ready to handle
those cases
16. 7. Pay attention to security!
โข Use the OWASP Top-
10 to check your code
security
https://www.owasp.org
โข Filter and validate
incoming data -> only
clean data in your
system (DB, code etc.)
17. 8. Your code will live longer than you expect!
โข Be nice to the people
who will work on your
code after you left the
company. They are
engineers like you.
โข If you find a mess,
clean it up
โข Bad code is not an
excuse to add more
bad code
Even at 80 years old, your code
should be able to do skateboard tricks
:-)
18. 9. Choose your symbol names carefully!
The code should replace a
documentation, so:
โข Avoid mistypings (it
looks unprofessional)
โข Donโt be afraid of long
names (your IDE will
autocomplete for you)
Be careful as an artist when coding
19. 10. There should always be fun tasks!
Developers which enjoy their
task โฆ
โข โฆare more focused
โข โฆthink about the project
even after work
โข โฆwill stay longer in your
company
๏ When choosing projects,
always ask yourself whether
your engineer will enjoy doing
it