Contents tagged with Stupid is as stupid does
-
Intel CEO Dr. Barrett is upset with his employees
It seems that Dr. Craig Barrett of Intel is upset with his employees. I disagree with his views, but I couldn't resist responding to his latest memo with a smartass comment of my own.
-
Where did this come from?
Ok, I think this file came from a link on weblogs.asp.net, but I can't find the link, just the file. I have a file called PerfNScale2-27-04.zip. Inside the zip file is a bunch of good info about how to create applications with .NET that scale up and perform well. The problem is that I can't find where this file came from. I think it came from GotDotNet.com, but I don't know from where. If you have that link, if you can please post it as feedback that would be awesome.
-
Secured my wireless..........finally
I had always stayed up on the fact that wireless was inherently insecure and that there were some steps that you needed to take to properly secure it, but I never did anything about it. Well, last weekend, I opened up my laptop at home and saw that my neighbor had installed a wireless network. Since I could get into his, I decided that this was a bad thing and I locked my down, finally. I hope that no one has been wardriving through the neighborhood...........................
-
Intel 64-bit processing
As a followup to my post about Intel's x64 bit x86 plans, News.com has posted an article about an upcoming Intel demo.
-
More on 64 bits with Intel and AMD
I just saw an article that leads me to believe that Intel is going to come out with a 64 bit extension for the 32-bit Intel x86 architecture.
-
Need Assistance - 0x8000ffff catastrophic error when debugging VB6 COM+ objects
Hi all. I am trying to debug some Vb6 COM+ components under Win2k3 server. I have inherited this code from someone else. I have loaded the components into a COM+ application. I have the com+ app running as the interactive user. When I run the components through the debugger and call them through the web browser, I get an 0x8000ffff catastrphic error. When I don't run the components within the debugger, everything runs normally. I can compile the components fine. The compiled components work properly when called directly,
the problem is when running underneath the debugger. -
What in the world is going on?
What is going on with learnasp.com?
-
I am tired of being marketed to...............
I saw where someone posted a mention of the MS article “A Guide to Building Enterprise Applications on the .NET Framework.” This article is horrible. It provides no value what so ever to developers. I, as a developer and someone that builds applications that have large numbers of users and millions of transactions each day, sees ZERO value in this article. It tells me nothing of value. It has no code within it. It is nothing more than marketing drivel. This article is not a guide to building enterprise applications but a sales pitch on using their technologies. There is no code. No specific situations addressed. No performance implications of doing anything. Basically, there is nothing that provides value to me as a developer. Halfway through the article, I felt like the child that had been given a lump of coal for Christmas as a joke.
-
Know where the bottlenecks are........
Do some analysis of your application before diving in head first and say “I can fix this.” Do you really need to modify your sql indexes when the problem is that you are starting up over 300 COM+ objects for one request?
-
For the database challenged amongst us.........
Do not pull all the records back from a table or view and then do an ADO Filter operation. This is typically a bad thing, causes too much network traffic, and is a general inefficient use of resources. Lets not say “select * from table.” Let's do at least a “select * from table where ........” You could also do a “select col1, col2, col3, ... from table where ......” which would be even better. Don't send too much info across the wire. Don't use too many resources. If you have some database experts in your development group, look into using stored procedures. Oh the pain......Oh the agony.....