Seeking Ideas on how to improve efficiency and workflow
This could also be a general question, but I'm asking it in the context of Data Assist because it's what I use most often and accounts for most of the coding on dynamic sites. SA is also in there too. I've never had the chance to actually compare myself to other developers, but it just feels like often It takes longer than it should to get something done. This is compounded if it's been a period of time since I looked at a project, and have to spend time getting up to speed.
Sometimes it's just revisiting the entires flow of the site, and other times it's just using the tool itself, I find myself forgetting how to use it! (this usually takes a few months or so though)
For example, tonight I was working on a simple admin section which involved a simple user search and profile updates. The update page itself was a little more complex in that depending on what was updated it would send an email out. But, I kept getting errors when attempting the update - in ASP, invalid use of null. After about an hour, it finally dawned on me when I made my field selections in the dialog I was actually pointing to the recordset values, not the form values.
The only solution I see for that is just to use DA more often, even if I don't have an actual project I'm working on. But as far as getting reacquainted with a site I haven't looked at for a while, how do you do this, how do most developers do this? I basically just open the pages and follow the trail.
And no, I don't document my work. Not it notes, or flowcharts or anything. It's just something that every programmer has heard or been taught, but my feeling has always been that those who actually do it are required to in their work environment as a matter or policy and/or they're working with a team of developers. Is that something I should start doing, and if so, what's the best way so that I'm not spending more time with drawing flowcharts than developing or relearning my previous work?
Also, with DA, how often do most people test - after each step, or maybe after a collection of items? I've found that stopping to test, sometimes breaks momentum. But of course the downside is, when an error pops up, debugging can be a little more complex.
So I would really like to hear any ideas anyone has! I just spent almost 6 hours doing something that should have taken two. Not good.