This Business and Moment...

One month till I start my new job. Was approached by my boss who is leaving end of December. Asked if I could delay leaving till the end of the December for this "swan-song" project he wants to work on. If I stay, he could secure an 8 to 18% bonus of my annual salary....

So I did the calculations, even at 18% its not good enough. I want 30% minimum, not a variable range at the low end.

Looks like I be declining their offer to delay my leaving date.
 
So after 16 years here I've accepted a new job! It's a customer I've been working with for a while and saw they had posted a position that is basically what I already do but a decent bump in salary.

Will be going from £68,000 -> £75,000 + 10% annual bonus. Hybrid working but 95% home based. It's a really good company to work for too.
 
Last edited:
I seem to have started an argument without intending to!

We have a mapping table from one system to another. One an accounting system and the other a reporting system. Our overall group has a few hundred companies who all report directly upward, for some reason the accounting system has 2 chart of accounts which are used with little reasoning as to which each company uses.

There is a mapping table which takes the 2 different GL account codes (for the same cost) and puts them into a single account in the reporting system, and the 2 account structures are 95% identical for all cost types except Salaries. However within the range one account structure uses 62XX and the other uses 72XX, these generally mirror each other so 6210 is the same as 7210.

However they’ve now created a new account code of 6202 for some new spend type, but only in 1 chart of accounts. Which means that for users of the other chart of accounts. The numerical structure is completely ruined. With a “salary” account sitting within their COGS just because they insist on using a singular code.

I've questioned the logic and just asked for a 7202 account to be added to the mapping table to feed into the account in the reporting system as 6202. I've argued my point with a guy in a similar position to me at our parent company, however he can't make the call and has moved it further up the chain, so i keep having the same discussion with people one line up the chain at a time. I feel like soon i'll end up at the CFO of the overall holding company!

I accept I’m likely going to have to shrug and fit in but it’s absolute stupidity. They either need to force everyone to use a single COA (which makes sense) or allow people use different and map them accordingly.
 
Last edited:
Wait till they want 6202a but also a 8202. Then you build a load of rules "if then do this, it not if that, it otherwise this". Use it for a few years. Then they want to start over. With a new system and do exactly the same thing again. Then want to combine it with the old system.
This is the stuff of nightmares for me. It's basically the digital version of crap spelling, which also makes me twitch (in published docs, I'm not a grammar Nazi with individual humans).
 
This is the stuff of nightmares for me. It's basically the digital version of crap spelling, which also makes me twitch (in published docs, I'm not a grammar Nazi with individual humans).

You'd hate the project I'm on. One or two people on the team are brutal at spelling. But also don't care to fix it. So they still spell something like "Today" wrong and it gets hard coded into the project then linked and referenced everywhere. After a few months its too big a job to fix.

But every time you reference it you have to remember to spell it wrong.
 
Last edited:
You'd hate the project I'm on. One or two people on the team are brutal at spelling. But also don't care to fix it. So they still spell something like "Today" wrong and it gets hard coded into the project then linked and referenced everywhere. After a few months its too big a job to fix.

But every time you reference it you have to remember to spell it wrong.
This reminds me of two things in our current massive project at work.

1. My company always ends up having 2 names for an app/product - the one we use during design and development, and inevitably a different one that is invented for the final commercial release. We've used the codename so widely for this new platform among docs and partner communications, that we can't shake it now. But using it as the actual configured key in all our code has really upset me. For reference it uses the term "next generation"... Which will look really crap when our config file lists a 5 year old superseded product as "next generation"...

2. Someone made a typo in our API spec document and a partner coded it into their firmware. When they said "This feature isn't working" we had to say "Yes you've spelled that wrong because we spelled it wrong, you'll have to fix it".

People just don't seem detail oriented any more :(
 
I think it's probably always been a problem, just more visible now.

A relatively common thing I see is typos in databases (Schema/Table/Column names) which then persist forever because people don't want the hassle/risks associated with changing it and updating everywhere it is referred to. And then for years in the future everyone is chuckling at how silly/unprofessional it looks.
 
I think it's probably always been a problem, just more visible now.

A relatively common thing I see is typos in databases (Schema/Table/Column names) which then persist forever because people don't want the hassle/risks associated with changing it and updating everywhere it is referred to. And then for years in the future everyone is chuckling at how silly/unprofessional it looks.
Makes it difficult for any intruders I guess!
 
On another note, for those not aware I work for VMware and we have the whole Broadcom takeover/China thing going on at the moment. It's a right mess, very little information going around and naturally everyone is worried about their jobs. I think I should be fine if it does happen, I'm on one of our largest accounts and for whatever reason I'm well respected. But with that said, Broadcom make the decisions and they'll do it from a spreadsheet or similar and will focus purely on numbers. Whether the takeover happens or not it's going to be a messy ride, our share value will plummet if the acquisition doesn't close, there will be mass redundancies, and I expect all C level people will be forced to resign by the board plus. At least TUPE should protect me somewhat no matter the outcome.
 
