You guys, I think I know what is it....I think I know why I wanted to be a developer.

It started off innocently enough. I was a young lad in IT. Wide-eyed. Absorbing anything and everything I could. Then, the asshole clients came.....

I would put on my best customer service face on, and address the client as calmly and as respectfully as I could. Reminding myself that their frustration is understandable.

To deal with the increased time dealing with clients took, I developed scripts to help me handle maintenance and keep my head above water. I developed scripts to streamline equipment provisioning for big deployments. I developed scripts to handle other technicians who didn't log-off the phone queue and fucked up our on-call flow. I put in place email rules to sift through the bullshit and time wasters.

I became a developer to streamline and make myself as efficient as possible. But the clients keep nagging. The bullshit keeps coming. The other players get in your fucking way.

There is no end you guys.... THIS IS ONLY TUESDAY. I can't script the passage of time. I'm....I'm.... I need a fucking nap.

*The Fearless Leader*

I get a call to check up on a robot that has been exceeding weight limits at certain points of its movement (Crashing). As I get to the pendant (robo-game controller thingy I like to call it) and look over the alerts and warnings I notice some oil around the main power box of the Robot.... Nothing around this has oil.. so I start looking around and it turns out that the issue wasn’t a crash at all! It was an oily shorted out wire that kept sparking mad heavy when that servo was called on.. causing a large servo failure that required a full restart of the power box. I called our fearless leader and showed him only to find out that there was a motor leaking oil from the electrical end... My fearless leader runs both the Maintenance and Robotics department. When the motor was eventually fixed we overheard the technicians say that our fearless leader knew about this a week ago and decided to leave it that way.... with oil... coming out of an electrical cable..... *sigh* well Anyway after all the wires were fixed and motors changed. He comes up to me and says that he can’t believe that I didn’t call maintenance and fill a report on negligence of technicians for failing preventative maintenance....

I lost my cool a little, firstly that’s not my job, I’m literally one of the lowest ranking here. I called my next in command to figure out what I should do. Secondly the technicians told me that you told them to leave it like that! So if this place caught on fire this would have been on you!

Later I found out that he was trying to fire a technician and wanted me to do the dirty work.. I’m not going to be the reason another man loses the means for him to feed his family. The technician is a pretty cool and fair guy too!

Our fearless leader was a forklift driver and has no experience in robotics or maintenance... I don’t know how this happens or even why but all I know is this man is running both departments to the ground and management loves him.....

Can't wait to get my phone screen repaired so I can finnaly get that inverted panda! :-D

Oh wait I'll never be able to afford to fix the screen because Australia hates hiring IT technicians :-)

My old job was great. I was writing automation software for one of the world's biggest storage deployments, and there was always a new challenge. But over time, I was asked to lend a hand with the tedious task of corresponding with procurement vendors and on-site technicians. At first it was one site, then it was two, and then it was an entire region of the US, spread across two time zones I'm not in.

I hated that work, and I found that I didn't have time anymore for software development, because of the time commitment the logistics work was. I was never hired to do logistics work, I was never trained, never qualified, and as I said, I hated it. I agreed to it to temporarily help out a weakness due to a shortage in staffing. But it never got taken off my plate, except for a short stint toward the end, just before I was placed on a PIP, because surprise surprise-- I'm bad at logistics.

About halfway through the PIP, I told my boss I wasn't doing it anymore. I said he could either put me back on software development or let me go, if ticket-monkeying and phone calls is the direction the wind is blowing for our team. I told him I had no intention of resigning, as you are not eligible for unemployment or severance if you resign, so their choice was to let me go. I'm told by people who are still there that everybody on the team is a ticket-jockey button-pusher now. Bleh.

My wife and I sold our old condo in Kansas City earlier in the summer, so we had about a year's worth of cushion, which was why I was willing to be let go. I was profoundly unhappy in my work, and it was bleeding through to my relationship with my wife and kids. So I took advantage of the time between jobs by spending more time with my family and just generally becoming a happier person again.

Meanwhile, I was in no desperate hurry to find a new job, so I got on linkedin, and had no more than two irons in the fire at a time. After just over two months I got an offer for a better job than before, which I accepted. There wasn't anything remarkable about that process though-- it's just something I've gone through recently.

I've had today a meeting with the CEO regarding some designs. Here have some quotes that he made:

