Lines spents

I have noticed I spend a lot of time deleting code. I think I might spent about 60% of my time at work deleting code. That is my own code, other people's code, random code in some library, code that could of been a config file, code never used, code that was meant to be a feature, but never quite made it to production, and code that made it to production, and now is now performing so terrible it should be removed.

I more feel like if code does not add production value it should be deleted. I think if possible there should be an A/B test as to whether the code does add value, and if it doesn't add value it should be deleted. I think it is okay to have a library of functions, once the code is in production, but it would be silly writing a library first, and then the production code second.

At a time with vibe coding, and people boosting about the number of lines they wrote being over 10k that day. I think it is with utmost stupidity thinking someone how vibed coded 10k lines of code will ever be able to maintain that code.

[Software] is pervaded by the reassuring illusion that programs are just devices like any others, the only difference admitted being that their manufacture might require a new type of craftsmen, viz. programmers. From there it is only a small step to measuring "programmer productivity" in terms of "number of lines of code produced per month". This is a very costly measuring unit because it encourages the writing of insipid code, but today I am less interested in how foolish a unit it is from even a pure business point of view. My point today is that, if we wish to count lines of code, we should not regard them as "lines produced" but as "lines spent": the current conventional wisdom is so foolish as to book that count on the wrong side of the ledger. prof. dr. Edsger W. Dijkstra, On the cruelty of really teaching computing science