Why You Should Never Write Bad Code as a Software Engineerby@aslin
521 reads

Why You Should Never Write Bad Code as a Software Engineer

tldt arrow
Read on Terminal Reader🖨️

Too Long; Didn't Read

"We just need a quick a dirty hack as a proof of concept" A romp through the misadventures that can be caused by quickly built proof of concepts and hacks in all aspects of programming. We must never write code assuming that it will not be launched into production because one day, it probably will. We must take responsibility for ensuring that we do not produce poor quality code or quick hacks to please our paymasters. Even if it is just for a hackathon where you are ply’d with free pizza for giving up your weekend.

Companies Mentioned

Mention Thumbnail
Mention Thumbnail
featured image - Why You Should Never Write Bad Code as a Software Engineer
Edward Aslin HackerNoon profile picture

@aslin

Edward Aslin

About @aslin
LEARN MORE ABOUT @ASLIN'S EXPERTISE AND PLACE ON THE INTERNET.
react to story with heart

RELATED STORIES

L O A D I N G
. . . comments & more!
Hackernoon hq - po box 2206, edwards, colorado 81632, usa