Really cool question. My programming ethics have changed so much over the years. I'm not sure all of these can be called ethics but they're my development/career guidelines.
Make the best thing you can with the resources you've been given. If you can't build the best product, be clear about that to stakeholders. If the best you can do isn't good enough for your own standards, don't do it.
If the application you're making doesn't make the world a better place, you shouldn't be doing it. Money should never be more important than your impact on the world.
If something can be made open source, make it open source. There is someone out there with your exact same issue and they could use your help.
Help junior developers. You had mentors when you started, they should too. There are no stupid questions, just interested developers who haven't had the time you've had to figure things out.
Stay healthy. Don't kill yourself over a project, it's not worth it. Eat well, work out, read, watch tv, hang out with friends and do side projects that make you happy. Your happiness and health are the biggest factors in your productivity. An unhappy developer is a bad developer.
Those are the most important rules I have when it comes to development, in no particular order.
I've been a professional C, Perl, PHP and Python developer.
I'm an ex-sysadmin from the late 20th century.
These days I do more Javascript and CSS and whatnot, and promote UX and accessibility.
In order to defend and preserve the honor of the profession
of computer programmers, I promise that to the best of my ability and judgement:
I will not produce harmful code.
The code that I produce will always be my best work. I will not knowingly
allow code that is defective, either in behavior or structure, to
accumulate.
I will produce, with each release, a quick, sure, and repeatable proof that
every element of the code works as it should.
I will make frequent, small releases so that I do not impede the progress of
others.
I will fearlessly and relentlessly improve my creations at every
opportunity, I will never degrade them.
I will do all that I can to keep my own productivity and the productivity of
others as high as possible. I will do nothing that decreases that
productivity.
I will continuously ensure that others can cover for me, and that I can
cover for them.
I will produce estimates that are honest, both in magnitude and precision. I
will not make promises without certainty.
I will never stop learning and improving my craft.
In all my communications (especially written and public ones), I will
not allow myself to be offended by what people say to me, but I will
do everything I can to not offend the people I speak to.
I've been a professional C, Perl, PHP and Python developer.
I'm an ex-sysadmin from the late 20th century.
These days I do more Javascript and CSS and whatnot, and promote UX and accessibility.
Top comments (9)
Really cool question. My programming ethics have changed so much over the years. I'm not sure all of these can be called ethics but they're my development/career guidelines.
Make the best thing you can with the resources you've been given. If you can't build the best product, be clear about that to stakeholders. If the best you can do isn't good enough for your own standards, don't do it.
If the application you're making doesn't make the world a better place, you shouldn't be doing it. Money should never be more important than your impact on the world.
If something can be made open source, make it open source. There is someone out there with your exact same issue and they could use your help.
Help junior developers. You had mentors when you started, they should too. There are no stupid questions, just interested developers who haven't had the time you've had to figure things out.
Stay healthy. Don't kill yourself over a project, it's not worth it. Eat well, work out, read, watch tv, hang out with friends and do side projects that make you happy. Your happiness and health are the biggest factors in your productivity. An unhappy developer is a bad developer.
Those are the most important rules I have when it comes to development, in no particular order.
perfect @stefandorresteijn
👏💖
Same here
Wait, you had mentors when you started? #sadface.jpg
Here are mine:
In order to defend and preserve the honor of the profession
of computer programmers, I promise that to the best of my ability and judgement:
I've hosted them on dmerej.info/oath.md.
Items 1 to 9 come from the Programmer's Oath by Robert C. Martin.
The last one is mine, adapted slightly from the Crocker's Rules.
It leaves money on the table. But not being dead inside benefits all aspects of life.
Try not to make anything worse.