The colleague:

- I can't work, my chair is uncomfortable
- I can't work, my chair is not ergonomic
- I can't work, my desk is too small
- I can't work, my legs are uncomfortable
- I can't work, my keyboard is not ergonomic
- I can't work on this task, John knows how to do it better
- I will only work on <this> type of tasks. I will not work on others
*gets assigned <other> task; browses the internet all day; at the EOD task isn't even touched*
- I can't work with Jack, he's too noisy
- I can't come to the office on time, there's traffic in the city
- I couldn't come yesterday, I was out of town. No, I will not log a vacation day - I was NOT on vacation. It's personal
- I can't<...>

Manager, 2 days to the end of said colleague's probation period:
- I am very sorry to tell you this, but our attitudes are not in line and we cannot continue working together. Since this is your 5th warning, we have to let you go.

The colleague:
- What?? How come?? I did NOT see this coming... You can't do this! I work here! This is where I work and you can't fire me!

*got his things from his desk and left. Never came back*

Everyone at the office:
- YAYYYY!!!! Let's have a shorter day today and let's celebrate this riddance in a pub! (manager agreed)

#3 Worst thing I've seen a co-worker do?

A 20-something dev, 'A', back in the early days of twitter+facebook would post all his extracurricular activities (drinking, partying, normal young-buck stuff). The dev mgr, 'J', at the time took offense because he felt 'A' was making the company look bad, so 'A' had a target on his back. Nothing 'A' did was good enough and, for example, 'J' had the source control czars review 'A's code to 'review' (aka = find anything wrong). Not sorting the 'using' statements, and extra line after the closing }, petty things like that. For those curious, orders followed+carried out by+led by 'T' in my previous rant.

As time went on and 'T' finding more and more 'wrong' with A's code, 'J' put A on disciplinary probation. 'A' had 90 days to turn himself around, or else.

A bright spot was 'A' was working on a Delphi -> C# conversion, so a lot of the code would be green-field development and by simply following the "standards", 'A' would be fine...so he thought.

About 2 weeks into the probation, 'A' was called into the J's office and berated because the conversion project was behind schedule, and if he didn't get the project back on track, 'A' wouldn't make it 30 days. I sat behind 'A' and he unloaded on me.
<'A' slams his phone on his desk>
Me: "Whoa...whats up?"
A: "Dude, I fucking hate this place, did you hear what they did?"
<I said no, then I think we spent an hour talking about it>
Me: "That all sucks. Don't worry about the code. Nobody cares what T thinks. Its not even your fault the project is behind, the DBAs are tasked with upgrades and it's not like anyone is waiting on you. It'll get done when it's done. Sounds like a witch hunt, what did you do? Be honest."
A: "Well, um...I kinda called out J, T, and those other assholes on facebook. I was drunk, pissed, and ...well...here we are."
Me: "Geez, what a bunch of whiney snowflakes. Keep your head down and you'll get thru it, or don't. Its not like you couldn't find another job tomorrow."
A: "This is my first job out of college and I don't want to disappoint my dad by quitting. I don't even know what I'm supposed to be doing. All J told me was to get better. What the fuk does that even mean?"
Me: "He didn't give you any goals? Crap, for someone who is a stickler for the rules, that's low, even for J."

Fast forward 2 weeks, I was attending MS TechEd and I was with another dev mgr, R.

