Fixing a parents iPhone, episode 1.

Problem: "Whatsapp is gone off my phone"

Debugging:

Me: *unlocks phone and sees whatsapp*, it's right here.

Mam: no, I no that I can't see my messages.

Me: ok, that is definitely not what "whatsapp is gone off my phone means".

*opens whatsapp*
*inside add contact screen*

App seems ok, your trying to add a contact?

Mam: that's a problem, whenever I open it I only see that page.

Me: *taps cancel button with shocked face*

Mam: omg there's my messages, how did you do that?

Me: ... ... ... I tapped the very easy to see, large cancel button in the top right hand corner.

Mam: but why was it opened there?

Me: *looks at opened message from unknown number*

If I was to hazard a guess, now stay with me on this one as it's a bit complex. I think ... I THINK ... you clicked the "add to contacts" button on the screen in front of you.

I am suspicious of one thing though.

Mam: what's that?

Me: how you managed to click the add contacts button, and when brought to the add contacts screen, you assume the app is broken.

Mam: oh will you **** off you sarcastic little ****. Thank you very much.

Me: no prob, 4 year computer science course put to great use.

My morning:

Me: Why did you just delete the failing unit tests?

Intern: I debugged it for a while and found one of the other developers broke it with his recent changes. I couldn't fix it.

Me: Did you let him know he broke it?

Intern: No.

Me: So you just deleted it and decided to pretend the feature isn't broken?

Intern: ... No ... I mean ... well you told us yesterday we needed to have all the tests passing.

(I NEED a stress ball people)

Best Valentine’s Day present ever! She knows me so well. This will be VERY useful in work.

Thanks @Number0, love you

Good Morning!, its time for practiseSafeHex's most incompetent co-worker!

Todays contestant is a very special one.

*sitcom audience: WHY?*

Glad you asked, you see if you were to look at his linkedin profile, you would see a job title unlike any you've seen before.

*sitcom audience oooooooohhhhhh*

were not talking software developer, engineer, tech lead, designer, CTO, CEO or anything like that, No No our new entrant "G" surpasses all of those with the title ..... "Software extraordinaire".

*sitcom audience laughs hysterically*

I KNOW!, wtf does that even mean! as a previous dev-ranter pointed out does this mean he IS quality code? I'd say he's more like a trash can ... where his code belongs

*ba dum tsssss*

Ok ok, lets get on with the show, heres some reasons why "G" is on the show:

One of G's tasks was to build an analytics gathering library for iOS, similar to google analytics where you track pages and events (we couldn't use google's). G was SO good at this job he implemented 2 features we didn't even ask for:

- If the library was unable to load its config file (for any reason) it would throw an uncatchable system integrity error, crashing the app.
- If anything was passed into any of the functions that wasn't expected (null, empty array etc.) it would crash the app as it was "more efficient" to not do any sanity checks inside the library.

This caused a lot of issues as some of the data needed to come from the clients server. The day we launched the app, within the first 3 hours we had over 40k crash logs and a VERY angry client.

Now, what makes this story important is not the bugs themselves, come on how many times have we all done something stupid? No the issue here was G defended all of this as the right thing to do!

.. and no he wasn't stoned or drunk!

G claimed if he couldn't get the right settings / params he wouldn't be able to track the event and then our CEO wouldn't have our usage data. To which I replied:

"So your solution was to not give the client an app instead? ... which also doesn't give the CEO his data".

He got very angry and asked me "what would you do then?". I offered a solution something like why not have a default tag for "error" or "unknown" where if theres an issue, we send up whatever we have, plus the file name and store it somewhere else. I was told I was being ridiculous as it wasn't built to track anything like that and that would never work ... his solution? ... pull the library out of the app and forget it.

... once again giving everyone no data.

G later moved onto another cross-platform style project. Backend team were particularly unhappy as they got no spec of what needed to be done. All they knew was it was a single endpoint dealing with very complex model. There was no Java classes, super classes, abstract classes or even interfaces, just this huge chunk of mocked data. So myself and the lead sat down with him, and asked where the interfaces for the backend where, or designs / architecture for them etc.

His response, to this day frightens me ... not makes me angry, not bewilders me ... scares the living shit out of me that people like this exist in the world and have successful careers.

G: "hhhmmm, I know how to build an interface, but i've never understood them ... Like lets say I have an interface, what now? how does that help me in any way? I can't physically use it, does it not just use up time building it for no reason?"

us: "... ... how are the backend team suppose to understand the model, its types, integrate it into the other systems?"

G: "Can I not just tell them and they can write it down?"

**
I'll just pause here for a moment, as you'll likely need to read that again out of sheer disbelief
**

I've never seen someone die inside the way the lead did. He started a syllable and his face just dropped, eyes glazed over and he instantly lost all the will to live. He replied:

" wel ............... it doesn't matter ... its not important ... I have to go, good luck with the project"

*killed the screen share and left the room*

now I know you are all dying in suspense to know what happened to that project, I can drop the shocking bombshell that it was in fact cancelled. Thankfully only ~350 man hours were spent on it

... yep, not a typo.

G's crowning achievement however will go down in history. VERY long story short, backend got deployed to the server and EVERYTHING broke. Lead investigated, found mistakes and config issues on every second line, load balancer wasn't even starting up. When asked had this been tested before it was deployed:

G: "Yeah I tested it on my machine, it worked fine"

lead: "... and on the server?"

G: "no, my machine will do the same thing"

lead: "do you have a load balancer and multiple VM's?"

G: "no, but Java is Java"

... and with that its time to end todays episode. Will G be our most incompetent? ... maybe.

Tune in later for more practiceSafeHex's most incompetent co-worker!!!

wk87 is a dangerous topic for me, i've been through a lot. I apologise for what I am about to inflict on this network over the coming week.

Most incompetent co-worker, candidate 1, "T".

T was an embedded C developer who talked openly about how he's been writing code since he was 14, knew all the C system libraries and functions like the back of his hand. For the most part, he did ... but not how to actually use them, as (based on his shocking ... well everything) he was inflicted by some sort of brain disorder not yet fully understood by medical science. Some highlights:

- Myself and the CTO spent 4 days teaching him what a circle buffer was and how to build one.
- His final circle buffer implementation had about 3 times as much code as he actually needed.
- When the code was running too slowly on the device, we didn't try find any performance improvements, or debug anything to see if there was anything taking too long. No not with T, T immediately blamed TCP for being inefficient.
- After he left we found a file called "TCP-Light" in his projects folder.
- He accused the CTO of having "violent tendencies" because he was playing with a marker tossing it up in the air and catching it.
- He once managed to leave his bank statements, jumper and TROUSERS in the bathroom and didn't realise until a building wide email went out.
- He once .... no hang on, seriously his fucking trousers, how?
- He accused us all of being fascists because we gave out to him for not driving with his glasses, despite the fact his license says he needs to (blind as a bat).

... why were his trousers off in the first place? and how do you forget ... or miss the pile of clothes and letters in a small bathroom.

Moving on, eventually he was fired, but the most depressing thing of all about T, is that he might not even be top of my list.

Tune in later for more practiceSafeHex's most incompetent co-worker!!!

Its Friday, you all know what that means! ... Its results day for practiseSafeHex's most incompetent co-worker!!!

*audience: wwwwwwooooooooo!!!!*

We've had a bewildering array of candidates, lets remind ourselves:

- a psychopath that genuinely scared me a little
- a CEO I would take pleasure seeing in pain
- a pothead who mistook me for his drug dealer
- an unbelievable idiot
- an arrogant idiot obsessed with strings

Tough competition, but there can be only one ... *drum roll* ... the winner is ... none of them!

*audience: GASP!*
*audience member: what?*
*audience member: no way!*
*audience member: your fucking kidding me!*

Sir calm down! this is a day time show, no need for that ... let me explain, there is a winner ... but we've kept him till last and for a good reason

*audience: ooooohhhhh*

You see our final contestant and ultimate winner of this series is our good old friend "C", taking the letters of each of our previous contestants, that spells TRAGIC which is the only word to explain C.

*audience: laughs*

Oh I assure you its no laughing matter. C was with us for 6 whole months ... 6 excruciatingly painful months.

Backstory:

We needed someone with frontend, backend and experience with IoT devices, or raspberry PI's. We didn't think we'd get it all, but in walked an interviewee with web development experience, a tiny bit of Angular and his masters project was building a robot device that would change LED's depending on your facial expressions. PERFECT!!!

... oh to have a time machine

Working with C:

- He never actually did the tutorials I first set him on for Node.js and Angular 2+ because they were "too boring". I didn't find this out until some time later.

- The first project I had him work on was a small dashboard and backend, but he decided to use Angular 1 and a different database than what we were using because "for me, these are easier".

- He called that project done without testing / deploying it in the cloud, despite that being part of the ticket, because he didn't know how. Rather than tell or ask anyone ... he just didn't do it and moved on.

- As part of his first tech review I had to explain to him why he should be using if / else, rather than just if's.

- Despite his past experience building server applications and dashboards (4 years!), he never heard of a websocket, and it took a considerable amount of time to explain.

- When he used a node module to open a server socket, he sat staring at me like a deer caught in headlights completely unaware of how to use / test it was working. I again had to explain it and ultimately test it for him with a command line client.

- He didn't understand the need to leave logging inside an application to report errors. Because he used to ... I shit you not ... drive to his customers, plug into their server and debug their application using a debugger.

... props for using a debugger, but fuck me.

- Once, after an entire 2 days of tapping me on the shoulder every 15 mins for questions / issues, I had to stop and ask:

Me: "Have you googled it?"
C: "... eh, no"
Me: "can I ask why?"
C: "well, for me, I only google for something I don't know"
Me: "... well do you know what this error message means?"
C: "ah good point, i'll try this time"

... maybe he was A's stoner buddy?

- He burned through our free cloud usage allowance for a month, after 1 day, meaning he couldn't test anything else under his account. He left an application running, broadcasting a lot of data. Turns out the on / off button on the dashboard only worked for "on". He had been killing his terminal locally and didn't know how to "ctrl + c a cloud app" ... so left it running. His intention was to restart the app every time you are done using it ... but forgot.

- His issue with the previous one ... not any of his countless mistakes, not the lack of even trying to make the button work, no, no, not for C. C's issue is the cloud is "shit" for giving us such little allowances. (for the record in a month I had never used more than 5%).

- I had to explain environment variables and why they are necessary for passwords and tokens etc. He didn't know it wasn't ok to commit these into GitHub.

- At his project meetups with partners I had to repeatedly ask him to stop googling gifs and pay attention to the talks.

- He complained that we don't have 3 hour lunch breaks like his last place.

- He once copied and pasted the same function 450 times into a file as a load test ... are loops too mainstream nowadays?

You see C is our winner, because after 6 painful months (companies internal process / requirements) he actually achieved nothing. I really mean that, nothing. Every thing was so broken, so insecure / wide open, built without any kind of common sense or standards I had to delete it all and start again ... it took me 2 weeks.

I hope you've all enjoyed this series and will join me in praying for the return of my sanity ... I do miss it a lot.

Yours truly,
practiseSafeHex

Dev: this task is done, can I put it in review and do something else?

Me: sure, of course.

Dev: cool, just be aware I'll make some changes to it later.

Me: ... wait, then it's not done.

Dev: no it is, I just need to re-read it and make some changes.

Me: yeah, so it will be done when those changes are made.

Dev: but I don't know what those changes are.

Me: ... I get that ... but ... ok I'm extremely confused. Why do you think it's done.

Dev: because I've written everything I need to and I'm happy with it.

Me: ok so why do you want to make changes.

Dev: I don't.