On another note, for those not aware I work for VMware and we have the whole Broadcom takeover/China thing going on at the moment. It's a right mess, very little information going around and naturally everyone is worried about their jobs. I think I should be fine if it does happen, I'm on one of our largest accounts and for whatever reason I'm well respected. But with that said, Broadcom make the decisions and they'll do it from a spreadsheet or similar and will focus purely on numbers. Whether the takeover happens or not it's going to be a messy ride, our share value will plummet if the acquisition doesn't close, there will be mass redundancies, and I expect all C level people will be forced to resign by the board plus. At least TUPE should protect me somewhat no matter the outcome.

Hope it's good news for you pal, hopefully Broadcom don't send it down the drain, although already some bad perceptions which may not have even come from BC such as the super-quick retirement of flings etc. Our AMs are super cagey on our deal at the moment too because of the situation.
 
In a very similar position I was earlier in the year in deciding whether to move roles

Was made redundant start of the year from my tech pre sales role, I’d been in tech pre sales for 10 years and loved it.

Took a job as basically a post sales technical account manager, combination of decent company with some of my great ex colleagues there, and being honest needing a job.

7 months in and I’ve been missing tech pre sales.

Now have an offer on the table for a tech pre sales role, should be a no brainer right?

Am struggling a little with the decision, I feel some loyalty to my current place for getting me out of a pinch (I know this shouldn’t be a thing, but I feel bad in letting down people who brought me in).

Also my boss and team are amazing and super nice, the work life balance is fantastic, but the actual work leaves me pretty cold, I have little enthusiasm for it and struggle to see where my future would be if I stay on this path.

I know I’ll likely go for the new role, but finding it a tougher situation to deal with than expected.

If people at my current place were horrible it’d be easy, but they aren’t :cry:
 
Last edited:
In a very similar position I was earlier in the year in deciding whether to move roles

Was made redundant start of the year from my tech pre sales role, I’d been in tech pre sales for 10 years and loved it.

Took a job as basically a post sales technical account manager, combination of decent company with some of my great ex colleagues there, and being honest needing a job.

7 months in and I’ve been missing tech pre sales.

Now have an offer on the table for a tech pre sales role, should be a no brainer right?

Am struggling a little with the decision, I feel some loyalty to my current place for getting me out of a pinch (I know this shouldn’t be a thing, but I feel bad in letting down people who brought me in).

Also my boss and team are amazing and super nice, the work life balance is fantastic, but the actual work leaves me pretty cold, I have little enthusiasm for it and struggle to see where my future would be if I stay on this path.

I know I’ll likely go for the new role, but finding it a tougher situation to deal with than expected.

If people at my current place were horrible it’d be easy, but they aren’t :cry:

No option to move into tech pre-sales in your current company?
 
Am struggling a little with the decision, I feel some loyalty to my current place for getting me out of a pinch (I know this shouldn’t be a thing, but I feel bad in letting down people who brought me in).

Also my boss and team are amazing and super nice, the work life balance is fantastic, but the actual work leaves me pretty cold, I have little enthusiasm for it and struggle to see where my future would be if I stay on this path.

1. Never feel you should be loyal to any company. Its a business at the end of the day and when it comes to the chop, they wouldn't think twice about letting you go.

2. If you have little enthusiasm for the role then you have answered your own question.
 
Hah, we had the G-CTO attempting to surprise us all with the 'please be here' consultation-not-consultation meeting, where he announced consultation without any form of planning or collateral, timeline or HR, tried to account consultation, without informing that people's roles could be at risk or anything else.. car-crash in motion.

Anyways, it is if it is, or not. I'm on one of the strategic requirement deliveries of which there's 5 FTE people.. so either they can the programme/transfer it completely... or it's not an issue. I've already planned in my 1:1 with him as he's requested for all of us.. interesting times on the magic roundabout.

Tonight is to relax. Tomorrow may be CV writing time.. so let's see.
 
Last edited:
Hi Diddums, I hope you're well.We have been instructed by our client to start confidentially approaching people regarding a prospective opening at one of their sites.I can't share a great deal at the moment, but what I can let you know is that it is a client-direct role working for a corporate client as a Senior Engineering Manager at one of their new skyscrapers. Salary is £80,000 plus package.Would it be worth us having a confidential chat if you'd like to find out a bit more?Thanks,Recruiter


Oof. Asked for a chat, let's see what she says.
 
Last edited:
Back
Top Bottom