Archive for Geek talk
Microsoft & Firefox joining forces?
Can it be true? Microsoft are opening their arms out to the Firefox/Thunderbird camp so they can work together with the development of the browser to run smoothly on Windows Vista?
http://arstechnica.com/journals/microsoft.ars/2006/8/21/5065
Well its good to see that Microsoft are taking an interest in the work on Firefox. About bleedin’ time!
Forever the synic, I have to wonder whether this is all just a ploy to make those anti-IE people see Microsoft in a better light. Rather than help the developers work on making Firefox run smoother, maybe they should concentrate on making their own browser more standards compliant!
@media podcasts
The wonderful guys at vivabit have got a number of podcasts from this years @media event up now.
http://www.vivabit.com/atmedia2006/blog/
Excellent stuff
Jack of all trades, master of none…
Back in the day, when I was a fresh graduate, applying for web related roles meant that you would fall into one of two distinctive camps. You were either a web designer, or web developer. A web designer role was simple…you knew how to use photoshop, you worked in flash (not necessarily actionscripting), you understood html, and knew how to use a package called dreamweaver. Developers would have to know Java, javascript, and either PHP, ASP or Coldfusion.
How times have changed. No longer are you able to fall in one of these two camps, because all these titles have emerged on recruitment sites:
- Web developer
- Back-end developer
- Front-end developer
- Ruby on rails developer
- Web designer/developer
- New media designer/graphic designer/developer
- Web master
- etc etc etc
It would seem that you need to be an uber geek these days to pass off as either a developer or designer. Read the rest of this entry »
CSS Caching Hack
I’ve been coming across a problem with one of the benefits of using CSS for layout…caching!
For those of you that may update their css files on a site that you frequently visit, you need to consider the fact that even though the html may change, the css file will remain the same on the client side (due to the caching).
Stefan Hayden has found a fix for this, which he wrote around April (I guess I was a bit slow on this issue), so HURRAH, looks like there is a solution to accessing different versions of css files without the need of renaming the files!

