What are web applications, really?
Published 5.18.2006 by ~mattg
So, as part of our monhtly newsletters, we typically include technical articles that deal with various aspects of our application. Since we are in the business of reliability engineering, I shall spare you the topics of most of them. As a developer, I get to write an article for an upcoming newsletter that deals with web applications.
Now, I know what a web application is, but trying to describe our in 1200 to 1800 words seems to be a bit more difficult that I would have expected. It’s not that there isn’t enough content… I just have a hard time intelligently identifiying everything that makes our web application worth it’s weight.
I just spent the last hour writing, and I ended up with 250 words. Unfortunately, I probably typed at least 500, but most of those were quickly delete and rewritten. I just can’t help but sound like an idiot writing about it.
Maybe it’s a case of writer’s block, who knows. Perhaps when the deadline gets closer, the words will come easier…. That’s typically my approach to writing papers, and it got me through college.
Filed under .NET Development
Here’s some advice from an ignoramus, who thinks he knows what a web application is, but really has no bloody clue. Try to answer these questions:
1. What does a web application do?
2. What purpose(s) does it serve?
3. What need(s) does it fulfill? (Is this question different from the previous two?!)
4. What steps does a web application take to fulfill its purpose(s) and to satiate its user’s need(s)?
5. What are some of the main problems or difficulties that designers of web applications face?
6. How does your particular design deal with or eliminate these problems?
7. Why do you rock?
If you answer me those questions, I’ll be tickled pink. You may also find yourself with 1500 words.
Or not.
I make no guarantees.
Thanks professor… I’ll have to let you know how it turns out.