Sony Breaks Ground With New PDA

– Just reading about the new PDA from Sony called the PEG-UX50 . The PEG-UX50 is the latest beautiful PDA from Sony running Palm’s OS (v5) with built-in support for 802.11b WiFi and Bluetooth. This PDA also includes a 0.3 megapixel digital camera that supports up to VGA (640×480) resolution. You can also record and play back video (MPEG4, 30 fps, 160×112).

The new screen design features a high-resolution 480×320 display. The screen also lifts to expose the keyboard, or swivels to hide the keyboard and use as a touch screen. Pretty neat design that’s unique to the Clie line. Wired News also has a pretty neat review/article titled Sony Breaks Ground With New PDA

This new PDA is priced at $700.00 which is pretty much in line with the standard WiFi PDA’s from Toshiba and Compaq/HP. $700.00 is pretty pricey for a PDA as I just read this article on The Register about a $799.00 tablet PC. I also remember when Lindows first announced their $799.00 laptop. Pretty bizarre. PDA and laptops are really the same price. Laptops has a much better form-factor and aren’t as ‘input disabled’ as typical PDA’s. What’s a geek to do? 🙂

Is there any bloody value in coding standards? –

Just caught this blog at the Software Craftsmen – Is there any bloody value in coding standards? And I have to answer with a resounding ‘maybe’ 🙂

But really, I think there is a lot of value in coding standards but turning them into religious wars isn’t right. I have to agree Oliver’s comment in the blog about working on large projects with many developers. I’ve created the coding standards at my company and they can be summed up in 2 pages. Most of the document revolves around best practices in things like use interfaces, make sure all value objects (DTO’s) are Serializable, etc. In fact, the document is called ‘Developer Standards and Practices’.

And since IDEA is our standard, developers can check out code and have it look the way they like it and format it to the corporate standard when they check it back in. Everyone’s happy 🙂

In reading the comments on the blog, it was great to see how people are using Checkstyle and Jalopy to get around the problem of standards and just reformatting the code to meet the corporate standard. Must investigate them more to see if they can add value without causing the typical headaches that most people face when talking about coding standard. In fact, the old adage that says ‘Never talk about politics or religion at the dinner table’ should be changed to ‘Never talk about politics, religion or coding standards at the dinner table’ 🙂

Software Craftsmen

Found these great articles on Mike Hogan’s blog while surfing TSS. Hosted under the site are 2 great articles titled Maintainability Pattern: Manage Dependencies and Maintainability Pattern: Write less code.

Apparently, Mike has been working on the same 50,000 lines of code for the last 2 years and obviously had some great exposure to maintenance issues. These articles linked above provide techniques people should employ to make code more maintainable. These articles talk about simple things that all developers *should* know. Great stuff Mike. Please keep it coming and thanks 🙂

My Amazon.com habit :)

Just got back from my trip to Boston to find a few pretty Amazon.com boxes waiting at the door. woohoo

My Amazon habit, as my wife calls it has me buying about 10-15 books a month. 🙂 The latest packages include a few new books including Java Persistence for Relational Databases by Richard Sperko, Java Data Objects by David Jordan, Craig Russell, Tomcat: The Definitive Guide by Jason Brittain, Ian F. Darwin and Head First Java by Bert Bates and Kathy Sierra. I am really looking forward to reading Java Persistence for Relational Databases as Rick is friend and a brilliant guy. This is bound to be a great book and I can’t wait to post the glowing review.

Another book I am really interesting in reading is Head First Java. I was intrigued by the description of the book when I first saw the press release. I am always looking for new and innovative ideas in teaching Java and this book looks great. I better post this and start reading — Lots of books to read 🙂 Cheers

BEA Releases XMLBeans to open source

Just back from vacation and catching up with my daily dose of TSS when I see this headline – BEA Releases XMLBeans to open source. I was just blogging about this topic earlier this month. This is great news and I hope the Apache group will accept XMLBeans as an Apache project and allow us to get to a really nice, rich, robust and now open XML – Java binding framework.

I’ve used XMLBeans that’s ships with the 8.1 release of WebLogic workshop and I just love the idea of getting away from writing XML plumbing code. It’s great to see another standards complaint tool out there that will simplify XML – Java binding and the schema validation is just the icing on the cake. Kudos to BEA and the XMLBeans team for making this happen.

Who says programmers don’t have a sense of humor :)

In my daily browsing of my ‘must-read’ blogs, I ran into this entry from Cedric’s blog. Cedric is another Uber WebLogic geek and the creator of EJBGen, an EJB code generator) The entry titled,
‘import *’ considered bad for your breath talks about limiting the usage of lines like ‘import java.util.*’. And I couldn’t agree with that more. In fact, that is another reason why I love IDEA. IDEA has configurable options on how imports and handled and in most cases will have the explicit import to that class you are using. Cedric is proposing the creation a group called ‘Society for Limiting Asterisks in Programming (SLAP)’. Cameron Purdy (Mr. Fluster Cluked – I still have the t-shirt from eWorld) proposed another group on TSS and I love Cedric’s idea of the merging of the groups 🙂 You’ll have to read the blog to see more 🙂

Software Craftsmanship: The New Imperative

A friend of mine just picked up a copy of the Pete McBreen book, Software Craftsmanship: The New Imperative and he was pretty impressed with it so far. The book presents an alternative approach to software development. I guess the premise is that organizations should spend more time on building people vs. getting certifications. Ok. How can you argue with that? Tim also tells me about a line in the book that says that good developers should make $150,000.00 to $200,000.00. Ok. I’m sold. 🙂

I’m a big fan of the The Pragmatic Programmer and wonder how this book will stack up. It was interesting to see Dave Thomas has written the foreword for this book.

I just ordered by copy from Amazon.com and want to check it out. Anyone out there have an opinion on this book?? Leave me a comment if you have any comments. Thanks.