The best line of code is the one you never write. That idea sounds like an excuse for laziness until you have spent a few years maintaining someone else's enthusiasm. Writing software feels like construction, but it behaves more like gardening. Left alone, a garden grows whether you want it to or not. Code does the same thing. The real craft is knowing when to stop planting.
Your Code Is a Liability
Every line you commit creates a set of ongoing obligations. You will read it again during a late-night incident. You will test it after your framework releases a minor version bump that changes string handling. You will debug it when logs from production make no sense. You will explain it to a teammate who joined last week, or to yourself twelve months from now when the context has evaporated.
This is not an argument for obscurity. It is geometry. Bugs need space to hide. The smaller your surface area, the fewer places failure can burrow in. A function with eighty lines and six nested conditions is not just harder to read; it is statistically more likely to surprise you. Restraint is not the absence of effort. It is the recognition that unwritten code has exactly zero defects.
When Cleverness Becomes a Tax
Consider the task of calculating an order total with a few business rules: apply a discount, check for taxable items, skip anything marked as removed. One developer writes a single expression. It streams the list through a complex filter chain, invokes a helper library, folds the result with a curried reducer, and returns the sum. It is compact. It might even be elegant in a academic sense. But to read it, you must understand the helper library's implicit casting, the order of operations inside the stream, and the business logic all at the same moment. You cannot set a breakpoint in the middle. You cannot drop a log statement without breaking the chain. The code is short on the page and long in the mind.
Another developer writes a basic loop. She declares a running total, iterates through the items, and uses a plain if statement to decide whether tax applies. The block is taller vertically, but the intent is obvious. You can read it from top to bottom without holding five abstractions in your head. You can step through it in a debugger. You can add logging on line four without refactoring the whole expression.
Clever code looks smart in a pull request for about ten minutes. Simple code looks boring, and boring is exactly what you want when you are troubleshooting at two in the morning. Your goal is clarity, not a demonstration of intelligence.
Systems Need Structure, Not Heroes
This principle scales up to architecture. A clever system might rely on handwritten consensus logic, bespoke orchestration scripts, and undocumented caching shortcuts that only one engineer truly understands. That system does not run on its own; it runs on the constant brilliance of whoever is holding it together. When that person takes a vacation or a new job, the system starts to wobble.
Well-designed systems rely on structure and constraints instead. They use database schemas that reject bad data, API contracts that define boundaries, type systems that catch category errors before deployment, and module separations that make the intended path obvious. They do not require heroics to stay stable. They are designed to survive contact with tired humans, which is the only kind of human who ever operates software in production.
The AI Amplification Problem
Artificial intelligence coding assistants make this lesson urgent. These tools generate text quickly. Present them with a simple problem and they will often return a large, complex solution that imports utilities you already have in-house wrappers for, handles edge cases that do not exist in your domain, and uses idioms from a framework version you migrated away from two years ago. The AI looks at the immediate task. You must look at the whole system.
اگر هر پیشنهادی را بدون مدیریت هزینههای بلندمدت بپذیرید، تولید کد منجر به تورم میشود. مخزن شما با کدهایی که منطقی به نظر میرسند، کامپایل میشوند و تستها را پاس میکنند، اما هیچکس واقعاً آنها را درک نمیکند، متورم میشود. خطر، یک خطای سینتکسی آشکار نیست؛ اینها در مرحله بازبینی (review) شناسایی میشوند. خطر، ضخیم شدن تدریجی پایگاه کد است؛ جایی که هر فایل به تنهایی معقول به نظر میرسد، اما کل مجموعه در ذهن هیچ انسانی نمیگنجد. اینگونه است که سرعت مهندسی از بین میرود؛ نه با یک سقوط ناگهانی، بلکه با انباشت بیصدای چیزهایی که هیچکس حاضر به حذف آنها نیست، چون از دست زدن به آنچه کاملاً درک نمیکند، میترسد.
حذف کردن یک مهارت طراحی است
مهندسان بزرگ خود را با تایپ سریعتر از دیگران اثبات نمیکنند. آنها با انتخاب سادگی و با ترجیح دادن حذف بر انباشت، پیروز میشوند. حذف کردن کد مستلزم درک آن است. شما باید جریان داده را ردیابی کنید، مطمئن شوید که یک ویژگی هیچ فراخوان پنهانی ندارد و تأیید کنید که نیاز تجاری آن دیگر وجود ندارد. حذف کردن از اضافه کردن سختتر است، زیرا نیازمند قطعیت است.
تیمها اغلب ویژگیهای عرضه شده و افرادی را که pull requestهای عظیمی ارسال میکنند، جشن میگیرند. تیمهای کمتری مهندسی را تحسین میکنند که چهار هزار خط منطق مرده را حذف کرده و سیستم را سریعتر و درک منطق آن را آسانتر میکند. اما این شمارش منفی خطوط کد، اغلب خدمت بزرگتری به آینده سازمان است.
بخش گرانقیمت
کد اکنون ارزان است. هر کسی میتواند در عرض چند ثانیه صفحات آن را تولید کند. منبع گرانقیمت، وضوح است. حفظ قابلیت درک یک سیستم، مستلزم زمان، قضاوت و خویشتنداری است. مهندسی واقعی در مرحله ویرایش اتفاق میافتد، نه در مرحله پیشنویس.
کمتر بنویسید. بیشتر حذف کنید. ساده طراحی کنید.