Tim Brown (CEO of IDEO) has written a great book on design thinking called Change by Design. Check out the link to see his mind-map of what the book is about.The basic premise of the book, why its …

Comparing software architects with actual architects is inaccurate. Physical-world constrains architect, and software evolves with user requirements.

Being a great software engineer doesn't make you a good architect. Although you might be good at designing architecture in your software projects, the software architect is a different role with various responsibilities and expectations.

How an architect thinks and approaches designing and architecting software systems? The architect's job is eventually a combination of tech lead, software engineer, R&D engineer, and strategist. But how are these responsibilities come together?