Learning CSS

Why should I care about CSS? If your a developer and have ever struggled with web-page development tools, for example Netscape composer, or frontpage, cascading style sheets are a very simple solution. Build simple web-pages first and then style them like a professional would through code re-use. You won’t need to purchase Dreamweaver or other expensive tools to get that professional touch. The references below will definitely help.

This blogs theme benefits greatly from CSS, which allows the seperation of style, structure and content.

Why do I recommend it? The specification is very simple to understand. Even simpler if your already programming in Java or some other programming language (like Ruby and PHP). If your working with HTML and Javascript then CSS is all the more important. Besides, I just wish someone would have introduced it to me earlier. I was inspired by Amit Singh (IBM and kernelthread.com fame).

Have a look at the resources below and before long you will begin customizing your web-design to suit your own style.

What are the caveats? CSS won’t work predictably on all browsers always when it comes to certain features. But if you understand the language and its mechanics you will be able to figure out why certain browsers break and when. It is also possible that you may find yourself getting bored with designing CSS layouts, in which case I recommend web-design as a break between your kernel hacking.

Without further ado, the resources:

• CSS Zen Garden. – a demonstration of what can be accomplished with CSS-based web-design.
• CSS reference on w3schools – handy reference of everything that can be accomplished in CSS, with examples.
• Eric Meyer on CSS. – fantastic book on hacking CSS for after you have picked up the basics.
• The CSS Box model will help you understand the CSS specification.
• CSS online resources on w3.org.
• OSWD.org – open source web-design.

Building Great Software: Solve For The 80/20 Case

Original Article: Building Great Software: Solve For The 80/20 Case.

I found the link on Jeff Barr’s blog.

It is always good to remind yourself who your building software for.

It’s also easy to compensate for user interface problems, to the point that you stop thinking about what you are doing to compensate. I watched this happen in real time this week when an executive I know and highly respect was giving a demo of a software package. In the middle of the demo, he alt-tabbed (in Windows) to another window to bring it to the forefront. He knew to do this without thinking… but the new user wouldn’t. When I called him on it, he said, without thinking, “Oh… I just knew to do that.” Then he thought about it for a second and turned to one of the company’s senior engineers and said, “Hey, we should fix that!”