Inspired by the article: Don't write simple code and an old manifesto
This article is about the others — about those who just happen to write code, or who happened to write code before. Or about those who happen not to write code, but really want to. (c) I'm sure all the nonsense written below is absolutely useless to anyone. There's only one thing that really needs doing (c)... well, you get it.
Just write code, while everyone else at the meeting argues about which board to move this ticket to. Because no Jira will ever write the bugfix.
Just write code — it won't make you super rich, but it'll be enough for bread and sausage, your conscience will be clean and prod alive.
Just write code, even if it's crap code, it'll work. Working crap code is far better than a dozen tickets in Jira.
Just write code, because you spend most of your life at work. Screw-ups always happen, but if your code works — that's not a screw-up yet.
Just write code, because instead of investing in engineers the company invested in board games and work-life balance — now we have an office "Evolution" champion, but the engineers don't know how to use a profiler.
Just write code, because when you said "let's learn and take courses," they said "let's hire more people." As a result, now every third person has a referral bonus, but still nobody learned to use a profiler.
Just write code, because when you tried to split the architecture into layers and modules, they answered: "That's all theorizing, we have business and features." And now this business rests on a crowd of juniors and a pile of jsons.
Just write code, because Habr is flooded with "How I sell cat scratchers on marketplaces" and "How I quit for the sake of inner balance," while an article about memory fences or perf counters — good luck finding one.
Just write code, because the "senior" title has devalued to the level of an NFT — three years of experience, talks pretty, zero use. Some don't even take offense at "prompt senior."
Just write code, because task boards have replaced common sense and design skills, and now instead of architecture they discuss when to schedule a call to discuss the new ticket.
Just write code, because at interviews they ask leetcode puzzles, and then are surprised the candidate doesn't know how vtable and raii work.
Just write code, because otherwise it'll be written by the one who came for the "work-life balance" and the one whose AI-assistant tab never closes.
Just write code — simple or complex, with abstractions or efficient — just because it saves you from burnout and mental aging.
Just write code, just so it works. So it doesn't crash. So you're not ashamed of your commits.
Just write code, because otherwise this project, like all the previous ones, will ship to prod on crutches.
Just write code, because otherwise it'll be Service Unavailable.
Just write code, because many people can no longer just write code without a chat window.
Just write code, because otherwise the pile of jsons will only get bigger.
Just write code — because you can. (cudos @tuxi)
You're not the first and not the last; there will be others after you, they'll understand and fix your mistakes.
If there are no bugs, it means you just didn't write any code.
← All articles