Julio Biason
5 years ago
3 changed files with 31 additions and 1 deletions
@ -0,0 +1,29 @@ |
|||||||
|
+++ |
||||||
|
title = "Things I Learnt The Hard Way - Don't Defend Bad Code" |
||||||
|
date = 2019-07-31 |
||||||
|
|
||||||
|
[taxonomies] |
||||||
|
tags = ["en-au", "books", "things i learnt", "personal", "bad code", "defend"] |
||||||
|
+++ |
||||||
|
|
||||||
|
Bad code exists everywhere. You shouldn't defend it, even if it is your own |
||||||
|
code. |
||||||
|
|
||||||
|
<!-- more --> |
||||||
|
|
||||||
|
Bad code isn't bad on purpose. It sadly happens. But because it is bad, you |
||||||
|
shouldn't defend it. |
||||||
|
|
||||||
|
For example, an application does whatever you need. But it crashes from time |
||||||
|
to time. Software shouldn't crash and you shouldn't defend it just because it |
||||||
|
does whatever you need. |
||||||
|
|
||||||
|
Your internal application works on a single browser. That's bad. "But maybe |
||||||
|
the other devs thought it wouldn't be worth working on all browsers". No. It |
||||||
|
is _bad_. You shouldn't defend the other devs because they decided to focus on |
||||||
|
a single browser due whatever problems they were facing. Sure it wasn't nice |
||||||
|
that they had to do this trade-off, but it is still _bad_ software. |
||||||
|
|
||||||
|
If we keep defending this kind of software, we will still get bad software. |
||||||
|
|
||||||
|
{{ chapters(prev_chapter_link="/books/things-i-learnt/own-your-shit", prev_chapter_title="Own Your Shit") }} |
Loading…
Reference in new issue