• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
  • Tim Cooke
  • Campbell Ritchie
  • Ron McLeod
  • Junilu Lacar
  • Liutauras Vilda
  • Paul Clapham
  • Jeanne Boyarsky
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Piet Souris
  • Carey Brown
  • Jesse Duncan
  • Frits Walraven
  • Mikalai Zaikin

Text Books in General

Ranch Hand
Posts: 681
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
When I first started programming I would pick up a book on the subject thinking that it would teach me all about that subject, only to find that the examples were half finished, didnt work , or the explanation was too simple or complicated. Also examples jump from simple to complicated with large amounts of code to right, i.e a form with other 15 items in one exmple to set in a struts book.

My idea of a perfect text book to teach a subject is chapter one start with introduction to the subject. Chapter 2 a very simple example that works. and then each succesive chapter builds on that one example. Making sure that at the end of each chapter. You have a built a application that covers that chapter. You can then spend time playing with that application ensuring that you have learnt the lessons of that chapter.

A Kind of RUP view of teaching a subject.

Consider Paul's rocket mass heater.
    Bookmark Topic Watch Topic
  • New Topic