Changes between Version 5 and Version 6 of PadawanPitfalls


Ignore:
Timestamp:
10/21/14 16:19:53 (5 years ago)
Author:
jbehrens
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PadawanPitfalls

    v5 v6  
    1616== Logging == 
    1717 Log as much as needed, and as little as possible: 
    18    Logging is a good thing in general, it helps to find bugs and to locate problems while running the software. But for two reasons it is a good things to use logging only sparsely: firstly logging is an expensive operation. Even if it is not that expensive, it's still extra work and consumes resources (IO is in general not that cheap because it is rather slow compared to everything else your plugin can do). Secondly if there are too many trees you don't see the forrest. This means that if you log too much the important stuff goes unseen. Thus report errors, and sparse special events that are good to now and happen rarely (like loading a plugin), log as much as you like during the development phase, but at a tournament make your application shut the f*** up. 
     18   Logging is a good thing in general, it helps to find bugs and to locate problems while running the software. But for two reasons it is a good things to use logging only sparsely: firstly logging is an expensive operation. Even if it is not that expensive, it's still extra work and consumes resources (IO is in general not that cheap because it is rather slow compared to everything else your plugin can do). Secondly if there are too many trees you don't see the forrest. This means that if you log too much the important stuff goes unseen. Thus report errors, and sparse special events that are good to know and happen rarely (like loading a plugin), log as much as you like during the development phase, but at a tournament make your application shut the f*** up. 
    1919 
    2020== Network Communication ==