personas. Personas. Personas. You must know your end users. Awesome idea, make then very personal by giving them normal people names. These videos are all great, I love having some insight as to how Microsoft does development; I can then employ some of these insights into my own development. And, using personas this way is something I'm definately going to try to do.
Such common sense, but you often loose sight of the fact that you should leverage the strengths of everyone instead of focusing on their weaknesses. But, don't forget to strengthen your weaknesses just because someone else is strong in that area.
It's terrible when your team leader isn't honest. I really hate it when they just say "oh, yeah I knew that" or "yeah I forgot about that" when they have no idea. Why would you or should you be afraid to say you don't know something? Maybe they are just afraid to learn something new. I also hate it when they reject new ideas just because they aren't familiar with that piece of technology.
I know someone in a team leader position that just throws around alot of buzz words, so to the not techies, it sounds like he knows alot. But, since I actually know what those buzz words are and their technologies, I can totally tell what he knows and doesn't know. It so frustrating since his boss doesn't know that he is probably hurting the entire dev team. I'm sure there's alot of you whom know or work for someone like this.
rhm wrote:I like the way he answered the "what langauge did you use to develop this?" with "DirectX". That's a real manager's answer
Isn't it though. I always love those types of answers.
My guess is that since it is probably going to come out with longhorn, and longhorn is the first OS to have the .NET Framework at "heart" of the OS. And, all the new API calls being put into Longhorn are supposedly going to be natively .NET. I think you guys can tell where I am going with this... I would guess that this app was written in C# utilizing DirectX 9.
I think x64 will be more widely adopted by the home and small bussiness pc market, and the Itanium more adopted by the Server market. I would prefer the x64, since I could still use my existing apps until new 64-bit versions come out. Just imagine the cpu speeds we will see in the 64-bit life cycle.
Can you really store a video recording of your entire life in a pedabyte? That is alot of video!! You wouldn't really need to remember things if you had that. You could literally search through your memories. That is really kind of scary if you think about it.
Jul 10, 2004 at 9:26PMAre you guys going to add this Drag-n-Drop ability to create databound fields to C#? This is just a feature of Visual Studio, and I think that all of Visual Studio's features should be available to you in whatever language you are writing in.
Manip, How much have you worked with VB.NET?
When I first started with VB.NET I was a little disorriented with all the changes from VB6. Once I just jumped in over my head, things just started to amaze me.
Here is a list of thing that amazed me about VB.NET versus VB6:
1) Alot of Win32 API calls built in the framework (not so confusing to use)
2) Better OOP / True Inheritance (I use Inheritance to add little features to Forms/Controls, you have the code in one place now, instead of having to paste it on every form in your application)
3) Better Delegate handling (You can have one function handle the same event for multiple objects, this also reduces the amount of copying and pasting code.)
4) Dim myVar As String = "Sweet"
5) You can have the code for multiple classes with in the same file. (That is why there is "Module/End Module")
6) Try/Catch blocks for trapping errors, instead of just using On Error (nicer for doing different error trapping in seperate parts of the same function)
7) "Get/Set End Get/End Set" (I think this make the structure of the code easier to read)
8) Faster Code execution versus VB6
9) No more DLL hell (Do I really need to explain this one)
10) And there are many, many more...
These are not listed in any particular order, that is just the order that they came to mind. There are many more reasons why I love VB.NET much more than VB6.
Don't think that I am new to VB6 or VB.NET. I have been working with Visual Basic since about 1997, I am a Microsoft Certified Solution Developer with Visual Studio 6, and a Microsoft Certified Application Developer with The .NET Framework. I am an expert with the Visual Basic language (both VB6 and VB.NET).