Win a copy of Five Lines of Code this week in the OO, Patterns, UML and Refactoring forum!
  • 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 all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
Bartenders:
  • Piet Souris
  • Frits Walraven
  • Carey Brown

Question for Kevlin - 97 things

 
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello,
I have been a senior developer for a while and have been trying to become an architect (by doing some parts of the architect's role).
How is the book going to help me transform into a complete architect?
Are there real business examples/scenarios that a developer can relate to in the book?
regards,
Madhav
 
author
Posts: 44
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Although I'm not the editor of 97 Things Every Software Architect Should Know, it has a similar structure and intent to the 97 Things Every Programmer Should Know book I edited. The book is not a book of case studies or worked examples and it does not have a structured narrative dictated by the editor. It comprises a set of individual and focused items from a range of contributors. What you are likely to learn is perspectives, good quotes, provocative questions and opportunities for further learning.

I hope that helps.
 
Don't get me started about those stupid light bulbs.
    Bookmark Topic Watch Topic
  • New Topic