-
-
Notifications
You must be signed in to change notification settings - Fork 16
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat(posts): add "Why you should understand your code"
Post: 2024-10-06-why-you-should-understand-your-code.md
- Loading branch information
1 parent
707f704
commit 5db06f4
Showing
1 changed file
with
15 additions
and
0 deletions.
There are no files selected for viewing
15 changes: 15 additions & 0 deletions
15
_posts/2024/2024-10-06-why-you-should-understand-your-code.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,15 @@ | ||
--- | ||
layout: post | ||
title: Why you should understand your code | ||
date: 2024-10-06 16:21:27 | ||
excerpt: Why you should understand the code you write. | ||
categories: code philosophy | ||
--- | ||
|
||
You should understand the code you write because it's your job to do so. It's like a car mechanic who understands the combustion engine and a doctor who understands the medicine he's prescribing. | ||
|
||
If you're copying answers without understanding them, then you're being a code monkey. The outcome is that code complexity, technical debt, and risk of bugs increase. As a professional, you have to set a bar on quality. Doing things blind will not help achieve that. | ||
|
||
But does this mean you need to know every single detail? Not really. For instance, you can still drive without having a deep understanding of physics. But comprehending high-level physics will give you a better mental model of how a car functions. | ||
|
||
So what is the conclusion? That learning is always part of the job. You won't know everything at the start, which is fine. But you will gain greater knowledge each time you work on a particular problem. As your expertise grows, you will form more connections so you can dive even deeper. |