Signal-less Programming - [Are We There Yet?]

Sometimes I like to drive.

I drive like a grandpa. I turn-on a turn-signal almost too early. I want to increase my chances to survive.
Other drivers have plenty of time to recognize my intent (yeah, I know, they don’t care).

On other hand there are a lot of drivers who just change lanes. No turn-signal. Just free flow.

I sense we almost always omit intent-signal in our current state [of software development].
So other humans (incl. ourselves two days later) have to guess somehow.

What’s an example of the intent-signalling you mean? Static typing? Variable/function-naming? Namespace descriptors?

It seems to me that many software best practices are about signaling intent, e.g good naming, declarative programming, code clarity, property-based testing, etc. Of course, whether we do a good job at that is debatable.

This topic was automatically closed 182 days after the last reply. New replies are no longer allowed.