1. So you can click, click, click, click, click
2. numbers are so complicated so I just said something
3. I like the vibe in Amsterdam
4. We are doing a rebranding. Our rebranding document is the color of the 2 blues and one orange
5. I've to ask my wife for the design (with no design experience) to make the rebranding documents
6. In <the app our technicians/support use>, you can brrrrrrrrrrrrrrrrrrrrrrrrrrrrrrb
7. This is what differeniate us between most applications; FAVORITE SQUARES
8. I never watch that mess. I don't even know if it works or have ever worked with it. (talking about a simple table view)
9. You have been reported to the admins (in an admin-only application for our customers)
10. It's always nice to see developers think; when I don't think
11. But it's already an iPhone (when looking at android designs & cries in largest userbase in my country)

Customer requested the implementation of a "Master PIN" Code for accessing their appliances, to be used by field technicians when the users forgot their PIN.
Actually they could also read or reset it via USB using the config utility, but then again it's much more convenient not having to carry a laptop all the time...

Our only contact person at that company - the guy we got all the requirements from, let's call him Mr. L - wouldn't talk only positive about the company and managers, but we never worried as the project was making good progress.

In the final phase of the project, Mr. L was often hard to reach, always seemed to be busy even when we just needed a prototype approved to start production.
He always claimed to be waiting for approval from his supervisors and engineers, still discussing minor things with them.

When he left the company about three months later, it turned out he was pretty much the only person knowing about the details of the project, and his successor would start asking us very basic questions about the appliance,
wondering why we had implemented certain things the way they were.
(Well, how about we implemented everything just as requested by a former co-worker of yours?!)

Somewhere in the preliminary specs previously exchanged with Mr. L, there is even a hint of a "Master PIN", but the value is never specified anywhere on paper.

Today, we are not sure if anyone except for him even knew about it.
Maybe we should ask them whether they are now selling a product that has a 4-digit backdoor PIN nobody at the company is aware of?

Obviously, it is the birth year of Mr. L.

I feel like "programmers are not computer technicians" joke is kinda overused lately. It doesn' matter if we are not technicians, we are very knowledgeable in computers and people knows that. People of course will try to get help from you when they can so it's not a wonder that they ask you to help with something they are not confident. Everyone that exercises practical professions lives through that. If your sister-in-law is a mathematician it's normal to ask for help if you are not able to come up with the right algorithm for the task. People depend on each other. That's how we survive.
But I'm not saying start helping everybody that can't open a pdf file. Just know who to choose to help. If they are a capable person or someone that's a part of your everyday life they will most likely repay you when you are also in need. Believe me everyone needs help time to time.

It was like this all day

Adventures with house IT

I'm currently experimenting with PowerShell but my scripts won't run even though I've got every local permission. The error message indicates it's a GPO problem.
"No problem" le me thinks and calls IT hotline.
After 2 incompetent and unprofessional technicians i've still got no solution. I'm waiting for the second tech to call back because he "needed some time to get to know PowerShell" (he is a trained and certified SysAdmin).
During my call he couldn't decide if it was a GPO problem or not.
And this is just one story of their incompetence...

First software refactoring in the company I worked for. No test environnement because "who needs it?", no unit testing, no comments, had to make sql updates and shit, was scared all day long that something would fuck up.
"Fuck fuck fuck, forgot a part of the where !" Had to fix everything quickly so no one would notice, no coffee/smoke pauses. On top of that, got a ton of retarded requests from the PM and other technicians working with me like "hey boi, could you add an icon to every button we made? There's like a thousand, we need it for tonight, our client will come visit us and I want to show him a better interface blablabla"
And since I was an intern, I couldn't refuse, had to work like a prostitute in virgin-land, and for what?

"Oi, you did good, now do other stuff"

its day 4 of updating documentation and consolidating data.

The webclient has broken on average 4 times a day.

The database took 20+ seconds on updating a password entry.

I explained to my boss the real cost of interrupting my attention with these pauses. I figure it's caused my productivity to go from record high last week to being literally losing about 4 hours a day lost, plus extra time in having to go back through and verify things worked.

The technicians and developers who are working on fixing the database system are apparently quitting left right and center; their company acquired it awhile back, so they don't actually have native developers on it. Yet they still are pushing out new integration features rather than fixing anything.

Yesterday, one of the other people on the documentation project lost half a days work due to the angular updating the local cache, but it never reaching the backend. He came back from lunch, reopened his browser, and all his work was gone. (at least thats what we think happened). So we are hard resetting the program every 10 minutes or so just to make sure it is updating the backend.

