Architecture
I saw this great article over at codeproject: http://www.codeproject.com/gen/design/theWrongObject.asp. Here is one part I found to be particularly on point: "Now, the diagram above is a bit
silly, but I think it's also illustrative of the evolution in both
hardware and software architectures. The last column, "Aspect
Computing", is something I have totally invented, but it seems to me
that as distributed services develop and components/component
communication is standardized, a significant amount of "programming"
will simply be gluing together disparate components, handling events,
and coordinating the flow of data between them." I totally agree with this and I would say we are almost there. With mashups becoming ever more popular...
I was surfing around today looking for information on .NET vs J2EE performance when I came across this site:http://msdn2.microsoft.com/en-us/netframework/bb499684.aspxSummary from that site:"This application is an end-to-end sample application for .NET
Enterprise Application Server technologies. It is a service-oriented
application based on Windows Communication Foundation (.NET 3.0) and
ASP.NET, and illustrates many of the .NET enterprise development
technologies for building highly scalable, rich "enterprise-connected"
applications. It is designed as a benchmark kit to illustrate
alternative technologies within .NET and their relative performance.The application offers full interoperability with J2EE and IBM WebSphere's Trade 6.1
sample application. As such, the application offers an excellent
opportunity for developers to learn about .NET...
As many of my colleagues know, I am not a really big fan of XML. I think it's bloated. I think it's not needed. I don't think it accomplishes much if anything that couldn't be done before just by sending text delimited in a different way. I'm not sure why if I want to tell someone a yes or a no answer on something being found, I have to wrap it in 1000 characters of SOAP data when i could just send a 0 a 1 or nothing and accomplish the same thing. Or why if I want a list...
Recently, I was looking for some articles on treatment of nulls in databases. This was a surfing thread that actually originated as my attempt to find some already done benchmarks on coalesce(col,'') != '' vs. col is not null for performance purposes. I had already found some positive match ideas for finding things that weren't null. In fact, I don't remember the original context for this particular search anymore, but I know that's what I was looking for. In any case, that led me to this answers page:
http://www.answers.com/topic/null-sql
This enlightened me on some issues I wasn’t aware of. For instance, my...
I'm a big fan of Fabian Pascal. Here are 10 Articles/Pages/Responses that I like the best. =P You can find tons more from these though. They are almost all pure gold. =)
On Grinding Water: Reply to St. Laurent
NO THEORY, NO RELATIONAL, NO THINKING
On Incompetence
ON CALLING A SPADE A SPADE: REPLY TO CALLAHAN
The Data Exchange Tail - Part 1
ON TRADE MEDIA'S "BALANCE": ANOTHER ONE BITES THE DUST
If You Liked SQL,You'll Love XQUERY
Something “Old,” Something “New,” Neither True
An Old Class of Errors
The XML Bug+ 1 Truth, Fads and Principles: What's Wrong with the Database Industry?
since i've had it in mind to write this for *so* long, i will at least write something, and maybe someday i'll come back and clean it up. =P
i was talking to a friend of mine quite some time back about what i call the 'triangle theory' of resource management at most companies. the idea is that most companies distributed resources in a triangular fashion. the top (narrow) part of the triangle is where the smallest amount of resources go. the top part also is where the most skilled people reside and is represented by the small area taken up...
Ah. Garbage Collection... how I love and hate thee. =P
I think one sad thing about programming in .net is that it seems many developers don't know or care anything about garbage collection and memory management. You used to *have* to know about it in order to write bug free code. I suppose it is a two edge sword in that developers can develop faster as the intention was to relieve developers of the need to know or care anything about memory management. I personally have always tried to follow best practices for implementation and have tried to stay somewhat cautious...
ha! i got ya! you thought this was a sql post, but it's not =P jeff atwood of codinghorror.com fame has a great article posted about his favorite top 10 lists. the top 6 ones to be exact.here is the brief version with a link to each of them.
Jerry Weinberg: The 10 Commandments of Egoless ProgrammingDare Obasanjo: Top 10 Signs Your Software Project is Doomed
Omar Shahine: Top 10 Tips for Working at Microsoft (or Anywhere Else)
Michael McDonough: The Top 10 Things They Never Taught Me in Design School
Andres Taylor: Top 10 Things Ten Years of Professional Software Development Has Taught...
Dave sent me the following link to examine. http://msdn2.microsoft.com/en-us/library/aa479086.aspx
Take a moment to peruse it and see what you think. We currently use this in
some apps and I’ve seen this strategy in place in the past as well. In general,
I personally haven't seen a place where it's *really* needed. The mixture of
all of the data together could normally be solved by the much simpler solution
of copying the data structure for each party. If you have common tables, some
simple tell could be done or a shared database could be setup. I think it
*seems* simpler because you can program common items for each...
reposted from herefor quite a few years now, i've had this idea of a virtual cpu. it all started back in... oh i guess 98 or 99 and my fascination with the beowolf architecture. i convinced a friend of mine to help me persuade the company we worked for to give us like 20 of the old computers. the intention was to setup 2 beowolf clusters and then to... i dunno make them do something. this is really before i was into development, but i loved scripting and batch files and using linux to do something like this seemed pretty...
Full Architecture Archive