CLEAN CODE, CLEAN ARCHITECTURE and NEW WORK
Allan kelly shares some important Background knowledge for Agile Teams. It´s a must-know knowledge for Agile Leader and Agile Coaches and for every Team that calls himself a Team that follows an Agile Approach.
This Post on Agile Times shares 5 ways how you can recondition or progress toward an agile mindset.
Have you ever thought about what it costs that you wait for Feedback during Programming? Piet Hadermann shares in his Blog some insights on this important topic.
This Article from Oreilly describes what NOT the Job of an Architect is. Sometimes I have the Role as an Architect, the Job is difficult enough if you understand you have to be part of the Team and support especially also with Software Development. Architects that get the Role of a "Powerpoint" Hero should get another Role Description like Technical Manager or Enterprise Architect...
Matthew MacDonald is claiming in his Post that Good programmers follow the insights. Poor programmers worship the rules.
Uwe Friedrichsen is tackling the actual Buzzword Microservices. In this Post 7 of his series, he explains actual reasons that justify the use of Microservices.