I see people blogging, ranting on boards, sending emails about the bug on IIS Manager when they install VS2005CTP. Yeah, microsoft should’ve solve that glitch before printing the cds but somehow just managed to describe it on the README file. Perhaps people should at least check the README file before asking and waiting for an answer which takes time.
If your going to use the VS.NET’s autogenerated Web References code, don’t name your web service’s [WebMethod] “Invoke”. If so, you’ll get some non-understandable silly error while compiling it.
If you’re going to put a title tag on a page, i think ordering of the articlename and sitename is quite important. Probably it’s just the creator’s “whereever-he-wants-to” decision, but i find it nice when the title is in the form […][articlename][…][sitename][…].
The main reason is when i save the page, the title is used as the filename and when the [sitename] comes first…because the files saved are viewed sorted by alphabetical order by default, it’s grouped by [sitename] which i think isn’t what i want. Is it just me? 😛
Read and Unread is always the basic state that most email client have. The problem isn’t that this classification is wrong but because the notification system notifies with only those two states assumed.
I’ve got a ton of unread email which i consider to read when i get the time so i leave them in the unread state. So it’s not actually an unread unread state but a perhaps-will-read unread state meaning that i shouldn’t be notified that a new mail has arrived. Most email client doesn’t understand this and keeps notifying me that i have new mail inferencing by my unread emails.
So, what i think is that there should be 3 states Read, Unread and New.
(or perhaps i don’t know how to set my email client to behave like that 🙂
There are a vast amount of products that claims that they separate presentation and logic but are they actually real? Mostly people will be negative with that opinion usually. So what’s the problem with the scenario.
What i think is that there are no product that assures roundtrip development(and code preservation) between the two. Designer’s input to programmers are mostly rough and apt to be modified. Of course if the modifications like code clean up and errors doesn’t change the original intent of the designer, there would be no problem. But in fact, most tools that both sides use doesn’t assure it and problem comes from that fact. Oppositely, Programmer’s input to designer’s is funnily changed most of the time. That’s also the tools fault. So, the mismatch goes on and on which prevents real logic and design separation.
Anyway, tools are evolving to support roundtrip development and tool vendors are combining their heads to solve that piece so in the near future(a few more years?)…and i’m thrilled to see designers and programmers get together without heavy noise on why they changed this or that 🙂
I don’t know. I actually thought that the process would be further advanced than it is by now. And I’m not sure why I got the time scale wrong. But because I know I did, I’m reluctant to make time scale predictions.
“Don’t know but will come.” How are people to understand what he’s thinking…when an opinion leader like himself talks like that. (Even after he says he’s been proven wrong way beyond on the predictions)
Starting the msmvps.com blog.
CSS color theme is snagged from Bryan Bell’s Blosxom Blog so credit goes there.
My name is B. K. Chung(people call me bk) and i’m a Microsoft MVP in korea.
This is my first “english” blog since i’ve been blogging in korean for about 1 and a half year.
Hope there are lots to say in this blog 🙂