R: "Did you hear? We had to let 'A' go today."
Me: "What the hell? Why?"
R: "He couldn't cut it, so we had to let him go."
Me: "Cut what? What did he do, specifically?"
R: "I don't know, 'A' was on probation, I guess he didn't meet the goals."
Me: "You guess? We fire a developer working on a major upgrade and you guess? What were these so-called goals?"
R: "Whoa...you're getting a little fire up. I don't know, maybe not adhering to coding standards, not meeting deadlines?"
Me: "OMG...we fire people for not forming code? Are you serious!?"
R: "Oh...yea...that does sound odd when you put it that way. I wish I'd talk to you before we left on this trip"
Me: "What?! You knew they were firing him *before* we left? How long did you know this was happening?"
R: "Honestly, for a while. 'A' really wasn't a team player."
Me: "That's dirty, the whole thing is dirty. We've done some shitty things to people, but this is low, even for J. The probation process is meant to improve, not be used as a witch hunt. I don't like that you stood around and let it happen. You know better."
R: "Yea, you're right, but doesn't change anything. J wanted to do it while most of us were at the conference in case 'A' caused a scene."
Me: "THAT MAKES IT WORSE! 'A' was blindsided and you knew it. He had no one there that could defend him or anything."
R: "Crap, crap, crap...oh crap...jeez...J had this planned all along...crap....there is nothing I can do no...its too late."
Me: "Yes there is. If 'A' comes to you for a letter of recommendation, you write one. If someone calls for reference, you give him a good one."
R: "Yea..yea...crap...I feel like shit...I need to go back to the room and lie down."

As the sun sets, it rises again. Within a couple of weeks, 'A' had another job at a local university. Within a year, he was the department manager, and now he is a vice president (last time I checked) of a college in Kansas City, MO.

Tech startups, an analogy:

After 18 years going from help desk teams to NOC teams, telecom engineering and all manner of startups in between I have concluded the following:

Imagine wanting to start an aerospace company because you know how to fold a paper airplane, but not how to actually design and engineer an actual craft that will pass basic air worthiness checks.

That’s 99% of “tech” companies.

Discuss. I’ll make drinks.

What an absolute fucking disaster of a day. Strap in, folks; it's time for a bumpy ride!

I got a whole hour of work done today. The first hour of my morning because I went to work a bit early. Then people started complaining about Jenkins jobs failing on that one Jenkins server our team has been wanting to decom for two years but management won't let us force people to move to new servers. It's a single server with over four thousand projects, some of which run massive data processing jobs that last DAYS. The server was originally set up by people who have since quit, of course, and left it behind for my team to adopt with zero documentation.

Anyway, the 500GB disk is 100% full. The memory (all 64GB of it) is fully consumed by stuck jobs. We can't track down large old files to delete because du chokes on the workspace folder with thousands of subfolders with no Ram to spare. We decide to basically take a hacksaw to it, deleting the workspace for every job not currently in progress. This of course fucked up some really poorly-designed pipelines that relied on workspaces persisting between jobs, so we had to deal with complaints about that as well.

So we get the Jenkins server up and running again just in time for AWS to have a major incident affecting EC2 instance provisioning in our primary region. People keep bugging me to fix it, I keep telling them that it's Amazon's problem to solve, they wait a few minutes and ask me to fix it again. Emails flying back and forth until that was done.

Lunch time already. But the fun isn't over yet!

I get back to my desk to find out that new hires or people who got new Mac laptops recently can't even install our toolchain, because management has started handing out M1 Macs without telling us and all our tools are compiled solely for x86_64. That took some troubleshooting to even figure out what the problem was because the only error people got from homebrew was that the formula was empty when it clearly wasn't.

After figuring out that problem (but not fully solving it yet), one team starts complaining to us about a Github problem because we manage the github org. Except it's not a github problem and I already knew this because they are a Problem Team that uses some technical authoring software with Git integration but they only have even the barest understanding of what Git actually does. Turns out it's a Git problem. An update for Git was pushed out recently that patches a big bad vulnerability and the way it was patched causes problems because they're using Git wrong (multiple users accessing the same local repo on a samba share). It's a huge vulnerability so my entire conversation with them went sort of like:

"Please don't."
"We have to."
"Fine, here's a workaround, this will allow arbitrary code execution by anyone with physical or virtual access to this computer that you have sitting in an unlocked office somewhere."
"How do I run a Git command I don't use Git."

