Software patterns are well know (Singleton, MVC, etc) as are anti-patterns (cut/pasting of code, etc.), but do developers ever think of their own personal patterns or anti-patterns?
Just as tool sets can vary from project to project and technology changes over time, personal patterns can turn to anti-patterns based on the project.
I know Java but I would not use Java on an iOS mobile device. The quality of the product would suffer vs using native tools. The same goes for trying to use Microsoft tools (does Mono come to mind?) on linux servers. But this is not about tools but about how you (as a developer) think about your role in development and how you personally effect it. If your pattern is thinking that Java is the perfect tool for any project, then that can become an anti-pattern if the project is on iOS.
The interaction between team members can also be effected by personal anti-patterns. Not asking questions is a personal anti-pattern, so is not making decisions or hiding errors. All behaviors that are not beneficial to you or your projects.
Take some time one of these days and just look at your self and see if you can spot any anti-patterns that you may have. Once you spot them (if you have any) see if you can not use them.
Just as tool sets can vary from project to project and technology changes over time, personal patterns can turn to anti-patterns based on the project.
I know Java but I would not use Java on an iOS mobile device. The quality of the product would suffer vs using native tools. The same goes for trying to use Microsoft tools (does Mono come to mind?) on linux servers. But this is not about tools but about how you (as a developer) think about your role in development and how you personally effect it. If your pattern is thinking that Java is the perfect tool for any project, then that can become an anti-pattern if the project is on iOS.
The interaction between team members can also be effected by personal anti-patterns. Not asking questions is a personal anti-pattern, so is not making decisions or hiding errors. All behaviors that are not beneficial to you or your projects.
Take some time one of these days and just look at your self and see if you can spot any anti-patterns that you may have. Once you spot them (if you have any) see if you can not use them.
Comments
Post a Comment