Me: ... ... ... ... you ... you are really not being clear. If you don't want to make changes, and you are happy with it, why are you planning on making changes later ... after marking the task as done.

Dev: well if I re-read it and see something I don't like, I would like to change it.

Me: ok, so re-read it as many times as you like and make as many changes as you like. But don't mark it as done until it is done.

Dev: but it is done.

Me: no it's not.

Dev: it is, look.

Me: ... yeah looks ok at a quick glance.

Dev: ok so I can mark it as done?

Me: are you going to make more changes?

Dev: yes.

Me: then no.

Dev: why?

Me: BECAUSE ITS NOT DONE.

Dev: ok maybe I'm not explaining it clearly.

Me: ... we can both agree on that. Ok so to summarise, we don't mark something as done until we have stopped touching it. We don't half finish something and say it's done and comeback to it later. We mark it as done when we are happy with i.....

Dev: but I am happ.....

Me: *raises hand* I repeat, if it's done, we lock it away and stop touching it. If someone reads it and complains, we can come back to it with a new ticket. But it's not done until we think we are ready to send it on.

Dev: I am ready to send it, I just may want to change it.

Me: ... ... ... ... ... due to a new policy implemented just now, we are only allowed to send 1 email to a person each week. So unfortunately we can only send on 1 copy. So when you have that 1 copy, let me know.

Dev: ok, let me re-read it a few more times then.

Me: there you go.

Came into work this morning to find someone had scarred my Mac monitor with this symbol of hate

Working with a team of interns, pointed out a bunch of unit tests are failing, they said they would take care of it.

10 mins later they opened a pull request to delete the tests that were failing.

fml, fml, fml, fml ... and ... oh yeah fml

PM: You know that screen that pops up at the start of the app asking for permission to access health data?

Me: Yeah the iOS HealthKit permission screen. What about it?

PM: Can you take that out. I don't think people are going to agree to it. I want people to use the app.

Me: Well we can't do that, apple says if we want to use HealthKit we have to ask for permission. We shouldn't be touching that data without permission anyway.

PM: Oh no permission is fine I get that, but is it not implied by downloading the app, its clearly a health app. I really don't want people to download it and then uninstall it because they don't like this.

Me: Not really, not everyone will know what data is needed, some of it might be sensitive to them.

PM: Nah I don't buy into that. I asked 5 of my friends on the golf course at the weekend and 3 of them said they wouldn't agree to it, thats 60% of our user base, we can't have that.

Me: ... ok, well I don't agree that your 5 friends is a fair sample to judge the whole world by, either way we have no choice.

Pm: No this isn't going to fly, can we not build our own HealthKit that doesn't have this kind of permission screen? Maybe we could start our own, and invite our partners to use it?

Me: ... no

Pm: why not? We'll have legal draw up something we put in the terms and conditions.

Me: ... it will take months to build for all the different types of devices we have, if they even let us get access to them, and then we will have a different standard to everyone else.

Pm: ... no your not seeing the big picture, i'll run the idea up the ladder.

**It was approved up the ladder, and subsequently cancelled when they realised the scale of the work involved which is both a "thank god" and a "wtf" moment**

Current mood:

- Referred to manager as "Mein fuhrer" to a colleague in slack.
- Reading an email from a recruiter.

Me: *sends email 45 minutes before a meeting*.

Boss: *20 mins into meeting*, any updates about the issues found yesterday?

Me: Yep I sent an email with an update on everything.

Boss: ok great, *shares screen*, *opens email*.

Ok want to walk us through it?

Me: ...... walk through my email?

Boss: Yeah we have everyone here in the meeting.

Me: ...... yeah I included all of them on the email.

Boss: Right, but it would be good to go through it for everyone’s benefit.

Me: *Reads email word for word, from the screen share*

I will now refer to him from this day forth as “The Time Vampire”.

Recruiter: Hi, i'm recruiting for xyz, your profile looks like a great fit. Would you be interested in discussing further?

Me: Hi, your company website says you only have an office location in Berlin. I've marked my profile as not interested in relocation, only interested in jobs in my country and said the same in my description. Are you expanding to my country?

Recruiter: You are correct, this role is based in AMAZING Berlin. Are you interested in relocating?

Me:

IT: Hi, how can I help?
User: Hi, I can't get onto the wifi / internet, my computer says "No Signal".

IT: Hm, we don't have wifi, your on a cable, what exactly is saying no signal?
User: Its just on the screen here.

IT: No but where, are you inside a browser, or is it a popup down the bottom corner?
User: No I haven't got that far yet, it just says no signal on a black screen, then it flashes and says no signal in another position.

IT: ...... did you turn on your computer after turning on the monitor ... thats the screen saying no signal from the computer.
User: ah yep, thats it, thanks!

Welcome back to practiseSafeHex's most incompetent co-worker!

*sitcom audience cheers*

Thank you, thank you. Ok so far we've had a developer from hell and a CEO who shot to fame for being the first rectum to receive a passport and be given a job.

2 pretty strong entrants if you ask me. But its time to slow it down and make sure everyone gets a fair chance. Its not all just about the psychopaths and assholes, what about the general weirdo's and the stoners who just made life awkward?

So here we go, Most incompetent co-worker, candidate 3, "A".

"A" was a bit of an unusual developer, despite having a few years experience in his home country, he applied for an unpaid internship to come work with us ... probably should have rang alarm bells but hey we were all young and dumb back then.

I had to say I felt very bad for A, as he suffered from 2 very serious, and job crippling personal conditions / problems

- Email induced panic attacks
- Extreme multifaceted attachment disorder (also known in layman terms as "get the fuck away from me, and do your job" syndrome)

While he never openly discussed these conditions, it was clear from working with him, that he had gone undiagnosed for years. Every time an email would come in no matter how simple ... even the services team asking to confirm his staff ID, would send him into a panic causing him to drop everything he was doing and like a homing missile find me anywhere in the building and ask me what to do.

Actually "A" also suffered from a debilitating literacy issue too, leaving him completely unable to read our internal wiki's himself. Every week we had to follow a set of steps to upgrade something and every week to mask his issue, he'd ask me what to do instead ... no matter how many times I sat with him previously ... must have been truly embarrassing for him.

But "A"'s finest moment in the company, by far, was the day where out of the blue, at the top of his voice (as if wearing headphones ... without wearing headphones) he asked

"DO YOU KNOW ANYONE WHO SELLS POT?"

... why no, manager of the entire department standing behind you, I do not

... why no, tech lead talking to manager, I do not

... why hello 50% of my team staring at me ... no "A", I do not!

Needless to say all our team meetings were a little awkward for the next few weeks after that but hey who doesn't like being thought of as a stoner / drug dealer by their team mates huh?

Will A make it to the top of the list of most incompetent? Well he has some truly logic defining competition yet to be announced.

Tune in later for more practiceSafeHex's most incompetent co-worker!!!

I GOT A JOB OFFER!!! IM OUT OF THIS FUCKING HELLHOLE!!!

🖕🖕🖕🖕🖕🖕🖕🖕🖕🖕🖕🖕

One of my worst meetings, as the sheer rage was unbelievable.

Backstory:
Architect: "Stop duplicating code", "stop copy pasting code", "We need to reuse code more", "We need to look at a new pattern for unit tests" etc.

Meeting:
Architect: What did you want to talk about?

Me: I built a really simple lightweight library to solve a lot of our problems. Its built to make unit testing our code much easier, devs only need to change a small bit of how they work.

Architect: I like the pattern a lot, looks great ... but why a library? can we not just copy the code from project to project?

... do you have a twin or something?

*came in this morning to see this conversation in slack from the remote teams*

Dev: Hey guys, I'm trying to push to the develop branch, telling me its locked. Is there a new process?

Lead dev: Yes I locked it because the repo is now dead, the last release that went out is the last for this year and ever for this app. Were merging this app with another, starting from the last release's code. We'll all have to swap over to the new repo soon.

Dev: ... eh ok I didn't put anything in the last release branch as it wasn't urgent. Normally our process is anything in /develop goes out in the new year. I've been merging to /develop for the last few weeks ... is that code now gone?
*14 question mark emoji reactions*

Lead dev: Yes
*27 angry emoji reactions*

Engineering manager: WHAT? when was this decided? When was it communicated?

Lead dev: oh I assumed my product counterpart had been spreading the messages around, have they not?

Several teams: no, nope, first i'm hearing of it.

Lead dev: Ok, i'll ask them what happened. Be aware then that most of the stuff thats going into develop now, most likely won't be allowed in until March. They want to prioritise releasing this new merged app and don't want anything to impact it.

Dev: So wait, i'm working on stuff now. What do I do? Where do I base the branch? Where do I merge?

<no response>

*My team comes into the office*

Dev: eeehhh ... what does this mean for our past 4 weeks of work? and all the stuff needed to go out in January?

Me: not.a.fucking.clue

I’ve been told my rants are being missed, since I left my hellhole of a job. So here’s a filler until something major goes wrong.

Right so here’s what my life is like at the minute. I’m working remotely from home. So this morning, instead of spending 2 hours in traffic, I got up at a reasonable hour and brought the dog for a walk. I don’t know who these people think they are, fucking up my routine like this. The audacity of them thinking it’s no big deal really pisses me off.

I’m the only iOS developer in the company. Normally I get bombarded with “why not use react-native” or “RxSwift is the future” and other shitty tools. Last week I said “i’d like to do X this way”. Do you know what those absolute bastards said to me? You ready? Hope you are sitting down ... they said ... “ok, sounds good” .... the fucking c***s.

Oh oh and the big one, wait for this now. Fridays are demo days, last Friday I showed what I was working on. Afterwards the CEO comes along, stares me in the eyes and without a care in the world what his comments might do to my self-esteem the fucker says “wow great job”. He fucking makes me SICK!!!

Feels good to get all that off my chest. I’ve missed venting. At this rate, I’ll be back very soon!

Rough analysis of LinkedIn inmail’s I get:

Hi <5% of time, not my name>,

I was looking at your profile <97% a lie>. I was very impressed with your <10% something I’ve never done> experience working for <5% a company I’ve never heard of>. Would you be interested in hearing more about <60% a job I’m not suited for>, they offer amazing benefits and have a great culture!

... no

Trying to debug something ... someone is looking for attention

The bloke that I share my office with is asleep on the job. Ffs, can I get any support around here?

This working remotely from home thing, just isn’t panning out

Fixing family / friends technical problems, episode 2.

Problem: "I lost my iPhone, I know there's a thing that lets you find it. Can you help?"

Debugging:

Me: sure, it's called "find my iPhone"

Friend: ah yes that's it. How do I use it?

Me: I'll show you, just login here and ... oh you didn't set it up?

Friend: Probably not, I don't know much about this computer stuff.

Me: ... when you setup your phone for the first time, it's a full screen thing that says "do you want us to locate your phone if it's lost. Yes / No". It's hardly writing an encryption algorithm now is it?

Friend: no it's not, but still I just didn't know. I probably clicked no for everything.

Me: ... says here you clicked yes for iCould ... and yes for photo sync ... so you read the one about your pictures but not about lost or stolen property ... nice.

Friend: ... so you can't find it then.

Me: No, natural selection took it away from you.

Friend: oh **** off.

So i've been a dev manager for a little while now. Thought i'd take some time to disambiguate some job titles to let everyone know what they might be in for when joining / moving around a big org.

Title: Senior Software Engineer

Background:
- Technical
- Clever
- Typically has years experience building what management are trying to build

Responsibilities:
- Building new features
- Writing code
- Code review
- Offering advice to product manag......OH NO YOU DON'T CODE MONKEY, BACK TO WORK!

Title: Dev Manager

Background:
- Technical
- Former/current programmer
- knows his/her way around a codebase.