The good news is that when it is done, we theoretically will be able to use this to cut back onboarding time and update times by about half, and it'll mean our new nano-server deployment project should be able to spin out with standards that can be referenced properly by everyone, not just the guy with the powershell script that he tinkered with for a particular project and never told anyone else what he did.

Theoretically.

Last week I wired up my home network (including custom modem and routers) myself, because the stuff my ISP wanted me to use was garbage.
Luckily Germany has "router-freedom" so ISPs are not allowed to force us to use their device to dial into the network.
I did everything myself, because the 'technicians' they kept sending me were just idiots who didn't know anything, considering the highly paid job they are doing. Usually they told me, to get the device from my ISP, because my "Router" (actually a business grade, standalone Modem by Cisco, to feed my Router) didn't even have WiFi ( lol ). Also all Technicians didn't arrive at the agreed date but at some other time. I wasn't able to wait any longer.
So I did it myself.

Consider me something more like a student of theoretical computer science. Not actually supposed to be experienced with hardware stuff.

The ISP is serving me with a DOCSIS 3.0 Network based on the television cable network in my city. For some reason they are providing the internet-access to only one socket in the apartment, which has a rather uncommon "WICLIC" connector. After having trouble getting an adapter for WICLIC to common coaxial F-Connectors (used by every DOCSIS-Modem), I made one myself.

After setting up everything (not that hard, once the connectors fit) my modem told me, that, while I'm perfectly connected to the ISPs internal Network, I still can't access the internet.

So I called the ISP...
After getting ranted at, about that what I'm doing is illegal and only certified employees are allowed to do this and I will break more, than actually do good and that I can't just connect my own "Router" (again I needed to correct her: Modem) I hang up the phone.
Also she accused me of hacking their devices because I'm not supposed to see my IP address... (My Modem told me on its web interface. I didn't even need telnet for that.)
I went to the ISPs head office, told the first desk as many technical terms as I could remember and got forwarded to something like the main technician.

He was a really nice guy. The only sane and qualified person I dealt with at this company. He asked me for my Address and Device Model, I told him my MAC and last internal IP, I had seen and he activated my internet access within a minute.
We talked a while about the stupid connector that ISP is using in the homes and he gifted me some nicer adapters to connect my modem to the wall.

Why do ISPs hate their customers that much?

One elementary school teacher of mine once said:

"In a football (soccer) game, the goalkeeper can be a very good player. He can make some incredible saves during the match. If he concedes a howler, people will remember him by that.

The forward can do everything wrong during the match. If he manages to score one goal, this is sufficient to justify why he was playing."

A team without a forward will have a harder time trying to win, but it is possible. A team without a goalkeeper will certainly lose. If you think into it, it's possible to conclude that the goalkeeper is more important than the forward. But football isn't rational; it isn't about fairness or importance. It is about emotions: forwards get all the visibility and fame because they get to do the "fun" part of the job.

Why people subject themselves to be goalkeepers then? Well, not every one is the same. In this game, if you, for any reason, aren't good playing with your foot, and still want to play, there is only one position you can take.

I think about this all the time because feel that in our work environment, managers are forwards and devs/scientists/technicians are goalkeepers.

If you want a self stem boost talk to some non programmers sometime. They seems to see us as gods with some mystical magical powers!!

Talked with a broker today and he told me about a damaged computer that he had with some important files. I told him that I'm not that kind of computer guy and proceeded to explain him briefly what I do (I build stuff) and he was like "oh, so you a the the REAL computer guy!" (no offense to any technicians here!)
I loved it!

So, get out and talk to the muggles and stop complaining that you are not good enough to work for Google (or Google is not good enough for you anymore anyways...)

When starting a new project full of challenges, do not go to your technicians right away; go to your artists first - they will know what to do. Then go to your engineers - because they will figure out how to do it.

Well here it goes,

I started out in customer support (A lot of stuff to tell here).

1.
One of my colleagues would come to work drunk, like every day he would smell of boze (the hard stuff 80%+). When a customer got on his nerves he endet the call and threw his Keyboard across the room. He worked in the company 3+ Years after I left.

2. Another colleague would connect to his Personal Computer at his home and play WoW while at work ( Allthough the man was a genius with a lot of free time, until a new task was assigned to him)

3. My Boss at the time did some really shitty things. I worked 17 hour days (while I was 18) for a week, and at the end of the week he shredded the accrued overtime with some Bullshit Explanation. (I did not stay long after this shitshow happened).

