Tag Archives: microsoft

Links

WSJ.com – Mac’s Moment?

It’s nice to see an article about Apple that’s not about the iPod! This time a reasonably sized Japanese company has switched most of it’s 2300 PCs over to Mac’s.

It’s a sensible move if you ask me! Given the ease of use, lack of virus and availability of MS Office I’ve never quite understood why Mac’s are not in wider use. I guess we need more conversions like this to reassure people that it’s not a foolish move.

The annoucement of a beta version of software to allow Windows XP to run on new Intel Macs, isn’t going to hurt either.

Links

How to avoid open source licensing pitfalls

I came across this article in the dead-tree edition of Computer Weekly: it discusses how to avoid open source licensing pitfalls. It’s an interesting but flawed piece.

What did he get right? I think it’s fair to say that people should assess the risks of installing free software. Free software is still new to a lot of people making the details of these risk somewhat unknown. He’s right to say that many people do not understand what obligations using some of the various free software licences put them under. I work for a very technically-focused company yet even we have had some internal problems with this.

Given that this is the crux of the whole article, what is my objection?

Well, how is this any different to proprietary software? Are the T&C’s on commercial software really less onerous than free software? Are they any better known? Let’s put that another way: did you read the EULA that came with your copy of Microsoft Windows? I thought not.

He makes a big thing of liability (“The risk of third-party intellectual property rights infringement … is a noteworthy concern”), giving a big red flag to open source software. While he concedes that “such risk is not confined to open source,” he then loses credibility by saying that the risk “is often perceived to be greater [in free software].” I’m not interested in the perception, as an expert in the subject I expect him to tell me the facts.

But is that right? Did Microsoft not make a big noise about them protecting you against violating patents while using their software?

They did, but then I came across this other article on ZDNet which talks about a patent ruling forcing Office upgrades. Yes, you read that right. Because Microsoft violated a patent, you may have to suffer the time and expense of upgrading all your installations of Office in order to be protected from legal action by Carlos Armando Amada, the guy who holds the patent.

So you may not get sued but you do have to pay for Microsoft’s mistake. The risks of using free software are different to those of using commercial software but it’s difficult to say that they’re lower. You need to be aware of the risks in both cases.

Note: Where I use the term Free Software here I mean the GNU definition (i.e., freedom) rather than “no cost.”

Opinion

Nostalgia

I though I’d start the new year with an unusual, for me at least, positive message. The message: we’ve never had it so good technology-wise and often we forget that.

I started thinking about this when I realised what I was doing with my computer. Right now, for example, I am typing this into Emacs. In the back-ground I am scanning in some film and burning the previous scans onto CD. Only a few years ago any one of these activities would have been more than enough for a simple home computer. A joke at the time was that Emacs stood for “eight megabytes and continually swapping,” and now my iPod has thirty-two megs of memory as a convenience, basically to avoid letting the battery run down too quickly.

Even better, for the sake of clarity I’ve missed out the programs that I’m not actively using. Mail and Adium are happily keeping a look-out for new messages, iTunes is bashing out some good music. iCal is ready to tell me that I was supposed to be meeting a friend an hour ago, I left the Address Book open last time I looked up a phone number, I can’t even remember what I was editing in Word but that’s open too and Safari is primed, just in case.

But even that is a simplification. The disc image that’s being burned is on a different computer, they’re connected wirelessly and using a protocol that’s native to neither (Mac to Linux using SMB).

I don’t mention any of this to brag, or suggest that I’m doing anything odd or unusual here, quite the contrary. I just mean to point out that these are complex but every day activities that we expect not only to work, but to work seamlessly at the same time as lots of other stuff. And that, frankly, is absolutely amazing.

Opinion

Joel On Software

Let’s cut to the chase: if you’ve read and enjoyed any of Joel Spolsky’s ramblings on the web you’ll like this book. Skip the rest of this review and just go buy it.

For the benefit of those that have not heard of him, who is this Joel chap and what is the book and his normal prose about? The “About the Author” section describes him as an industry veteran that writes an “anti-Dilbert manifesto” on his website. I can’t think of a better description, which is why I have shamelessly copied it rather than finding my own phrase…

He writes about software development at every level from bashing out code right through to strategy and he applies the same degree of pragmatism, common-sense and humour to every subject he covers.

The book is split into four sections and an appendix. In the first he talks about “the practise of programming,” which is the low level stuff. He starts with choosing a programming language (or, at least, why it’s probably not as important as you might think), moves on to the now almost classic “Joel Test” (Google it if you’re in any doubt how influential it has become), moves onto functional specs, schedules and the like.

