Jason Mauss' Blog Cabin

Newsletter Table(s)

As part of my DevCampus website, I plan on allowing people to get newsletters via email or RSS. For those newsletters, I'm building a database table and trying to think of every kind of possible attribute (column) associated with my newsletters I might want to track. After asking my friend Darren for his input he suggested I blog about it to get feedback from readers and so, here you have this blog post. I'm sure a lot of you guys have built a "newsletter table" or something similar before - if so - what did your table or tables look like?

Here's what I have so far: (column name - data type - key)
Title - varchar - Primary Key (the title of the newsletter will be unique and probably include a date reference e.g. "DevCampus.com Newsletter - 9/30/2005")
CreatedDate - datetime (the date someone first creates a newsletter record)
DistributionDate - datetime (the date the newsletter is actually published/mailed)
HTMLContent - text (for subscribers that want HTML emails)
PlainTextContent - text (for subscribers that only want plain text)
PageViewsGenerated - int (to track how many hits to the website came via links in newsletters)

I'm thinking of adding "CreatedBy" and "DistributedBy" foreign key columns to track which user created and published the newsletters - just in case at some point in the future I have someone else help me administrate the site. So anyway, yeah, tell me what you think. You know you don't have anything better to do, LOL.

Data Modeling and Enums

How should enums be modeled in your database? Static Lookup Table? Or should they be left out of the data model and contained only in the object model? Specifically, I'm thinking about an enum that is represented in the UI layer by something like a combo or list box.

Rather than just coming to a decision on my own - I thought I would open it up to my readers (both of you..heh) to give me your opinions on how enums should be modeled in the database. I'm guessing that there are a couple of different ways of thinking on this that both have convincing arguments.

Light Posting here - but more on Project Fazr

This month has been very light on posts, mostly because I'm now splitting my time between blogging here and blogging over on my Project Fazr blog.

In the next month we're going to start divulging more information about our first product and in the month after that probably start looking for beta testers. If you're interested, go have a look here.

Interesting Essay on why Software Sucks

I've enjoyed a lot of Scott Berkun's essays and this one is worth a read if you have 15-20 minutes.

#46 - Why Software Sucks

Sitepoint Book Review

DHTML Utopia: Modern Web Design Using JavaScript & DOM
Stuart Langridge
Sitepoint, May 2005

I received this book from Sitepoint shortly after it was published. I was excited to see that it was going to cover AJAX and some more modern techniques that web designers are using today, and not a summary of what was being done a year or two ago. Since I'm usually reading a half-dozen books at any given time, this one sat in the queue of "books to read" for a couple of months before I got around to it. I also have a Firefox Secrets book from Sitepoint that I've begun reading - review forthcoming.

I've read quite a few books on web design from authors like Eric Meyer, Jeffrey Zeldman, Danny Goodman, Scott Isaacs, and others. While the authors name wasn't new to me, I hadn't read too much of his writing before. I'm happy to say that the writing style in this book was very clean and organized - perhaps Stuart is a great writer, or just had a great editor...it's usually at least one of the two. :-) (I've written enough to know that a good copy editor can save your bacon!)

So, the book:

Sometimes I start reading a book with some preconceived notion of what I'm going to learn but with this book I was just going to go along for the ride and really didn't have any expectations. So, I can't really say the book did or did not meet my expectations. Having said that, I think this book does a great job in a few areas.

1. It doesn't dumb down DHTML concepts to the point that you feel you're learning HTML and DOM from the beginning. It provides a brief overview of HTML, CSS and JavaScript - but covers them quickly just as a way of saying, "if you don't find yourself skimming over these parts...you might get a little lost later on." I appreciated this because of the fact that I've started reading a few books on DHTML just to find myself getting very bored with the mundane beginners introduction to HTML and "what the internet is" or "how the internet and web pages work". An introduction for a book on DHTML should be like this one was. Short and sweet.
2. After the introduction it gets right to the point, wastes no time. Case in point: Chapters 2, 3, and 4 are on the DOM, Handling DOM Events, and Detecting Browser features. Like I said, all technology introductions were covered in the first chapter.
3. After code samples are listed - the author takes the time to analyze them in detail, a line or two at a time. This not only helps those a little unfamiliar with JavaScript learn but, it also helps experienced JavaScript'ers reinforce their knowledge and confirm that they understood the script correctly. Plus, it's easy to skip over the "what did we just do here" areas if you read the script block and had no questions about it.

The chapter on AJAX "Remote Scripting" was good. I felt it was a little bit cluttered with information that didn't need to be there, such as the origins of XmlHtttp and what not but overall it was a good overview of using JavaScript to manipulate DOM elements by calling the server for data. There is also a short 15 page chapter on using XPath that didn't seem to fit in the book. In my opinion, if you're going to talk about XPath only and not even really introduce XSLT's purpose and the other associated technologies then don't bother with XPath. I just skimmed over this chapter since XPath, I will admit, has never really intrigued me that much.

So, overall - this book falls somewhere between good and great. It covers DOM very well. It covers common JavaScript usage very well. Personally, if I were writing a book like this - I would use something other than a DHTML menu for my samples because it's already been done by a hundred people a hundred different ways. The information on AJAX/Remote Scripting was well done and much more thorough than what you'll find on most websites and free resources. The book isn't very thick (~300 pages) and reads quickly so if you're pressed for time it won't take too much of it. If you're a really experienced JavaScript and DOM developer then you probably won't learn a heck of a lot from this book but if you're like me (really like web design but cautious to learn more advanced techniques) then this is a good book to give you the knowledge that will make you more confident in designing modern, dynamic web pages.

Visual Studio 2005 Guide now online!

Project Fazr seeking a talented designer