Year: 2006

Categories
Development Personal Web

Blogs and careers

Wow, blogs can help your career. I never knew. 😉 We’ll I did. And I guess most people that follows blogging a bit knows. Especially within the high tech industry where the web/google/blogs are used as a main information source. I google for information that is pretty technical each day, and I probably find around 40% or something of what I need on blogs.

I do this mainly out of interest, a small bit of fun (hey, I can’t deny it’s gratifying to see the stats go up) and a small bit of self promotion. Sometimes I blog a lot, and sometimes less. What I would really like to do is turn it towards a lot more content than just linking. That is my goal, but time rarely permits.

Rands is an excellent example of a good blogger. He really is one of my favourite bloggers in tech. Of course he blogs mostly management, but related to the software industry.

Maybe adding a bit of attitude to my blog would make it better? Nah, don’t have it in me. Maybe after a couple of beers like Matt suggests. 😉

Categories
Development

JSR-170 explained

I stumbled upon Apache Jackrabbit tonight. I had heard about JSR-170, and could see some benefits, but this article got me thinking.

As I see it a fairly large corporation has a lot of content. By content I mean a lot of unstructured data as text. This might be stuff like:

  • Regulations
  • Information
  • Procedures
  • User handbooks
  • Tutorials
  • Screen instructions

And the list could go on. Some of this fit nicely together and would probably require the same view and editing systems, while others would require something entirely different. Important gains you get from this is:

  • All content in one place eases data maintenance like cleaning and integrity checks
  • All systems get the common and often required features for this type of information
  • Content can be viewed/edited by several front-end applications without duplication and difficult integration
  • Highly specialised views/editors for the given context are much easier to build

Separating concerns into a repository and “the rest” really makes sense for an large enterprise. When this standard gets wider adoption one can choose the best frontend for different target audiences but still have information centralised and easily accessible.

Categories
Development

NetBeans platform development

This is probably old news, but check out this demo on how to build applications for the NetBeans platform. Seems pretty painless. I’ll have to search for a demo of the Eclipse RCP too.