Responsibilities:
- Recruiting / interviewing new staff
- Keeping the team focused and delivering tasks
- Architecture decisions
- Lying about complexity of architecture decisions to ensure team gets the actual time they need
- Lying about feature estimations to ensure team gets to work on critical technical improvements that were cancelled / de-prioritised
- Explaining to hire-ups why we can't "Just do it quicker"
- Explaining to senior engineers why the product manager declined their meeting request

Title: Product / Product Manager

Background:
- Nothing relevant to the industry or product line what so ever
- Found the correct building on the day of the interview
- Has once opened an Excel spreadsheet and successfully saved it to a desktop

Responsibilities:
- Making every key decision about every feature available in the app
- Learning to ignore that inner voice we like to call "Common sense"
- Making sure to not accidentally take some advice from technical staff
- Raising the blood pressure of everyone below them / working with them

Title: Program Lead / Product Owner

Background:
- Capable of speech
- Aware of what a computer is (optional)

Responsibilities:
- Sitting down
- Talking
- Clicking random buttons on Jira
- Making bullet point lists

Title: Director of Software Engineering

Background:
- Allegedly attended college/university to study computer science
- Similar to a technical product manager (technical optional)

Responsibilities:
- Reports directly to VP
- Fixes problems by creating a different problem somewhere else as a distraction
- Claiming to understand and green light technical decisions, while having already agreed with product that it will never happen

Had a PR blocked yesterday. Oh god, have I introduced a memory leak? Have I not added unit tests? Is there a bug? What horrible thing have I unknowingly done?

... added comments to some code.

Yep apparently “our code needs to be readable without comments, please remove them”.

Time to move on, no signs of intelligent life here.

Sorry if I make a typo, my hands a still a little shaky, just had to stop myself from crying.

This morning I came in, opened my email, saw an automated response from Jira saying .... saying ..... saying the backend team provided details about their new endpoint.

After a year of screaming, they finally did it. It was so beautiful I fell to the floor and wept like a baby.

Thank you all for your support through this difficult time. Together we can accomplish anything!!!

Manager: Hey, how are things with everything thats been going on? Hows the mood?

Me:

Things have been a little too quiet on my side here, so its time for an exciting new series:

practiseSafeHex's new life as a manager.

Episode 1: Dealing with the new backend team

It's great to be back folks. Since our last series where we delved into the mind numbing idiocy of former colleagues, a lot has changed. I've moved to a new company and taken a step up as a Dev manager / Tech lead. Now I know what you are all thinking, sounds more dull and boring right? Well it wouldn't be a practiseSafeHex series if we weren't ...

<audience-shouting>
DEALING! ... WITH! ... IDIOTS!
</audience-shouting>

Bingo! so lets jump right in and kick us off with a good one.

So for the past few months i've been on an on-boarding / fact finding / figuring out this shit-storm, mission to understand more about what it is i'm suppose to do and how to do it. Last week, as part of this, I had the esteemed pleasure of meeting face to face with the remote backend team i've been working with. Lets rattle off a few facts to catch us all up:

- 8 hour time difference to me
- No documentation other than a non-maintained swagger doc
- Swagger is reporting errors and several of the input models are just `Type: String`
- The one model that seems accurate, has every property listed as optional, including what must be the primary key
- Properties go missing and get removed at the drop of a hat and we are never told.
- First email I sent them took 27 days to reply, my response to that hasn't been answered so far 31 days later (new record! way to go team, I knew we could do it!!!)
- I deal directly with 2 of them, the manager and the tech lead. Based on how things have gone so far, i've nick named them:
1) Ass
2) Hole

So lets look at some example of their work:

- I was trying to test the new backend, I saw no data in QA. They said it wouldn't show up until mid day their time, which is middle of the night for us. I said we need data in our timezone and I was told: a) "You don't understand how big this system is" (which is their new catch phrase) b) "Your timezone is not my concern"

- The whole org started testing 2 days later. The next day a member from each team was on a call and I was asked to give an update of how the testing was going on the mobile side. I said I was completely blocked because I can't get test data. Backend were asked to respond. They acknowledged they were aware, but that mobile don't understand how big the system is, and that the mobile team need to come up with ideas for the backend team, as to how mobile can test it. I said we can't do anything without test data, they said ... can you guess what? ... correct "you don't understand how big the system is"

- We eventually got something going and I noticed that only 1 of the 5 API changes due on their side was done. Opened tickets. 2 days later asked them for progress and was told that "new findings" always go to the bottom of the backlog, and they are busy with other things. I said these were suppose to be done days ago. They said you can't give us 2 days notice and expect everything done. I said the original ticket was opened a month a go *sends link* ......... *long silence* ...... "ok, but you don't understand how big the system is, this is a lot of work"

- We were on a call. Product was asking the backend manager (aka "Ass") a question about a slight upgrade to the new feature. While trying to talk, the tech lead (aka "Hole") kept cutting everyone off by saying loudly "but thats not in scope". The question was "is this possible in the future" and "how long would it take", coming from management and product development. Hole just kept saying "its not in scope", until he was told to be quiet by several people.

- An API was sending down JSON with a string containing a message for the user with 2 bits of data inside it. We asked for one of those pieces to also come down as a property as the string can change and we needed it client side. We got that. A few days later we found an edge case and asked for the second piece of data to be a property too. Now keep in mind, they clearly already have access to them in order to make the string. We were told "If you keep requesting changes like this, you are going to delay the release of the backend by up to 2 weeks"

Yes folks, there you have it, the most minuscule JSON modifications, can delay your release by up to 2 weeks ........ maybe I should just tell product, that they don't understand how big the app is, and claim we can't build it on our side? Seems to work for them

Thats all the time we have for today,

Tune in for more, where we'll be looking into such topics as:

- If god himself was an iOS developer ... not
- Why automate when you can spend all day doing it by hand
- Its more time-efficient to just give everything a story point of 5
- Why waste time replying to emails ... when you can do nothing instead

See you all next week,
practiseSafeHex

“Hybrid is the future, it’s faster to develop, more efficient and has no real downside or impact”

Manager: I just think you are being too negative. Like sometimes other people have opinions too and we should hear them out before saying no.

Me: Well your opinion is the devs shouldn't be able to estimate their own tasks and you should decide on our behalf how long something should take.

You also want to decide what tech stack we use, because you followed a "Hello World" tutorial last night and it worked out for you.

Just because you got a simple webpage up and running in 2 hours doesn't mean all websites take 2 hours with the tech. Were not sitting in the corner laughing that you think its taking us 3 weeks to build this.

I'm not being negative simply because I don't agree with you. I'm not being unreasonable if I say I can do 6 weeks work in 2 weeks. And although it sounds offensive, i'm actually doing you a favour by telling you to get your head out of your ass

Million dollar app/service idea.

Automatically reply to all LinkedIn inmail’s with “I don’t have any experience with that on my profile”.

Even without any NLP I estimate over a 90% success rate.

Boss: lets set the domain to <productName>1.com.

Me: ok ... why 1?

Boss: ... because its version 1 of the software.

Me: .....

Boss: People will get it

My linkedin profile = ~7 years as an iOS developer. All of my job titles are "iOS Developer", "iOS Engineer" or "Mobile lead".

Recruiter: Hi, your profile looks great, I have a number of open roles matching your skills. Would you be free for a call to discuss your salary expectations, skills, what you are looking for etc.

Me: Hi, sorry I don't have time for a call right now, here are answers to your questions. Can you send me on any iOS job specs you have and i'll review. <answers>

Recruiter: Sorry I have no open iOS roles at this time.

Bitch ... ima find you and make you understand

pfft, all you bloody 2 space indentation hipsters

4 spaces for life!

Me: we only got 40 minutes notice that we had to stay in late for a meeting with the USA team. Can we politely ask them to give us like a days notice in future? I can’t just stay late at any time, neither can the guys with kids to collect.

Manager: oh ok. I’m very sorry this has affected you. Here, let me explain why this is going to keep happening and you’ll need to deal with it.

I greeted my staff this morning with the phrase

"Morning, mind if I ruin your Friday?"

They laughed, but won't be soon enough. The task we've been working on for weeks, ripping apart the codebase changing it to work a different way, fixing a tonne of bugs, making it faster and simpler to add features too. Well business has decided they want us to stop, undo it, spend a month on something "with higher ROI" and then finish it off after that.

Business are expecting this to have no impact on any of the timelines and just to be like flipping a switch. Now obviously I won't let that happen and fight back for more time, but yet another session of compromises, arguments, and yelling. YIPEEE!!!!!!

Me: Oh I see were using a non-standard architecture on this app. I like this bit but what is this doing? never seen it before.

Him: Ah we use that to abstract the navigation layer.

Me: oh ok, interesting idea, but that means we need an extra file per screen + 1 per module. We also can't use this inbuilt control, which I really like, and we've to write a tonne of code to avoid that.

Him: Yeah we wanted to take a new approach to fix X, this is what we came up with. Were not 100% happy with it. Do you have any ideas?

**
Queue really long, multi-day architecture discussion. Lots of interesting points, neither side being precious or childish in anyway. Was honestly fantastic.
**

Me: So after researching your last email a bit, I think I found a happy middle ground. If we turn X into a singleton, we can store the state its generating inside itself. We can go back to using the in-built navigation control and have the data being fetched like Y. If you want to keep your dependency injection stuff, we can copy the Angular services approach and inject the singletons instead of all of these things. That means we can delete the entire layer Z.

Even with the app only having 25% of the screens, we could delete like 30+ files, and still have the architecture, at a high level, identical and textbook MVVM.

Him: singleton? no I don't like those, best off keeping it the way it is.

... are you fucking kidding me? You've reinvented probably 3 wheels, doubled the code in the app and forced us to take ownership of something the system handles ... but a singleton is a bad idea? ... based off no concrete evidence or facts, but a personal opinion.

... your face is a bad idea

*finds royalty free clipart*

*clicks "free download" button*

*Brought to "purchase subscription page"*

What in the name of fuck is going on with this misleading ass website.

PM: 2 months? no thats way too long, do it in 1.

Director: I had a chat with someone else who doesn't work on this team, he says that developer you complained about is a good guy and we should keep him on the team.

Business: No, we don't have time for tech debt, lets build these new features as quick as possible and lets see where we are.

everyone: WHAT DO YOU MEAN IT CRASHED AGAIN??? THIS IS UNACCEPTABLE

Boss: Great news, we are getting another backend dev from another team to help us out.

Me: Cool, hopefully we don’t have the same trouble as the others, not replying, never writing anything down etc.

Boss: No, I’ve worked with her before. She’s much more passionate about doing things right, using best practices and all that stuff.

Me: Oh that’s perfect, great news!

Boss: Yep! ... just be aware she has a tendency to get very easily confused. She delivers the wrong thing from time to time and might need to redo stuff semi-regularly.

Me: ... ... ...

Boss: It’ll all work out. Don’t worry. Ok gotta run.

*deep breath*

Remain calm, don’t freak out, remain calm, don’t freak out.

*deep breath*

Ok, so my sort of new manager (had a slightly different manger-ish role on the team), has for the third time in as many months, just sent an email criticizing the dev team for our working from home-ness (which for the record has not been that bad, 2/3 or 3/3 have been in everyday for the past month)

In this same period, there has been late nights, weekends, successful releases, I’ve been invited to talk at a conference about my work (not a particularly big one, but still). Point is, everything is going well, very well in fact.

There has been no emails discussing our great work, thanking us for extra work, thanking us for picking up slack from other teams who are down a few people etc. no our major concern it seems is the “optics” of our team not being present in the open space.

Our contracts list flexible working hours, and his boss has frequently told us WFH is fine when things are too busy. But no he is complaining for us to get our hours in the office in line and make sure we are in the office more.