Section two is all about managing developers. Personally, I think this is the part that he really excels at. Indeed, the best bits of the other sections are actually about the higher level stuff. One of the highlights is about what he calls “leaky abstractions,” basically that clever things that try to hide their underlying details tend to fall down in unpredictable ways. Ever got confused about the way a string class works in C++? This is the chapter for you!

The penultimate section is a random collection of articles, including his thoughts on the 80/20 myth, various business models and open source. I particularly like the piece on getting things done when you have no authority to do anything officially. Most books assume that you just need to learn what the right thing to do is, so it’s refreshing to find a book that deals in Real Life!

The final section is less relevant to someone like myself with a Unix background (and interest). There are three pieces on Microsoft’s .NET architecture. Nevertheless, I did read them and thought that he had some interesting things to say.

There is also an appendix, which is a “best of” collection of questions from the “Ask Joel” section on his website. This is perhaps the weakest section in the book and, although entertaining, most of the good advice in this section has already been expressed more clearly in earlier sections.

You can probably see by that I was impressed. It was an easy book to read — something that a lot of technical writers forget about — and even when I disagreed with certain things I could at least see where he was coming from.

The facts

Author: Joel Spolsky

Cost: $24.99

ISBN: 1-59059-389-8.

Buy from Amazon.co.uk.

Opinion

Coder to Developer

The concept

I liked the blurb on the back:

“This title addresses all of the skills required to effectively design and develop complex applications, including planning, building and developing the application and coding defensively to prevent bugs.”

It suggests that it can bring you from the stage where you focus entirely on the code to the point where you can take in a whole project, make it all work and delight your customers. Mike Gunderloy has 25 years of commercial experience and so has a lot to say.

As he points out in the early chapters, there is a lot of ground to cover. There is everything from actually writing better code, through to planning, risk management, release management and handling your team. He covers all of these areas, providing handy hints and war stories clearly gleaned from hard-won experience.

For example, I liked the way that he sticks to the things that you need to know, even splitting them up into categoories where it makes sense. Gunderloy seems to be as amazed as I am about how m any projects do not use source control, and he lists Three Levels of Source Code Control Enlightenment, from Opening Your Eyes (just six commands and many benefits!), to SCC Journeyman (which he acknowledges may be all many people need), through to Experts Only (which he spends so little time on that it’s difficult to know what the various options he talks about are for).

Windows Coder to Windows Developer?

What you’ve seen so far is praise for the general concept of the book rather than anything very specific. There’s a reason for that. For a general software engineering book, it’s strange that there is such a strong Windows and .Net slant. There is no need for such details and it will reduce its longevity and usefulness. Steve McConnell’s “Code Complete” is ten years old and is still relevant (even though a new edition has just come out). In six months Coder To Developer could well look dated.

There is also a question-mark over the accuracy of some of the information. For example, he credits the the iterative development process to Microsoft and Rational, forgetting Bohem’s spiral model predated both by well over ten years. He seems to be much more fluent in more recent practises like Agile and XP, which is commendable but seemingly lacking the foundations makes it difficult to put these newer methodologies into perspective.

But if you can ignore these problems, there is lots of good advice. He’s pragmatic ? using the good bits of, say, XP without taking the process as gospel ? and the writing is accessible and friendly. Even disagreeing with some of the early chapters, I still persevered as it wasn’t a dense or difficult read.

The facts

Author: Mike Gunderloy

Cost: $29.99

ISBN: 0-7821-4327-X.

Buy from Amazon.co.uk.

Comedy Errors

Oracle Client Software Comedy Errors

Oracle Data Browser

Oracle Data Browser, part of the Discover 2000 suite, is one of the least amusing applications that Oracle supply. Not because it’s bad, but because it almost works…

  • Windows 95 has a ‘full screen drag’ feature (freely download-able from Microsoft‘s web site). If you load Data Browser you don’t. It suddenly stops working.
  • Now this is supposed to be a feature, but I’m not convinced. The word ‘Browser’ seems to indicate that it’s a read-only product. In fact a version comes with it that isn’t.

Oracle Data Query

Until we started really using SmartClient, we thought that Data Query, half of the Discoverer 2000 suite, was the lemon of the Oracle product library. That’s not to say that it’s good, just that after all that’s happened with Applications we’ve more or less forgotten a lot of the really annoying stuff. Lucky Oracle.

  • Data Query makes Windows 2.0 seem stable. Even in it’s 32-bit version.
  • It often magically moves the input focus to somewhere you don’t want.