Much has been written and debated on whether software architects should write code. Many argue the more architects understand the language, tools and environment they are designing for, the more effective they are and this is best achieved by implementing some or all of the design. Non-coding architects, sometimes called “PowerPoint architects”, “astronaut architects” or “ivory tower architects”, may use archibabble and talkitecture to convince non-technical stakeholders of their expertise while delegating the unsolved, real problems to developers, so much so that it has become an organizational pattern (“Architect Also Implements“) and corresponding anti-pattern (“Architects Don’t Code“). Others argue that architects responsible for implementing their architectures lose focus on the bigger issues and longer term vision. Understanding does not necessarily require knowledge of the minutiae and, as systems scale up and diversify, implementing it requires too much time or spreads the architect too thin. Therefore, should software architects write code?
“An investment in knowledge always pays the best interest.” – Benjamin Franklin
Many of the best software developers have T-Shaped Skills: Deep expertise in programming and software development, and broad knowledge of diverse areas including testing, DevOps, UX design, team organization, customer interaction, and their domain areas. While there is unfortunately no substitute for experience, reading is probably the next best thing. Over the past 10 years I’ve read a lot in an effort to deepen and broaden my knowledge as a software developer. Along the way I’ve been organizing books and concepts into the reading list I share below. I have been trying to design a core curriculum for “modern” software development by asking myself:
What core concepts are required to be a world class software developer?
What is the best book for introducing and teaching each concept?
Despite the currently most selling brand in Pakistan. Q- Mobile is very low in quality and hardly completes its warranty period. You will be lucky if it dies sooner so you can claim your warranty.
I have used Nokia and there is a marginal difference between the quality of Nokia products and Q-Mobile. Recently my Q-mobile A9 losses it touch sensitivity making it a complete dump. I can’t even retrieve any data within the phone.
Beware before buying Q-mobile specially touch screen. It’s better if you try out a low specification HTC mobile. It will be more durable as compared to your so called brand new Q-mobile.
I have even used Q-mobile with key pad they aren’t even comparable to Nokia mobile. They do provide a bit more features but the quality of Camera, Keypad and Mic is very low. So you have to change your mobile within very short span of time.
Note:- If you are still looking for any other doctor bill do mention it in comment box. I will add that to the list as well. Also if you have some knowledge about any other doctors timing do mention it here.