It’s been a particularly long and frustrating week, and I’m very tempted to inform him that if he is concerned about my chair and desk looking empty, that I can put them somewhere for him where they will always be occupied until a surgeon can remove them.

However, thanks to the deep breaths, I’ve managed to restrain myself long enough to run this past you all first and ask advice.

Please help,
Sincerely,
My sanity

Write a small js function using setInterval to fire a request every second ... then copy paste the code 450 times (literally, not an exaggeration) into a massive file to create a load test script.

This load test script also had no means to gather metrics or test response times or anything useful. It was literally a “did the server crash” test.

Me: *sends meeting request*

Attendee: *3 days later*, hi is there anything in particular you needed to discuss?

Me: ... nope, none what so ever. Decided to take 30 mins out of my busy day to talk to you, a person I don't know, for 30 mins. Definitely the title of the meeting request has nothing to do with it, I wouldn't bother reading that now, since you haven't yet anyway. Cheers!

Me: So i've cloned the iOS project, i've run carthage, but it won't build.. Have I done something wrong?

Devs: Oh read this doc on github, we do loads of custom stuff. The depenedncy manager can't do it all by itself. You need to run `./scripts/boostrap.sh`

Me (another day): I've switched branches and i'm getting all these errors. Any ideas?

Devs: Ah this happens when someone modifies xyz. Read this pinned slack message. Run `./scripts/bootstrap.sh` again.

Me (another day): I've switched branches again, getting different errors, re-running boostrap didn't fix it.

Devs: Ah yeah, this happens when someone modifies abc. You need to run `./scripts/nuke.sh` and then boostrap when this happens.

Me (another day): Guys When I try to run the prod app its not building any ideas?

Devs: Ah yes have a look at this confluence link. You need to run `./scripts/setup_debug_release.sh`, then nuke, then boostrap and you'll be good.

Me: .... ok

Devs: Oh btw very important! do not commit any changes from `./scripts/setup_debug_release.sh`. It will break everything!

Me: ... no i'm sorry we have a much bigger problem than that. We need to talk ... like right now

Just got this email with no body, and a vague subject / title in all caps.

... you ask questions on stackoverflow don't you

Just found out the backend developer I’m always complaining about. The one who:

- Can’t implement OAuth, and we have to have app users login every 24 hours because we have no way to generate new refresh tokens.

- Who used the phrase “your time zone is not my concern” to avoid building something that would let us inject test data.

- Who’s been debugging a critical bug affecting many users since December.

- Who can’t conduct API tests from external internet (you know, like the way the app will be in the wild) because it takes too much time.

- Who replies to Jira tickets only on a blue moon.

- Who has been 90% of the reason for my blood pressure situation

... is a fucking principal engineer in this company. In pecking order, his opinion should be considered more valuable than mine and everyone on my team.

I’ve just lost the will to live. How are big organizations THIS bad. Seriously, what promotion discussion did he go into

“So, you are a complete and utter bastard, nobody can stand to speak to you and you’ve yet to deliver anything of worth that actually works, over the course of several years ... ... ... interested in having your pay doubled??”

External company HR: We are sorry to hear you've decided to turn down our offer. You made a great impression and we thought you'd be a good fit. If you change your mind please let us know.

Me: I too am sorry you didn't tell me you were moving to the other-side of the county in two weeks, making it impossible for me to travel to and from work. I too have feelings about having done all the interviews and this being the end result. Thank you

Friend: Why don't you just quit your job?
Me: I want to, I just can't right now, it would cause too many issues.
Friend: oh really? Will it affect your health insurance or pension?
Me: No my office is the shipping address for my new iPhone. Haven't got it yet.
Friend: Oh ffs .... seriously?

IT: Its controlled via SSO, everyone has access by default

Me: oh i'm sorry, you are correct, I don't have an error message on my screen saying I don't have access. I made it all up. Thank you, you may close the support ticket

Newspaper: This CEO is one of the top entrepreneurs in the country, a true tech visionary shaping the future.

--- 3 months previous ---

Lead dev: O2 have said they are will pre-install the app on all their Androids but they need documentation from us.

CEO: documentation? on what?

Lead dev: Our unit test coverage, bugs found / fixed, security scan results, performance assessment, if and where its storing any data etc.

CEO: Ah were not doing any of that crap, bloody unit tests, its not necessary, tell them no.

lead dev: ..... eh ok

O2: *approved*

... true visionary, well done to everyone involved.

Mam: Hey can I ask you a question about Facebook?

Me: (Christ give me strength) ... sure whats up?

Mam: You know when you get a notification and you click on it and see what someone uploaded?

Me: ... you are not on Facebook, you can't be getting notifications

Mam: well I do. Is it possible to...

Me: No hang on a second, it is 110% not possible for this to happen. Something else is going on that you think is a notification.

Mam: You know when you are on, and you see a message like "12 new notifications"

Me: on? on what? this is happening on your phone is it? Can I see?

Mam: No its on my laptop at home.

Me: ... you have an old laptop with an old windows, you can't get notifications on it.

Mam: OH FOR GOD SAKE! ... you know when you are in your emails and it says "12 new notifications"?

Me: ... right so we are talking about EMAILS about unread notifications and not getting notifications on your phone. So you have an old account then that you don't use?

Mam: Yeah I don't know the password to it, haven't logged in, in years.

Me: of course

Mam: Right anyway. When I get one and click on it, lets say its about you, can you see me reading your notifications?

Me: ..... you can't not read my notifications.

Mam: uh, can you see me reading your emails then smart arse?

Me: ... can't do that either.

Mam: So what the hell am I doing then?

Me: You are reading a post someone uploaded, which you got alerted to from an email.

Mam: Right, can you tell when I've read your POST then?!?!?!

Me: no

Mam: was that so hard?

Me: ... yep

iPhone app riddled with memory leaks from a team of interns. Big series of demos coming up. Managements solution?

Send instructions to the person giving the demo to kill the app every 20 mins or so.

Welcome back to practiseSafeHex's new life as a manager.

Episode 2: Why automate when you can spend all day doing it by hand

This is a particularly special episode for me, as these problems are taking up so much of my time with non-sensical bullshit, that i'm delayed with everything else. Some badly require tooling or new products. Some are just unnecessary processes or annoyances that should not need to be handled by another human. So lets jump right in, in no particular order:

- Jira ... nuff said? not quite because somehow some blue moon, planets aligning, act of god style set of circumstances lined up to allow this team to somehow make Jira worse. On one hand we have a gigantic Jira project containing 7 separate sub teams, a million different labels / epics and 4.2 million possible assignees, all making sure the loading page takes as long as possible to open. But the new country we've added support for in the app gets a separate project. So we have product, backend, mobile, design, management etc on one, and mobile-country2 on another. This delightfully means a lot of duplication and copy pasting from one to the other, for literally no reason what so ever.

- Everything on Jira is found through a label. Every time something happens, a new one is created. So I need to check for "iOS", "Android", "iOS-country2", "Android-country2", "mobile-<feature>", "mobile-<feature>-issues", "mobile-<feature>-prod-issues", "mobile-<feature>-existing-issues" and "<project>-July31" ... why July31? Because some fucking moron decided to do a round of testing, and tag all the issues with the current date (despite the fact Jira does that anyway), which somehow still gets used from time to time because nobody pays attention to what they are doing. This means creating and modifying filters on a daily basis ... after spending time trying to figure out what its not in the first one.

- One of my favourite morning rituals I like to call "Jira dumpster diving". This involves me removing all the filters and reading all the tickets. Why would I do such a thing? oh remember the 9000 labels I mentioned earlier? right well its very likely that they actually won't use any of them ... or the wrong ones ... or assign to the wrong person, so I have to go find them and fix them. If I don't, i'll get yelled at, because clearly it's my fault.

- Moving on from Jira. As some of you might have seen in your companies, if you use things like TestFlight, HockeyApp, AppCenter, BuddyBuild etc. that when you release a new app version for testing, each version comes with an automated change-log, listing ticket numbers addressed ...... yeah we don't do that. No we use this shitty service, which is effectively an FTP server and a webpage, that only allows you to host the new versions. Sending out those emails is all manual ... distribution groups?? ... whats that?

- Moving back to Jira. Can't even automate the changelog with a script, because I can't even make sense of the tickets, in order to translate that to a script.

- Moving on from Jira. Me and one of the remote testers play this great game I like to call "tag team ticketing". It's so much fun. Right heres how to play, you'll need a QA and a PM.

*QA creates a ticket, and puts nothing of any use inside it, and assigns to the PM.
*PM fires it back asking for clarification.
*QA adds in what he feels is clarification (hes wrong) and assigns it back to the PM.
*PM sends detailed instructions, with examples as to what is needed and assigns it back.
*QA adds 1 of the 3 things required and assigns it back.
*PM assigns it back saying the one thing added is from the wrong day, and reminds him about the other 2 items.
*QA adds some random piece of unrelated info to the ticket instead, forgetting about the 3 things and assigns it back.

and you just continue doing this for the whole dev / release cycle hahaha. Oh you guys have no idea how much fun it is, seriously give it a go, you'll thank me later ... or kill yourselves, each to their own.

- Moving back to Jira. I decided to take an action of creating a new project for my team (the mobile team) and set it up the way we want and just ignore everything going on around us. Use proper automation, and a kanban board. Maybe only give product a slack bot interface that won't allow them to create a ticket without what we need etc. Spent 25 minutes looking for the "create new project" button before finding the link which says I need to open a ticket with support and wait ... 5 ... fucking ... long ... painful ... unnecessary ... business days.

... Heres hoping my head continues to not have a bullet hole in it by then.

Id love to talk more, but those filters ain't gonna fix themselves. So we'll have to leave it here for today. Tune in again for another episode soon.

And remember to always practiseSafeHex

So I've been screaming for months that push notifications are not reliable enough to build critical functionality on top of. Management won't listen and keep pushing ahead with making teams use it because its cheap and easy.

Been debugging an issue on/off for several weeks. Turns out someone in management asked the backend team to cut the expiration time of items down to 5 minutes to increase throughput (without telling mobile). Notifications are regularly taking +4 mins to get to the phones, leaving our users with barely any time to react. They are now complaining.

I swear if there is a single IQ point available between the whole team i've yet to see any evidence of it

So the remote manager who won't reply to my emails or slacks, won't invite me to meetings with product / design, won't ask for my opinion on deadline dates and won't tell me whats being said in meetings (despite repeated effort on my part to change this);

Has decided to send an angry email, cc'ing a bunch of people, about "constant deadline slippage" and poor planning on our part focusing on features that should have been de-prioritised.

ahem
*clears throat for maximum yelling rant-ability*

<rant>
I HAVE BEEN EMAILING YOU FOR FUCKING WEEKS ASKING TO TALK ABOUT THE DEADLINES YOU FUCKING COLOSSAL ASS CLOWN.

I'VE BEEN REPEATEDLY TOLD THAT THESE FEATURES ARE A MUST HAVE AFTER ASKING TO DE-PRIORITISE THEM, AND HAVE TOLD YOU THE DATES ARE NOT FEASIBLE.

ONE MORE, ONE MORE EMAIL OR BAD COMMENT AND I'M EXPENSING A TRIP OVER THERE, TO KICK YOU SQUARE IN THE NUTS AS HARD AS HUMANLY POSSIBLE. I'LL HAPPILY BREAK MY FOOT OFF IF NECESSARY, YOU USELESS PIECE OF SHIT.
</rant>

... the above is work appropriate to email back to him and all the higher ups right?

"years of experience" basically means nothing, both for people and organisations. You can work with someone who has 30 years experience who knows nothing, and someone with 1-2 years who's practically an expert.

