Code That Says Exactly What It Means

[monkyyy]

On Sunday, 26 October 2025 at 06:33:11 UTC, Peter C wrote:
> Among D developers, the idea of adding a new visibility 
> attribute like scopeprivate often meets with scepticism.
>
> For developers who care about clarity, maintainability, and 
> correctness, that's not redundant - it's a meaningful step 
> toward code that says exactly what it means.

"What do you call a specification that a computer can turn into a 
program? code we call it code"; this cuts both ways, both telling 
"business logic"/vibe coders to go to hell; and you to shut up if 
my code compiles.

If you take 300 lines to implement what I can in 10, your *just 
factually* being verbose and redundant, mere assertions otherwise 
are absurd. I hate function coloring, I hate "stop working" 
tagging, I hate extending dependencys... I hate safetyism itself.

> code

You wrote a big class, only to use floats to represent money. All 
the safety keywords and you broke your type theory. When you do 
this, youd be fired instantly; but if for some reason you managed 
to ship people would steal pennies with floating point errors.

Your reducing clarity.