I’ve been guilty of applying a decision to a project I’m not sure of, just to see if I could make it work. I’ve considered just ignoring it, but I don’t want to let my project sit in the shadow of an indecision.
Just because you want something doesn’t mean you have to implement it immediately. Just because you want to apply a decision to a development project doesn’t mean you should. You need to talk it over with your team first (and make sure its something you want to do), then either put a new date in or drop it altogether.
A lot of people would agree with this. It’s not that their decisions or what they want to be done with their projects are just wrong. They’re wrong because it’s different. They are wrong because their decisions are actually done. Just because they’re wrong doesn’t mean they’re wrong.
This is one of the reasons I feel that the way we work on projects is not the best way. When we make a decision or change a project, I feel that the team has to be involved in the process and that it shouldnt be done as a group of individuals. Also, when a project is going through development, the team needs to be allowed to make changes or even have them made.
I think any good dev group should be a collaborative group. If they are not, then they will create problems and if they create them, then they will be treated with contempt. One thing that I think is important though; you can’t just say you are going to do something and then do it. I think there must be an ongoing process, something that the team is not allowed to do, and that the team should be involved in the process from the start.
This is where the idea of a “code of ethics” comes in, as I’m sure you’ve guessed. I believe that everyone should be allowed to make changes to their own code of ethics as long as they’re not damaging to anyone else or threatening to others. If a developer or another member of the team thinks that something they see as an improvement is harmful to the project (rather than a small improvement), they should be allowed to make that change.
The team should always have a “code of ethics” document, which contains a list of the things that members should not do. At the very least, it should contain a list of things that are not allowed. When the team is in a position to write new code, they should include a code of ethics list to make sure they are following the rules of the game.
The team should always have a code of ethics document, which contains a list of the things that members should not do. At the very least, it should contain a list of things that are not allowed. When the team is in a position to write new code, they should include a code of ethics list to make sure they are following the rules of the game.
As a developer, if you’re working on a project that you feel strongly about, you should definitely include a code of ethics. You don’t want to create a product that you’re not willing to release.