Joined a large multi-national fresh out of college, that had been around for +90 years. I expected them to know software development inside and out. Didn't expect to see so many failed projects for stupid reasons, so many over sights, so many .... morons, to be honest.

Worked for a startup company where most only had 1 or 2 years more experience than me and learned so much.

Worked for a small company where everyone had 1.5 - 2 times my experience, where I learned the meaning of "bewilderment".

Never feel small, or less valuable because of a number. Theres a good chance you are working with jackasses - practiseSafeHex

Acceptable places to leave your bag when you get in, in the morning:

- Under your desk
- On your desk
- Infront of your locker
- On the back of your chair
- etc.

Unacceptable, is to throw your bag behind you and to the right, so it ends up in the middle of the floor and behind my chair.

Consistent use of this space, and me tripping over it will result in 2 things:

1. I will intentionally run over your bag, back and forth until I am satisfied everything is broken.

2. I will then pickup said bag and throw it, with force, at your head.

Senior development manager in my org posted a rant in slack about how all our issues with app development are from

“Constantly moving goalposts from version to version of Xcode”

It took me a few minutes to calm myself down and not reply. So I’ll vent here to myself as a form of therapy instead.

Reality Check:
- You frequently discuss the fact that you don’t like following any of apples standards or app development guidelines. Bit rich to say the goalposts are moving when you have your back to them.

- We have a custom everything (navigation stack handler, table view like control etc). There’s nothing in these that can’t be done with the native ones. All that wasted dev time is on you guys.

- Last week a guy held a session about all the memory leaks he found in these custom libraries/controls. Again, your teams don’t know the basic fundamentals of the language or programming in general really. Not sure how that’s apples fault.

- Your “great emphasis on unit testing” has gotten us 21% coverage on iOS and an Android team recently said to us “yeah looks like the tests won’t compile. Well we haven’t touched them in like a year. Just ignore them”. Stability of the app is definitely on you and the team.

- Having half the app in react-native and half in native (split between objective-c and swift) is making nobodies life easier.

- The company forces us to use a custom built CI/CD solution that regularly runs out of memory, reports false negatives and has no specific mobile features built in. Did apple force this on us too?

- Shut the fuck up

My LinkedIn profile bio:

... however I’m not interested in hybrid mobile or contract work.

My LinkedIn “notes to recruiters”:

... I’m not interested in hybrid mobile or contract work.

My preferences:

- ticked full time permanent
- listed native technologies in the tag selector.

Email this morning:

Hi are you interested in the below role:

Role: Hybrid mobile developer
Salary: xxxxx
Type: 6 - 12 month contract.

No I am not you fucking fucktard. Read my fucking profile or go fuck yourself with a fucking cactus!

A tool I built for my past company just got nominated for a European Data Science and AI award!!!

I'm over the moon that something I built is up for such an award. Be early next month before winners are announced. Oh and given I don't work there anymore, how I was told about it is a REALLY funny story .... I wasn't.

Saw a Linkedin post from my ex-manager congratulating the company and the org for great work done. He/They just forgot to mention the fact that me and another ex-employee did everything, left it practically finished and completely changed the direction of the project within the first month as their plans made no sense.

fuckers.

Dev manager: great news guys. We’ve built a new tool to do automated testing on apps. We’ve gotten rid of the old Appium solution we were using and built this new one.

Me: why not just use the inbuilt native stuff? Click to record works really well.

Manager: nah we thought it would be more flexible to build it ourself.

Me: ... ok ... moving on ... how does it work?

Manager: well this new .jar, you download it, pass in a config file, setup up your simulator and appium and the jar will do everything for you.

Me: ... wait you said you hate Appium? Now you’ve built a wrapper around it? And it doesn’t even set everything up, you’ve to do it all by hand?

Manager: oh we had too, would be too much effort to replace it. Don’t worry we can now write all our tests in .yaml config files instead of using Appium.

Me: so we’ve lost the ability of auto-complete and type ahead, everyone has to upskill on a new tool, it offers no new features over what’s available out of the box and we’ll have to deal with new bugs and maintenance and stuff our self ... because we need more flexibility?

Manager: oh don’t worry. The guy who built it is staying here. He’s going to deal with bug fixes and add features. He’s only one guy, but he’s really sharp, it’ll be great for us and the team.

Me: ... ... ...

*audible noise of soul breaking*

Me: ... ok thank you. I’ll look into this new tool

Product sending an email: Can I confirm feature A is all set for its release on April 30th?

Me: ... what? no that feature is going out with Feature B, that was pushed back to June because of the server issue.

Product: No, the release plan document says April 30th for this.

Me: ... theres 6 copies of this doc now. Someone is after deleting my comments saying "releasing with Feature B". Oh look heres a link to another doc that says this. See Feb14th "Will go out with Feature B". This is because they are touching the same code, we can't separate them now without re-writing it.

*Me to myself*: Ha product are going to hate this, their shitty processes have finally caught up with them.

*next day*

Other manager: So heres my plan for the app release x, y, z.

*Me to myself*: ... his plan? this is my app, I mange this. What the hell is this?

*reads email thread*

*Me to myself*: ... oh so product really didn't like my reply, took me off the thread, sent a response to all the other managers asking for alternatives, CC'ing upper management. The same upper management I had a private conversation with yesterday about how shit our product team are.

*cracks knuckles*

I'm going to enjoy writing this reply.

If the below is you, please stop. I'm starting a revolution called #AnswerTheQuestion

A: Hey, just checked your code, you have a huge security issue in XYZ, you should really address that.

B: Oh god I had no idea, how do I fix it?

A: Well it depends on how you *want* to fix it, no one solution is always the right one.

B: ... Ok, well could you give me some advice?

A: Well, there are many ways to approach this kind of work, but all I can say is that this way, is definitely not the correct one.

B: ... Ok, well how would you do it?

A: That would depend on the customer requirements.

B: ... the requirements is to have a website that isn't easily hackable, what do I do?

A: Nowadays, its pretty hard to make a website completely not hackable.

B: ALL THE SERVERS ARE SHOWING RED, PLEASE HELP ME!!!

A: ........ you really shouldn't prejudge colours. The colour red doesn't always mean danger, depends purely on the use case.

Me: *Installs travis*

Dev: oh what's travis?

Me: it's a continuous integration tool I wanna setup.

Dev: ... contin.... ?

Me: continuous integration, a tool that performs builds.

Dev: ah!, is it the new version of that deprecated tool we were using "client access"?

Me: ... no ... that's an authentication service that generates and stores oauth tokens. This is the continuous integration tool I told you about yesterday (and last week and the week before).

Dev: ... contin....

Me: ... con ........ continuous integration. It listens to branches on GitHub, downloads, builds, tests and then deploys the code.

Dev: ah ok ok, cool.

I would bet my monthly fucking salary he can not repeat what I said, tell me what oauth is, or explain what he's working on at the minute.

Jesus at this rate I'd bet my salary he can't tell me my name.

save a life, check its not production

Having a server with a lower spec CPU and RAM than dev machines, to ensure that if it works on the dev machine it will always run perfectly on the server.

This means we can avoid any debugging tools or techniques (including console logs), because “it will be perfect and it’s not necessary”.

Remote manager: Hey, that contractor you are working with that sits with me. We are thinking of sending him over to you guys, get him a visa, pay relocation and all that stuff and have him sit with you guys as a full time employee. What do you think?

Me: .... eh ... look I have to be honest, that guy is awful. He doesn't listen to me, constantly working on other things, and the architecture he forced onto the rest of the team is some of the worst i've ever seen.

RM: hhhmmmm, ok but what if we have him report to you, can you whip him into shape?

Me: Honestly I think theres too much effort involved. We are very short staffed. I'd prefer to hire someone else here who has more experience. Its a firm no from us on this guy.

RM: Ok, understood, thanks.

*2 weeks later*

Contractor: Hey guys, was chatting to my manager last week and he said the company is finally looking to convert me to a full time employee, and best of all he wants to move me over to sit with you guys. Isn't that great?

..... not really no

This being the view from my desk

- "Finance are too busy to look at this"
- "Finance have too much to do"
- "We can't this sorted at the minute because finance are overloaded"

Finance just sent me a request for "detailed description" for each business trip i've made. Attached is a spreadsheet report with 122 columns detailing every facet of my travel expenses that they have recorded so far. Not even just one row per trip, but one row per item, like:

- Trip 1 - Airport parking: .....
- Trip 1 - Airfare Outbound: ....
- Trip 1 - Airfare Inbound: ....

This is way you are too busy, because this is fucking ridiculous. Fix your shitty process and stop bitching.

FYI, your "detailed descriptions" can be found in the contracts we've signed, which outline all the travel needs, which you've already reviewed and signed off on. Get your shit together and stop bugging me

Spent most of the day debugging issues with a new release. Logging tool was saying we were getting HTTP 400’s and 500’s from the backend. Couldn’t figure it out.

Eventually found the backend sometimes sends down successful responses but with statusCode 500 for no reason what so ever. Got so annoyed ... but said the 400’s must be us so can’t blame them for everything.

Turns out backend also sometimes does the opposite. Sends down errors with HTTP 200’s. A junior app Dev was apparently so annoyed that backend wouldn’t fix it, that he wrote code to parse the response, if it contained an error, re-wrote the statusCode to 400 and then passed the response up to the next layer. He never documented it before he left.

Saving the best part for last. Backend says their code is fine, it must be one of the other layers (load balancers, proxies etc) managed by one of the other teams in the company ... we didn’t contact any of these teams, no no no, that would require effort. No we’ve just blamed them privately and that’s that.

#successfulRelease

What a day and what an achievement!!!

Today ladies and gentlemen I broke my record for number of passive aggressive “as per last email” comments, in a single email.

I now stand at 11

Today is a great day and I’d like to thank everyone not reading my emails who got me to this point. You guys are the real record holders!

Product replying to Jira ticket: We think this issue has been resolved. Can you please reach out to the user and confirm?

Customer care: User xxx has responded to say she "has given up in frustration, and the app simply doesn't work". She has requested to have her account deactivated. This user has requested to not be contacted any further by the program.

Hows your day going devrant? mines going VERY well

Well today I got a fantastic surprise (truthfully). We hired a dev some months ago, who was on 6 months probation and, to put it politely, he was not going to pass it.

*side note: for details of some of the above, read my last 10 or so rants. They are pretty much all him.

Anyway, management put him on an improvement plan to make sure everything was fair, it wasn't working out, but they said we had to finish it to be fair.

So we had another 2 weeks left when he announced last night he's leaving for a new junior role, technical but not a dev.

Months of stress, heartache, bewilderment, late nights and weekends all just came to an end.

The English language fails me to express my overwhelming joy at this moment. The only way I can come close to it is to say that when he made his announcement, a colleague told me I should stop smiling as it could be taken as being rude.

I'd like to take this moment to thank the community for supporting me over the past few difficult months. Without you I probably would have tried to kill him with my dev rant stressball.

Thanks,
practiseSafeHex

Assume the sales team lied

HR: Hi we got your application. We'd like to schedule a call. Can you fill this out to pick a time?

Me: Sure, sorry first I'd like to ask a question. You are based on the other side of the country and i'm not able to relocate. Are you open to remote workers? Your job spec didn't mention either way.

HR: GREAT question! At this moment no we are not. We need people here on site. If you'd like, we can have a call to discuss if you fill out the form.

Me: ..... take time out of my day so you can tell me "No" again? ..... i'm alright thanks

Sales manager: Hi all, we are launching a new internal hackathon. Form up a team with the right expertise to help with address the problem statement and get going!

Me: what’s the problem statement?

