The craft over art pattern talks about the importance of organizing utilities and knowing the value of software development like art. Programming is seen as a craft and should be able to create useful tools that help the needs of the customers instead of personal views. Craft over Art talks about how craftsmanship in software development, not only involves quality work that satisfies the customer but may also sacrifice the app’s aesthetic beauty. It’s important to find the balance between the two. This pattern highlights the customer’s needs and satisfaction over artistic expression. I found this pattern interesting because it talks about having an artistic side in software development but also keeping the customer in mind. You can be as creative as you want when designing a program but it’s also important to make sure that it’s user-friendly and know when to cut back on the creativeness when programming. This pattern is about making a practical approach to software development and making sure that the primary goal is to make valuable solutions for the customer even if it means being less creative.
This pattern has me thinking about the way I work because when it comes to be creative I usually go over my head and end up forgetting the whole purpose when it comes to programming. It helped me realize that I can be creative but I just need to remember that for the customer sake that it’s easy to use and understand. If I spend a lot of time on a program that most people can’t understand then I have to go back and spend more time on fixing it, making it understandable wasting the time I spent in the first place making it. The pattern also makes it known that its okay to make creative sacrifices if it helps the customer because they are important. I don’t disagree with this pattern because no matter how creative you want to be with programming you should always consider if it’s user-friendly and if it’s complicated. It’s important to consider the customers since they will be using the program the most and if it’s not user-friendly then customers will stop using it and try to find something else. This pattern want’s people to make sure they are making valuable decisions when programming even if it means sacrificing creativity.