Web archives and the IT-business has always been a fun combination. Some sites with great expectations crash and burn fast – while other underdogs seem to make it quite well. Predictions and initial expectations seems to be just as bad no matter if it’s hardware, software or devices… Take these iPod comments from the initial launch as a great example, that you really shouldn’t try too hard to predict that future of IT too stubbornly.
Why is it that lawyers and project managers keep information to themselves until the very last minute, and the present the non-negotiable deadline to developers when the point of ”reasonable notice” is long past? – Today marked yet another occasion. … and even more strange – why is it, that we developers do magic every time and actually make the impossible happen? – I’m seriously questioning if that’s a bright strategy, if we ever want to get something in due time – and not burn the midnight oil while the project managers a sleeping.
I usually edit more code others made, than I create new files, and while most of the code is in PHP, there’s a huge difference in the coding style applied by different developers, and some styles are much more annoying than others. I do respect that people are different and that is probably more efficient to allow for some degree of personal style than to try to enforce a single common style. If possible try to make standards where all can agree upon them, and where it isn’t possible, don’t force it too hard (on less pressing issues makes it necessary).
I was browsing across some pages at Telia Mobile – one of the largest mobile providers in Denmark (and Scandinavia) and frankly, their webshop leaves something to be desired in terms o user-friendly behaviour. I can to some extend accept to be rejected if there are reasonable reasons behind it, but this rejection – that’s just too much and too amaturish in 2005:
First the Internet Explorer doesn’t ship with OSX any more – Safari does and shouold be supported, if you intend to support Mac-users.
There are actually two ways to wipe a mysql table either using delete or using truncate – which is better and why? So far my most commonly used form to wipe a table has simple been by using:
DELETE FROM tablename;TRUNCATE tablename;Besides the fact that it seems to be faster (even on small tables with few rows) – which in itself is a reason to favour this method - it also has another nice feature, which may be desirable. It resets the AUTO_INCREMENT field if it exists, and let the counter start over from 1.