|
More on Interop |
|
|
By JD Conley on
7/26/2006 9:00 PM
|
|
|
|
I'm sitting on a plane on my way back to Sacramento (a whopping 1 hour flight) and I thought I'd try to
give a little more information about the interop event. After two days of testing it appears as though, without any previous official testing, we're actually very close to having quite a few fully interoperable XMPP implementations.
|
 |
|
|
More...
|
|
|
|
|
Fun Installing Vista Beta 2 on AMD x64 |
|
|
By JD Conley on
6/2/2006 12:50 PM
|
|
|
|
As a self proclaimed geek and MSDN subscriber I feel as though it's my duty to explore all the new software that Microsoft comes out with. This last week I have been embarking on one such journey. Working with beta software is always a bit trying, but tack on a beta driver model and a "new" hardware platform (x64) and things get really interesting.
|
|
|
|
|
More...
|
|
|
.net 2.0 web service hair puller |
|
|
By JD Conley on
5/12/2006 3:02 PM
|
|
|
|
Every couple of weeks I spend four hours doing something that should take five minutes. It just happened, and now I feel compelled to take another few minutes and explain so it doesn't happen to you. Not only did I waste my time, but the time of another one of our developers. What might waste four hours, you say? We recently migrated our entire web site to .NET 2.0 and a new portal. Since we were building a new web site anyway we thought, "What the heck, let's re-factor the licensing subsystem. The database was hacked together over three years and we don't want no stinkin' .NET 1.1 code running on our shiny new site!" Well, this didn't turn out exactly as planned. The SoapBox licensing web service is quite simple. There's a single method called "Activate" that takes in a unique hash of some information on the user's computer (so we can track duplicate usages) and the serial number. It returns an XML document containing all the license inf ...
|
|
|
|
|
More...
|
|
|
from the trenches of my first software startup |
|
|
By JD Conley on
5/9/2006 2:53 PM
|
|
|
|
I was born and raised an entrepreneur (I'm pretty sure that's how you speel that). During my lifetime my dad never had a single "real job". He has always been a small business owner. From a carpet cleaning business, to a trucking company, to a coffee shop, he was always working on something he could call his own. Every time we get together we end up talking about businesses we'd like to start. If only I had the time. . . Somehow, after seeing him (and my mom) constantly working at least 80 hour weeks, stressed out, and exhausted, I still decided I wanted to start a company.
|
|
|
|
|
More...
|
|
|
FakeOutTheUserToThinkWeDontUseAnyMemory |
|
|
By JD Conley on
5/8/2006 3:28 PM
|
|
|
|
There comes a time in every project where the developers realize we are building software for the users, rather than for ourselves. A user's perception can be the difference between a good and a bad reference, and we all know how detrimental bad word of mouth can be. This unfortunate reality hit me square in the face recently when I was told by a customer that "your application is bloatware".
Any desktop application with a user interface, written in .NET, that does anything interesting, can easily be mistaken for bloatware. It's quite easy to create a super elegant application with no memory leaks that appears to use 50MB or more of memory. I say appears, because the figure everyone sees in Task Manager is the "Working Set" size. Users (myself included, up until recently) see large working set sizes as a sign of bloatware and poor programming.
This is simply not the case. The working set is more along the lines of the amount of physical memo ...
|
|
|
|
|
More...
|
|