[lanstin]

I have been programming for decades, and I have never had a time of outstanding productivity without times of times of much less activity. Creative activity, for many people, is non-linear and not a recipe based activity. Sure, writing the fourth app in a framework, you can crank it out, but coming up with a great framework for the type of applications rhat your business and technical environment requires something else, a metaphorical walk around the park, while the various possible pieces od solitions kind of simulate themselves in your muttering only half conscious imagination. The sort of solutions that achieve the agile manifesto imperative to maximize work not done. You find interfaces that simplify the problem space so much that so much possible code becomes unneeded.

I find too many people mistaking velocity for progress to be an almost insolvable organization problem. if you want to end up with mega lines of code that are all part of a useless of incomprehensible solution that is certainly a job, but might fail as a life's contribution.

I am no longer an eager youth, but when i was, the thing that hooked me to push on past limits, was my excitement and joy about solving real problems, at scale, with software, with a simple yet powerful idea. It was not any history of frequent commits or risong to rhe 95th %ile or the barren useless of a streak. It was having an idea born out of real needs and made simple enough to need almost no comlexity to implement. Having that novel simplicity go into production and be used was motivation for a lifetime of work.

I certainly have periods of stillness and more restful learning than prodigious output, but they are, for me at least, completely necessary. they may be fairly lethargic as well.