Steve's Seaside Life Blog
Back in 2001, I was given the opportunity to create my own team. It was a great opportunity and I pulled a team of about 30 people together to work on Architecture and Systems Integration projects in the Infrastructure arena. We hit upon a slight problem though we could not find any space within the existing company buildings in the area. This presented us with another great opportunity, work from home, or find and design our own office. This is the story of how we designed our Office and what we learned.
- At the time, (and still today), my company designs its offices by giving a guy with Visio a template desk and char and an outline of the office and asking him to cram as many desks in as he can. We actually have a few show case offices where they go to the other extreme, but we had no where near that budget.
- Starting with a very small budget and a very traditional culture we set about our search and found a large empty space not far from one of existing buildings.
- We spent our budget with great care. For example …
Having been a loyal user of Radio Userland, with all of its quirks, for 6 months I have finally made the switch over to blogmedia who host the blogware platform. I did a trial switch over to typepad a month or so ago, but it did not go too well and I decided to stick with Radio. But yesterday I ran out of disk space on the Radio Userland server and it went like this …
- So without any notice in my event log, I see that uploads are failing because I have used up my 40MB allocation. 40MB seemed a huge amount for text blog entries, but apparently radio has lots of different renderings and archives it maintains.
- I thought this should be easy – tidy up – but this has proven almost impossible to do cost effectively
- So I thought I will get more disk space, but it’s incredibly expensive. For the same price as I pay for 80MB of space on Radio I can get 1 GB on blogmedia.
I really was not keen to change, because of the effort involved but I was so annoyed last night with trying to free …
Just recently I have been reading about luck and whether there is such a thing a lucky person. It’s a big subject, but two ideas stuck with me:
- People interact with so many people and things in so many different way these days that statistically “miracles” happen. If you define miracles as events that have less than a 1 in a million chance of occurring then I read somewhere that most people will hear of one about once a month. That means that people are going to come across someone being very lucky/unlucky , (perhaps 1 in 10,000 chance events), pretty much every day just based on chance.
- The second idea is much more interesting. It seems that people who describe themselves as lucky seem to know more people than those that describe themselves as unlucky. Not surprisingly the more people you know the better the chance that one of those people will be able to help you out in some way, or will know someone who knows someone ….This networking theory although obvious once it’s explained is pretty powerful.
It seems that in an analysis of the expressions on Olympic medal winners faces on the podium the happiest people won gold, then bronze then silver. It seems that the people who won bronze were thinking “I nearly didn’t get a medal at all”, whereas the silver winners were thinking “if only I had tried that bit harder I would have got gold”. I then got to thinking about how I think in these terms and it goes something like this:
- I always think about the worst that could happen. I think through the worst scenario but while I am doing so I look for something good that could come out of it.
- I don’t dwell on this worst scenario though, I am quite a positive person so I quickly accept it as a possibility, and then assure myself that its fairly unlikely and move on.
- If it’s a repeat of some event that happened in the past I try and remember something good about that event as well.
- Any outcome from that point onwards is then better than the worst scenario that I have already accepted as a possibility, but then set aside and not …
Our local library celebrated its centenary today, there was a fete and a fancy dress competition, my wife loves making costumes and the girls all love dressing up so it’s no surprise that they all entered. Stephie as Catherine Linton, Jenny as Heidi, Tessa as Mary Poppins and Anna as...
In this article, webservicespipeline.com discusses the rate of adoption of .NET compared to J2EE. Its conclusions are quite suprising. It seems that the rate of .NET adoption continues to grow at quite a rate, and puts usage on a par or slightly greater than J2EE. It puts .NET success mainly down to increaded developer productivity and ease of deployment and management.
This is signifiacnt for three main reasons:
- In the hard nosed business of IT software development, even with all of Microsoft’s woes, when it comes down to making business decisions, many IT companies still seem to make decisions based on rational criteria, and long term strategy and architectural elegance or portability don’t win out in many cases.
- There is likely to be a lot of new software developed for the Windows platform
- Mono is going to be a pretty important Open Source project
I have been quite happy with my two monitor setup at home, but using maxivista I am now able to drive three monitors from my main desktop PC. This is just great. I can now have my email in one, my RSS feeds in another, be using Office in another...
This is one of the areas I am going to be looking at so its good news that there has been a recent flurry of activity around it. here are some of the more important links. The debate was started by the EC report into this topic which is summarised...
I just read this post by Greg that describes the impact RSS has had on his productivity, it’s as if I wrote it myself so for once I will repeat it here in full!
My RSS reader saves me about 300 hours a week
The one about how using RSS opens up information to me in a way that is so reliable I could only do it this way manually if there were two of me…
Okay, so maybe it’s a little exaggerated. But seriously, I read an incredible amount of information these days. So much more than I ever did, and a lot of it on the Internet. Not only that, but I get the information I need (or want) so fast now that I can practically always act faster than most people when news breaks. Research that used to take hours and hours of searching and browsing now takes just minutes. I’m consuming much, much more information and doing so in much, much less time. What I can accomplish today in the information gathering department would have taken two of me just a year or so ago, before I found the real beauty of RSS.
I use RSS feeds …
I have recently been doing some research into Open Source, its an interesting subject from so many perspectives. That’s not what this article is about but if you want to follow up on it I recommend The Success of Open Source. Anyway reading this book prompted me to think a bit more about daily builds. Yes I know I already posted on this topic a few days ago but I can’t resist linking it with the Linux philosophy which can be summarised as:
“get it working then make it better”
Now this really appeals to me for a few reasons:
- I am a pretty poor programmer, a reasonable designer and a pretty good architect, (hopefully :-)). So I incline to grand concepts, but I can never get them to work in code unless I start really simply. In fact in most cases I start with someone elses code first and hack it around until I have proved the basic concepts.
- My real background is in systems integration so I never expect anything to work as documented. In fact when I started programming with VB 2, I fell found of a whole …
