April 2003 - Posts
I have thought about this for some time now and decided to write it down and let people tell me how ludicrous my theory is….
I believe that it is not possible to ‘Do your best’ when it comes to developing an application. I think this because as developers we are constantly evolving in our skill sets. Even within the scope of a small, say 4-6 week project; we have learned things by the end of the 6 weeks that make us better than when we started. Thus, to do our best we would need to re-code the things done at the project outset and then at the end of the re-write we would once again be in the same boat. This is all said with the unrealistic consideration that I asked for 10-12 weeks for the project, when I really needed 18-24 and the client only gave me 4-6.
So in order to truly ‘Do your best’ on a project, there would need to be no deadline (thus an unlimited budget) and you would have to do the entire project without learning anything new or knowing of any possible way that any line of code could work better!
Translation: This just ain’t gonna happen in the real world!
So – the next time you complete a project, don’t say ‘I did my best!’
Dont like it, lacks emphasis on new articles.
I was also really hoping that with this design they would create some type of sticky context as too who I am. Kinda like in VS where I can tell the IDE that I am a C# developer, wish MSDN would do that!
Oh well, congrats guys on the new design - still the best dev site ever!
I am sure that since most of you are like me and want to drink as much Kool-Aid as possible; I am sure you prolly read Paul Thurott's great stuff on The SuperSite and WinInfo. If you don't, give him a look some time; he is about as connected in MSFT as any person I know of...Today there is a new interview with the executive godfather himself!
NOTE TO PAUL: Can you join the gave and give us an RSS feed!?
First of all let me say that most salary surveys are blatantly wrong. But for this exercise we will assume these assessments as truth. C# developers on a whole make more because their skills sets tend to be more multi-faceted. I don’t know of any C# devs who don’t know VB! By virtue of the fact that they are comfortable in c based syntaxes, chances are they know C,C++ or Java. They tend to have a wider range of experience and much smaller learning curves. (this is demonstrated by the fact that they are working with such a new language and framework.) The simple fact is that C# developers make more because they tend to have more experience (in general) than their VB counter-parts. Not because C# is better, or tougher.
Another thing that comes into play is the simple economic factor of supply and demand. Many more VB guys out there than C#, this is complicated by the fact that the IT decision makers have some how gotten the idea that Redmond is phasing out VB and moving C# in so they in turn need to get on that bandwagon.
Finally, C# guys make more money than the VB guys because we are far more handsome!
...Been working on a custom content management system for a client lately, started using some of the basic contenteditable capabilities in IE. Kinda wanted to go the route of a Rich Text Box but #1 did not want to waste the money, #2 did not want to waste the time. Then today I stumble across a sweet little open source clone at http://www.fredck.com/fckeditor/
Hey, if someone else will do it for me; more power to 'em!
I Was having a talk with a few of my cronies this morning and was telling them about the C# vs. VB.NET moaning going on here and one of them brought up what I thought was an interesting point; whichever language gets VB6 style enc (edit and continue) first will be their choice.
Now I started out as a VB guy and saw the ! LIGHT ! about 2 years ago on a flight from Louisville to Tampa. Personally I have gotten over the omission of this great feature but I would love to see it make a comeback. My good friend and msdn regional director once told me that he heard it would be a feature in the next release, but then I read a chat from the C# team where they kinda alluded as if it was not important to them…?
Anybody got the scoop on this?
OK, been working on a line of business app for one of my clients and I have gotten to the point where I need to do some real world testing. The app is pretty small; something like 40 tables in the db but it will expand pretty rapidly. How can I test this thing with a bunch of data in it? So I threw together a lil utility that will call the stored procedures and pass in dummy data; worked great, in a few minutes I was testing with 500K+ rows in some of the tables; an important thing to do, something often overlooked.
So here is my thing, I wonder now if this is useful...teaching the app tables rather than stored procs would be easy but it would be slick if I could make it understand keyed relationships…?!?
So let me know, is this something useful? Is there something already out there? Am I insane for wasting a couple hours on this?