diff options
| author | Aki <please@ignore.pl> | 2024-05-05 23:53:27 +0200 |
|---|---|---|
| committer | Aki <please@ignore.pl> | 2024-05-05 23:56:40 +0200 |
| commit | d56fb4b66a8bfbbf37eb616de7d7c1076af3321b (patch) | |
| tree | 796e976ed658d6d7d178cb48dbcc7fec3034943d /respect.html | |
| parent | 54e9ce8c71373bec26668f2dbebc282ab88985b4 (diff) | |
| download | ignore.pl-d56fb4b66a8bfbbf37eb616de7d7c1076af3321b.zip ignore.pl-d56fb4b66a8bfbbf37eb616de7d7c1076af3321b.tar.gz ignore.pl-d56fb4b66a8bfbbf37eb616de7d7c1076af3321b.tar.bz2 | |
Published Respect post
Diffstat (limited to 'respect.html')
| -rw-r--r-- | respect.html | 46 |
1 files changed, 46 insertions, 0 deletions
diff --git a/respect.html b/respect.html new file mode 100644 index 0000000..4db825f --- /dev/null +++ b/respect.html @@ -0,0 +1,46 @@ +<!doctype html> +<html lang="en"> +<meta charset="utf-8"> +<meta name="viewport" content="width=device-width, initial-scale=1"> +<meta name="author" content="aki"> +<meta name="tags" content="programming, software development, practices"> +<meta name="published-on" content="2024-05-05T23:53:27+02:00"> +<link rel="icon" type="image/png" href="favicon.png"> +<link rel="stylesheet" href="style.css"> + +<title>Respect</title> + +<header> +<nav><a href="https://ignore.pl">ignore.pl</a></nav> +<time>5 May 2024</time> +<h1>Respect</h1> +</header> + +<article> +<p>As a programmer, one of my primary tasks is to <em>represent</em> some domain knowledge. I don't need to be an +expert. It helps, but having a grasp of things is enough. To build this grasp, I use books, references, or you know, a +helpful expert. +<p>I spend a lot of time reading, talking, playing around, trying to understand things enough to be able to synthesize a +good design. After making one, it gets pushed into the feedback loop and sooner or later a next iteration gets the same +treatment. +<p>After, depending on the field, a month, a year, or two, I finally get <em>a good grasp of it</em>. There's always +complexity left, knowledge to process, skills to master, or things to discover. +<!-- Well, almost... Stop nitpicking and looking at the comments! Point is: appreciate things and stay humble. --> +<p>It's amazing. +<p>All I want to have is pure respect towards the people involved and appreciation to author of references I use and +experts I talk with. +<p>Because of the "meta" nature of programming, I have seen myself forgetting about this basic statement. I have seen +serious iterations of "software will [magically] handle it" and some weird software development messiah complex. +Somehow, I managed to avoid these extremes and I'm thankful for that.</p> +<img src="respect-1.png" alt="i'm a genius"> +<p>What I didn't manage to avoid is the kind of "cultism" that we have within the programming field itself. X is the +only true way of doing everything. Y is the worst abomination that humankind ever witnessed. You shall never do Z, +because it is wrong, because you shall never do Z. +<p>Of course, these are exaggerated. Yet, how many times did I deny some piece of code or opinion because it didn't +match my usual approach? How many times did I look at 10 or 20 year old code as if it was the worst thing that ever +happened to me? How many times did I discard someone's workflow simply because they mismatched mine? All, a non-zero +amount of times. +<p>I'd rather not. I want to dive into new fields with respect and simple curiosity, and appreciate things as I learn +more. I want to play around with programming languages, paradigms and codebases the same way. And I better not forget. +</article> +<script src="https://stats.ignore.pl/track.js"></script> |