Getting Into the Code

I spent today exploring the dataflow through the web application, web services, and supporting Perl scripts and other executables. At this point, I’ve gotten through a few of the rendered ASP.NET pages, and down into the actual linguistic bits that I don’t really understand.

I have almost 10 pages of notes, most of which is for my own benefit. I am of the learning style where writing something down solidifies it in my memory. Right now I’m starting to develop a picture of the whole thing in my head. At the same time, I’m learning a bit about C# and the ASP.NET class hierarchy. Whee.

Gah. I am turning into a Windows developer.

Very little of the code is commented. Nick Coding Style™ requires that any code file be at least 25% comment. Ask Dan or Fritz if you don’t believe me.

ASP.NET 2003 produces HTML 4.0 code. That’s an 8-year-old standard. ASP.NET 2005 will use XHTML 1.1 and CSS 2.1, but it’s only in beta right now, so we’re not about to start using it. Le sigh.

A lot of my suggested improvements would probably be in the code-cleaning and code-documenting departments. But then again I’m generally particular about such things.

I am also announcing that I will be starting a regular LJ series, “Reasons Why I Hate Windows”. The first few posts are already ready…

Minstrels Song” from Question Of Balance by The Moody Blues


2 responses to “Getting Into the Code”

  1. heh. don’t let C# get you down. i used it at work last summer for ASP.Net stuff and came away pretty impressed. No point-and-click development for me neither; it takes quite a bit of getting used to after coming from PHP or ASP classic, but after that it’s quite a powerful tool. (And if I remember correctly, it feels a whole lot like JSP development too.)

    And re: Nick Coding Style, Jangie coding style is also 25% comment. However, the commenting done in mine is usually done as bad code that got commented out, not as anything really … umm … useful.

  2. Where are you working, again?

Nurd Up!