4. A dispatcher who sent our technicians out scheduled their tasks so that they were on the road for weeks and did not see their families. This led to a very strong turnover among technicians.

And yes, this company still operates today.

Assumptions are a terrible idea, yet I find myself making them all the time about other people. I am finding the very sobering reality about people who use technology vs people who create technology. The users have zero intellectual interest in how the technology accomplishes a task. While the creators get absorbed into the details and often relish in being able to maximize capability.

A point of frustration for me is users who are in a semi technical field yet take zero time to learn how to configure a piece of tech. They get a plug and play attitude and seek in panic when things don't work. The work is semi technical because they need to understand some of the fundamental physics involved to assess things using instrumentation. Yet when asked about a system they actively modify as to how it is normally setup they are clueless. Me, who helps write the software to control these devices, is stumped that they have zero interest (or capacity?) to understand how the system is normally configured. This is not the first time I have made assumption about what they know in technical contexts. I have run into this before with managers, but not with technicians.

How do you manage your expectations with people who won't invest any time into how their equipment actually works? How does someone operate that way to begin with? Where is their curiosity about how things work?

On the flip side, I swear at my fucking phone because I don't care how it works, but I just want it to stop doing everything besides being a phone... Fuck you, we are not the same, I think...

When my boss told me this:
Boss: I have some bad news that I didn't want to tell you on the phone.
Me: So I'm fired?
Boss: No, the roof of the server room collapsed and most of the computers are really damaged.
Me: Then tell the technicians to start fixing, why are you telling me?
Boss: Now it is your job ...

I really don't like the atmosphere in hospitals. Only thing I like about hospitals are the beautiful nurses and doctors, esp those who look in the eyes when talking.

If you think about it, basically what a doctor is to a humans or animals is same as what a computer technician is to a computer.

Maybe a dozen decades down the future, the reality may be such that there will be a convergence between the doctors and computer technicians as humans start integrating humanoid elements in their body.

I think it's l inevitable.

I got the Aero15. Had to send it in because ctrl+alt+shift+s (IntelliJ Preference menu) and some others critical shortcuts weren't working. Got a reply a week later.

"Thank you for using our service. The explained fault isn't actually a fault. If you want to use that button combination simply remap the FN key. Mind you this will disable any FN key combinations."

....

"What about all the other combinations?"

....

"Ok we returned it to the technicians who will do their best to repair it."

....

I await their response. But seriously, for a company that makes GAMING keyboards this is pretty embarrassing. I'm surprised it hasn't gotten more attention.

Any recommended reading material for someone deploying a go web application for the first time?

I am trying to see if I can deploy a go app into one of my institution's test linux servers. I would have one of the technicians create the server, so It doesn't really matter what it is, but lets say for argument's sake that the servers in question are either an ubuntu server or a red hat/centos server. Any recommendations before I dive in?

People that aren't into IT and act as if they are the best technicians in the world... People that tries to set the same windows resolution on two different monitors...

I've just learned that our front-end application throws a simple 404 error when trying to retrieve an avatar that does not exists.

But our technicians/support use this error in the console to show the customers that there is indeed a problem with the application functionality but have unsufficient logging from the back-end to troubleshoot with their internal tools.

What a bunch of liars trying to keep the customer satisfied and it works relatively well :D

Is it normal for a developer to go the customers to troubleshoot a certain problem?

I mean, we got technicians & support department

Outlook irritates the heck out of me with its distracting notification bar that's recently begun popping up almost every time I start the god damn shitty application. What's worse, there doesn't seem to be any way to disable this annoying crap. Our support technicians are unable to solve it, so I wrote feedback to Microsoft. I don't think they are ever going to answer, though. They haven't even responded to another problem with Outlook that I reported nine months ago! Microsoft are reallly inconsistent, to say the least. Some of their products, like Visual Studio, VS Code and Microsoft Flight Simulator, are excellent! But, more mainstream software, like MS Office and Outlook, suck. Windows (I'm using Windows 10) is so so. It works alright if you know your ways with the registry editor. The same goes for the support. If you're lucky, you can get hold of a real, flesh-and-blood person who patiently guides you through the cumbersome process of, for example purchasing and installing Minecraft (believe me, it isn't easy, took almost an hour for the support person to solve. Creds to him). Sometimes, like when activating an old Windows license, you get to talk to a bot and that, surprisingly, works very well too. However, if you report any bug or feedback to Microsoft through an application's help section, you 'll never hear from them. They just ignore it.