Software Craftsmanship
An approach to software development that emphasizes the coding skills the the software developers themselves.
- interesting that the Software Craftmanship Manifesto took assumptions of the Agile Manifesto even further and basically stated that software engineers should acquire a certain set of basic competencies in programming rather than having a very strict engineering approach.
- the metaphor of software developers and medieval guild traditions in Europe is an interesting idea and not at all far from the truth. Throughout the course of college, I have seen a lot of change and progression in my code and software ability. People with much more programming experience have more tools and it is clear that, with time, they have grown in their software developing skill.
- I really liked how the article states that there will always be room for people to write software with their own unique knowledge. I have always found it interesting to look at code of much more experienced programmers and see how different two programs with the same functionality can be so different. Each programmer comes from a different background and it is neat to see what people have learned over the years that influence the way they write software.
- In the Software Craftsmanship Manifesto, I love the value "Not only responding to change, but steadily adding value" - This is something anyone who writes software should focus on. Merely sticking a band-aid on code so it works again should not be consider acceptable. The code should not only handle new technology and change well, it should become more polished and work even better than before
After reading this article, I was so inspired that I even went and signed the Manifesto for Software Craftsmanship and if you believe in Craftsmanship over Crap then YOU SHOULD TOO!
No comments:
Post a Comment