Your web-browser is very outdated, and as such, this website may not display properly. Please consider upgrading to a modern, faster and more secure browser. Click here to do so.
I’ve fallen in love with Google Chrome in most ways. Not that Chrome’s anything extra, it’s rather that it’s not.
Everything is slimmed down, it’s super fast and it feels like it got less than half of both the competitors GUI (in a good sense) and their settings.
One of the best things about Chrome is the sense of versions. Background: I grew up with IE6, which still harasses my workplace’s usage statistics, the same app that MS doesn’t bother getting rid of (maybe they do, but as far as I know, they’ve yet to implement the subtle updating process of Chrome in IE 9).
Except being a wonder for us developers, the hidden update is good because:
When working with retailers, one must walk a thin line in order to keep the retailers interested by teasing them and promoting your services, while at the same time retailers must be given the time and information to seduce their clients in turn.
Are your retailers clients or co-workers?
I’m trying to follow the development of an open source CMS called Pimcore but having a hard time following its development process, the same thing goes for my favorite PHP framework, ZF.
Read my lips: provide statements in one medium, reflect it elsewhere
These are all sources for news:
and not least, in official sources quickly multiplies the difficulty of focusing in the right spot. The same thing goes for official sources concerning a submodule/sister of the main project.
Everybody knows how to backup but the important thing is to know how to restore from that backup.
I’m thinking this POV often is missing when discussing documentation of software. The Wikipedia article on Software Documentation is focusing a lot on pigeonholing the different type of documentation that may exist so that no type is left out. That’s sometimes what I feel myself when trying to document a process - have I really made sure that this way of documenting is #1 or should I just go over the alternatives again?
Hold your horses. From now on, every inch taken towards documenting something must be questioned.
Make documentation as automated as possible. Invalid documentation is worse than spaghetti code because you believe you got everything under control and then… there’s a deadline and you’re toast.