Posted on
We all want to write quality code for our projects, but what defines quality code to begin with?
For further actions, you may consider blocking this person and/or reporting abuse
Are you capable of chipping in across sysadmin, ops, and site reliability work, while supporting the open source stack that runs DEV and other communities?
This role might just be for you!
Nick Taylor -
BekahHW -
Erin Bensinger -
Gabor Szabo -
Once suspended, shadowphoenix will not be able to comment or publish posts until their suspension is removed.
Once unsuspended, shadowphoenix will be able to comment and publish posts again.
Once unpublished, all posts by shadowphoenix will become hidden and only accessible to themselves.
If shadowphoenix is not suspended, they can still re-publish their posts from their dashboard.
Once unpublished, this post will become invisible to the public and only accessible to Rose.
They can still re-publish the post if they are not suspended.
Thanks for keeping DEV Community 👩💻👨💻 safe. Here is what you can do to flag shadowphoenix:
Unflagging shadowphoenix will restore default visibility to their posts.
Top comments (1)
Hi Rose,
You can find many books out there written on conventions and widely accepted methodologies. But for me it boils down to three important things:
Documentation: a well documented code will reduce the time and effort you spend on understanding it.
Modularity: a code constructed to be modular will be easy to debug and change a certain part of your code without altering the rest of your program.
Maintainability: this includes the other two and may encompass other agreed upon conventions. Mainly, the whole point of writing a quality code is to make it maintainable for a longer time.
As I said, there are several methods and conventions out there. This is my personal view.