Programming meanwhile often boils down to "how can we turn this extremely complex problem into something we can solve step by step?" meaning edit file, git commit, repeat. Any time I try to design some kind of big plan for my software, it's mostly just overwhelming and I decide to go back to step by step or heuristics. Like I don't know about other people, but I'm not going to read the full documentation for framework X, Y, and Z to then decide which framework will suit my future needs best. When designing an API, at best I can have some rough idea of what it's going to be, but I won't even try designing the API beforehand. So I wish CS would be more "mathematical", but unfortunately it isn't in practice. But maybe that's just me being limited in my capabilities. I'm curious whether you agree
Maybe just go full pidgin:
“Tool to suck dust, make tidy for walk in home.”
s/, 'cos/;/You have to get others to guess a (typically multi-syllabic) word or phrase, but use only one syllable words to get them there.
"Tool suck dust, make not dirt for walk in home."
It is a tool to suck up dust and dirt from rugs, wood or even tile.
https://www.quora.com/Mathematics/What-do-grad-students-in-m...
> a bit like trying to explain a vacuum cleaner to someone who has never seen one, except you're only allowed to use words that are four letters long or shorter.
> What can you say?
> "It is a tool that does suck up dust to make what you walk on in a home tidy."