I spend a long time getting requirements for a job. Then a couple of days reading documentation and slowly coding my way into a bunch of corners resulting in co

I spend a long time getting requirements for a job. Then a couple of days reading documentation and slowly coding my way into a bunch of corners resulting in code that doesn't work. So after 3-4 days of "working" on a project, I'll actually get into a groove where I can knock out a decent app or tool in about two days. Then add another day for testing and documentation. With fixes needing to be made here and there, that means two good days of coding (and a couple days of bad coding that might be thrown away) for two weeks. If I start spending a lot of my time coding, that means I'm running off without getting requirements, or I'm stuck with a problem I don't know how to make progress on. So for me this is a good cadence.