Skip to main content

Fight, Never Surrender or Fight Never, Surrender

Years ago, a teacher told our class how Caesar could have lost a battle because of the placement of a comma. (of course, they neglected to tell us it would have been in Latin which means the point would have been lost but that's up to teachers and badly educating people) - but the point was never lost on me.

I'm a stickler for good punctuation (errors in blog posts aside, of course ) but I saw this story on RocketBoom and wanted to follow it up. Burt Rosen would likely find the humour in this, since I was beating him up on some comma issues in some user docs recently.

The statement?
The agreement “shall continue in force for a period of five years from the date it is made, and thereafter for successive five year terms, unless and until terminated by one year prior notice in writing by either party.”

I read this - and I agree with the CRTC - I can cancel this agreement with written notice by one year. But Rogers wanted to ensure they couldn't cancel in the first five years.

Poor Rogers - this little gaffe will cost them over 2 million dollars. A few years ago, that would only be 1.5 million US - nowadays, it's getting pretty close to the same amount in US as it is in Canada.

globeandmail.com : Comma quirk irks Rogers

Comments

Anonymous said…
You may have read it, but there's a brilliant book called Eats, Shoots & Leave by Lynne Truss (ISBN 1861976771) all about punctuation.

Stewart

Popular posts from this blog

Blogs and RSS come to Microsoft.com

MS has just introduced their portal and it's pretty comprehensive. Nothing quite like learning that some people use AIM instead of MSN messenger, or that there really may be a need for supporting 4 monitors ( Cyrus Complains ) However, it's really a great sign that MS is serious about supporting the blogging community which seems to have um, exploded in size in the past year. Blogs and RSS come to Microsoft.com

Elevating Project Specifications with Three Insightful ChatGPT Prompts

For developers and testers, ChatGPT, the freely accessible tool from OpenAI, is game-changing. If you want to learn a new programming language, ask for samples or have it convert your existing code. This can be done in Visual Studio Code (using GitHub CoPilot) or directly in the ChatGPT app or web site.  If you’re a tester, ChatGPT can write a test spec or actual test code (if you use Jest or Cypress) based on existing code, copied and pasted into the input area. But ChatGPT can be of huge value for analysts (whether system or business) who need to validate their needs. There’s often a disconnect between developers and analysts. Analysts complain that developers don’t build what they asked for or ask too many questions. Developers complain that analysts haven’t thought of obvious things. In these situations, ChatGPT can be a great intermediary. At its worst, it forces you to think about and then discount obvious issues. At best, it clarifies the needs into documented requirements. ...

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction...