Isn't the appropriate response to immediately upload the NT source code that was released a few years ago? Now that I type that it doesn't seem as funny...
Boring home page. At least on myspace they try to invite you into the site with some content and "new profile" pics.
Last time I checked, my computer had a keyboard attached. I think *touch-typing* should be taught. All the stuff about how many carriage returns in a business letter or how to align the paper in the roller can be replaced with some basic computer knowledge.
This whole "contest" sounds like "please write code for our web site for us." The first challenge is an article submission system like/.. The requirements read like a spec for work. "It should have this and this and this and be able to do this. And make it so we can reconfigure it for our database." Geeze. Some contest. It might be fun to submit really bad examples and see if they end up using them on their own site. OK, that's mean, but hey...
In my web development I've found that breaking an application out into small pieces and estimating on the peices was effective. Writing a complete spec is also helpful before coding to work out a datamodel and pageflow before any code is written. This makes it easy to identify on paper where code can be reused. The spec is also a great tool for understanding the application fully. By the time I sit down to type all the real thinking is done. Standard items are very easy to estimate now that I've done them many times and have library code to work from.
Slashdot Mirror
Isn't the appropriate response to immediately upload the NT source code that was released a few years ago? Now that I type that it doesn't seem as funny...
Boring home page. At least on myspace they try to invite you into the site with some content and "new profile" pics.
Last time I checked, my computer had a keyboard attached. I think *touch-typing* should be taught. All the stuff about how many carriage returns in a business letter or how to align the paper in the roller can be replaced with some basic computer knowledge.
This whole "contest" sounds like "please write code for our web site for us." The first challenge is an article submission system like /.. The requirements read like a spec for work. "It should have this and this and this and be able to do this. And make it so we can reconfigure it for our database." Geeze. Some contest. It might be fun to submit really bad examples and see if they end up using them on their own site. OK, that's mean, but hey...
In my web development I've found that breaking an application out into small pieces and estimating on the peices was effective. Writing a complete spec is also helpful before coding to work out a datamodel and pageflow before any code is written. This makes it easy to identify on paper where code can be reused. The spec is also a great tool for understanding the application fully. By the time I sit down to type all the real thinking is done. Standard items are very easy to estimate now that I've done them many times and have library code to work from.
I felt it was a nice change from the trumpets and sweeping chord changes of all the previous shows. Worst ST theme: Deep Space 9