So that dealt with, I start taking a look at our toolchain, trying to figure out if I can easily just cross-compile it to arm64 for the M1 macbooks or if it will be a more involved fix. And I find all kinds of horrendous shit left behind by the people who wrote the tools that, naturally, they left for us to adopt when they quit over a year ago. I'm talking entire functions in a tool used by hundreds of people that were put in as a joke, poorly documented functions I am still trying to puzzle out, and exactly zero comments in the code and abbreviated function names like "gars", "snh", and "jgajawwawstai".

While I'm looking into that, the person from our team who is responsible for incident communication finally gets the AWS EC2 provisioning issue reported to IT Operations, who sent out an alert to affected users that should have gone out hours earlier.

Meanwhile, according to the health dashboard in AWS, the issue had already been resolved three hours before the communication went out and the ticket remains open at this moment, as far as I know.

Story of onboarding in the age of Corona!

Monday:
Office is big but almost empty, people are working from home. Guy welcoming me says he is not the one supposed to help me(he is sick I'm told) and the rest of the team is not there. The man I'm talking to is this other guys boss. It's OK I think it will work out.

Turns out this guy helping me is actually the CTO so he does not have that much time on his hands. He shows me were to get my computer and desk and hands me documentation to setup some software.

I spend the time before lunch installing linux, setting up git and some other software. CTO checks up on me once.

Then after lunch nothing...I look for him but he is in some meeting. I find some videos by myself labled "onboarding" on the company website. They are OK. I ask my deskmate if he heard what team I will be in. He doesn't know. I sneak out a little early since I have nothing left to do.

Tuesday:
The CTO is now also sick I see in an email when I arrive at the office. Still don't know what team I am in.

I spend the morning reading coding blogs and websites. After lunch I have a meeting. The only one in my calendar. It's about the product software architecture for all new employees. It's good but still no news about what team. I aimlessly read up on some software architecture untill I go home.

Wednesday:
I arrive at the office first, only the receptionist is there. I listen to podcasts until a few more people show up. I ask another guy if he knows what team I'm supposed to be in. He doesn't but laughs and says it was the same when he started last year.

I send out messages on slack looking for anyone that knows...still no one knows. I guess Im in limbo now. Perhaps i should just start making coffee for people or something...

Worst thing I've seen a co-worker do?

Its all relative, I've seen a lot of "worst's". Here's one of many I'll try to post.

A (married) DBA would often come to work drunk, starting fooling around with a couple of devs (which we suspect she had sought adventures outside the IT dept based on rumors), and ultimately got fired because she was caught sleeping at her desk (and she was drunk). One of her conquests told us she came from a very poor childhood and this was her first real high paying job. Abusive husband, being attractive herself, and being surrounded by other attractive, highly intelligent, single bucks (aka horny) that had no morals, equaled bad decisions.

She wasn't the worst, it was the assholes who took advantage of the situation that makes it in my top 10 worst things I've seen.

Worst hack/attack I had to deal with?

Worst, or funniest. A partnership with a Canadian company got turned upside down and our company decided to 'part ways' by simply not returning his phone calls/emails, etc. A big 'jerk move' IMO, but all I was responsible for was a web portal into our system (submitting orders, inventory, etc).

After the separation, I removed the login permissions, but the ex-partner system was set up to 'ping' our site for various updates and we were logging the failed login attempts, maybe 5 a day or so. Our network admin got tired of seeing that error in his logs and reached out to the VP (responsible for the 'break up') and requested he tell the partner their system is still trying to login and stop it. Couple of days later, we were getting random 300, 500, 1000 failed login attempts (causing automated emails to notify that there was a problem). The partner knew that we were likely getting alerted, and kept up the barage. When alerts get high enough, they are sent to the IT-VP, which gets a whole bunch of people involved.
VP-Marketing: "Why are you allowing them into our system?! Cut them off, NOW!"
Me: "I'm not letting them in, I'm stopping them, hence the login error."
VP-Marketing: "That jackass said he will keep trying to get into our system unless we pay him $10,000. Just turn those machines off!"
VP-IT : "We can't. They serve our other international partners."
<slams hand on table>
VP-Marketing: "I don't fucking believe this! How the fuck did you let this happen!?"
VP-IT: "Yes, you shouldn't have allowed the partner into our system to begin with. What are you going to do to fix this situation?"
Me: "Um, we've been testing for months already went live some time ago. I didn't know you defaulted on the contract until last week. 'Jake' is likely running a script. He'll get bored of doing that and in a couple of weeks, he'll stop. I say lets ignore him. This really a network problem, not a coding problem."
IT-MGR: "Now..now...lets not make excuses and point fingers. It's time to fix your code."
IT-VP: "I agree. We're not going to let anyone blackmail us. Make it happen."

So I figure out the partner's IP address, and hard-code the value in my service so it doesn't log the login failure (if IP = '10.50.etc and so on' major hack job). That worked for a couple of days, then (I suspect) the ISP re-assigned a new IP and the errors started up again.

After a few angry emails from the 'powers-that-be', our network admin stops by my desk.
D: "Dude, I'm sorry, I've been so busy. I just heard and I wished they had told me what was going on. I'm going to block his entire domain and send a request to the ISP to shut him down. This was my problem to fix, you should have never been involved."

After 'D' worked his mojo, the errors stopped.

Month later, 'D' gave me an update. He was still logging the traffic from the partner's system (the ISP wanted extensive logs to prove the customer was abusing their service) and like magic one day, it all stopped. ~2 weeks after the 'break up'.

Weirdest co-worker... We'll not to be judgy, but I think our industry is sort of home of the weirdos, but.. there's a few over-the-top weirdees we've had at work.

First one that comes to mind was a guy that walked liked Mr. Burns, hands behind the back & chest out. He microwaved the same thing every single day for breakfast - crackers, sausage and cheese. 😖This guy would get to his tasks very slowly, wouldn't talk to anyone on our team, and would go missing from his desk a lot, sometimes for extended periods (2+ hours). He really struggled to catch on to easy tasks. He quit after a few months, thank god.

Another weirdo we had was a girl who just couldn't dress to save her soul. She would wear these ugly ass sneakers that had neon colors reminiscent of bowling shoes (neon orange and green) and would wear turtlenecks and floor length skirts that all the colors just clashed. Her outfits were uglier than your great grandma's. Myself, her and 2 other girls dressed up as the Dr. Seuss things for Halloween, but did h1, h2, etc. tags instead and she put like rope from curtains in her hair with like 10 little pony tails. Just like wtf. She would play her gameboy at lunch and not talk to anyone much. She was really bad at our job, a lot of clients complained. She would literally read a book, braid her bangs or nap at her desk. Needless to say, she was fired.

Best co-worker quitting story?

"T" I've refereed to in previous rants knew he was close to being fired, so he jumped ship. 'T' sent the usual "I'll miss you guys" email to the department, except me (and a few others that didn't fall for his BS and not scared of him). His mistake was he sent the email out a day early (buddy forwarded me the email) and left the stuff (box of pics, books, etc) he planned on taking with him. One item in particular was a new company provided laptop bag, which technically wasn't his to keep (supposed to leave/turn-in any company provided equipment), so I grabbed the bag and hid it.

The next day I heard him slamming drawers (looking for the bag) and a loud cursing. Other devs peeking over the walls asking what's wrong.

Dev1: "Dude, what's up? Whatcha' looking for?"
T: "Nothing...fuck!...damn it...nothing...assholes...fucking assholes!"
Dev2: "Who's the ass? What's wrong?"
Dev3: "Need help looking for something?"
T: "No..no...nothing...I'm fine...making sure I don't forget anything."

'T' never found out who took the bag and I've had that laptop bag underneath my desk ever since.

Stop calling people by their old occupation titles. .
Please address them by using their new titles accordingly
and they will like it their job more.

OLD: *Garden Boy*
NEW: *Landscape Executive and Animal Nutritionist*

OLD: *Petrol attendant*
NEW: *Fuel transmission engineer*

OLD: *Receptionist*
NEW: *Front Desk Controller*

OLD: *Typist*
NEW: *Printed Document Handler*

OLD: *Messenger*
NEW: *Business Communication Conveyer*

OLD: *Window Cleaner*
NEW: *Transparent Wall Technician*

OLD: *Temporary Teacher*
NEW: *Associate Teacher*

OLD: *Tea Boy*
NEW: *Refreshment Director*

OLD: *Garbage Collector*
NEW: *Environmental Sanitation Technician*

OLD: *Guard*
NEW: *Security Enforcement Director*

OLD: *Prostitute*
NEW: *Practical Sexual Relations Officer*

OLD: *Thief*
NEW: *Wealth Relocation Officer*

OLD: *Driver*
NEW: *Automobile Propulsion Specialist*

OLD: *Maid*
NEW: *Domestics Managing Director*

OLD: *Cook*
NEW: *Food Chemist*

OLD: *Gossip*
NEW: *Oral Research and Evaluation Director*

Which one got you more?

Because DevOps in a lot of organizations is really “help desk for clueless developers”, conversations like this happen a lot:

Dev “hey the thing seems to be not working right”

Me “what does that even mean? I need you to be a good deal more specific. What thing. What isn’t working?”

Dev “I dunno”

Me “Are there error messages?”

Dev “yes”

Me “….would you like to share them with me?”

Dev *sends error*

Me “ok did you actually read this error message?”

Dev “yes”

Me “…so you’re good then? It says you’re trying to use a variable that hasn’t been declared yet. You should fix that. “

Dev “…”

Me “good luck”

that one legendary guy who cranks out code and builds insane features. PMs (product management) love him because he builds features in several months which 10 devs together couldn't have built in the same time (so they say), features that are loved by customers as well, become their new standard and that have saved our company's asses in the past.
features are really awesome, performant and have very few bugs (compared to the rest of the software シ).
but this guy seems to live for this job. he also works at weekends, at unholy times of day and night and even in his holidays (he doesn't care that this is actually illegal, in terms of employee's rights, and he wouldn't listen to his superiors, no matter what they tell him)
so far, so good - except that he will probably die of some stroke or something very soon due to this lifestyle.
but it must be an absolute pain in the ass to work with him, as long as you're a developer (or his superior).
he lives in his own world and within the software, his features are also his own world. since the different modules interact with each other, sometimes you would be assigned a bug that might have its cause in some interaction of your and his module. talk with him about it? forget it. he wouldn't answer most devs who contacted him for some reason. ever. fix it in his module yourself? might happen that he just reverts your changes to his module without comments. so some bugs would lie on your desk forever because theoretically you know what would need to be done but if you cannot reach out into HIS world, there's no way to fix it. also - his code might be good in terms of performance and low bug numbers. but it seems to be hard to work on that code for everybody else but him.
furthermore, he is said to be really rude. he is no team player, but works on a software that is worked on by a huge team.
PMs think he's a genius, just a great dev, but they don't understand that other devs need to clean up the mess behind or around him.
everyone who's been his superior so far recommends to get him fired, but the company wouldn't fire him because they don't want to lose his talent. he can just do what he wants. he can even refuse to work on certain things because he thinks they are boring and he is not interested in them. devs seem to hate him, but my boss said, they are probably also a bit jealous because of his talent. i think, he's not wrong. :)
i haven't actually met him so far or was actually "forced" to deal with him, but i've never heard so many contrastive things about one person, the reputation of his, let's say vibrant personality really hurries ahead. he must be a real genius, after all i've heard so far, like he lives in the code. i must say i'm a bit curious but also somewhat afraid of meeting him one day.
do you also have such a guy at your company?

Years ago we hired a new employee in our department, her first week was kind of slow, she had training materials to get through but otherwise didn't have much newby work for her. I noticed she was missing one day, she wasn't at her desk or in the area training, I found her hiding behind a door playing a video game and texting on her phone. She didn't last long there. She should have asked for something to do, or asked what she could be doing, instead of sneaking off and playing on her phone.

My cat decided to jump on the PC at 5 AM.

Lesson learned: Never going to put my PC on the desk again.

A becomes B
B becomes C
C becomes A
D becomes B
E becomes A

Now add real hostnames... Make this list longer (roughly 15-18)

Add resource calculation, migration of VMs, organizing new hardware, removing and rebuilding hosts, etc.

I think my brain is permanently damaged and cannot be repaired.

Hardware migration finally over tomorrow.

I really won't miss the fuckton of Excel lists, constant speaking mistakes, having sore fingers from mutilating the desk calculator etc.

I'm too tired to be happy. But... It's over.

Undoubtedly the most common mistake that devs do : Ignoring your personal health, be it mental or physical.

I almost went through a burnout before realising things need to change.

Changed my lifestyle upside down after that
- Switched from wfh to an office job
- I cycle 12kms a day now
- Got a standing desk for myself to be more active
- and have a journal where i literally dump everything off my brain

In my current company (200+ employees) we have 3 guys who deals with everything related to service desk (format computers, fix network issues, help non-tech people...)

The same team is responsible for the AWS accounts and permissions, Jenkins, self hosted Gitlab... anyway, DevOps stuff.

Thing is: only one of them have enough DevOps background to handle the requests from the engineering team (~15 people). Also, he usually do anything "by hand" clicking trough the AWS interface on each account, never using tools like Infrastructure as Code to help (that's why I started to refer to his role only as Ops, because there's no Dev being done there).

Anyway... I asked my manager why that team is responsible for both jobs, despite the engineering guys having far more experience with those tools. He answered with a shamed smile, as he probably questioned the same to his manager:

- Because they are responsible for everything related to our Infrastructure.

Does it make sense for anyone? Am I missing something here? In what universe this kind of organization is a healthy choice?

An intern made a very bad impression on the first day.

This was before I become a developer. I was working in commercial art sales. One day, I had an appointment to onboard two new interns together.

Intern 1 shows up and I ask her for her signed confidentiality agreement. The boss had sent it out a week before and told me the interns were bringing the signed paperwork on their first day. I see the surprised look on her face and she says she forgot. She’s lucky I had access to another copy. If I didn’t, things could have gotten pretty awkward if I had to contact my boss, who was out of office. If there’s no signed agreement, I can’t onboard her and I’d have to send her home. The appointment was made with intern 1’s availability in mind, so intern 1 could have spent her time coming to the office for nothing and being turned away because of a stupid mistake she made.

While we wait for intern 2 to arrive, I try to engage in small talk with intern 1. I try to get to know her a little better and I ask “are you still in college/university?” She word vomits that she thought she had graduated, but six months later she hadn’t received her diploma and she called the school and they told her her pre-college credits had not transferred, so she’s finishing those credits now.

Oh, intern, you should have just simplified all this to “I’m finishing up my degree” or “yes, I’m still in college.” This is TMI. You don’t want to give out information about yourself that could put you in a bad light. You need to know to be discreet about yourself. You’re 22 years old. It’s really bad judgement to say this to your supervisor (me) and we’ve only known each other for ten minutes. I’m not your friend, I’m your supervisor. Honestly, I thought the explanation didn’t make sense because she would have found out about the credits when she tried to transfer them and when she applied for graduation. I didn’t prod for more details.

I did have to tell my boss about intern 1 forgetting the paperwork. It’s not something the intern would be reprimanded for, but it is something that’s not a good sign. The paperwork had been sent by the boss a week prior. It’s troublesome that an intern would forget to complete an important task that was sent by the boss. This was never a problem with prior interns.

Boss did freak out because boss thought I onboarded intern 1 without intern agreeing to the confidentiality agreement. Boss hadn’t considered an intern would forget the paperwork and didn’t tell me what to do if this did happen. I reassured boss that I had printed a new copy and had intern 1 sign the agreement.

I didn’t say anything about the word vomit. The content was troubling, but I was concerned this would be gossip and I wasn’t out to sabotage the intern.

Forgetting the paperwork and the word vomit were signs the intern wasn’t reliable. Intern had trouble taking direction even when it was written down. She’d do stupid things like invite her boyfriend to the office for hours and let BF sit at the boss’s desk—boss caught her and boss’s office is visible from our public viewing floor, so visitor did see this too. I suspected she might have an diagnosed learning disability.

In the end, intern didn’t ask for a reference letter. Boss said that if intern asked for one in the future, the answer would be no.

Intern 1 is the reason why I don’t want to be in change of interns ever again even though I’m not in art sales anymore.

What Pop! Funkos do you have @ your desk? 🤔
I have
💟 Lara Croft
💟 Nathan Drake
💟 Holly Golightly
💟 Eleven (Stranger Things)
💟 Diana (Wonder Woman)

I have noticed I have had great success using another co-worker as a metaphorical rubber duck (sometimes intentionally, sometimes unintentionally). It improves my productivity vastly. However, I know that it probably distracts others when I am using them in that way.

That's why I want to buy a literal rubber duck and talk to it. I could do it very quietly and most of my close co-workers use noise-cancelling headphones 80% of time while sitting at their desks. My only concern is other people passing by my desk would think that I am weird. My desk is in an open space and several people pass by it every hour. (however on my floor besides developers we have HR, marketing and people from high up who might be unfamiliar with the rubber duck method).

Is it unprofessional to talk to a rubber duck at the office?

Kinda pissed. Ordered a WD red plus 8TB on November 20th from newegg along with some other stuff. He drive showed up DOA on the 26th, tested everything I could to make it work. But in the end I couldn't even get it to initialize.

Ok. No problem this happens. request a return and replacement.

Got that in today. Over 2 weeks later. Fucking EXACT same problem.

and just to make sure I'm not fucking crazy I grabbed a 1tb thats been sitting on my desk unused for years. Plugged that into my NAS. Works fucking perfectly. Even able to pull it and wipe it using my USB drive reader on my desk after. I can even fucking reinitilize it back and forth from mbr to gpt.

Not asking for replacement this time. Just refund. Gonna order directly from WD. If this one fucks up I'm switching to Seagate for a couple of years

My surname is also a common firstname, so sometimes people mix them up and call me by my surname. I'm never offended and just answer by calling them by their surname too, so they understand... usually.

Today, the following e-mail exchange happened:
(Following are made-up names)
Me: Alexander William
Colleague 1: Kurt Richardson
Colleague 2: Amy Lopez

From: k.richardson@contoso.com <Kurt Richardson>
To: a.william@contoso.com <Alexander William>
Cc: a.lopez@contoso.com <Amy Lopez>

Hi,
Could I have an USB-C to HDMI adapter please ?
Thanks.
--------------------------------------------------------------------------
From: a.william@contoso.com <Alexander William>
To: k.richardson@contoso.com <Kurt Richardson>
Cc: a.lopez@contoso.com <Amy Lopez>

Hi Kurt,
I'm currently remote-working but if you are on premises tomorrow I could give one to you.
If you're not there tomorrow, I'll just drop it on Amy's desk so you can get it from her.

Regards,

Alexander William
--------------------------------------------------------------------------
From: k.richardson@contoso.com <Kurt Richardson>
To: a.william@contoso.com <Alexander William>
Cc: a.lopez@contoso.com <Amy Lopez>

Hi William,
I'm working on premises every thursday.
Regards.
--------------------------------------------------------------------------
From: a.william@contoso.com <Alexander William>
To: k.richardson@contoso.com <Kurt Richardson>
Cc: a.lopez@contoso.com <Amy Lopez>

No problem, Richardson. As I said I'll then drop it on Lopez' desk.

Regards,

Alexander William
--------------------------------------------------------------------------
From: k.richardson@contoso.com <Kurt Richardson>
To: a.william@contoso.com <Alexander William>
Cc: a.lopez@contoso.com <Amy Lopez>

Good evening William, [Editor's Note: this was received at 14:23]
Thanks.

Is he fucking dense or what?

My favorite thing at my desk is my adult coloring book. I'm a developer/project manager hybrid so I have to deal directly with the clients AND build their sites. 🙄👎🏼 Coloring in this is very therapeutic; the sayings are hilariously vulgar.😆👌🏼

Developer's frustration..

I currently don't have the space (believe it or not) to accommodate two screens onto my desk.
I've been developing on a single 15" laptop for years (since 2010).

I'm getting tired of constantly having to switch between windows. lol.

Mmmmust figure out wayyyy to incorporate new screen into my setupppp. lol

In a continuation of my previous rant:
Alright KVM is running.

First devrant post from my Windows inside my Linux with dedicated pass-through graphics card. So far, looks like it's working.

Installing Horizon Zero Dawn to gage gaming performance. But it looks promising. With a stylish button on desk that switches between Windows and Linux.

New office stories during the emotional turmoil...

Story 1: The creepy fuck

So being unaware of the fact that I was connected with this guy on LinkedIn already.

Ron walks upto my desk and greets me on my first day on floor. Weird, but whatever.

I politely interact, because gotta make friends and create my following to get shit done.

The next day, randomly comes asking for a laptop sticker and I am like WTF! He is like sticker was an excuse, I just wanted to say Hi!

👀

Day 3: same random creep shit. Talks about personal topics and invades personal space uninvited.

Day 4: Keeps starring at me while I ignore and judges me evidently with stupid suggestions on how to exist without being asked for.

Fuck this guy.

Story 2: The classic case of Dunning Kruger effect

So I get introduced to my tech team today and everyone start piling on me to guide them on decision making. The CTO creates a Slack thread with me and Co-founder asking me to get things moving on priority.

The co-founder shut him out right away. Fucking hilarious.

But, a retard starts schooling me on how to use Slack. Lmfao.

Me being polite, said I'll follow.. dude starts bragging on how he wrote company policy to get everyone on Slack yada yada..

To be honest, the Slack experience is beyond broken based on what these idiot has setup.

He literally opened my Slack and responded to the CTO thread.

That's where I got pissed. I upfront told him that hey! Calm your tiddies down. I know how to use Slack. I have used it since it was in the beta.

I have been in much much mucy bigger orgs and places more well structured than what you have here.

I told him on his face what the flaws where and how I felt a downgrade from where I am coming from.

The look on his face was priceless and he started sweating. Lol

Never again he'll school anyone.

I mean I understand if you are humble and genuinely guiding a new hire. But being cocky unnecessarily and shoving things down my throat without yourself knowing shit or know about the other person is purely asshole move.

Anyway, I am still upset about the scam. Fuck this world.

I recently moved to a house where my gf and me each have our separate office space. However, i’m sitting with my back to the door so whenever i’m in the zone with noise cancelling on and my gf walks in i don’t hear her. Resulting in me having a couple of almost heart attacks lately.

I have ideas about mirrors or sensors but since i’m working of three screens i din’t think it will do. The second option is ofcourse to move the desk to the other side of the room so that i’m facing the door more. But there are no power plugs.

My gf basically locks her door by sitting in front of it. Also she doesnt have a noise cancelling head set.

!rant

Any suggestions for a balance board for standing desk?