This story starts over two years ago... I think I'm doomed to repeat myself till the end of time...

Feb 2014
[I'm thrust into the world of Microsoft Exchange and get to learn PowerShell]

Me: I've been looking at email growth and at this rate you're gonna run out of disk space by August 2014. You really must put in quotas and provide some form of single-instance archiving.
Management: When we upgrade to the next version we'll allocate more disk, just balance the databases so that they don't overload in the meantime.

[I write custom scripts to estimate mailbox size patterns and move mailboxes around to avoid uneven growth]

Nov 2014
Me: We really need to start migration to avoid storage issues. Will the new version have Quotas and have we sorted out our retention issues?
Management: We can't implement quotas, it's too political and the vendor we had is on the nose right now so we can't make a decision about archiving. You can start the migration now though, right?
Me: Of course.

May 2015
Me: At this rate, you're going to run out of space again by January 2016.
Management: That's alright, we should be on track to upgrade to the next version by November so that won't be an issue 'cos we'll just give it more disk then.

[As time passes, I improve the custom script I use to keep everything balanced]

Nov 2015
Me: We will run out of space around Christmas if nothing is done.
Management: How much space do you need?
Me: The question is not how much space... it's when do you want the existing storage to last?
Management: October 2016... we'll have the new build by July and start migration soon after.
Me: In that case, you need this many hundreds of TB
Storage: It's a stretch but yes, we can accommodate that.

[I don't trust their estimate so I tell them it will last till November with the added storage but it will actually last till February... I don't want to have this come up during Xmas again. Meanwhile my script is made even more self-sufficient and I'm proud of the balance I can achieve across databases.]

Oct 2016 (last week)
Me: I note there is no build and the migration is unlikely since it is already October. Please be advised that we will run out of space by February 2017.
Management: How much space do you need?
Me: Like last time, how long do you want it to last?
Management: We should have a build by July 2017... so, August 2017!
Me: OK, in that case we need hundreds more TB.
Storage: This is the last time. There's no more storage after August... you already take more than a PB.
Management: It's OK, the build will be here by July 2017 and we should have the political issues sorted.

Sigh... No doubt I'll be having this conversation again in July next year.

On the up-shot, I've decided to rewrite my script to make it even more efficient because I've learnt a lot since the script's inception over two years ago... it is soooo close to being fully automated and one of these days I will see the database growth graphs produce a single perfect line showing a balance in both size and growth. I live for that Nirvana.

Tech support to family member:

Mom: "App just goes black after 30 seconds"
Me: "remove it and install again"
Mom: "how?"
Me: "tap the icon and hold till icon wiggles"
Mom: "doesn't do anything"
Me: "did you tap and hold?"
Mom: "hold what?"
Me:"Tap and and don't pull your finger up"
Mom: "Nothing... oh wait, yes it jiggles"
Me: "lift finger, tap the x that appeared on the icon, follow instructions"
Mom: "ok did that so what do I do now?"
Me: Grrrrrrrrr
Mom: "ok it's deleted"
Me: "Go to app store, and search for the app. after you tap the appstore icon, in a moment or so you should see a magnifying glass icon with the word search, tap that"
Mom: "nope no magnifying glass"
Me: ggrrrrrrr "yes their is one"
Mom: "nope"
Me: "yep"
Mom: "nope, it isn't their, I'M NOT STUPID YOU KNOW JUST BECAUSE I'M OLD!!! WHY DO YOU ALWAYS THINK I'M SO STUPID? THERE IS NO MAGNIFYING GLASS!!!"
Me: Deep, deep deep breath to the point of bursting my lungs (which is the preferable outcome)
Me: "top right corner or bottom right corner"
Mom: silence.... a few crickets in the background then some giggles followed with "Oh yea, their it is "....

20 minute call. no hi, how are you, how's your day. Just hello, I have a problem, it's fixed, bye.

Sometimes, and I don't want to sound mean BUT I wish we could pick our family.....

Dev: This content might be too large to fit into this area on mobile.
We might need to add scrolling or design it differently.

Designer: It fits perfectly in the design.

Dev: But the user might have a smaller screen size than in the design.

Designer: We don‘t optimize for small screens.

Dev: But we still need to handle it somehow.
Also, the text might be longer for other languages.

Designer: No problem, we will provide short text for all translations.

Dev: We have 30 languages and the translations are made by a third party. We can not control it.

Designer: We‘ll manage somehow.

Dev: Also, the user might be using an accessibility setting on the device which makes the font size larger.

Designer: Unlikely

Dev: Also, the available screen size might be reduced by the on-screen keyboard.

Designer: … Ok then.

-

It‘s always a conversation like this. It repeats indefinitely.

Why don't we call infinite loops "Groundhog cycles"?

It’s like the twilight zone

"For me, it means..."

For me it was not one specific meeting, but rather a series of meetings with a customer over some years.

It was like the movie "groundhog day", it was the same all over again.

We had this technical term, and our customer had his own definition of what it meant and what it's supposed to be. No need to say that his definition did not match the one the engineers and developers of the world had agreed on.

At least a dozen times, i convinced him, but as soon as the meeting ends, it's all reset and we start at zero next time with his new or old definition of what a definition should mean. Sometimes i was just sick and tired of it so i let him explain how it is while i just stared into the void. Didn't matter he told me once, it will happen again next time again, like it never happened before.

Happy @Sunday,
May you enjoy the last few hours of stressless paradise before our evil lord @Monday appears!

I'm a stupid twat. Spent at least three hours today, all wasted. I had to update a user manual and change all the branding for a system I've licencesd and going to resell to my dumb clients. There was no original to work from only a pdf. Managed to convert it to word but all the formatting was fucked. So set up some heading and paragraph styles, proper header and footer and auto generate TOC's. I did all this without actually reading it, thought I'd get the formatting and branding out of the way first. So after all that I started the job of editing it and updating it. Quickly realised that PDF I converted was for a different but similar system. Tommorow is Groundhog Day.

I would find a way to get me out of groundhog day

On a lighter note I'm feeling like the old guy who keeps dying in groundhog day

Do they forbid music at your office? They do at mine. It's always like a weird atmosphere until the loud people come in. lol. Not a sound, not a peep. If you didn't look around, it's as if people weren't there.

Seriously. It's a bad idea to have music?! I understand that from a concentration perspective, but come on. Let's make business even more boring. lol.

On the other hand, I did work at a place where they had radio playing but they never changed station. It felt like Groundhog day. lmao.

My aim for this year is to change to a job which doesn't feel like that movie groundhog Day.

The current project I'm on makes me want to switch careers.

Skein: noun - a type of access modifier, allowing a property to be read internally or externally, but only written to *externally*. See "orwell" for opposite access modifier.

hermit (noun) - an access modifier specifying a property may only be written or read internally.

Gopher (noun) - an access modifier not to be confused with a groundhog.

Blackhole (noun) - can be written to, can never be read. See dev/null for details.

In other news I wrote the basis for a cms in lua.

Because I hate the cloud.

Happy Groundhog Day!

Happy Monday #4 everyone, hope it's not terrible!

Sweet vermouth, rocks, with a twist, please. Mine,.. too! Rome's my favorite too, the way the sun, hits the water, on the boats...

To the groundhog!