Sales manager: you have to sign up first. There’s proprietary company info with our plans for next year involved. You have to agree to terms and conditions before continuing. Legal say so.

Me:

*signs up*,
*fills in docU-sign*,
*clicks through 3 other screens*

Ok let’s see this problem statement.

“What new and magical customer experience can you create and launch to win in our markets”

... that’s not a fucking problem statement ... and why the fuck does that require filling out a docu-sign form to see?

I REALLY fucking hate legal / sales people. Wasting everyone’s time.

Had a follow up meeting today to resolve the issue of Product ignoring our comments about possible issues, better ways to do it etc.

New rules:
- We are allowed to suggest to Product that they might be doing something wrong
- We are not allowed to tell product they are doing something wrong
- If Product don’t listen, that’s fine, we will document our comments to protect us later.

Conclusion:
Product are too sensitive to have a conversation with. We are now going to let them fuck everything up, make some notes and say “I told you so” at a later date.

Maturity at its finest ladies and gentlemen.

Me: Why is there such a delay between the app and the hardware device?

Colleague: Ah, same old same old, TCP is just an inefficient protocol. We should stop development and build our own replacement to TCP.

(PS. The actual problem was his code)

Got very little sleep last night, not in a great mood to begin with. Came into work to find someone borrowed one of my cables that I need and hasn't returned it. It was wrapped around a few things to keep it tidy, all of which have been moved, stretched, bent etc. Now my battery is running low and he has emailed to say won't be in for 30 minutes.

Think the only reasonable course of action in a just world, is for me to strangle him with the cable when he gets in. I mean come on, whats the alternative? Still haven't gotten that pen back from last year ... this place is going downhill fast!

CS lecturer and I were sitting in the canteen trying to discuss something on my laptop. While waiting for it to load this is what we discussed:

Me: funny story, this weekend I was out with my friends an.......

Lecturer: *hang on* ... you have friends?

Recruiter: hi, I have an iOS Developer role. Would you be interested?

Me: sure, send me on the spec.

Recruiter: ok great so for this Full stack app developer role we are looking for someone with:

- 5+ years embedded C/C++ experience
- 5+ years of working with Windows and Linux
- Native Android development
- As well as Native iOS experience

Interested?

Me: ......... ok buddy, you and me are going to have a little chat about what “iOS Developer” means

Me: Hi Guys, theres no docs on our custom push notification / deeplinking implementation. I've tried to work backwards from a QA testing doc to add new links. Can someone tell me if this is all ok? It seems to behave a little weird.

Dev: Looks ok, but we've moved to the braze platform for sending notifications. You'll need to trigger braze notifications now. Test that it works ok with that <confluence-link>

*hour later*

Me: I've tried the debugging tool, both with my payload and one of the samples from the link. It displays on the phone, but tapping it doesn't trigger the deeplinking.

Dev: No it works, try one of these <screenshot of samples I used>

*hour later*

Me: Tried it again on the real device to make sure, as well as on develop and master. Not working with those samples or mine.

Dev: No it does. It comes in here in this library <github link to line of code>

Me: ... Nope, debugged it, it doesn't get passed the next 'if' check on the next line as its missing a key/value. The whole function does nothing.

Dev: Oh do you want to send a braze notification?

Me: ..... you told me I had too .... yes I guess.

Dev: ok for a braze notification it works different, send this <entirely different sample no where on the link>

Me: ...... but ..... this is only for braze notifications ..... why .... all the samples have deeplink url's .... but they don't ....... are you ..... FFS!!!!! !@#?!

