I’m showing my ignorance by asking this question, but feel I need to.
In your book “Easy HTML for eBay” on page 119 with a headline “Styling Text”, you show a screen called “Create Arbitrary Styles”, with the following code:

p {font-weight bold}

My question: Is that code in the Body or Head of the page?

I tried to find the Erratum for the book on the Que site but there was no such section, and I know that you wrote the book a long time ago.

I’ve used some to the book with success, but would appreciate your input as to which section the Style code belongs.

You wrote very useful quick-start book that got me studying deeper. I’d greatly appreciate your answer if/when you get a chance.

Thanks.

Bill Miller
w.d.miller@verizon.net

Thanks!

—- Nick

sure modeling and agile can work together… I use UML (mainly class diagrams) when I’m unfamiliar with a code base or when I have to explain it or walk through it with someone. I sketch it in a piece of paper (and generally use the wrong notation), but when the other guy (or myself) gets it, I generally throw it away… no need to keep it of file it because it’s likely to have changed the next time you want to use it, and no one is going to update it anyway.
But for what I gathered, in this case you are working on a new project and I think that by yourself, so the communication factor is not really a ‘factor’.

I’d say the same about using scrum… you generally use agile to facilitate communication among team members. Scrum meetings are a good way to know what’s going on and if someone is stuck and who can help out. Other figures there as the customer or the product owner keeps you in contact with what you are building… but in this case, it’s just you!

I find stickies and Kanban panels very useful. Any kind of visualisation technique to talks to you about the state of your project can be very helpful. Also XP techniques such as TDD (BDD) or continuous integration are helpful even if you are the only one coding.

But as I said, whatever works for you is always better!