Spam and slayings
Apr. 20th, 2010 11:28 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
stephbgAustralian Computer Society meetings can be more exciting than expected.
Tonight's topic was eNewsletters and for the life of me I couldn't imagine that there was enough to say about delivering institutionalised spam to fill an hour (including question time). Fortunately it was a story of business and product development full of schadenfreude moments about the joys of working with email protocols (or the lack thereof). What's the opposite of a protocol? Every-admin-for-themselves?
If I ever show signs of wanting to become a sysadmin, shoot me.
I learned Something Interesting about goings on in certain government grant programs, which explains a lot about a certain surprisingly intense audit a year or two ago. My employers/clients were afaik honest in their dealings, but there were some allegedly bent consultants about the place who caused all sorts of problems for SMEs. They are now "helping police with their enquiries" I believe, so I'd best stop at that. It's a very small town.
The presenter made a HILARIOUS* reference (joke, possibly?) to yesterday's prison/gangland slaying and related commercial opportunities. Clearly he didn't know who he was talking to. One really shouldn't make jokes at the expense of organised crime figures unless you know your audience really well. I resisted the urge to point this out.
I am in no way implying that the ACS could arrange for an unfortunate accident to befall this person or any other, but did he know that? Hmmmmm? Also, too soon. Ah, the many pitfalls of public speaking. Otherwise, good job.
OK, there's probably *something* in the Code of Ethics about not bumping off the opposition or dealing harshly with irritating stakeholders or conference presenters.
I like this bit of the Code:
4.6.6 I must advise my clients and employers when I believe a proposed project is not in their best interest.
...or as I like to put it: "People will never pay for that." With optional "No-one in charge of the money cares if it's an entirely new rendering/reporting/calculating/security engine/model/platform. It looks exactly the same as the last release. At least change the font and call it a productivity enhancement." I've said that many many times in my career on the bleeding edge of technology :-)
Perhaps my epitaph shall read:
She was incurably honest and very annoying, but frequently right.
:-P
(*) Quite.
Tonight's topic was eNewsletters and for the life of me I couldn't imagine that there was enough to say about delivering institutionalised spam to fill an hour (including question time). Fortunately it was a story of business and product development full of schadenfreude moments about the joys of working with email protocols (or the lack thereof). What's the opposite of a protocol? Every-admin-for-themselves?
If I ever show signs of wanting to become a sysadmin, shoot me.
I learned Something Interesting about goings on in certain government grant programs, which explains a lot about a certain surprisingly intense audit a year or two ago. My employers/clients were afaik honest in their dealings, but there were some allegedly bent consultants about the place who caused all sorts of problems for SMEs. They are now "helping police with their enquiries" I believe, so I'd best stop at that. It's a very small town.
The presenter made a HILARIOUS* reference (joke, possibly?) to yesterday's prison/gangland slaying and related commercial opportunities. Clearly he didn't know who he was talking to. One really shouldn't make jokes at the expense of organised crime figures unless you know your audience really well. I resisted the urge to point this out.
I am in no way implying that the ACS could arrange for an unfortunate accident to befall this person or any other, but did he know that? Hmmmmm? Also, too soon. Ah, the many pitfalls of public speaking. Otherwise, good job.
OK, there's probably *something* in the Code of Ethics about not bumping off the opposition or dealing harshly with irritating stakeholders or conference presenters.
I like this bit of the Code:
4.6.6 I must advise my clients and employers when I believe a proposed project is not in their best interest.
...or as I like to put it: "People will never pay for that." With optional "No-one in charge of the money cares if it's an entirely new rendering/reporting/calculating/security engine/model/platform. It looks exactly the same as the last release. At least change the font and call it a productivity enhancement." I've said that many many times in my career on the bleeding edge of technology :-)
Perhaps my epitaph shall read:
She was incurably honest and very annoying, but frequently right.
:-P
(*) Quite.
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
no subject
Date: 2010-04-20 11:34 pm (UTC)Gladly. It is not a fate I would wish upon anyone. And anyone who makes a career out of being a sysadmin is clearly psychotic, and a threat to society.
That would be a damned fine epitaph, and one I would be proud of.
no subject
Date: 2010-04-21 02:07 am (UTC)What is the point of no return? When do you pull the trigger and what can be done to prevent it?
no subject
Date: 2010-04-21 05:27 am (UTC)