UPDATE 11.21.12 | Since writing this post, I’ve come to the realization that it’s more accurate to say “markup” instead of “code” in this instance. A programmer I am not!
- In the design stage, brainstorm with the team regarding all of the design ideas to try for the ebook. And then assign a hierarchy of importance to the ideas for the sake of productivity on a tight deadline. In this way no ideas get ruled out and, if you start at the top and work your way down, you will always be working on the next most important element of the project. This is especially helpful when I have to learn the code as I go along. Some things come together quickly while some things take a long time to research and get right.
- Working with code feels a lot like learning to recognize patterns. Everything that opens must close. Look at it and work with it long enough and it starts to make sense.
- Type code slowly and with thought. I’ve spent too much time trying to find unclosed tags. One trick I like is to type “/” in Dreamweaver while editing in the HTML doc to check for unclosed tags. If “/body” pops up, the file is in good shape. If any other tag pops up I go back and try to find the error. This saves time and less rounds of validation (but validation comes in handy for those times I just can’t find that &%@#! unclosed tag).
- Try a regex action on one example and be sure it works the way I want it to before applying it to every open HTML file. Enough said there.
- It’s going to take me a while to learn the cascading aspect of CSS.
- If I feel like I have all the answers on one day, I will inevitably feel like an idiot the next day. Conversely, when I feel like an idiot on one day, I will inevitably feel like I know what I’m doing the next day. Hang in there. That’s what learning feels like. I remember back when Quark felt the same way.
- There’s always going to be more to learn and this makes code seem fun and interesting. This makes my brain happy. (Reminder to myself to revisit #6 when this does not make my brain happy.)