TONY EASTLEY: The Federal Opposition says it won't be able to provide a fully costed broadband policy by the next election but its plan will be cheaper and completed sooner that the Government's National Broadband Network.
The Opposition's communications spokesman Malcolm Turnbull says information from a survey to be launched today will help a future Coalition government decide which areas to prioritise for faster broadband services.
NAOMI WOODLEY: How long will it take for the Coalition network to be rolled out? NBN Co's timeframe is around 10 years. Yours is sooner, can you say how sooner?
MALCOLM TURNBULL: Well it will be a lot sooner. But let me just first say that NBN Co says its target is 10 years. There are many people in the industry very close to the NBN who believe it is more likely to take 20 years.
The approach that we will take in most of the built-up areas of what's called fibre to the cabinet or fibre to the node, the experience around the world is that takes around a third of the time of fibre to the premises, sometimes even less.
Thirty Years in I.T. Theories, Ideas, Opinions.... Leveraging knowledge of the past to understand now. @SteveJCbr & stevej.cbr@gmail.com
2012/09/24
NBN: Coalition cannot cost its proposal
Malcolm Turnbull has finally addressed just what he meant by "sooner, cheaper" in an ABC radio interview and an article based on the interview. [Update: 7:30 Report Interview, Coalition B'band Survey]
2012/09/14
NBN: Coalition supports Free Markets not Monopolies
Mr Turnbull wrote a commentary on a speech by the Chairman of NBN Co, "Policy Choices in Project NBN".
Mr Turnbull engages in the usual political rhetoric, specious comments and gratuitous insult, summarised at the end, but does raise two points that need addressing:
Mr Turnbull engages in the usual political rhetoric, specious comments and gratuitous insult, summarised at the end, but does raise two points that need addressing:
- Monopolies, and
- Provision of new services during the transition from Telstra to NBN Co., "greenfield" installs.
- The key words here are “without making the subsidies explicit and transparent.”
- And therein lies a very big difference in philosophy.
- Not only do we prefer competition to government monopoly, but we believe that subsidies should be explicit and transparent.
- We are thoroughly committed to providing access to broadband to regional and remote Australia at city prices –
so there is no discrimination by reason of geography – - but the cost of doing so should be transparent.
- (precedent) What, after all, is the USO?
2012/09/12
NBN: Coalition support for Free Markets vs Monopolies
Mr Turnbull wrote a recent commentary on a speech by the Chairman of NBN Co, entitled "Policy Choices in Project NBN".
[Long. 2850 words total, 2000 words of mine]
I made this comment on his blog:
[Long. 2850 words total, 2000 words of mine]
I made this comment on his blog:
Malcolm,Here are my criticisms of his blogpost.
You keep on top of the debate and are continually moving it forward. Excellent work as both a Shadow Minister and prospective Minister.
I’m impressed with your criticisms of the NBN Co rollout. Informed and useful.
Here is not the place to nitpick the Coalition policy. You have one, have made promises that can be evaluated and have publicly committed to continuing a National Broadband Network.
Thanks for being so active in this debate and not allowing the incumbents to be complacent or go unchallenged. Well done.
regards
steve jenkin
2012/09/10
Future of Big Iron servers and Expensive Databases
This article came across a list, what follows was my response.
The eDRAM from IBM for the L3 cache is a big move. Like when they figured out how to use Copper in chips and reduced power use, hence heat production significantly.
I suspect we're seeing a replay of the late 1980's demise of mainframes... Not fast, not universal, not complete, but 90+% of the business goes away, killing weak supporting businesses.
Everyone but IBM's System Z and Unisys ClearPath went away - or into emulation.
[Clearpath = emulation on Xeon of 2200 & B-series]
In my view, two forces have converged to push these high-end niche processors into irrelevance:
If the whole of a relational DB (tables) fits in memory (or fast Virtual memory), then doesn't the DB become very simple, modulo ACID tests and writing "commits" to persistent, high-reliability storage?
Which means we might start seeing a bunch of in-memory DB's, like NoSQL, but for normal-sized DB's (1-5Gb), not large collections.
There's an economic rule on product substitution that led to the relatively quick decline in IBM mainframe sales:
Whilst Oracle licensing costs are beyond me (I don't track them) - but are becoming a major component of Enterprise Computing costs.
How many "little" DB applications need to succeed with two low-cost ($10k) servers, 3 SATA drives each in simple RAID and 1 Fusion-IO board, run as H/A with an in-memory DB?
If organisations can build a complete, high-performance, high-availability, simple-admin solution for $20-$30k per group of DB's, they can afford to deploy them immediately based on direct maintenance savings.
Follow-up comment:
I remember seeing John Mashey of MIPS talk in 1988 where he plotted CPU speed for each of ECL, bipolar and CMOS technologies. ECL had been overtaken by then, bipolar was due to lose the lead within a few years.
The 486 in 1991 was a complete system-on-a-chip and changed the landscape.
It answers the question "Where did all the supercomputers go?"
A: Inside Intel. [and Power and SPARC. possibly Z series]
The Intel chips seek "maximum performance" - they pull all the tricks that super-computer designs used, and its is that technology that is approaching Pattersons' "Brick Wall" [heat, memory, ILP]
And as an aside, GPU's are filling the "vector processor" niche of CDC and Cray.
ARM has pursued a very different strategy, more based around 'efficiency': MIPS/Watt
So, while I agree with you, I think the situation is nuanced.
ARM processors are obvious choices for low-power and mobile/battery devices.
Because of design simplicity (small PSU, no CPU-fan) and smaller size, they'll become more interesting for low-end PC's, especially portable devices.
There is a company, Calxeda, now producing high-density ARM boards for servers.
They are hoping to leverage MIPS/Watt for highly-parallelisable loads, like web-servers.
But I can't see anyone taking on Intel soon in the supercomputer-on-a-chip market.
It's not just servers, especially for large DB's, but workstations and 'performance' laptops.
The problem with that evolution of the market for Intel is ARM taking sales from multiple market segments. Seeing that Winders-8 will run on ARM, we might see the end of WinTel for low-end & mid-tier laptops.
As a company, can Intel survive such a radical change in demand for its major product line?
Will its work on MLC flash fill the financial void?
I've no idea how that will go.
But like you said, ARM is going to shake up even the Intel server market.
The "secret sauce" that the ARM architecture has is that it's a licensed design.
Although chip design companies might not own or be able to access chip FABs within 2 or 3 design cycles of Intel, they can produce highly optimised and use-case targeted chips.
Which Intel can't do. They are focussed on the bleeding edge of CPU performance and FAB design.
Manufacturers like Apple/A5 and Calxeda can produced ARM-based designs that can outperform Intel-based systems by an order-of-magnitude on non-MIPs metrics.
As Apple has shown, there are very big markets where raw MIPs isn't the "figure of merit" in designs.
IBM and Oracle Present Rival Chips for 'big Iron' ServersWonderful to see the Dinosaurs still dukeing it out.
The eDRAM from IBM for the L3 cache is a big move. Like when they figured out how to use Copper in chips and reduced power use, hence heat production significantly.
I suspect we're seeing a replay of the late 1980's demise of mainframes... Not fast, not universal, not complete, but 90+% of the business goes away, killing weak supporting businesses.
Everyone but IBM's System Z and Unisys ClearPath went away - or into emulation.
[Clearpath = emulation on Xeon of 2200 & B-series]
In my view, two forces have converged to push these high-end niche processors into irrelevance:
- Patterson's Brick Wall (2006):
- Power Wall + Memory Wall + ILP Wall = Brick Wall
- "infinite" IO/Sec and virtual-RAM with PCI-SSD. eg Fusion-IO
- Big Iron Databases
- Big Iron Storage Arrays and supporting SAN's
- Big Iron multi-chip fast uniprocessing cores.
If the whole of a relational DB (tables) fits in memory (or fast Virtual memory), then doesn't the DB become very simple, modulo ACID tests and writing "commits" to persistent, high-reliability storage?
Which means we might start seeing a bunch of in-memory DB's, like NoSQL, but for normal-sized DB's (1-5Gb), not large collections.
There's an economic rule on product substitution that led to the relatively quick decline in IBM mainframe sales:
- when the capital expenditure on a substitute is less than the operational costs of the current system, barriers to adoption are removed.
- capital costs are 'sunk' and can't be recovered.
- To realise savings, you have to wait for the next upgrade or refresh cycle.
- But the conversion costs have to be factored in, and incumbent vendors take care to price upgrades, even "forklift upgrades" (complete replacement) under the total cost of moving to a new solution. [Used to advantage by Tier 1 Storage Array vendors currently].
- But Operational Costs, like maintenance charges, aren't 'sunk'.
- They are due every year.
- When a whole system is less than recurrent costs, businesses can quickly and easily justify the change.
- They write-off the CapEx for the old equipment and wheel it out the door.
- Usually "Big Iron" hardware has zero residual value, even when 2 years old.
- When the equipment is on the cusp of being obsolescent, it is worse.
- Or they have to figure out how to break the lease.
- Unless they went into debt to fund the CapEx, they can move away quickly.
Whilst Oracle licensing costs are beyond me (I don't track them) - but are becoming a major component of Enterprise Computing costs.
How many "little" DB applications need to succeed with two low-cost ($10k) servers, 3 SATA drives each in simple RAID and 1 Fusion-IO board, run as H/A with an in-memory DB?
If organisations can build a complete, high-performance, high-availability, simple-admin solution for $20-$30k per group of DB's, they can afford to deploy them immediately based on direct maintenance savings.
Follow-up comment:
Intel are looking over their shoulder at becoming dinosaurs. Maybe I won't live to see it, but ARM servers could very well do in the x86_64.And so they should for most general purpose computing.
Ed
I remember seeing John Mashey of MIPS talk in 1988 where he plotted CPU speed for each of ECL, bipolar and CMOS technologies. ECL had been overtaken by then, bipolar was due to lose the lead within a few years.
The 486 in 1991 was a complete system-on-a-chip and changed the landscape.
It answers the question "Where did all the supercomputers go?"
A: Inside Intel. [and Power and SPARC. possibly Z series]
The Intel chips seek "maximum performance" - they pull all the tricks that super-computer designs used, and its is that technology that is approaching Pattersons' "Brick Wall" [heat, memory, ILP]
And as an aside, GPU's are filling the "vector processor" niche of CDC and Cray.
ARM has pursued a very different strategy, more based around 'efficiency': MIPS/Watt
So, while I agree with you, I think the situation is nuanced.
ARM processors are obvious choices for low-power and mobile/battery devices.
Because of design simplicity (small PSU, no CPU-fan) and smaller size, they'll become more interesting for low-end PC's, especially portable devices.
There is a company, Calxeda, now producing high-density ARM boards for servers.
They are hoping to leverage MIPS/Watt for highly-parallelisable loads, like web-servers.
But I can't see anyone taking on Intel soon in the supercomputer-on-a-chip market.
It's not just servers, especially for large DB's, but workstations and 'performance' laptops.
The problem with that evolution of the market for Intel is ARM taking sales from multiple market segments. Seeing that Winders-8 will run on ARM, we might see the end of WinTel for low-end & mid-tier laptops.
As a company, can Intel survive such a radical change in demand for its major product line?
Will its work on MLC flash fill the financial void?
I've no idea how that will go.
But like you said, ARM is going to shake up even the Intel server market.
The "secret sauce" that the ARM architecture has is that it's a licensed design.
Although chip design companies might not own or be able to access chip FABs within 2 or 3 design cycles of Intel, they can produce highly optimised and use-case targeted chips.
Which Intel can't do. They are focussed on the bleeding edge of CPU performance and FAB design.
Manufacturers like Apple/A5 and Calxeda can produced ARM-based designs that can outperform Intel-based systems by an order-of-magnitude on non-MIPs metrics.
As Apple has shown, there are very big markets where raw MIPs isn't the "figure of merit" in designs.
2012/09/05
Recruiting FAIL: Part 3. ITCRA complaint
Lodged an formal complaint with ITCRA [IT Contract and Recruitment Association], the Industry Body for Recruiting companies.
Several of the Agents actions were serious breaches of the ITCRA Code of Conduct.
In 30 years of dealing with Agents, this guy is by a long margin, the worst I've come across. Not just incompetent or "poor with details" such as misspelling Workseeker name on contract. Also demanded an apology as pointing this out was "offensive".
Background:
This was a *permanent* position for a senior IT staffer.
Workseeker required to move interstate.
Agency approached workseeker, no job application ever made by workseeker.
Job never advertised with a start date, no immediacy ever stated. Comment "expected to take 2 months to fill position" [by October]
Complaints.
Misleading statements:
1. Confused an email from himself to workseeker with a written offer from the Client. Insisted this was a "Job Offer", implying a binding contract.
2. Promised help finding accommodation for relocating interstate, none provided. Having local accommodation was always a condition of accepting the position.
Harassment or cyber-stalking:
3. One incident of a dozen calls/texts in 30mins.
Asked, in an email, to desist.
Repeated again later with more very inappropriate and abusive statements.
Privacy Act breach.
4. Used Referee's contact details for purposes data not supplied for. When workseeker would not answer Agents calls, Agent rang referee to complain and abuse.
Possibly Criminal over-stepping
5. When workseeker had failed to receive a contract 10-days from 1st proposed start date, informed Agent of inability to start due to personal circumstances.
Agent then harassed and browbeat client.
Seriously overstepped by continuing to demand exactly what the personal circumstances were.
Justified by saying "I need to explain to the Client".
This was uncalled for as the Client had no urgency on filling position, nor was there any advertising start date.
6. General Incompetence and lack of attention to legal details
a. Misspelled Workseeker name on contract. Demanded a written apology to Client for pointing this out.
b. Sent 7 emails in 15 minute period informing workseeker of Job Offer. Kept issuing 'recall' emails for incorrect offers sent.
c. Commented that Agents' manager was continually chasing him to comply with company requirements and document all communications.
7. Failing to act on Instructions.
Workseeker requested 3 times in email that Agent ask Client if 9-day fortnight [with RDO] would be acceptable during first 3 months while transitioning to Sydney.
Agent never asked Client [confirmed].
Client was happy to comply when asked.
Agent deliberately misled workseeker by stating the job "was full-time only" and RDO's were not possible.
Emails/SMS's documented at:
[http://stevej-on-it.blogspot.com.au/2012/09/recruiting-fail-how-to-foul-up-employee.html]
2012/09/02
Recruiting FAIL: Part2 - Red Flags and Lessons Learned
This experience was unpleasant enough that I took down my LinkedIn account with around 300 contacts, and resolved I wouldn't look for work as a System Admin again.
Whatever I do in looking for work, it's wrong, there is no point in pursuing a strategy that's failed me time and again for over 10 years.
I took a clear decision to provoke a crisis by sending my 'problem' email.
I had accommodation organised and paid for the first week, had packed and organised myself to start on the Monday and a plan, if a little shaky, to continue.
I've learnt a harsh lesson, which means "better to abandon earlier than later":
Lesson 1: If it's important to you, get it in writing early on. More so for "dealbreakers".
I never got Slippery Sam the Agent to make a written commitment on what he was promising to deliver. He, and the company, couldn't be held to it.
Lesson 2: Relocating cities is a Big Deal. Allow time, Plan the Move and organise Reconnaissance.
Driving a few hours up the road for an interview isn't the same as moving your life. Even if single, you have to devote a decent chunk of effort to the task. It will take time to do properly.
Lesson 3: You can't make these decisions alone. Talk them over with a friend.
If I'd talked through my decisions and the way I was being treated with a friend, I may have slowed the process down and set a much better process and plan to move in place.
Lesson 4: Be wary when there's a Big Rush and you're not asked when to start, but told.
There was never any hiring date from the Agent or company. They seemed to turn it into a huge rush, but hadn't declared there was any problem that needed someone there Right Now!
There wasn't a contract negotiation, there should be at least a start-date negotiation or specified in original request.
Lesson 5: One Red Flag is enough. Two is a dealbreaker.
Agents and Salesmen will always come across as Great Friends. Which you are until they got your signature, then you're a pariah.
The first Red Flag should've been the apparent haste (Job Spec on Wed 8-Aug, Interview on Mon 13-Aug, organised on Fri 10-Aug).
The next, the lack of a specified start date.
The Red Flag, par excellence, was rescheduling my interview a) earlier and b) on the day.
Slippery Sam the Agent went on to harassment (12 calls/texts in 30mins), browbeat me and completely overstepped the boundaries by demanding I explain my personal circumstances.
That little escapade was, in retrospect, an Instant FAIL.
Agents are there to facilitate the engagement, not beat-up on you and heap on abuse.
Whatever I do in looking for work, it's wrong, there is no point in pursuing a strategy that's failed me time and again for over 10 years.
I took a clear decision to provoke a crisis by sending my 'problem' email.
I had accommodation organised and paid for the first week, had packed and organised myself to start on the Monday and a plan, if a little shaky, to continue.
I've learnt a harsh lesson, which means "better to abandon earlier than later":
Things go on as they start. or It will only get worse, not better.
Lesson 1: If it's important to you, get it in writing early on. More so for "dealbreakers".
I never got Slippery Sam the Agent to make a written commitment on what he was promising to deliver. He, and the company, couldn't be held to it.
Lesson 2: Relocating cities is a Big Deal. Allow time, Plan the Move and organise Reconnaissance.
Driving a few hours up the road for an interview isn't the same as moving your life. Even if single, you have to devote a decent chunk of effort to the task. It will take time to do properly.
Lesson 3: You can't make these decisions alone. Talk them over with a friend.
If I'd talked through my decisions and the way I was being treated with a friend, I may have slowed the process down and set a much better process and plan to move in place.
Lesson 4: Be wary when there's a Big Rush and you're not asked when to start, but told.
There was never any hiring date from the Agent or company. They seemed to turn it into a huge rush, but hadn't declared there was any problem that needed someone there Right Now!
There wasn't a contract negotiation, there should be at least a start-date negotiation or specified in original request.
Lesson 5: One Red Flag is enough. Two is a dealbreaker.
Agents and Salesmen will always come across as Great Friends. Which you are until they got your signature, then you're a pariah.
The first Red Flag should've been the apparent haste (Job Spec on Wed 8-Aug, Interview on Mon 13-Aug, organised on Fri 10-Aug).
The next, the lack of a specified start date.
The Red Flag, par excellence, was rescheduling my interview a) earlier and b) on the day.
Slippery Sam the Agent went on to harassment (12 calls/texts in 30mins), browbeat me and completely overstepped the boundaries by demanding I explain my personal circumstances.
That little escapade was, in retrospect, an Instant FAIL.
Agents are there to facilitate the engagement, not beat-up on you and heap on abuse.
Recruiting FAIL: Part1 - How to foul-up employee engagement.
It began, as I recall, on a sunny winters afternoon in August, a Tuesday.
22 days later it had ended acrimoniously with an SMS and my email in response, and the removal of my LinkedIn account to avoid such agents/events in the future.
It fits my saw "your priorities are what you do, not say".
The response to my questions, I found fantastic, as in beyond belief.
In 3 separate emails, I'd asked B if CO would consider letting me work 9-day fortnights for the first 3 months or so, so I might attend to business in Canberra. While I said it wasn't a "drop-dead", it was important enough for me to keep raising the issue.
B was very adamant that "this was a full-time job, CO won't let you work a 9-day fortnight".
Only I hadn't told him I'd guessed C's email address and had a conversation about this and a few other topics. C was more than happy to arrange flexible hours and an RDO. He didn't want "stress".
C was delegated to reply to my questions, which while apparently honest, didn't strike me as being well thought through, nor complete [whole email not included]:
The first Red Flag was C rescheduling my appointment 2 hours earlier. I was rung by B while I was driving up. It cost me $45 in parking, but I was able to make their changed timetable.
At the end, C raced out without properly terminating the interview as he'd run overtime discussing his technical problem and had a taxi waiting.
At 16.05, I finally received a contract from F at CO, whom I'd not heard of or from before. Mess with names and questions is above.
The Red Flag extraordinaire was a dozen missed calls and texts from B in 30 minutes while I walked down to the Post Office, sans phone, to put a signed copy of the contract in the mail (express post) so it'd be there in their office 09:00 next working day. Canberra is treated as Regional NSW by Australia Post with normal mail normally taking 2 days going via Wollongong.
I then got The Third Degree from B, demanding four or five times to know just how my personal circumstances had changed as "he had to sell it to the client". I felt abused, browbeaten and upset after that little tirade.
All of which was pretty surprising as they'd never suggested a start date, never suggested there was any hurry to fill the position and then I found out C, the manager, was going to be away just after I started.
Just to show that B did know that Accommodation was Drop Dead for me, I include an email from him.
I got another call from B around 3PM the next day, Tuesday, while I was driving back from Bowral where B said he was having a little trouble getting anything for me from an a Real Estate agent.
I specifically asked that he sent me the contact details of at least one agent.
Nothing came that evening and I waited until around Noon the next day before sending my "problem" email.
One of the things I found "Not Quite Right" early on was a request that I take a look at a Performance Problem on one of their production systems as part of the Interview process. Turns out it wasn't fake data or a test, but I was in front of a console of a running production system, having someone else type my commands, trying to diagnose a live problem for them. Without any background, system maps or application briefing...
This had been my initial queasiness at the request.
Part of the problem was the uncertainty of employment, and since 2002, I've had 3 failed attempts to make it through to permanent employment. I've become very wary of Hidden Agendas of employers and managers...
Very kindly, the boarding house allowed me a 2/3 refund, as they'd not informed me of the 14-day cancellation policy. In the end, I got through this sorry mess for under $250.
In Part 2 I will try to extract the Red Flags and my Lessons Learned...
22 days later it had ended acrimoniously with an SMS and my email in response, and the removal of my LinkedIn account to avoid such agents/events in the future.
Please pick up your phone and talk with me steve. Like adults, let's discuss this. At the moment, you are really damaging my relationship with my client which is not fair and not right. I have really done all I can to help you and you won't even talk to me. SMS: +6145206812. 29/08/2012 15:42:49and
To: B and CI precipitated this crisis with an email just before Noon to the Agent (B), the manager (C) and (F) the person in CO that'd sent me the contract. B was very upset that I'd sprayed a message all over CO - told by my friend G, whom he'd first contacted as a referee and then again after this note when I declined his repeated calls.
Subject: Harassment
Date: Wed, 29 Aug 2012 16:43:44 +1000
B,
it's bad enough that against my express wishes you've been bombarding me with calls and texts - that amounts to harassment.
BUT TO CALL MY FRIEND??? What the HELL were you thinking??
Yes I'm ignoring your calls, not because I'm petulant or sulking, but because:
a) I've been doing stuff today, including taking a load of stuff to the tip (loading, driving, unloading, driving - not available to talk), and
b) because there is only ONE thing of interest you can say to me...
Which is: "This is how we can work this out..."
Unless you've got a plan to get me reasonable temporary accommodation while I find a place I can sign a lease on, then there's nothing new to be said.
I can't afford to commit to $10,000 or more in a lease on the chance I'll still have a job in 6 months.
I'm happy to work at C/O, I like C and his team, I think the work would be interesting and think I could make a positive contribution there.
There is just one thing, no more, standing between me and starting there and that's I don't have a place to stay and you haven't helped.
If I had applied for a job in Sydney via you, then it would be my problem to look after myself, pure and simple.
But that didn't happen.
YOU approached ME.
If YOU want me THERE, YOU have to make it happen.
Moving states, you of all people should know its a big deal.
So far you've made empty promises and hung me out to dry...
So - STOP HARASSING ME.
The only message I want to get from you is "It's fixed..."
Otherwise, we've said all that needs to be said.
steve
To: B, C and FThe manager, C, responded with this, making it very plain he wouldn't help me, personally or corporately, nor attempt to negotiate a solution.
Subject: problem
Date: Wed, 29 Aug 2012 11:49:41 +1000
I'd like to start by reminding you that I didn't apply for a job with CO - that you've chased me, being insistent to the point of browbeating.
You've known from before you talked to me that I had to move cities to take up your position.
I made two things very, very clear at the outset:
- I do NOT have any temporary accommodation in Sydney, not family or friends I can crash with for a week or two, and
- I required assistance to find a place. From out of town, it's very hard to find anything, especially if a constrained timetable is imposed, as you've done.
Rephrasing this: My employment with CO has always been conditional on finding accommodation, and you've been aware of this.
Two weeks ago, I was promised introductions to estate agents and assured it'd present no problem finding me somewhere to live, presumably reasonably before your selected start date.
As yet, that promise hasn't been fulfilled.
With 2 and a bit days to find a place, I really don't think I could find a place, and certainly not something that I could afford or that I would want to live in.
You've run out the clock on me. I've no idea why.
This week, there was a news item about a murder in a boarding house and I thought: "never again".
A number of times when I was contracting and working in Sydney, I stayed in these unpleasant little dives. Since the news item, I won't be forced for no good reason, to go there again.
I've not been impressed with either how you've generally communicated with me, nor the seeming absence of internal communications at your end.
So I need to spell this out:
In normal engagement scenarios, asking people move inter-city involves a bunch of things you haven't done:
- You need to get back to me on this.
- You need to come back with an explicit proposal, either of accommodation or something that's guaranteed to lead to it.
- I expect ONE professional communication back to me on this.
- no browbeating or harassment, this is a problem of your devising (I got 12 calls/SMS in 30mins when I walked to the Post Office)
- flying the candidate to the in-person interview
- making allowance for the relocation in the start-of-work date
- paying or, or contributing to relocation expenses, every airfares
- providing temporary accommodation, usually some months, while the person finds new accommodation
- providing time-off to search for accommodation and settle affairs, as needed.
regards
steve jenkin
It fits my saw "your priorities are what you do, not say".
Subject: Re HarassmentThere had been a fuss previously with the contract. I'd been invited by F to ask questions.
Date: Wed, 29 Aug 2012 16:51:44 +1000
Hi Steve,
We CO have no way of providing you with a solution for your accommodation here in Sydney and as I mentioned in our phone conversation before, although it is in Agency's best interest to match CO with the right candidate for our job posting, it is not their job either. Unfortunately we will have to miss out on this opportunity to work together.
I wish you the best of luck in your future endeavours.
Cheers,
C
The response to my questions, I found fantastic, as in beyond belief.
- I was told both B and F found it "offensive" and condescending, but was never told just what I'd written they been offended by.
- The CEO was shown my email (itself an interesting move, not entirely legal) and laughed. Said he liked my directness and saw no cause for offence.
- B blew me up for writing to "his client" without permission and instructed me to never contact F directly again.
- I eventually got B to understand that he'd not mentioned this rules earlier that day when we talked and inventing rules after the event and then chastising me for not following them was impossible logic.
- I never got an apology for this abuse.
- B demanded I write F an apology the next day, with him vetting it first.
- I did so by 09:32.
- B insisted I was to not write that he'd been involved in asking for, or vetting, my apology.
- I objected against this, as it is a deliberate fabrication.
To: B and FThe issue of RDO's was critical.
Subject: Re: Employment Agreement
Date: Tue, 21 Aug 2012 17:31:40 +1000
F,
Hate to do this to you, but my surname is singular, not plural:
JENKIN, no 's'. [At top and on signature line]
It happens a lot, which is why I emphasised it originally, I can't think how that may have been overlooked.
The contract needs to be redone to correct this.
I will sign and post a copy to you tonight (express post, delivery tomorrow) with the incorrect name noted. On my start day we can sign the new version.
My formal name for legal docs is "William Stephen Jenkin", but I'm called "Steve". No need to put one of my Christian names in brackets.
Questions:
0. Whom do I report to whilst my erstwhile manager, C, is away on leave?
1. Clause #3, probationary period.
The Fair Work Act sets a 6 month minimum for lodging dismal cases.
Would that be a more effective period than 3 months?
2. Clause #5, working hours.
The wording suggests fixed start/end times resulting in an 8 hour work-days or 40-hour weeks, yet ordinary hours are 2 hours less. Could you please clarify this for me.
3. Clause #5, flexible hours.
As I'll be relocating from Canberra, I was hoping for the first six months of my employment that I could work 9-day fortnights, i.e. 76 ordinary hours in 9 days with alternate Mondays off (RDO style). [An extra 51 minutes/day]
Will that be possible?
4. Clause #5 and #6. On-call duty and remuneration.
[snip]
5. Clause #10, Intellectual Property.
[snip]
Will the company advise me of all everything it does.
I can't see how in my position I could adequately fulfil that obligation.
6. Clause #10, Intellectual Property.
To be clear, the contract makes no mention of contributing to "Open Source Software". My understanding is that such work falls outside the scope of this clause.
regards
steve jenkin
In 3 separate emails, I'd asked B if CO would consider letting me work 9-day fortnights for the first 3 months or so, so I might attend to business in Canberra. While I said it wasn't a "drop-dead", it was important enough for me to keep raising the issue.
B was very adamant that "this was a full-time job, CO won't let you work a 9-day fortnight".
Only I hadn't told him I'd guessed C's email address and had a conversation about this and a few other topics. C was more than happy to arrange flexible hours and an RDO. He didn't want "stress".
C was delegated to reply to my questions, which while apparently honest, didn't strike me as being well thought through, nor complete [whole email not included]:
2. It's been a long time since I've done 40 hours of work at CO. We regularly do more than 40 hours of work on a week. I am hoping that with you joining the team this will get better, but this is not a place where we work 9 to 5. Working hours are in general flexible with some restrictions given that as a team we have to ensure our 8am to 6pm support line has someone here to answer the phone.The really important Red Flag occurred on the Friday after the Interview of Monday 13th.
3. We can manage that internally and informally. [RDO's]
The first Red Flag was C rescheduling my appointment 2 hours earlier. I was rung by B while I was driving up. It cost me $45 in parking, but I was able to make their changed timetable.
At the end, C raced out without properly terminating the interview as he'd run overtime discussing his technical problem and had a taxi waiting.
Subject: Re: FW: Confirmation of OfferThe first Red Flag was a total of six emails from 09:43 to 10:05 on Fri 17, first confirming the job offer, then "recalling" the email as he'd made an error, and again and again... Geting the contract details right is a necessary competency for an agent.
Date:Fri, 17 Aug 2012 12:00:27 +1000
B,
I'm happy to accept the offer generally BUT my personal circumstances have changed slightly since the informal offer on Tuesday/Wednesday and I can no longer start on the 27th.
With C now going on holidays, it wouldn't be operationally effective for me to start on the originally advertised date, Mon 3-Sept-2012.
I'm happy to negotiate a start date when or after C returns from holidays, but realise that CO may wish to rescind this offer to me and go with a "Plan B".
Hope to hear from you soon.
regards
steve jenkin
At 16.05, I finally received a contract from F at CO, whom I'd not heard of or from before. Mess with names and questions is above.
The Red Flag extraordinaire was a dozen missed calls and texts from B in 30 minutes while I walked down to the Post Office, sans phone, to put a signed copy of the contract in the mail (express post) so it'd be there in their office 09:00 next working day. Canberra is treated as Regional NSW by Australia Post with normal mail normally taking 2 days going via Wollongong.
I then got The Third Degree from B, demanding four or five times to know just how my personal circumstances had changed as "he had to sell it to the client". I felt abused, browbeaten and upset after that little tirade.
All of which was pretty surprising as they'd never suggested a start date, never suggested there was any hurry to fill the position and then I found out C, the manager, was going to be away just after I started.
Just to show that B did know that Accommodation was Drop Dead for me, I include an email from him.
I got another call from B around 3PM the next day, Tuesday, while I was driving back from Bowral where B said he was having a little trouble getting anything for me from an a Real Estate agent.
I specifically asked that he sent me the contact details of at least one agent.
Nothing came that evening and I waited until around Noon the next day before sending my "problem" email.
Subject: Are you free to chat today?
Date: Mon, 27 Aug 2012 14:39:30 +1000
Will you be free to chat today?
I have some people that can talk to you regarding accommodation and keen to catch up.
Thanks
B
One of the things I found "Not Quite Right" early on was a request that I take a look at a Performance Problem on one of their production systems as part of the Interview process. Turns out it wasn't fake data or a test, but I was in front of a console of a running production system, having someone else type my commands, trying to diagnose a live problem for them. Without any background, system maps or application briefing...
This had been my initial queasiness at the request.
Subject: Re: Interview RequestI had paid $350 to a boarding house for a weeks' accommodation. I had organised accommodation for the first week, but decided I was going to be miserable living there in a state of permanent anxiety both for my safety and if I'd have to find a new room at short notice.
Date: Sat, 11 Aug 2012 19:14:18 +1000
B,
On reflection, I'm thinking there's a mismatch between this part of the Interview process (snippet below) and the job description as given...
Still going to do the interview, but I'd like to flag my concerns with you first.
The questions they are asking in the Interview are specifically:
- Capacity Planning (circuit planning, load forecasting, provisioning) and
- Performance Analysis (scalability, bottlenecks, rearchitecting, design, interactions, ...)
The closest thing in the job description is:
"A multi-skilled technical profile is required with proven ability to monitor and troubleshoot database and web server performance."
Which includes fault analysis but NOT architecture redesign and Performance Analysis.
If they're wanting a free consult (with current data), I'm not happy with that. I've done enough consulting gigs to be wary of customers asking "just one little question", then getting stiffed on the purported contract
I'd be very happy to look at data from a year ago and analyse that, then compare my analysis with what they did and what happened.
That's completely fair to both them and me.
They don't give away their secrets and I can't be conned into a freebie.
I'm not inclined to give them high-quality consulting advice for free.
Remember that I have bailed multiple large, high-profile Govt. sites out of extreme situations before, so they might just be casting around for that.
Extremely happy to be engaged by them as a consultant for an appropriate daily fee and look at any problems they give me, if that's what they truly want
Anyway, I hope they are being straight with me or just a little naive.
That's the position I'll take until I confirm otherwise.
cheers
steve
Part of the problem was the uncertainty of employment, and since 2002, I've had 3 failed attempts to make it through to permanent employment. I've become very wary of Hidden Agendas of employers and managers...
Very kindly, the boarding house allowed me a 2/3 refund, as they'd not informed me of the 14-day cancellation policy. In the end, I got through this sorry mess for under $250.
In Part 2 I will try to extract the Red Flags and my Lessons Learned...
Subscribe to:
Posts (Atom)