(╯°□°）╯︵ ┻━┻

┻━┻ ︵ヽ(`Д´)ﾉ︵ ┻━┻

(ノಠ益ಠ)ノ彡┻━┻

┌П┐(ಠ_ಠ)

I’m sorry I didn’t read your marketing email within 2 minutes of getting it. Please forgive me.

So i've been put in charge of bringing the devs together to form a small dev team, instead of having 3 separate devs (including me) sitting apart on separate projects. The idea was to have us talk more, work together more, learn more about the other projects, reuse more code etc.

(I've been arguing to let us do this for a while)

So I asked my manager could we move to the 4 desks in the corner, so we can have our own space, talk without having to book a meeting room each time etc. Its also a bit quieter over there and we all really need that in our noisy office.

Manager sent me an IM today while I was working from home to tell me we can have the desks. Was super happy, messaged the devs to tell them they can start moving.

Just got a message from one of them to say our manager has started moving his stuff over too. Seems he agreed with me that it is quieter over there and he doesn't like the noise either ... so he's joining us.

A huge part of the move was us wanting to work on side projects to automate and speed up various things in the team, that he has been against. We know we can make huge improvements but he doesn't see it. He's only interested in Word, Excel and Powerpoint.

So now we have our space, and anytime we try to work on something we are actually interested in, we'll have a little voice in the corner to pop up and point out what other things he deems more important and tell us to stop wasting our time.

Pretty fucking annoyed to be so happy and then get shot down like that. Happy weekend everyone!!

Me: hey I have a major issue I need to discuss. Would you be free tomorrow at any of these times: A, B or C?

Him: Yes

Me: ... ... ... ok I’ve a new issue I need to discuss with you right now!

“Your time zone is not my concern” - manager of the backend team

I asked if there’s another way for us to get test data into QA. That doesn’t involve us staying on until 9pm to get a backend dev to modify the db manually, everyday.

My morning (RO = remote office):

Me: Your xxx implementation is very strange.
RO: Yes we are following a new example from experts in this field. See this link.

Me: Paragraph 1, use xxx class in these situations. Were not doing that.
RO: Yes we had problems with that, we decided to skip that.

Me: Paragraph 2, always use xxx when accessing data. Were not doing that.
RO: Yes that create many bugs, we skipped that.

Me: This section on debugging says to enable this flag while in development to allow the IDE to alert you to issues.
RO: Yes this causes the app to crash constantly. So we took it out.
Me: ... because its finding issues ... and telling you where the problem is, with an error message.

... your not following the experts at all.

RO: We are!, please read the link we provided.

... this will be discussed on my exit interview

Them: We really need you to fill out this sheet today with estimated release dates.

Me: I really need you to respond to any of the emails I’ve sent over the past week, asking questions about what these tickets mean.

Subject: FW: Twilio integration
Date: 20th June
From: <program-lead>

PractiseSafeHex I need you to fill in the dev completion dates for the Twilio task for the mobile team by EOD today. Backend have already supplied theres. Otherwise I will be forced to mark the task as “At Risk”. Please let me know if there is an issue or you are blocked.

—- Begin Forwarded Mail ——

Subject: Twilio integration
Date: 18th June
From: <program-lead>

Hi All,

Documenting today’s meeting minutes. Backend confirmed they will handle the Twilio integration from their side entirely. There will be no mobile work required for this task.

Thank you,
<program-lead>

Recruiter: Hi practiseSafeHex, I’ve looked at your LinkedIn profile and you look like a perfect fit for my new client. The role is a lead Java developer with experience in .......

Me: Where on my profile have I listed or mentioned Java in any way?

LinkedIn Notification: a person who chose to remain anonymous, with the title “Recruiter” just viewed your profile.

Wow, I wonder who could it possibly be? I’m stumped!

Also probably the first time he did look. Getting fed up with these asshats

Yes of course we can have a fourth meeting this week to discuss possible KPI’s for the project.

I have a suggestion though, since the first deliverable is 3 weeks away and it doesn’t work yet, maybe I could spend time ON the project ... so I can build something that could be a KPI ... and not piss off the other companies for delivering nothing.

Of course I’m not a manager, so what do I know, but this shit might be why people keep leaving the team. Perhaps devs don’t enjoy having no time on the project while simultaneously being yelled at for not getting it done.

The 4 stages of collaboration:

- Stage1:
Hey dude, I setup some online docs and left some instructions / discussion points in slack, but you haven't been logged in. Can you login and have a look when you get a chance?

- Stage 2:
Oh Hey, did you ever get a chance to have a look at those docs / discussion points?

- Stage 3:
Hey, look this is due by close of business tomorrow, can you take spend an hour on it before you leave?

- Stage 4:
*loads shotgun* HEY YOU! ... sit here, login to that ..... STOP CRYING AND HURRY UP ..... see that right there? thats missing your input, you have 15 minutes left ... GO!

I'm fast approaching stage 4 and loading my efficiency shotgun as we speak.

Dev: To send push notifications, please open a ticket to get access to the new tool we are using which is dedicated to managing push notifications and push notification campaigns.

Me: ok done.

*5 days later*

Tool owner: Can you please add to the ticket the reason you need access?

Me: “To use it”

Waterproof S8 ... should have announced a fireproof one and made a joke out of it

“Do you think you might be a bit dramatic?”

Me: not at all

Also me:

So we had a dev on our team who was on a performance improvement plan, wasn't going to pass it, but decided to quit before it was over saving us 2 weeks.

I was ecstatic when he left (caused us hell). I knew updating his code wouldn't be great, but he was only here 6 months

"how bad could it be" - practiseSafeHex - moron, idiot, suicidal.

A little run down would be:

- Despite the fact that we use Angular 2+, one of his apps is Angular 1 ... Nobody on the team has ever used Angular 1.

- According to his package.json he seems to require both mongoDb and Cloudant (couchDb).

- Opened up a config file (in plaintext) to find all the API keys and tokens.

- Had to rename all the projects (micro services) because they are all following a different style of camelcase and it was upsetting my soul.

- All the projects have a "src" folder for ... you know ... the source code, except sometimes we've decided to not use it for you know, reasons.

- Indentation is a mess.

- He has ... its like ... ok I don't even know wtf that is suppose to be.

- Curly braces follow a different pattern depending on the file you open. Sometimes even what function you look at.

- The only comments, are ones that are not needed. For example 30+ lines of business logic and model manipulation ... no comment. But thank god we have a comment over `Fs.readFile(...)` saying /* Read the config file */. Praise Jesus for that one, would have taken me all week to figure that out.

Managers have been asking me how long the "clean up" will take. They've been pushing me towards doing as little as possible and just starting the new features on top of this ... this "code".

The answer will be ... no ... its getting deleted, any machine its ever been on is getting burned, and any mention of it will be grounds for death.

“No we don’t use the time zone info you send on each request. We get all the drivers for the store ID, choose one of them randomly and take their time zone. We have been assuming it will always be the same for all drivers for each store.”

This is my new favorite response to a Jira ticket in this company.

I may have to print it out and hang it on my desk

Friend: you really should give Windows another chance, it's really not that bad.

Me: are you in possession of the only Windows computer that doesn't blue screen whenever there's a strong breeze outside?

Friend: No ... That does happen every now and then.

Me: So what's great about it then?

Friend: Look at this cool wallpaper, it's a slideshow of pictures of my kids.

Me: ... stop talking to me immediately ... and sit over there.

I'll be moving to a new job soon. Myself and a colleague are working on a new feature before I leave. He's building an IoT device, i'm doing the backend work. Were testing a "ping" style system, where his IoT device replies to a message from the backend.

The JSON payload he's sending is {traitor: true}

Today @ 4pm:

New dev: I need help with this issue, i've been stuck on it all day.

Me: ok let's look ...... ok, and did you try google this?

New dev: ... no

Me: ... why?

New dev: well this is clearly my issue, why would I google it? I only google for things I don't know

Me: ... ok ... we'll do you know what this bug is then?

New dev: haha ok, fair point, I'll give that a try. Thanks for the tip.

Seriously, should I be worried? I feel worried

"Simply log into our portal to access a list of toolkits designed from the ground up to help with your given needs. Using our unique tailored framework we can .... "

Sandra, calm the fuck down. You have a website with some reading material, a form and a few buttons. Get over yourself.

follow on from my last rant.

I've finally gotten my new Jira project. Only thing I seem to have access to change is the Kanban board columns. Still has 50+ fields when creating a ticket etc.

Asked the support team handling the request if this was a mistake. He said no, i'll need to open another ticket to have those changes requested.

Opened and got a reply. Currently there are 2 versions of Jira running. They are working on consolidating them atm and won't help me right now until this is done. I've been asked to re-open my request after the consolidation is done in March 2019.

5 ... fucking ... months, so I can have a competent ticketing process.

He pointed me to a page explaining the move and listing all the changes taking place. Well lets look at the changes they are making that are so critical:

Change 14: Rename "More info" status to "Needs more info".

... Oh pardon me. I didn't realise such critical show stoppers were being addressed. Please do continue. Don't mind me, i'll just be over here taking 4 hours to create an Epic and 6 stories. As you were

YOU CAN'T JUST SWAP THESE DATES AROUND WITHOUT TELLING US AND EXPECT IT TO BE FINE, YOU USELESS FUCKING SKIDMARK!

... ahem ... sorry about that, just needed to vent ... as you were

Colleague: Hey want to get access to our repo so we can see each others code, collaborate, discuss design patterns etc?

Me: Yeah sounds like a great idea. Would love to get to know a bit more about how others are building mobile apps in the company.

Colleague: Heres the link to the iOS app: xxxxxxxxxx

*Opens link*
*looks around a bit*
*Opens cocoapods folder*
*Sees 89 dependencies*

Me: .......... actually, you know what, I have major deadlines coming up. I can't look at this right now. Lets talk in the new year.

*closes slack*

"Hi xxx, please stop asking me the same question. I've answered it 4 times already via email, slack and in person on our zoom calls, over the past 2 weeks. I do not own the ticket and have no idea of the status or the dates. Ask the owner."

- slack response I was forced to write this morning to the guy my company put in charge of the entire product (mobile, multiple backends, frontend etc.).

QA: When I open the app I get this strange error message that includes "No data connection could be established" near the start of it.

Me: I'll clean up how thats displayed, but the error means your phone doesn't have internet connection.

QA: No that can't be it, I do.

Me: You screenshot shows no WiFi or 3g / 4g symbols.

QA: No those are never there, please investigate.

Me: I have investigated and found that every other one of your screenshots had a WiFi or a 3g symbol. Example: <link>. Please check your connection and try again, i'll clean up the error display.

PM: Oh i've had an issue something like this before. We really need to show users an error screen. We can't just leave them on this screen with no error message at all.

Me: ... we have an error, thats what QA is complaining about, its not loading the text and displaying the error object.

Anyone else want to not pay attention and complain about something else that doesn't make sense? ... no? ... ok good, back to work then

Mobile app crashed a lot after latest release. Everyone called for a meeting to discuss the issue and find resolutions.

Engineering lead for backend team: well part of our problem is we haven’t had time to test everything fully. Maybe product could give us a list of all the features that can’t go down and we’ll prioritize those for testing?

Product: ... ... ... all of them?

Me: laughing hysterically while on mute

Have a week off, no yelling over email, no sarcastic slack messages, no shouting to myself in the office ... honestly have no idea what to do with myself ... might try this “being happy” thing everyone is always going on about

10am: meeting invite for 9:30pm my time.

*decline with comment: can’t attend*

9:40pm: email, “is anyone from engineering going to attend?”

*ignored*

10:05pm: email, ok the results of the call were X, Y and Z. But we’ve been asked to supply architecture diagrams (which don’t exist). Can we do this today?

*ignore*

10:45pm: email, guys this is urgent can we do this ASAP!

*ignore*

... welcome to the new world bitches, bite me

My teams current process is:

1) Asked by product to create “T-Shirt size” estimates, also known as a WAG (wild ass guess). The process is the mental equivalent of throwing darts while blindfolded, after being spun around in a circle and pointed in the wrong direction.

2) Product make firm commitments to upper management based off these. Ensuring them that all these features will make it out in Q2.

3) 4 days before Q2 starts, product ask engineering to figure out the real estimates based off no concrete information what so ever.

4) 4 Weeks into Q2, product provide the missing information.

5) Engineering inform product that the estimates are out by a factor of 1.5 - 3 times the original estimates.

6) Product sends angry email to upper management that through not fault of product, engineering are unable to meet the deadlines.

7) Everyone shout and complain until 1 week before Q3, then see point 1.

Following this process, you and your team can be just as delightful as me.

That’s the practiseSafeHex guarantee!

I've been wondering for a while, how the backend my team has to use could have so many issues. I was convinced they had no alerting system in place and have been commenting on it for a while now, and complaining about it.

Was on a Zoom call with one of the backend devs today, he shared his screen and had his email open. I saw a folder he had setup called alerts, and sub folders under that. One of them was named the name of the service/app we are using ... it had over 360,000 un-reads ... and emails are automatically deleted after 4 months in my company.

So they have alerts setup, they just don't care ... problem solved. Enjoy your weekend folks!

Don't cha just love it when you download your "native" desktop application to host a meeting, only to find out its actually a wrapper around a browser?

How did I find out? Well I innocently tried to drag and drop an image to share, only to have the browser open and render that file instead of uploading it, killing the application it was running behind it, closing the meeting for everyone on it ... and not even be able to access a back button to re-open the session.

viva la hybrid!

Today I was asked to decide on a handheld or "madonna" microphone for a conference I have to speak at in 2 weeks. Its time to come clean, I never thought the day would actually come, i'm far too terrified to actually go through with it. I just wanna write code in my dark little corner and be left alone. I wonder can I get out of this or is it too late

Got a LinkedIn message from a recruiter looking to know if I’m interested in a full stack developer role, to only work on front end. The requirement is that I know one of:

“go, node.js, rails, python, C# .NET, RoR etc”.

I wonder who it is that doesn’t have a clue, company or recruiter (or both?).

I’m actually going to reply to this one for fun to try figure out this mess (yes I’m that bored)

12 - 1pm is lunch time. What the hell is it with this team and arranging meetings for this time, does nobody eat?

*Propose new time*

Justification: ... i'm fucking hungry

Should you use webpack in your next front end application? Well heres one question to ask yourself to help you decide:

While developing your application, do you feel your application could benefit from the introduction of 14,372 impossible to understand errors, each requiring hours of research to debug ...

you do? well boy are you in luck!

Admin work, because its all manual:

- Each new project has to fill out an Excel tab in a workbook, with a list of all the major tasks and who is responsible. This then needs to be used to create a Gantt chart, manually, in the same tab, showing in what month a task starts and ends.

- Every month we have to manually enter status updates into a powerpoint slide on a shared deck. Which has a collision at least once per month.

- Once a quarter we need to do something similar as the powerpoint slides, but into a word doc instead.

- Once a week we need to track our time on projects in a tool that can't be integrated with (no API or anything). Meaning we can't link up a ticket tracking system to it, so again, all manual.

- Once every 6 months a new round of research funding opens up and we write proposals. The status for which are tracked in another Excel spreadsheet, manually, once a week until the deadline.

- The instructions for what to do with the proposals are so vague and badly documented that there is an unwritten rule, that for the first time you will have to ask a bunch of questions to the project manager. This is accepted by everyone and its just the done thing.

- Everything is stored in a dropbox style system, which has become so cluttered I can only find resources by saving the links sent out previously.

- Some of these updates / reports also get a 1 hour meeting for everyone to stand up and read out what they've entered.

- From time to time random things will need to be reported on to the higher ups (how many publications, research papers, patents, times and dates etc.). Again rather than a tool, a new Excel spreadsheet is whipped up and emailed to everyone on the team. Whoever sent it out, then has to merge the 20+ copies into 1 doc.

- Some of the staff (mostly the devs), use a ticket tracking system to keep track of everything. Management refuse to use it to track the things they need. Instead we have to copy paste from it into the word docs, powerpoint, excel etc.

- By far the most annoying. Management force all the above as they need the info for finance, accounting, legal etc etc. So we have to do it, but whenever there is a question from legal, management send the question to us. So despite having documented every facet of everything imaginable, it all gets ignored in favour of endless emails.

I once tried to to put an end to all of this madness by proposing the use of a ticket tracking system, and then building reporting tools on top of it.

... I was told that it "wasn't appropriate". Still don't know what that means.

One of my top 10 worst meetings, was for an interview for a job I really wanted. The guy started off the technical interview by asking me about language features that had been replaced since before I started learning the language. Told him when I started learning and his reply was:

"Yeah I see that on your CV, but come on, you MUST know this stuff".

eh no asshole, because its been removed for 4 years, you MUST know its not relevant

Colleague started a slack channel for our team, management wanted nothing to do with it. We used it to work and have a bit of fun.

Some push / drive came form somewhere and now all the managers are on it. Yesterday I was told my screenshot and "snarky comment" are not appropriate for the workplace and to delete my slack message.

My comment was a joke about about a new app the company has to use "to increase efficiency" that broke and wouldn't let me do what I needed. It wasn't offensive, demeaning, sexist to anyone or even contain any bad language.

How petty and childish to be monitoring a private channel making sure everything is positive. We all joked that from now on our meme's must be about how awesome the company is and how much time we are saving on a daily basis.

God forbid we're allowed to speak honestly and openly or have a bit of fun.

Internal support article to get access to a tool:

"To get access click 'NO' in the 'was this article helpful section' and open a support ticket, making sure to mention the tool you are looking to get access to"

What fucking fresh hell is this? Why not have the article, contain the fucking link to open the ticket.

You have intentionally put up a useless article, in order to hack your way around this stupid system.

keeping up with the ridiculous job titles, WTF is an "iOS King"?

I would actually avoid applying for that job as I couldn't bare to call myself that, or have others

Colleague: Oh i've noticed your PR uses tabs instead of spaces, we use spaces, can you change yours please?

Me: ..... can you leave the building immediately, for your own safety

Typically my low motivation stems from some form of management dickhead-itis, too much red tape or restrictive processes (current place took 3.5 months + 2 forms to order a webcam our client had paid for as part of the project ... it was €45).

How I deal with it? I try to give a go changing it, talking with managers, explaining the issues, suggesting alternatives. Such as removing your head from your ass, when done, it can have a wonderful impact to the team.

When that fails (not if) ... I quit. Which I actually just have. Got a job offer last week, although I really wasn't a fan of how things were going on this team, I was working on some cool projects and wasn't sure what was right for me, career-wise.

Then I had a argument with a new manager as he doesn't remember agreeing to allow the developers to estimate their own tasks. He was annoyed I told him we can't do X in 2 weeks, we previously asked for 2 months.

That was enough to knock me over the edge, so I handed in my notice, took the job with much more management style responsibility and hoping for a fresh start.

It's getting close to that time of year when we are all encouraged to think of others and spread joy around the world. I've decided to go against my usual snarky/anti-social nature, and do something to help others this year.

I'm announcing the practiseSafeHex charitable fund, to give back and help others.

This fund will invest in cutting edge medical research to detect the genetic abnormality in humans that results in project managers not being able to comprehend the simplest of concepts.

Together we can find the reason why the concept "more meetings = less work" is uncomprehendible.

Together we can discover why we can't use an automated bot to generate reports, instead of spending hours in excel spreadsheets.

And together we will find a reason why the answer to the question "can we please just try it?" is always "No".

We do this not for ourselves for short term gains, we do this for the greater good. Together we can find the cause and build a test to filter these people out. So that never again will stressed out developers have to deal with these petty ridiculous issues.

Together, we will solve this!

Thanks,
practiseSafeHex, CEO and managing director of the practiseSafeHex charitable fund for the betterment of developer sanity

Was asked to help a team of interns in a remote country, finish an app. Not only were they terrible at literally every aspect of development, but were arrogant and argued their "new" ways were right.

Spent weeks on the project being nice, trying to help them, sending them links to standards and documents, pointing out unit tests shouldn't be failing, everyone needs to have the same versions of the tools etc. You know, basic shit.

Things got quite heated a few weeks in when they started completely ignoring me. Shit was breaking all over the place and crashing, as I thought we were going to build it one way, and they went and built it another.

Was practically begging the team architect and my manager for help dealing with them. Only reply I got was the usual "were aware of the problem and looking into it" bullshit.

Eventually after the app was done, a mutual agreement was reached that the 2 teams would split (I maintain they were kicked out). All the local devs were happy, managers had mentioned how difficult they were and it would be great for us to finally work on our own.

So I thought everything was fine ... until my end of year performance review came along.

Seems I'm quite poor at "working with others" and I "don't try hard enough with others", it was clear I was struggling with the remote team and "made no effort".

WELL FUCK RIGHT OFF

Not being cocky, but I've never had anything like that in a performance review for the past 7 years. I'm a hard worker, and never have trouble making friends with colleagues. Everyone in the country complained about these remote fuckers, even the manager, who I begged for help. And the end result is I need to work harder.

I came in early, stayed late to fit their timezone, took extra tasks, did research for them, wrote docs. And I was told to work harder.

Only reason I didn't quit, was my internal transfer request was approved lol. New team is looking at projects orders of magnitude more impressive, never been happier.

Random dev online: Any chance you could help me figure out how to use something the company you worked for wrote? I need to do XYZ

Me: I didn't write it but sure. Theres a doc here about the full process of doing XYZ <link>

Random dev 5 seconds later: But how do I actually do it? The link doesn't show how to do it via code.

Me: You'll find if you actually read it, that it does. Because I checked. Good day

Team quarterly capacity planning:

- Confluence document created with a big table (+100 rows) by product / business. Each row is something that needs to be worked on for the coming quarter.

- Row 1 could be an Epic with 15 tickets attached. Row 2 could be adding a single log to our analytics. No consistency.

- For each row, we create a separate confluence document with the "technical details". 75% of the time these remain blank. 1% of the time there is something useful, the rest its a slightly longer version of the description from the bigger document.

- Each row gets a high level estimate by the leads. 50% of the time without sufficient background info to actually do get it accurate.

- These are then copied into the teams excel spreadsheet, where it will calculate if we are over/under capacity.

- We will go backwards and forwards between confluence and excel until we are "close enough" to under capacity without being too much.

- Once done, we then need to copy them into the org/division's excel spreadsheet. This document is huge, has every team on it and massive 50pt text saying "Do not put a filter on this document".

- Jira tickets + Epics will now be created for each one, with all the data be copied over by hand, bit by bit, by product. Often missing something.

- Last week, at the end of this process for Q2 (2 weeks late), 6 of the leads were asked to attend a 30 minute meeting to discuss how to group the line items together because we had too many for the bigger excel spreadsheet.

- This morning I was told business weren't happy with one of our decisions to delay one line item. Although they were all top priority (P0), one of them was actually higher than that again (P-1?) and we need to work it back in.

... so back to step 1

- Mid way through Q2, a new document will be created for Q3. Work items that didn't make the cut will be manually copied from one to the other. 50/50 whether anything that didn't get done on time in Q2 will make its way to the Q3 doc.

- "Tech excellence" / "Tech debt" items (unit/UI tests, documentation, logging, performance, stability etc) will never be copied over. Because product doesn't understand them and assumes therefore that they are unimportant.

==================

PS: I'd like to say this was a rare event for Q2, but no. Q4 and Q1 were so bad, we were made assurances from the director of engineering that he would fix this process for Q2. This is the new and improved process (I shit you not) that has resulted in nothing tangible.

Me: Anytime 9am - 12 my time suits me fine.

Him: Sure, noon our time suits us fine.

Me: *talking to myself* I said no later than 12 my time, theres a 2 hour difference. FFS, uh, I'll have to cancel this, move that around, skip that, ARGH!!! fucking hell jackass ... FINE!!!

...

Him: That calendar invite is for 4pm our time, thats a little too late for us.

Me: ...... but they are 2 ..... 2 hours ahead so ..... oh, thats 10am my time .... oh shit

1. Finally publish some of my open source projects.
2. Career progression (move to more of a tech leadership role).
3. Stop taking shit from managers who know nothing about code.

Me: well guys, after the 4th attempt and a week of waiting, I’ve gotten a response from the remote backend team about the errors affecting this release. Which are the same issues affecting the last release 2 months ago. The findings are: “there is in fact some issue with the API”.

I’d like to thank everyone who put in so much effort to get us to this momentous step forward. We can expect a fix any year now.

*equally sarcastic colleague on another team listening in*:
oh wow, this months long thing has just been “some issue” all this time? Well that’s fantastic. You should mark the ticket as “done” and reply “thank you” for all their hard work.

..... I laughed so hard at how ridiculous all this is and the joke, that I nearly did, hoping someone from product/business would have to review it

WWDC was last night. Joined my companies "iOS" slack channel this morning expecting to see lots of activity about SwiftUI, Combine, Federated Login, New iPad updates ... but no. The only comment

"Does anyone else feel like the event artwork is lazy and uninspired?"

... I am just fundamentally in the wrong company

Have I mentioned lately how much I LOVE the stability of slack (and electron apps in general)?

Got notified of a new message in slack, clicked the channel and this is what I see, even after a restart. No content or UI controls of any kind are being rendered. No workspaces, no loading spinners, no errors, no warnings ... just nothing.

I don't give a fuck about your integrations, apps, giphy, video calls, search, threading ... I just want to read text.

Piece of fucking shit

Last night I met up with some old colleagues for food and drinks to have a catchup. Things have been stressful in work, was great to get out and have a bit of a rant and just relax ... until I saw the menu.

Hamburger:
xyz dressing / sauce, crispy onions ... and cheddar cheese.

That sir, is a fucking cheese burger, and just piss poor documentation. How have you managed to stay in business with such misleading information and false advertisements in your menu.

Thank you for ruing my evening!

Working on a project where the coordinator is insisting on using OneDrive. Lost the link he sent out in an email so decided to:

- Google "OneDrive": Eventually brought me to "office.live.com/...." with a view of my settings and apps ... no OneDrive.

- Spent a while using a bit of logic to click around and find it, forgot logic doesn't work well with MS products and ended up on Outlook instead.

- Spent a while searching for the original email with the link, found it, brings me to "...sharepoint.com/....".

- Inside sharepoint (OneDrive?) the banner says "Office 365".

- But the browser tab says OneDrive.

Are Microsoft just afraid of consistency at this point? I mean seriously, pick a name and use it everywhere. Why is that so hard? why is that so complicated?

"Users don't need or like detailed error messages. Just use a generic phrase like `an error occurred`. Visually it looks nicer and they won't read it anyway"

- Lead UI / UX Designer, large m.n.c, 10+ years experience

/* Shameless hack */

Hybrid apps

Who’s in a bad mood?

Boss: We need health data for this iOS app.

Me: Cool, so we'll use apples HealthKit.

Boss: No that requires the user agrees to it.

Me: ... well yeah ... its private data.

Boss: No we need it to work regardless. If the user says no to HealthKit, just give them textfields for all the metrics HealthKit has and they can enter manually.

Me: .... but ... eh ....

Boss: and we'll partner with some companies and support their devices.

Me: ... see, the thing is ...

Boss: We also need to store it locally and then sync it to the cloud app. What do you think?

Me: ... ... ... no

Co-worker keeps cursing in Spanish and then smacking the table.

When it happens I have 2 choices:

1. Keep suppressing the rage until I can't take it anymore and book a meeting room just to get away.

2. Ask him to keep it down, to which he replies sorry followed immediately by "can you take a look at this?", which turns into 20 mins of teaching him how to use google.

I'm one bad day away from taking a swing at him.

I've come to a conclusion today: Management are fucking with me. I know it sounds far fetched, but its the only thing that makes sense.

I was in a meeting today, discussing some bad emails back and forth. Part of my issue was the amount of time spent on useless meetings, or waiting around to give demos.

The meeting got cut short, so I could prepare a demo for a VP ... after an hour and a fucking half of waiting around ... theres no time to see my demo.

What the actual fuck, seriously .... seriously what the actual fuck. What if the name of mother fucking christ is going on with this team, that they call me into a mother fucking meeting to discuss the "developers attitude" only to go and cut it short ... so they can fucking waste my time ... for the second time in 3 mother fucking days.

Oh i'd rather fuck myself with a cactus than spend the rest of my days dealing with this utter bullshittery.

Starting to work with a new senior designer in the remote office (red). Spent 4 days explaining to him that we need .png's in multiple sizes for the app, trying to teach him to use Zeplin to let us export them. Everything failed, his manager told him to just send us the .png's via slack ..... has he seen a computer before?

It fucking staggers me how many backend/devops-y people don't understand what a client side "request timeout" is, versus a server side one.

What does it mean:

The client was fed up with the servers bullshit, and decided to piss off and not wait around for the server to take forever to respond, because life's too short.

How not to solve/debug this issue:

- "I've checked the API request in tool xyz, and it works fine for me"

Congratulations, you've figured out how to call an API once, in isolation to the rest of the application, and without any excessive load. And using a different client to me, with a different configuration. Lets get back to actually looking at the issue shall we?

- "I only see HTTP 200's in the logs"

Yep, you probably will in most circumstances, because its the client complaining about it taking too long, not the server. If the server was telepathetic and knew what the client was thinking/doing at all times, we wouldn't have half of the errors we do.

- "Ah ok, I understand ... so how do I solve this?"

Your asking me? I don't fucking know, I didn't build the server! Put better logging in place and figure out why sometimes it takes forever.

Jesus fucking christ

Currently in the middle of quarterly planning (its been fun so far). Needs to be signed off by business today.

- My team has ~25 man weeks available in terms of capacity.
- Looking at only priority 0 tasks, last night we calculated the ask from product stands at 64.
- Including P1's, P2's etc. its well over 100 man weeks.
- Email was sent around from business with a list of tasks, asking which can be dropped, de-scoped etc.

Product (non technical) response this morning:
- This one can't take 2 weeks, its not that complicated.
- This one needs to stay, It was originally a Q1 task.
- Can we make this one smaller? (currently only a 3 week task)
- 14 comments on other teams items.

<extreme-sarcasm>
... ah perfect, that cut down the items by less than half. We are now ready for the deadline in 4 hours to have all this signed off on. Great job everyone. Thanks for all the insightful discussions. Go team!
</extreme-sarcasm>

Backend: Sorry the fix we had isn't going to work. Turns out app is sending an "undelivered" status after you call the API where you claimed we had an issue. This is in fact the cause, please address it.

Me: We do not have an "undelivered" status anywhere in our codebase. We do not do this.

Backend: *CC product* turns out this issue is only affecting 0.1% of users, its very minimal. Lets push ahead with the release.

Product: Ok, lets go live.

Me: ... ... ... we all just gonna ignore that "undelivered" bullshit? ... ok ... very stable release, here we go.

Well I’ve had my LinkedIn status to open for a little while now. Time to check what exciting offers (me, an iOS developer / team lead) has received.

- Senior python engineer with multiple years machine learning experience.

- a job 3000 miles outside the only city I’ve marked myself as interested in.

- Architect for a .NET team.

- Senior UX Researcher.

- The same job for a bank 6 times. But each time they won’t initially give the name of the company. Only “my fav client to work with” until I respond.

... not much hope in this process

Do Travis CI's email subjects really need to say "Still failing". As if I don't feel bad enough.

Fuck you Travis i'm trying!!!