awesome-talkscurated list on GitHubRecommends
Under “Methodologies”
Demanding Professionalism in Software Development by **Robert C. Martin** (Elapse Technologies 2012) 45:03
0:00 / 0:00
#professionalism#agile#cleancode
Robert C. Martin (Uncle Bob) - Demanding Professionalism in Software Development
ElapseTechnologies
547 subscribers • 1 video on Hallway
- Recommended by 2 people: 1 in engineering communities and 1 curated list.
- Presented by Robert C. Martin
- An opinion. It argues one side of a question engineers disagree on.
Beginner. No background in the topic needed.
100K views14 years ago2 recommendations
Tools and practiceCareers and interviewsCode review and teamworkCareer growthDeveloper productivity
Robert C. Martin explains why professionalism, ethics, and high standards are essential for software development teams and their managers.
Provided by Elapse Technologies - elapsetech.com Robert C. Martin explains in his own unique style why professionalism is so important for software development teams and their managers. This event has been recorded live at an event co-hosted by Agile Quebec City and Elapse Technologies in Septembre 2012. --- Bob Martin présente dans un style bien à lui pourquoi le professionnalisme au sein des équipes de développement logiciel est un enjeu incontournable pour les gestionnaires et les équipiers. Cette conférence a été enregistrée lors d'un évènement organisé par Agile Québec et Elapse Technologies en septembre 2012.Why it's here
2 people recommend thisWhat people say. Recommended as a classic talk on software craftsmanship and the importance of maintaining high professional standards.
Moments people linked to
u/danielt1263iOS Developer (15 YOE)in r/ExperiencedDevs • Recommends
On “Do other companies spend a disproportionate amount of time cleaning up their messes?”
I'd say, stop making a mess. Follow the boy scout rule and leave the codebase a little better off than you found it, every single time. There is literally nobody stopping you from doing this. You own the code, not your manager. If the code is crap, it's because you(re team) let it become crap over the past five years. Nothing ships until you say it's done, so stop saying it's done before it's done.
I don't necessarily agree with Bob Martin's particulars, but when it comes to high level concepts, he hits it on the nose. You need to be a professional.