How do you stay persistent in a long (and hard) path?
Ordered life maximizes efficiency. Although it bores and demotivates quickly. At least for me and creative friends. But I neither favor chaotic life, because it has too low persistence for many things. Some things need high persistence and focus in order to develop them. For example, I can't develop and test feature X quickly because it relies on complex logic, it needs design which is about to develop in one week, UI code is one of things which can't be generated efficiently. So I probably need to save my work in a way, which can easily be continued later. Also for this reason software engineers have design patterns: it's easier to place modular bricks together, than to place brick in entangled labyrinth. But too much depth of patterns leads to "over-engineering": it's a situation when you spend much more on coding than on implementing a feature. So depth of design patterns correlates with instrinsic complexity of feature and delegation of work. But there are other, non-technical ways to "save and continue" progress.
Diary. I can write what I've done this day, which insights I've had this day, what to do next day, and then read it. So that short and mid term memory keeps a track with long and persistent path, which can be detalized, glued, executed, rewarded etc. in progress. It's like a very small friend. Old but good.
#blog #thoughts #pesistence #work #diary #slowlife
I love this slice of Software Engineering cake!
#softwareengineering #softwaredevelopment #programming
#blog #thoughts #meme #memes