Code is a liability, not an asset. So goal of software engineer is delivering the maximum amount of desired functionality at the cost of the least amount of code complexity, even as desired functionality evolves over time.

Dec 24, 2022 · 3:03 AM UTC

166
420
56
3,876
Replying to @gdb
Controlling complexity is the essence of computer programming
2
Replying to @gdb @orenellenbogen
That’s a bit reductive; it’s like saying your car engine is a liability when it’s clearly a must-have. As you alluded, though, an over engineered car engine with many moving parts that can malfunction can become a problem. Similarly: Code isn’t a liability; complexity is.
1
1
36
Replying to @gdb
Does make you wonder why some people would evaluate the effectiveness of a developer by the number of lines they've written...
4
Replying to @gdb
I try to explain this. Many companies have huge code footprints with the accompanying maintenance costs and risks. But what is driving this waste? In my view premature domain coupling.
4
Replying to @gdb
@elonmusk It's not just applicable to software engineering! It's for any engineering: The goal of engineering and engineer should be delivering the maximum amount of desired functionality at the cost of least amount of complexity, even as desired functionality evolves over time!
2
Replying to @gdb
Actually is kind of applying to everything in life: the simple the better (google search, #ChatGPT…) but maximal quality.
1
Replying to @gdb
💯 best code is that you don't write. Complex code is created for readability and comprehension. With AI support we eliminate this. Dope but scary for the industry 😅
2
Replying to @gdb
Indeed! can we also stop measuring line-of-code check-ins as developer productivity metric?
1
Replying to @gdb
An asset is just an unrealised expense so don't really follow your point.
1
Replying to @gdb
$ of revenue per line of code
1