Stand still and watch the patterns, which by pure chance have been generated: Stains on the wall, or the ashes in a fireplace or the clouds in the sky, or the gravel on the beach, or other things. If you look at them carefully you might discover miraculous inventions. (Leonardo da Vinci)
 

10 Anleitungen um einen besseren Job zu machen.

Februar 20th, 2009 Knowledge, Websites|

Gestern bin ich auf eine spannende Website gestoßen, die das Wiki-Prinzip auf einen neuen Bereich anwendet: http://www.wikihow.com. Hier geht es nicht um lexikalisches Wissen, sondern um Anleitungen zu verschiedensten Themen. Wie in Wikis üblich werden die Inhalte der Anleitungen durch die Community erstellt, erweitert und berichtigt: Die Weisheit der Massen. Neben den einfachen textuellen Anleitungen sind einige auch per Video dargestellt.

Folgende 10 Anleitungen können die eigenen Softskills verbessern:

  1. How-To manage Geeks
  2. How-To be a good manager
  3. How-To develop an IT Change Management Program
  4. How-To establish an IT project
  5. How-To be an effective Project Manager
  6. How-To run an effective meeting
  7. How-To motivate Staff
  8. How-To access useful Web Development Tools
  9. How-To Have successful Open-Source projects
  10. How-To improve your Skills as a programmer

Tags: Development, How-To, Job, Knowledge, Management, Projects, Self-Imporvement, Video, Websites, wiki

2 Comments on “10 Anleitungen um einen besseren Job zu machen.”

  1. 1 Volker said at 8:59 on März 13th, 2009:

    Point 8 is a little bit outdated, since I almost never use the Web Developer Toolbar but far more often FireBug. Firebug let’s me inspect the DOM, change it on the fly, see all CSS definitions, that apply to an element (even those which where overridden) and change them, inspect AJAX calls and much, much more. Just search for FireBug in the add-on repository of mozilla, you’ll see.

  2. 2 Bastian said at 11:51 on März 13th, 2009:

    indeed, you’re right. especially in ajax environments this is one of the most powerful tools out there. and it’s even more as you mentioned: you can debug your javascript: set breakpoints oing through running code step by step, watch variables …

Leave a Reply