"You gave us bad code! We ran it and now production is DOWN! Join this bridgeline now and help us fix this!"

So, as the author of the code in question, I join the bridge... And what happens next, I will simply never forget.

First, a little backstory... Another team within our company needed some vendor client software installed and maintained across the enterprise. Multiple OSes (Linux, AIX, Solaris, HPUX, etc.), so packaging and consistent update methods were a a challenge. I wrote an entire set of utilities to install, update and generally maintain the software; intending all the time that this other team would eventually own the process and code. With this in mind, I wrote extensive documentation, and conducted a formal turnover / training season with the other team.

So, fast forward to when the other team now owns my code, has been trained on how to use it, including (perhaps most importantly) how to send out updates when the vendor released upgrades to the agent software.

Now, this other team had the responsibility of releasing their first update since I gave them the process. Very simple upgrade process, already fully automated. What could have gone so horribly wrong? Did something the vendor supplied break their client?

I asked for the log files from the upgrade process. They sent them, and they looked... wrong. Very, very wrong.

Did you run the code I gave you to do this update?

"Yes, your code is broken - fix it! Production is down! Rabble, rabble, rabble!"

So, I go into our code management tool and review the _actual_ script they ran. Sure enough, it is my code... But something is very wrong.

More than 2/3rds of my code... has been commented out. The code is "there"... but has been commented out so it is not being executed. WT-actual-F?!

I question this on the bridge line. Silence. I insist someone explain what is going on. Is this a joke? Is this some kind of work version of candid camera?
Finally someone breaks the silence and explains.

And this, my friends, is the part I will never forget.

"We wanted to look through your code before we ran the update. When we looked at it, there was some stuff we didn't understand, so we commented that stuff out."

You... you didn't... understand... my some of the code... so you... you didn't ask me about it... you didn't try to actually figure out what it did... you... commented it OUT?!

"Right, we figured it was better to only run the parts we understood... But now we ran it and everything is broken and you need to fix your code."

I cannot repeat the things I said next, even here on devRant. Let's just say that call did not go well.

So, lesson learned? If you don't know what some code does? Just comment that shit out. Then blame the original author when it doesn't work.

You just cannot make this kind of stuff up.

Boss: "Could you join the new DevOps team for a week or two, for some coaching?"

Me: "I'd rather watch you masturbate furiously in a corner of the office while you cry over your ex boyfriend"

Boss: "Yeah... that's why I ask you. You are the only one brave enough to watch"

Me: *Sigh* "But I don't know shit about what DevOps does, I'm a DBA. I've told you the difference a million times. Can't we just douse it in gasoline and set it on fire?"

Boss: "What?"

Me: "Not the team, the servers..."

Boss, imitating Gimli: "And my ex!"

Me: "I get why he left you"

Boss: "It's funny, he was actually better with computers than me, maybe even better than you. He hated me for starting this company, told me I was just chasing money instead of ideals. He just isn't grown up enough to see that there is more to the world than computer games, brewing beer, maker festivals and gay bars, that you need to take responsibility... Maybe it just never works out between managers and geeks..."

Me: "Indeed. The difference in competence is too large"

Boss: "Ugh. You are like straight version of him... but will you at least take a look?"

Me: "Fine, unzip your pants..."

Boss: "No, not that... you need to teach DevOps this docking thing, with the parallel stuff, and the horizontal growth"

Me: "Damn I really hope we're talking about servers now... Do you mean Docker?"

Boss: "That's it. They want to learn how to dock on the Windows servers. They reserved two 4xlarge on AWS. Is that enough for docking?"

Me: ...

Me: ...

Me: "You know what. I'm going back to hug my DB designs, and wash my brain with some queries. Then I'll return here to burn everything to the ground. There is no hope for you left"

Boss: "That's what he said"

Me: "You're using that meme wrong"

Boss: "OK. So what if you just stay on DB management, and I'll just give you the budget to recruit a new DevOps lead and pay for training?"

Me: "That would work"

Boss: "Why are you grinning?"

Me: "Because I have your ex's phone number"

Dear self proclaimed wordpress 'developers/programmers', kindly go fuck yourself.

I'm not talking about wordpress devs/designers who don't claim to have a better skillset than they have and are actually willing to learn, those are very much fine.

I'm talking about those wordpress people who claim that they're developers, programmers or whatever kind of bullshit which they're obviously not.

"A client's site crashed, you have to fix it!!!!!" sorry, come again? It's YOUR client's site. It's hosted on our hosting platform meaning that WE are responsible for KEEPING THE SERVERS UP AND FUNCTIONING.
You call yourself a wordpress 'developer' with 'programming experience' for 10 years but the second one of your shitty sites crashes, you come to us because 'it's your responsibility!!!'.
No, it's not. Next to that fact, the fact that you have to ask US why the site is crashing while you could easily login to your control panel, go to the fucking error logs and see that one of your facebook plugins crashes with a quite English error message, shows me that you definitely don't have 10 years of programming experience. And if you can't find that fucking article which tells you exactly where the motherfucking error logs are, don't come crying to us asking to fix your own fucking bullshit.

"My clients site got hacked, you have to clean it up and get it online again ASAP!!!!" - Nah, sorry, not my responsibility. The fact that you explicitly put your wordpress installation on 'no automatic updates' also doesn't help with my urge to fucking end you right now.
Add to that that we have some quite clear articles on wordpress security which you appearantly found too difficult (really? basic shit like 'set a strong fucking password' is too difficult for you?), you're on your own.

"I'm getting an error, please explain what's going wrong as soon as you can! this is a prio 1!!!!" - Nope. You were a wordpress dev/programmer right? Please act like one.

I'm not your personal wordpress agent.

I'm not your personal hacked wordpress site cleanup guy.

I'm not even a fucking wordpress professional. No, I'd rather jump off a bridge than develop wordpress bullshit for a living.

That you chose to do this, not a problem. Just don't rely on me for fixing your shit.

I'm sick of cleaning up your bullshit.

I'm done with answering your high prio tickets about bullshit which any dev could find out with just a few minutes of searching.

Oh your wordpress site isn't showing up so high in google? Yeah sure, shoot a ticket at us blaming us for your own SEO mess. I'm a fucking sysadmin, not a SEO expert.

I'm fucking done with you.

Go die in a fucking corner.

I have a couple of stories that I think are memorable from co-workers quitting in funny/interesting ways.

1. At one of the first companies I worked at, they gathered everyone to make an announcement that began with, “this is just a reminder, any heavy objects/packages need to be removed through the freight elevators, and cannot be taken through the main lobby.” We’re all thinking OK... why are you telling us this. Next part of the announcement was, “so and so (co-worker) is no longer with the company.” Apparently, which we found out later, the guy either quit/and/or got fired and wheeled his desk chair out the front door through the lobby (keep in mind this is an office on one of the busiest avenues in Manhattan). The whole thing was crazy. That’s the last we ever heard about him.

2. This one was strange. A really quiet dev at one of my previous companies was clearly constantly bored at work (he barely had any responsibility and was pretty much ignored) but the job was pretty cushy. One day, he was out from work, and no one thought much of it. Then he was out another day, then another, and before we knew it, it was like a week. No one knew where he was. Eventually, he sent an email saying he got stuck out of he country or something and he wouldn’t be coming back. Ok... weird, but kind of made sense.

But, one of our ops guys was able to see the ip/location of where he logged on to send the email, and it was right from NYC! So pretty much this guy was just fed up, left one day (with no notice), and just never came back. And then lied that he was out of the country when trying to explain is hasty departure.

At the airport.

Security: Please put all your electronics in the bin, including your watch.

Me: No problem

<goes through scanner>

Me: there was an Apple Watch in here and now it is gone.

Security: Oh, you lost your Apple Watch?

Me: No! I put my Apple Watch in the bin like you instructed and YOU lost my Apple Watch.

Security: It must be in the spinners.

Me: So my $500 Watch is in the spinners being run over by bins?

Security: you have to put the small things on the bottom.

Me: It was on the bottom and I did as you asked, this is entirely on you. Do not try to shift the blame to me again please.

Security: As I said...

Me: As I said, Do not try to shift the blame to me again. This is entirely your responsibility once you separate me from my electronics so you can perform security theatre. Have a nice day.

—————

Fuck this god damn security theatre. Fuck the dumbasses they hire. Fuck your country. Fuck your god damn feeling of insecurity. Fuck Your ineffective security theatre.

Sick my fucking dick until you choke and gag you worthless pieces of shit. Homeless people the street provide more security than you incompetent, under-educated assholes. Fuck you

And yes, I have 2 fucking laptops. I have a real fucking job where I provide actual value and for that I need a work laptop. I don’t come to work in a stupid looking outfit with a chip on my shoulder looking to inconvenience people. I come to work to provide real value to someone.

Fuck you and your worthless bullshit

@Devintrix , congrats and happy lifes with your wife. this joke is for you :)

Dear Tech Support:

Last year I upgraded from Girlfriend 7.0 to Wife 1.0 and noticed that the new program began running unexpected child processing that took up a lot of space and valuable resources.

In addition, Wife 1.0 installs itself into all other programs and launches during system initialization, where it monitors all other system activity. Applications such as PokerNight 10.3, Drunken Boys Night 2.5 and Monday Night football 5.0 no longer run, crashing the system whenever selected.

I cannot seem to keep Wife 1.0 in the background while attempting to run some of my other favorite applications. I am thinking about going back to Girlfriend 7.0, but un-install does not work on this program.

Can you help me please?

Thanks,

Joe

——————————————————–
Dear Joe:

This is a very common problem men complain about but is mostly due to a primary misconception. Many people upgrade from Girlfriend 7.0 to Wife 1.0 with the idea that Wife 1.0 is merely a “UTILITIES & ENTERTAINMENT” program. Wife 1.0 is an OPERATING SYSTEM and designed by its creator to run everything.

It is unlikely you would be able to purge Wife 1.0 and still convert back to Girlfriend 7.0. Hidden operating files within your system would cause Girlfriend 7.0 to emulate Wife 1.0 so nothing is gained.

It is impossible to un-install, delete, or purge the program files from the system once installed. You cannot go back to Girlfriend 7.0 because Wife 1.0 is not designed to do this. Some have tried to install Girlfriend 8.0 or Wife 2.0 but end up with more problems than the original system.

I recommend you keep Wife 1.0 and just deal with the situation. Having Wife 1.0 installed myself, I might also suggest you read the entire section regarding General Partnership Faults (GPFs). You must assume all responsibility for faults and problems that might occur, regardless of their cause. The best course of action will be to enter the command C:\APOLOGIZE. The system will run smoothly as long as you take the blame for all the GPFs.

Wife 1.0 is a great program, but very high maintenance. Consider buying additional software to improve the performance of Wife 1.0. I recommend Flowers 2.1, Jewelry 2.2, and Chocolates 5.0.

Do not, under any circumstances, install Secretary With Short Skirt 3.3. This is not a supported application for Wife 1.0 and is likely to cause irreversible damage to the operating system.

Best of luck,
Tech Support

I started in 2015 at my current job. The first contract was for a year, very normal in the Netherlands. Also, I had only 6 months of professional experience with programming.
I already knew that I would replace an older colleague who's going to retire and I would get some of his responsibilities.

One year later (6 months ago) I had an evaluation with my boss. He told me he was proud I learned everything so quick and offered me a permanent position and wanted me to take over one of the major products we sell. Even more, he wanted me to decide how to change the framework since it's over 20years old. (Multiple languages combined)

I am currently working on a new design and UX as well, which I presented last year. The love it.

I've never felt so appreciated and valued before.

My last promotion was a 2% raise for a hell of a lot more responsibility

Guess who's updating their CV 🙃

Fuck open office spaces.

A few months ago I landed a super sweet job as a senior full stack developer, mainly going to work with their Python microarchitecture. The company pays well, has a sweet balance between freedom and responsibility, 30 days vacation etc.

During the recruiting process they walked me around the office that was super cozy with 14 devs in on large room and 10 people from marketing in another. They also mentioned that they would move and merge office with operations and customer service (around 100 more people) in a few months.

Life was good in the old office, I thought that this is the company where I will work for a looooong time.

Now we are in the new office and its fucking shit. No walls or FUCKING CEILINGS between departments. Right above my head there is balcony with customer service talking loud as fuck 24/7. Everyone that is not a developer is just so fucking loud.

I have to use earplugs AND earmuffs to get silence, or blast my ears with way to loud music. Every day around lunch I'm completely done mentally.

I know I'm extra sensitive to noise because of my ADHD, but seriously who the fuck thought this was a good idea?

All the devs have told our boss what needs to be done. If they listen i don't know. In the meantime I will start looking for a new job....

TL;DR
Deadline means shit for management and they can't fucking understand wtf a prototype is for.

Hahahahaha so we are gonna present this prototype tomorrow ( 2018-03-08 ) at a meeting with investors and our management practically demanded a landing page to be at this presentation.

The landing page is gonna be made by a 3rd party, they asked for directions on the content about the landing page with a deadline set for Friday ( 2018-03-02 ) .

Management sent an email yesterday with the following content:
- Changes on the prototype ( A LOT OF CHANGES )
- The landing page content: a fucked up confusing as fuck word document with crossed over text, red text. A lot of noise that meas nothing and only makes the reader confused as fuck

Why am I laughing you may ask?
Our front ender took the prototyping role out of my hands and the landing page is a third party responsibility.

None of this is my work, I'm here watching the world burn for the first time and boy its funny and warm.

:)

How I went from loving my job to wishing i dont wake up tomorrow just to avoid it.

Ive been a backend dev in the company im at for 2 years now.

First year was a blast, i loved my work so much, I used to get so many random features to do, bug fixes, campaigns, analytics, etc..

Second year i started getting familiar with the part of the code that has to do with Search in our music streaming app. Nobody wanted to work on it, so i wanted to take initiative and start doing a few tasks.

A few tasks turned into sprints, and sprints turned into months worth of sprints. And because the code was the definition of tech debt, and because it was so messed up that changing one thing can blow up everything else, working on Search was not too fun.

However, people seemed to be happy search tasks are no longer piling up and someone is handling them so that used to make me feel good about it. They also gave me so much freedom and i felt like my own manager because no one told me what to do (not even my actual manager) they just let me be and were happy i was handling the part they want nothing to do with. I was also given an intern to mentor and have her work on Search tasks with me which turned out amazing.

During the last few months, I completely rewrote search, made it 10 times more performant in such a neat way, made an inhouse dashboard to automate certain tasks so we wont need to waste developers on them (all of which were extra effort on my own time without being asked), all meanwhile still tending to the fixes of the old implementation.

I felt so accomplished, and in a way, i felt like a lead (even tho im not managing any employees, i had so much freedom and I was literally responsible for everything about Search and if i decide to play with the sprint task order i can even do that).

Then 6 or so weeks ago my manager left the company, and while i thought id be a standalone team / person (single person teams are not uncommon in the company) i was instead put under someone else. Someone who likes to micro manage the fuck out of me. I have been happy working on shit code because it was my baby, my project, no one interferes and no one tells me what to do and everyone would call me the search lead (unofficially). now if i dont report to that guy every two hours he calls to see if im working. preplans sprints i no longer have a say in, and im the only dev who knows the code so all tasks go to me. I feel i got demoted so fucking much. I felt like a lead on a project and now im back to being a normal code minion. From deciding everything about a project to blindly following a some irrelevant manager's opinion. (who btw is making Search worse) And after all the extra effort i put in, after actually caring, after actually embracing Search as my responsibility i get rewarded with losing everything i liked about my job...My Independence. From feeling like a lead to feeling demoted. I am so demotivated.

I love the company, but this is hell for me and this made me hate a job i always loved. I am thinking of talking to the CTO asking to work on other stuff because i no longer want this. If i am to be a code minion at least let it be on code i like, let me go back to dealing with PMs, fuck my new manager I dont wanna work with that guy he can take the project along with all its poopoo.

1. Humans perform best if they have ownership over a slice of responsibility. Find roles and positions within the company which give you energy. Being "just another intern/junior" is unacceptable, you must strive to be head of photography, chief of data security, master of updating packages, whatever makes you want to jump out of bed in the morning. Management has only one metric to perform on, only one right to exist: Coaching people to find their optimal role. Productivity and growth will inevitably emerge if you do what you love. — Boss at current company

2. Don't jump to the newest technology just because it's popular or shiny. Don't cling to old technology just because it's proven. — Team lead at the Arianespace contractor I worked for.

4. "Developing a product you wouldn't like to use as an end user, is unsustainable. You can try to convince yourself and others that cancer is great for weight loss, but you're still gonna die if you don't try to cure it. You can keep ignoring the disease here to fill your wallet for a while, but it's worse for your health than smoking a pack of cigs a day." — my team supervisor, heavy smoker, and possibly the only sane person at Microsoft.

5. Never trust documentation, never trust comments, never trust untested code, never trust tests, never trust commit messages, never trust bug reports, never trust numbered lists or graphs without clearly labeled axes. You never know what is missing from them, what was redacted away. — Coworker at current company.

A quite severe vulnerability was found in Skype (at least for windows, not sure about other systems) allowing anyone with system access (remote or local) to replace the update files skype downloads before updating itself with malicious versions because skype doesn't check the integrity of local files. This could allow an attacker to, once gaining access to the system, 'inject' any malicious DLL into skype by placing it in the right directory with the right file name and waiting for the user to update (except with auto updates of course).

From a company like Microsoft, taking in mind that skype has hundreds of millions of users worldwide, I'd expect them to take a very serious stance on this and work on a patch as soon as possible.

What they said about this: they won't be fixing it anytime soon as it would require a quite big rewrite of skype.

This kinda shit makes me so fucking angry, especially when it comes from big ass companies 😡. Take your fucking responsibility, Microsoft.

A lot of the people are complaining about working in inhumane conditions. I want to debunk some bullshit that I think is causing this.

Devs are hard to find. That makes you valuable. A good dev that actually works for 30-40 hours per week is extremely hard to find.
The relationship with your employer / client should be simple: you work, they pay. What you do NOT:
1. Do not take responsibility for other people's decisions
2. Do not internalize other people's problems (you've got your own, better stick to them)
3. Do not let ANYONE guilt trip you into anything that you're not indeed guilty of.
4. Do NOT work for an effective rate that's significantly lower than you know you can get elsewhere.

There are indeed some utterly evil assholes out there that will try to manipulate you, into thinking that you're "part of the project", or that "you're all a team". Yeah, you are, but when it comes to making money, you'll only get the salary, regardless of how successful your work will be. THEY have a motivation to stay up late, to work extra hours, etc. You DO NOT. If you do that, and don't get paid extra, you're working for free, which means that you're not a professional.

Are you a professional? Then have respect for yourself, and bill for every fucking second of your time. Don't let the assholes think they own you.

As a professional, you MUST do EXACTLY what you're paid to do. No more, no less. Well, if you're feeling good about it, then you can do slightly more. And anyone that's demanding more, basically has no respect for you, and doesn't consider you a professional. That is the plain truth. See it as it is, and handle those scumbags accordingly.

In a user-interface design meeting over a regulatory compliance implementation:
User: “We’ll need to input a city.”
Dev: “Should we validate that city against the state, zip code, and country?”
User: “You are going to make me enter all that data? Ugh…then make it a drop-down. I select the city and the state, zip code auto-fill. I don’t want to make a mistake typing any of that data in.”
Me: “I don’t think a drop-down of every city in the US is feasible.”
Manage: “Why? There cannot be that many. Drop-down is fine. What about the button? We have a few icons to choose from…”
Me: “Uh..yea…there are thousands of cities in the US. Way too much data to for anyone to realistically scroll through”
Dev: “They won’t have to scroll, I’ll filter the list when they start typing.”
Me: “That’s not really the issue and if they are typing the city anyway, just let them type it in.”
User: “What if I mistype Ch1cago? We could inadvertently be out of compliance. The system should never open the company up for federal lawsuits”
Me: “If we’re hiring individuals responsible for legal compliance who can’t spell Chicago, we should be sued by the federal government. We should validate the data the best we can, but it is ultimately your department’s responsibility for data accuracy.”
Manager: “Now now…it’s all our responsibility. What is wrong with a few thousand item drop-down?”
Me: “Um, memory, network bandwidth, database storage, who maintains this list of cities? A lot of time and resources could be saved by simply paying attention.”
Manager: “Memory? Well, memory is cheap. If the workstation needs more memory, we’ll add more”
Dev: “Creating a drop-down is easy and selecting thousands of rows from the database should be fast enough. If the selection is slow, I’ll put it in a thread.”
DBA: “Table won’t be that big and won’t take up much disk space. We’ll need to setup stored procedures, and data import jobs from somewhere to maintain the data. New cities, name changes, ect. ”
Manager: “And if the network starts becoming too slow, we’ll have the Networking dept. open up the valves.”
Me: “Am I the only one seeing all the moving parts we’re introducing just to keep someone from misspelling ‘Chicago’? I’ll admit I’m wrong or maybe I’m not looking at the problem correctly. The point of redesigning the compliance system is to make it simpler, not more complex.”
Manager: “I’m missing the point to why we’re still talking about this. Decision has been made. Drop-down of all cities in the US. Moving on to the button’s icon ..”
Me: “Where is the list of cities going to come from?”
<few seconds of silence>
Dev: “Post office I guess.”
Me: “You guess?…OK…Who is going to manage this list of cities? The manager responsible for regulations?”
User: “Thousands of cities? Oh no …no one is our area has time for that. The system should do it”
Me: “OK, the system. That falls on the DBA. Are you going to be responsible for keeping the data accurate? What is going to audit the cities to make sure the names are properly named and associated with the correct state?”
DBA: “Uh..I don’t know…um…I can set up a job to run every night”
Me: “A job to do what? Validate the data against what?”
Manager: “Do you have a point? No one said it would be easy and all of those details can be answered later.”
Me: “Almost done, and this should be easy. How many cities do we currently have to maintain compliance?”
User: “Maybe 4 or 5. Not many. Regulations are mostly on a state level.”
Me: “When was the last time we created a new city compliance?”
User: “Maybe, 8 years ago. It was before I started.”
Me: “So we’re creating all this complexity for data that, realistically, probably won’t ever change?”
User: “Oh crap, you’re right. What the hell was I thinking…Scratch the drop-down idea. I doubt we’re have a new city regulation anytime soon and how hard is it to type in a city?”
Manager: “OK, are we done wasting everyone’s time on this? No drop-down of cities...next …Let’s get back to the button’s icon …”

Simplicity 1, complexity 0.

Worst thing you've seen another dev do? Long one, but has a happy ending.

Classic 'Dev deploys to production at 5:00PM on a Friday, and goes home.' story.

The web department was managed under the the Marketing department, so they were not required to adhere to any type of coding standards and for months we fought with them on logging. Pre-Splunk, we rolled our own logging/alerting solution and they hated being the #1 reason for phone calls/texts/emails every night.

Wanting to "get it done", 'Tony' decided to bypass the default logging and send himself an email if an exception occurred in his code.

At 5:00PM on a Friday, deploys, goes home.

Around 11:00AM on Sunday (a lot folks are still in church at this time), the VP of IS gets a call from the CEO (who does not go to church) about unable to log into his email. VP has to leave church..drive home and find out he cannot remote access the exchange server. He starts making other phone calls..forcing the entire networking department to drive in and get email back up (you can imagine not a group of happy people)

After some network-admin voodoo, by 12:00, they discover/fix the issue (know it was Tony's email that was the problem)

We find out Monday that not only did Tony deploy at 5:00 on a Friday, the deployment wasn't approved, had features no one asked for, wasn't checked into version control, and the exception during checkout cost the company over $50,000 in lost sales.

Was Tony fired? Noooo. The web is our cash cow and Tony was considered a top web developer (and he knew that), Tony decided to blame logging. While in the discovery meeting, Tony told the bosses that it wasn't his fault logging was so buggy and caused so many phone calls/texts/emails every night, if he had been trained properly, this problem could have been avoided.

Well, since I was responsible for logging, I was next in the hot seat.

For almost 30 minutes I listened to every terrible thing I had done to Tony ever since he started. I was a terrible mentor, I was mean, I was degrading, etc..etc.
Me: "Where is this coming from? I barely know Tony. We're not even in the same building. I met him once when he started, maybe saw him a couple of times in meetings."
Andrew: "Aren't you responsible for this logging fiasco?"
Me: "Good Lord no, why am I here?"
Andrew: "I'll rephrase so you'll understand, aren't you are responsible for the proper training of how developers log errors in their code? This disaster is clearly a consequence of your failure. What do you have to say for yourself?"
Me: "Nothing. Developers are responsible for their own choices. Tony made the choice to bypass our logging and send errors to himself, causing Exchange to lockup and losing sales."
Andrew: "A choice he made because he was not properly informed of the consequences? Again, that is a failure in the proper use of logging, and why you are here."
Me: "I'm done with this. Does John know I'm in here? How about you get John and you talk to him like that."
'John' was the department head at the time.
Andrew:"John, have you spoken to Tony?"
John: "Yes, and I'm very sorry and very disappointed. This won't happen again."
Me: "Um...What?"
John: "You know what. Did you even fucking talk to Tony? You just sit in your ivory tower and think your actions don't matter?"
Me: "Whoa!! What are you talking about!? My responsibility for logging stops with the work instructions. After that if Tony decides to do something else, that is on him."
John: "That is not how Tony tells it. He said he's been struggling with your logging system everyday since he's started and you've done nothing to help. This behavior ends today. We're a fucking team. Get off your damn high horse and help the little guy every once in a while."
Me: "I don't know what Tony has been telling you, but I barely know the guy. If he has been having trouble with the one line of code to log, this is the first I've heard of it."
John: "Like I said, this ends today. You are going to come up with a proper training class and learn to get out and talk to other people."

Over the next couple of weeks I become a powerpoint wizard and 'train' anyone/everyone on the proper use of logging. The one line of code to log. One line of code.

A friend 'Scott' sits close to Tony (I mean I do get out and know people) told me that Tony poured out the crocodile tears. Like cried and cried, apologizing, calling me everything but a kitchen sink,...etc. It was so bad, his manager 'Sally' was crying, her boss 'Andrew', was red in the face, when 'John' heard 'Sally' was crying, you can imagine the high levels of alpha-male 'gotta look like I'm protecting the females' hormones flowing.

Took almost another year, Tony released a change on a Friday, went home, web site crashed (losses were in the thousands of $ per minute this time), and Tony was not let back into the building on Monday (one of the best days of my life).

Seeing OOP classes with more than a 1000 lines of code really pisses me off.

At one of my former jobs, I had a four-day-week. I remember once being called on my free Friday by an agitated colleague of mine arguing that I crashed the entire application on the staging environment and I shall fix it that very day.

I refused. It was my free day after all and I had made plans. Yet I told him: OK, I take a look at it in Sunday and see what all the fuzz is all about. Because I honestly could fathom what big issue I could have caused.

On that Sunday, I realized that the feature I implemented worked as expected. And it took me two minutes to realize the problem: It was a minor thing, as it so often is: If the user was not logged in, instead of a user object, null got passed somewhere and boom -- 500 error screen. Some older feature broke due to some of my changes and I never noticed it as while I was developing I was always in a logged in state and I never bothered to test that feature as I assumed it working. Only my boss was not logged in when testing on the stage environment, and so he ran into it.

So what really pushed my buttons was:

It was not a bug. It was a regression.

Why is that distinction important?

My boss tried to guilt me into admitting that I did not deliver quality software. Yet he was the one explicitly forbidding me to write tests for that software. Well, this is what you get then! You pay in the long run by strange bugs, hotfixes, and annoyed developers. I salute you! :/

Yet I did not fix the bug right away. I could have. It would have just taken me just another two minutes again. Yet for once, instead of doing it quickly, I did it right: I, albeit unfamiliar with writing tests, searched for a way to write a test for that case. It came not easy for me as I was not accustomed to writing tests, and the solution I came up with a functional test not that ideal, as it required certain content to be in the database. But in the end, it worked good enough: I had a failing test. And then I made it pass again. That made the whole ordeal worthwhile to me. (Also the realization that that very Sunday, alone in that office, was one of the most productive since a long while really made me reflect my job choice.)

At the following Monday I just entered the office for the stand-up to declare that I fixed the regression and that I won't take responsibility for that crash on the staging environment. If you don't let me write test, don't expect me to test the entire application again and again. I don't want to ensure that the existing software doesn't break. That's what tests are for. Don't try to blame me for not having tests on critical infrastructure. And that's all I did on Monday. I have a policy to not do long hours, and when I do due to an "emergency", I will get my free time back another day. And so I went home that Monday right after the stand-up.

Do I even need to spell it out that I made a requirement for my next job to have a culture that requires testing? I did, and never looked back and I grew a lot as a developer.

I have familiarized myself with both the wonderful world of unit and acceptance testing. And deploying suddenly becomes cheap and easy. Sure, there sometimes are problems. But almost always they are related to infrastructure and not the underlying code base. (And yeah, sometimes you have randomly failing tests, but that's for another rant.)

It's maddening how few people working with the internet don't know anything about the protocols that make it work. Web work, especially, I spend far too much time explaining how status codes, methods, content-types etc work, how they're used and basic fundamental shit about how to do the job of someone building internet applications and consumable services.

The following has played out at more than one company:

App: "Hey api, I need some data"
API: "200 (plain text response message, content-type application/json, 'internal server error')"
App: *blows the fuck up

*msg service team*

Me: "Getting a 200 with a plaintext response containing an internal server exception"
Team: "Yeah, what's the problem?"
Me: "...200 means success, the message suggests 500. Either way, it should be one of the error codes. We use the status code to determine how the application processes the request. What do the logs say?"
Team: "Log says that the user wasn't signed in. Can you not read the response message and make a decision?"
Me: "That status for that is 401. And no, that would require us to know every message you have verbatim, in this case, it doesn't even deserialize and causes an exception because it's not actually json."
Team: "Why 401?"
Me: "It's the code for unauthorized. It tells us to redirect the user to the sign in experience"
Team: "We can't authorize until the user signs in"
Me: *angermatopoeia* "Just, trust me. If a user isn't logged in, return 401, if they don't have permissions you send 403"
Team: *googles SO* "Internet says we can use 500"
Me: "That's server error, it says something blew up with an unhandled exception on your end. You've already established it was an auth issue in the logs."
Team: "But there's an error, why doesn't that work?"
Me: "It's generic. It's like me messaging you and saying, "your service is broken". It doesn't give us any insight into what went wrong or *how* we should attempt to troubleshoot the error or where it occurred. You already know what's wrong, so just tell me with the status code."
Team: "But it's ok, right, 500? It's an error?"
Me: "It puts all the troubleshooting responsibility on your consumer to investigate the error at every level. A precise error code could potentially prevent us from bothering you at all."
Team: "How so?"
Me: "Send 401, we know that it's a login issue, 403, something is wrong with the request, 404 we're hitting an endpoint that doesn't exist, 503 we know that the service can't be reached for some reason, 504 means the service exists, but timed out at the gateway or service. In the worst case we're able to triage who needs to be involved to solve the issue, make sense?"
Team: "Oh, sounds cool, so how do we do that?"
Me: "That's down to your technology, your team will need to implement it. Most frameworks handle it out of the box for many cases."
Team: "Ah, ok. We'll send a 500, that sound easiest"
Me: *..l.. -__- ..l..* "Ok, let's get into the other 5 problems with this situation..."

Moral of the story: If this is you: learn the protocol you're utilizing, provide metadata, and stop treating your customers like shit.

Imagine if a structural engineer whose bridge has collapsed and killed several people calls it a feature.

Imagine if that structural engineer made a mistake in the tensile strength of this or that type of bolt and shoved it under the rug as "won't fix".

Imagine that it's you who's relying on that bridge to commute every day. Would you use it, knowing that its QA might not have been very rigorous and could fail at any point in time?

Seriously, you developers have all kinds of fancy stuff like Continuous Integration, Agile development, pipelines, unit testing and some more buzzwords. So why is it that the bridges don't collapse, yet new critical security vulnerabilities caused by bad design, unfixed bugs etc appear every day?

Your actions have consequences. Maybe not for yourself but likely it will have on someone else who's relying on your software. And good QA instead of that whole stupid "move fast and break things" is imperative.

Software developers call themselves the same engineers as the structural engineer and the electrical engineer whose mistakes can kill people. I can't help but be utterly disappointed with the status quo in software development. Don't you carry the title of the engineer with pride? The pride that comes from the responsibility that your application creates?

I wish I'd taken the blue pill. I didn't want to know that software "engineering" was this bad, this insanity-inducing.

But more than anything, it surprises me that the world that relies so much on software hasn't collapsed in some incredible way yet, despite the quality of what's driving it.

Well, here's the OS rant I promised. Also apologies for no blog posts the past few weeks, working on one but I want to have all the information correct and time isn't my best friend right now :/

Anyways, let's talk about operating systems. They serve a purpose which is the goal which the user has.
So, as everyone says (or, loads of people), every system is good for a purpose and you can't call the mainstream systems shit because they all have their use.

Last part is true (that they all have their use) but defining a good system is up to an individual. So, a system which I'd be able to call good, had at least the following 'features':
- it gives the user freedom. If someone just wants to use it for emailing and webbrowsing, fair enough. If someone wants to produce music on it, fair enough. If someone wants to rebuild the entire system to suit their needs, fair enough. If someone wants to check the source code to see what's actually running on their hardware, fair enough. It should be up to the user to decide what they want to/can do and not up to the maker of that system.
- it tries it's best to keep the security/privacy of its users protected. Meaning, by default, no calling home, no integrating users within mass surveillance programs and no unnecessary data collection.
- Open. Especially in an age of mass surveillance, it's very important that one has the option to check the underlying code for vulnerabilities/backdoors. Can everyone do that, nope. But that doesn't mean that the option shouldn't be there because it's also about transparency so you don't HAVE to trust a software vendor on their blue eyes.
- stability. A system should be stable enough for home users to use. For people who like to tweak around? Also, but tweaking *can* lead to instability and crashes, that's not the systems' responsibility.

Especially the security and privacy AND open parts are why I wouldn't ever voluntarily (if my job would depend on it, sure, I kinda need money to stay alive so I'll take that) use windows or macos. Sure, apple seems to care about user privacy way more than other vendors but as long as nobody can verify that through source code, no offense, I won't believe a thing they say about that because no one can technically verify it anyways.

Some people have told me that Linux is hard to use for new/(highly) a-technical people but looking at my own family and friends who adapted fast as hell and don't want to go back to windows now (and mac, for that matter), I highly doubt that. Sure, they'll have to learn something new. But that was also the case when they started to use any other system for the first time. Possibly try a different distro if one doesn't fit?

Problems - sometimes hard to solve on Linux, no doubt about that. But, at least its open. Meaning that someone can dive in as deep as possible/necessary to solve the problem. That's something which is very difficult with closed systems.

The best example in this case for me (don't remember how I did it by the way) was when I mounted a network drive at boot on windows and Linux (two systems using the same webDav drive). I changed the authentication and both systems weren't in for booting anymore. Hours of searching how to unfuck this on windows - I ended up reinstalling it because I just couldn't find a solution.
On linux, i found some article quite quickly telling to remove the entry for the webdav thingy from fstab. Booted into a root recovery shell, chrooted to the harddrive, removed the entry in fstab and rebooted. BAM. Everything worked again.

So yeah, that's my view on this, I guess ;P

Me: Boss, your new project is ready, we've tested the technical aspect but we're waiting on your approval before deploying, will you test it?
Boss: yeah sure, I'll test it in 5

*2 weeks later*

Boss: why isn't that project deployed yet?
Me: you haven't tested it, and we haven't gotten approval
Boss: oh right, I'll go test it right now!

*2 weeks later*

Boss: I NEED that project to go live RIGHT THIS MOMENT!!!
Me: sure, have you tested it yet?
Boss: nope, but I need it
Me: well, I'll put it live, but me and my colleagues are shifting responsibility to you, since you haven't tested it. Are you sure?
Boss: yeah, yeah whatever...

*put product online*

*2 days later*

Angry call from boss, bugs have been found, tell him that he approved the state of the product and that the bugs will go on the to-do list...

Boss is extremely pissed, but recognized his mistake...

Now, the boss actually tests everything thoroughly at the moment we tell him to! No more bugs, complaints, and I got a raise!

Can I only pick one?

I don't hate a lack of skill by itself. Incompetence, in my book, refers to a lack of skill combined with being in a position of responsibility.

The junior/intern in my team writes pretty bad code, but that is OK. He asks questions, I give pointers and bounce back his PRs ten times in a row, and he keeps fixing things without complaints.

My boss however... still writes PHP as if he's living in the 90s. He doesn't visit scrum meetings because he "isn't a developer". He thinks of a new feature while pooping, writes it without telling anyone, and throws it into production without making a PR.

Come back from vacation to find that 80+ e-mails were sent out to the entire team for a critical process that was failing to run due to an incorrect password. No one did anything for a week. Fixed it in 30 seconds.

I wonder why banks are always so terribly insecure, given how much money there's for grabs in there for hackers.

Just a while ago I got a new prepaid credit card from bpost, our local postal service that for some reason also does banking. The reason for that being that - thank you 'Murica! - a lot of websites out there don't accept anything but credit cards and PayPal. Because who in their right mind wouldn't use credit cards, right?! As it turns out, it's pretty much every European I've spoken to so far.

That aside, I got that card, all fine and dandy, it's part of the Mastercard network so at least I can get my purchases from those shitty American sites that don't accept anything else now. Looked into the manual of it because bpost's FAQ isn't very clear about what my login data for their online customer area now actually is. Not that their instruction manual was either.

I noticed in that manual that apparently the PIN code can't be changed (for "security reasons", totally not the alternative that probably they didn't want to implement it), and that requesting a forgotten PIN code can be done with as little as calling them up, and they'll then send the password - not a reset form, the password itself! IN THE FUCKING MAIL.

Because that's apparently how financial institutions manage their passwords. The fact that they know your password means that they're storing it in plain text, probably in a database with all the card numbers and CVC's next to it. Wouldn't that be a treasure trove for cybercriminals, I wonder? But YOU the customer can't change your password, because obviously YOU wouldn't be able to maintain a secure password, yet THEY are obviously the ones with all the security and should be the ones to take out of YOUR hands the responsibility to maintain YOUR OWN password.

Banking logic. I fucking love it.

As for their database.. I reckon that that's probably written in COBOL too. Because why wouldn't you.

GROW SOME FUCKING BALLS AND TAKE RESPONSIBILITY YOU FUCKWIT!
I can't even count how many times I've heard people excuse themselves with sentences like:

"It's not my fault I only got a C, our teacher was shit"

"How can I finish this assignment when the teacher haven't learned me this?"

"I'll be late to work because my dick was stuck in the sink"

(This is a real one I've experienced myself. A teacher said this last week)
"I wasn't able to put up your material for your assignment before now because we're busy with exams" - The day before the assignment was due. Gj.

"He doesn't deserve to get fired, it's not his not at fault for being incompetent"

Then who the fuck is? The government? Your neighbor? My dog? A stray dog?

STFU! I'm so fucking tired of all these excuses! Grow some hair and take responsibility.
The only thing you achieve by not doing so is making everyone else drown in your disgusting vomit your constantly letting out of your mouth.

Being one of the top devs (and a good student admired by most lecturers) at college, my most humbling experience was when I joined my first job. I thought I knew SQL, I thought I knew C#. I realized in the first week, the thing I didn't know was "I don't know jack".
Thanks to a couple of great mentors (it took a few of them to bring me up to speed :P), I learned that the more I learn something, the more I will realize how much more there is to learn. I used tools to create storyboard animations in WPF, and my mentor would write it all in XAML! I'd write messy SQL and the other mentor just reduces it to a couple of elegant lines. They were like tech gods to my college self, all while being humble and friendly.
They also imbibed in me a sense of responsibility to carry on the culture of mentoring my juniors, which taught me much more than just the technical side of our profession.

This company!
Ugh.

Two days ago we had an hour and a half meeting on which projects to focus on, with the result being all seven are top priority. Because of course.

Last night I told my boss why an api he has me hitting always returns 401s; even gave him the line# responsible for the response (in his code). After an hour and sixteen minutes of him debugging, he finally admitted I might be right. zzz. This morning, he tells me it's on my end, and to ask someone else for their project's API code. The problem is that the server is not accepting the new application's key, since that key is not in the allowed list. That other project works just fine. Guess why? Their key has been whitelisted for months. But it's totally my code. Yeah. Bloody brilliant. 🔅

Anyway, today we're discussing "Winning with Accountability," a 100 page book that boils down to "do what you say you'll do, by when you said you'd do it, and take responsibility if you don't." But a huge part that the boss is stressing is: provide the exact date, time, and timezone of when things will be completed by. I mean That's fine for sales calls and reports and such trivial busywork. But dev projects? Not so much.

And that's been my past three days!
Friggin joy.

DO NOT let employers demoralize you into staying with the company.

I've been with this one company for about 2 years. Everything was great, despite being underpaid, and having a lot of responsibility (I was the only front-end developer maintaining 4 big eCommerce sites).
One day about 2 months ago, I got a better offer. Better pay, more freedom, and way less stress (Customers screaming in your ear vs. no customers at all).

I talked to my team lead since I wanted my company to have a fair chance to counteroffer - I was fairly comfortable after all, and I felt like it would be a nice gesture.
If my team lead had just said "No, sorry, we can't counter that offer", there's a big chance that I would have stayed with them anyway. Instead, I got a fairly uncomfortable and personal rant thrown back at me.

He basically said that I should be happy with my salary, that he didn't feel like I had much responsibility, and that "I wasn't the type of person companies would hire for that salary".
He ended by saying I might as well stay, as there was no going back if the new place didn't work out - basically trying to tempt me with job security.

I told him that I would think about it. The worst part is that I actually did, since his rant really made me feel somewhat worthless as a developer. Luckily I came to my senses, and sent my resignation the next day.

I talked to an old coworker today, and they are still unable to find a developer who wants to take the job. I see that as justice :)

tl;dr: If a company tries to make you stay by demoralizing you - Run.

Qualification != proficiency

Worked at a company where this bloke (Jepediah mcShitFart we shall call him) had enough programming certs and qualifications to fill a page.

I was the one fixing his fuck ups, because he coded like his ass, debugged like his ass, talked like an ass, and used to shrug off responsibility like an ass. Hr did nothing because he 'was a long time employee'.

Plus, I have met hundreds of programmers who would put many to shame, and they don't have a single qualification.

I login this morning

Everyone going crazy as prod is broken in a million ways. 2.5 million exceptions In 24 hours.

We talk for 1 hour and solve nothing.

I diagnose the 2 biggest sources of exceptions and explain every step I took with screen snippets to reach my conclusions

The one other competent person on my team agrees. Otherwise complete silence.

I'm told not to fix the issue because I am leaving in 6 weeks and other people have to start taking responsibility.

No one fixes the issues. Instead they leave early. Now it's the weekend and the product is fucked.

Fucking useless people. Can't wait to leave.

Public service announcement: Do not get married to your language, tools, or way of doing things. If there's an easier solution to something, try it before dismissing it. No language is perfect, and dumping everything on the responsibility of an API or framework can cause more headache then solve it.

Case in point: I love Java for backend programming, but node.js is a better solution to frontend programming then depending on JSP's and HTML within the same Java project. Less things go wrong and it's easier to debug issues.

There is no best programming language. Only best practices and using the right tool for the right job.

#exceptC++fuckthatlanguage

:^)

Someone fucking scratched my personal laptop. No one at home ready to take the responsibility. 😒

Fun fact: the cape of the Batman in the arkham game series was the responsibility of one guy, and it took him 2 years to provide the perfect flexibility, fluidity and strectchibility to it for the final installment of the game arkham knight.

I'm tired of everyone playing the fucking victim all the damn time.

Grow the fuck up and take responsibility of your fuck ups, not blame everyone but yourself.

God people piss me off these days

The Indian state of Kerala uses Linux(Edubuntu) in all the schools. This incident happened back in 2010. I was not that proficient in Linux but I liked it for some reasons.

So one day, one of my IT teachers was handed the responsibility to edit a video. Being the School Student IT Convenor, he asked for my help. I'm no Video Editor but this thing was so easy that Openshot was enough.

While I was at it, he said: "Why does the govt. want us to use such unprofessional stuff? If it was Windows we could do everything very easily. Who is ever gonna use Linux in a professional environment? The govt. is spoiling the children by urging them to use Linux, Free Software and Open Source."

I couldn't argue that day. But today I so wish I could go back and roast him!

It's fantastic how you blame me, the back-end developer, for the things that the manager, business analyst, and front-end developer missed.

The front-end developers didn't make the user interface and admitted they didn't get to do it and outright forgot about it due to workload, oh it must be the back-end guy's fault for not asking them. You, the manager, have no fault here at all. Why are they overloaded again? And they, as the developers who totally missed out, were just innocent creatures who "were not informed".

The business analyst admits that he thought I was the front-end developer even though I corrected him during the first meeting where he said, "Oh okay, so Rutee is the back-end and <this other guy> is the front-end." EVEN THOUGH every day, we have a meeting and you see my JIRA ticket in all caps "BACK-END". Ever thought about asking? Then the manager comes in there and says, "No, it's not your fault. We as a team should take responsibility. That's how smart teams work." And yet your fucking face, I hate your face, man, and your fucking insinuations. I swear you're all just looking for a scapegoat, now it's making sense why you borrowed me.

While I'm doing my job here minding my own task and knowing that shit has been assigned to the proper person, the manager, business analyst, and other developers who's been in this project for years never bothered to ask for updates regarding the front-end until now. Why is back-end making noise the past few weeks? Because someone is WORKING on it. Someone is RAISING issues. Someone is CLARIFYING the requirements.

I had my own problems. Your requirements are severely lacking, your setup fucking sucks and doesn't fucking work, there were issues and dependencies from several other teams, and now it's my fault that I didn't ask about the front-end? How is that? I create the API, you fucking call it. If anything, you should be asking me about the endpoint but I guess I have to do EVERYTHING and know EVERYTHING in this project where I was just borrowed and I'm technically the new guy here.

I guess it's a "let's blame the new guy" game around here. You can hire the most senior of all developers you can but no one can ever just guess or read your fucking minds. You can't just put someone in one project and expect them to know all your processes, your repositories, your developers, your fucking uncommitted code changes THROUGH EXPERIENCE and PROGRAMMING LANGUAGE PROFICIENCY. This has nothing to do about proficiency and being proactive. I can be proactive TO AN EXTENT. I can't do YOUR job for you.

Jesus fucking Christ. This project is so disorganized and yet you can't acknowledge that. Then I would get an advice from someone else that we should have talked while front-end is there. He WAS, he's even on the invite. Every fucking time shit hits the fan, you all get a week to fix something and I get a couple of hours or a day. Issue two weeks ago? Resolved Friday after my shift, yet I managed to deliver the next morning. Issue last week? Resolved Friday afternoon, yet I managed to deliver before end of day.

"This is the first time this happened." I highly doubt that. You just want to correlate my *new* presence to your failure so you can insinuate that the new guy is to blame. Your team sucks. Your management sucks. "Oh, that's just how he manages, he tells you the end goal and it's up to you to THINK what you have to do." I did THINK but why the hell do I have to THINK for them or for everybody else?

So yes, another rushed deadline. Another excuse for the slacking pieces of shit, "Oh, I can't do my job because back-end doesn't have this other endpoint I need for this one. Guess I'll go home." When did you say you need another one? "Just now. But you should have known earlier if you asked." IF I ASKED. At what point of my life would I randomly ask, "Do you need this endpoint that isn't part of the requirements but does this/that?" where "this/that" is some functionality I know nothing about because it was never discussed.

Seriously, fuck you and your fucking requirements. You fucking lazy pieces of shit cunt whore motherfucker. I hate all of you. You ruined my entire fucking month. How do you expect this to be less chaotic when you defend the slackers and punish the ones who actually do their jobs and use them as scapegoats?

Three more fucking days, man, and I'm out of this shit. When I get back, I hope you don't bother me with this shit anymore. Your mom's a hoe and I'm accepting calls from recruiters anyway.

I am old enough to go to jail.
I am old enough to have my own household.
I am old enough to pay my own bills.
I am old enough to have children.
I am old enough to take responsibility for my hypothetical kids and for my self.
I am old enough to gamble, drink and lease cars.
I am a self confident dude who took responsibility for creating machines that were worth millions.
And so on and so on..

But hey, it is ok if the fucking teacher at technical school treats you like a 16 yo pubescent child. Im glad he is interested whether i do my god damn homework. And yes, it is totally fine for me, that im getting treated like a unworthy dog who needs surveillance.
So, maybe i should suggest that we should ask for permission if we want to go to fucking toilet. Yes. That would be great. Gonna do that.

Playing cool with people who

- Do the same mistakes repeatedly
- Do not think through use cases and blabber out the first thing that comes to their heads
- Are always downplaying the effort others put into their work
- Do not know when to have a discussion
- Do not take responsibility for their mess
- Are rude to newbies who are trying their best
- Are mean to the minimum wage workers

LAST MINUTE:

The heavenly time window we're all thankfully entitled to!

Its where 90% of my productivity lies,

Its when 80% of my projects were developed,

Its when 'responsibility' synonymous to 'panic',

Its when i start to realise the dark and deep depths of the universe,

Its what gives me my purpose in life.

Just wanted to say cheers to all those coders among you who make sure their login is encrypted, their passwords are hashed and salted, their codes are tested and their forms are code injection safe.

No client will understand what you did, so take my props for it! After all, its our responsibility to make sure software is secure. That's all :)

Man I really need to get this off my chest. So here goes.
I just finished 1 year in corporate after college. When I joined, the team I got was brilliant, more than what I thought I would get. About 6 months in, the project manager and lead dev left the company. Two replacements took their place, and life's been hell ever since.

The new PM decided it was his responsibility to be our spokesperson and started talking to our overseas manager (call her GM) on our behalf, even in the meetings where we were present, putting words in our mouth so that he's excellent and we get a bad rep.

1 month in, GM came to visit our location for a week. She was initially very friendly towards all of us. About halfway through the week, I realized that she had basically antagonized the entire old team members. Our responsibilities got redistributed and the work I was set to do was assigned to the new dev (call her NR).

Since then, I noticed GM started giving me the most difficult tasks and then criticizing my work extra hard, and the work NR was doing was praised no matter what. I didn't pay much attention to it at first, but lately the truth hit me hard. I found out a fault in NR's code and both PM and GM started saying that because I found it, it was my responsibility to fix it. I went through the buggy code for hours and fixed it. (NR didn't know how it worked, because she had it written by the lead dev and told everyone she wrote it).

I found out lately that NR and PM got the most hike, because they apparently "learnt" new tech (both of them got their work done by others and hogged the credit).They are the first in line to go onsite because they've been doing 'management work'. They'd complained to GM during her visit that we were not friendly towards them. And from that point on if anything went wrong, it would be my fault, because my component found it out (I should mention that my component mostly deals with the backend logic, so its pretty adept at finding code leaks).

What broke my patience is the fact that lately I worked my ass off to deliver some of the best code I'd written, but my GM said in front of the entire team that at this point "I'm just wasting money". She's been making a bad example out of me for some time, but this one took the cake. I had just delivered a promising result in a task in 1 week that couldn't be done by my PM in 4 weeks, and guess what? "It's not good enough". No thank you, no appreciation, nothing. Finally, I decided I'd had enough of it and started just doing tasks as I could. I'd do what they ask, but won't go above and beyond my way to make it perfect.

My PM realized this and then started pushing me harder. Two days back, I sent a mail to the team with GM in cc exposing a flaw in the code he had written, and no one bothered to reply (the issue was critical). When I asked him about it, he said "How can you expect me to reply so soon when it's already been told that when anything happens we should first resolve within the team and then add GM in the loop?" I realized it was indeed discussed, but the issue was extremely urgent, so I had asked everyone involved, and it portrayed him in a bad light. I could've fixed it, but I didn't because on the off chance if it broke something, they'd start telling me that I broke the tool, how its my fault and how its a critical issue I have to fix ASAP, etc. etc., you get the idea.

Can anyone give me some advice of how to deal with this kind of situation? I would have left but with this pandemic going on, market being scarce and the fact that I'm only experienced by 1 year, I don't think I qualify for a job switch just now.

I joined a company 6 months ago.
No CTO.
No development process.
Spagetti code.
Takes loads of new requirements on top.

Later
I advised the software head and managing director on how to improve our software development process.
New tools
Less requirement good quality software
New products and micro services.

Both of them agreed but they said they are waiting for new CTO to confim as an authority and responsibility.

Well I cant do much just to do my work.

1 month ago new CTO joined
Revised whatever I advised and implementing it right. I like it.

Got my confirmation after 6 months instead of 3 months.

CTO called me in for review and gave me 2/5. And said you need to improve more.

I asked him, in what do I need to improve.
He replies in technologies and development process.
And he takes credit for all changes and implementation.

I argued about it. I already suggested what you did but was ignore because we didnt have CTO.
Hes like ignored me.
Fucking you CTO.

Office manager sending a mail that all spaces now only have "sustainable vegan leather" furniture, "to carry responsibility for the planet and commit to a greener company image".

You mean you bought uncomfortable plastic chairs.

Vegan leather is just fucking plastic.

Not all plastics are bad, but in this case it's a very toxic plastic, a PVC softened with phtalates and stabilized with cadmium stearate, produced cheaply in a country with no regards for public health or the environment.

It's about as sustainable as munching down a vegan quinoa avocado salad in a private jet on a transatlantic flight.

There are moments where I'm glad that I'm still working from home, because I would have planted that ugly fucking desk chair straight into the equally ridiculous power-slurping hipster "sustainable vertical herb garden" with its 500 watt growlight bulbs.

Would you board a plane that you were resonposnible of programming?

Pm: '[...] So when will you set up the server its urgent'

Me: 'look buddy i applied here as a java dev, ended up doing fronted. Fine, i like js, i can do that. But then dont fucking ping me daily with server stuff what has been overcomplicated and i got no idea about, theres a backend team, ask them.'

Pm: 'you said you would do the frontend'

Me: 'yeah that doesnt contradict a word i said'

Pm: 'you took responsibility, fix it'

Me: '?????? THATS WHAT IM SAYING YOU FUCKFACE COCKSUCKER ASSHOLE THAT I DIDNT AND I WONT, FUCK A HORSE'

Last year I applied for a similar position to that I have now (Front-end Dev), but with a higher salary and less responsibility.

The interview went fairly well I thought, but I was also given a short written exam, where I was supposed to point out errors in the code provided. I'm certain I got everything right but I took too long (about 20 minutes for 20 questions) and they got inpatient pressing me several times.

My excuse was that I haven't used a pen in about 3 years. My hand didn't know what was happening! Who even writes anything anymore nowadays?!

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.

Week 26 advice - you all probably know this but good to refresh!

Eat healthily

Sleep well

Document clearly

Annotate your code

Use version control properly

Keep yourself in check with project management tools

Your peers are your friends... And competition.

As much as your boss is an idiot respect them and your life will be easier.

With great power comes great responsibility; don't touch that keyboard until you think through what you are doing chances are your first idea is not the best.

Don't write quick fixes and say you will go back to clean it up later on when you have time. That time will never come.

be me
first year at the college
C course in computer lab
teacher says "we will connect to school servers via ssh and compile with gcc"
do as said
suddenly a nice idea "can i use sudo?"
try something starts with sudo
server response: "with great power comes with great responsibility. do you want to continue? "
omg its happening, press enter
"you have no permission" sad face

Before I took on my current position (internal transfer), I stated that for what my boss asked for I would need a small team.
He agreed to that and promised I would get 2-3 developers.
6 months after (with countless reminders) he told me I could train some people at one of our providers.
Turns out those guys were Java developers, even though I asked for C# (since our codebase is .net)
After a few training sessions, where concepts as source control were a big topic ("why not just copy the code to a new folder with _good_ naming?"), I gave them a test assignment.
After reviewing their code I just gave up. They cannot program. They don't understand concepts like scoping of variables. Concepts of separation of responsibility.

I told my boss this but I had to make it work with them.

I went to my bosses boss (Head of IT) with my resignation in hand, since I felt my boss didn't want to support me actually getting a team. After a few talks I was asked to "keep it cool" and wait until he presented his new organization.

Now my boss asked me for which skills new developers should have. To which I could just laugh at him and forward countless mails from the last 6-8 months asking for developers.

<Irony>I love my boss</Irony>

Well on my first job we had to integrate payment gateways in client apps for online payment. On my second week in office I published an app on the play store with payment gateway credentials for a different client cause they were there as default values. So the money for one client would go to the other. Nobody noticed it for two weeks and when they did, I thought I had just lost my job and also I would now have to pay all the losses out of my pocket but fortunately I didn't have to cause no transactions​ had yet been made. After that I always checked my integrations atleast five times before publishing. The incident scared the shit out of me but taught me the value of developer responsibility.

Lemme be frank for a moment

Just because the compiler tells you that you need to do a certain thing, DOESN'T MEAN YOU SHOULD SEE THAT AS THE ONLY FUCKING SOLUTION

DON'T START FUCKING UP THE SINGLE-RESPONSIBILITY PATTERN JUST BECAUSE THE COMPILER SAYS YOU SHOULD, HOW DENSE MUST YOU BE TO THINK THAT'S THE FUCKING SOLUTION?! PERHAPS YOU SHOULD DIG A LITTLE BIT DEEPER? I CAN'T EVEN LAUGH ABOUT IT IT'S SO SAD. DEADLINE IS GETTING CLOSER DAMNIT

Oh btw, another instance:

"I'm doing X to achieve Y because I'm more familiar with step 1 of X"

Fine, but that takes more time and can be done in way Z, in that way, you don't loose precious time and can just work on the other steps in the proces that contineously get harder.

* Person proceeds to do X anyway and get stuck, in the end having nothing done *

🙄

I like helping people, I really do

But I'm not going to loosen the knot around your neck if you keep tightening it

#First

I joined a start up and worked after college hours as an intern over there. I would usually bunk my college and go to my internship. I had limited knowledge at that moment. I worked very hard over there because I wanted (still want) to gain practical knowledge.

Almost a month into it and I had to take a break from it because I had college work. Rejoined the same start up during my vacations. Worked quite a lot and learnt quite some stuff. I continued the internship after my one month vacation for another month once my college started. All this while I was not being paid, not even a little bit of allowance. But that didn't matter because I wanted to learn

Fast forward six months to November 2016. I have been placed in an MNC through my college placements. One day I get a call from this start up owner(we had become good acquaintances by then) if I was willing to work as a paid intern while I was working on the projects that the company landed (so I guess as a free-lancer) and as an unpaid intern while I was working on the company projects. I agreed. Jump to December. I have joined and started working on an Android project of this very big company.

At time point, I should inform you'll that I'm not very good at Android and that the company size is very small. Company owner plus the tech lead in one city (where I'm from) and another two full time employees in another city. Out of which one quit to start his own company apparently. The start up would primarily employ interns and provide exposure to them while getting their work done.

Back to the story. The tech lead vaguely assigns everyone their work. Everyone over here includes new interns and previous interns like me who will get paid some amount. 3-4 days into the project, the tech lead quits. The tech lead and the company owner call three of us and says that one of you will have to be a project manager for this project. And then both of them and 2 of my colleagues look at me. And I don't know what to say. I hesitate initially because it's too much responsibility but agree to it finally.

The next day I come to office and read about the project thoroughly and catch up with my colleagues about the progress. The entire day I'm panicking about what I'm going to do. In the evening, my boss tells me that we have to go for a meeting with the client for whom we are doing this project. At this moment, the shit out of me has been scared. Mostly because I don't know what the fuck am I going to do over there apart from being stupid and asking dumb questions. So we reach the client's office and wait for him. The entire time I'm thinking to myself that I'm going to drown this company by opening my mouth. Surprisingly, all the questions that I asked seemed legitimate and I asked a lot of questions. And so I didn't drown the company after all...phew!

It's been more than a week. And holy fuck! What a pain it is to manage people. Half of my time is spent on updating excel sheet about their progress, where are they stuck and what is needed. And the other half about thinking what the fuck am I doing or how am I gonna do it.

So to sum up, intern-turned-freelancer-turned-project manager who has no idea what the fuck is going on. Seems pretty crazy, don't you think.

Russian Roulette - Developer Edition:

Have a random generator for a number between zero and one hundred. Every developer present picks a unique number.

The generator must then reroll until somebody's number of choice is the result. It is now this person's responsibility to begin an untested deployment at 4:59pm the next available Friday.

My instincts are telling me that i should resign from this company asap.

My team lead knows a to z of the project and he is the all rounder guy here. If my team lead leaves, I could be the one replacing him. But i don't want to accept this kind of responsibility.

My life goal is to not get sucked into the 9 to 5 life or work in this kind of environment.

The only pro i find is that i now have few more cool friends.

But I'd rather be be my own boss and work 24/7.

I now feel like living a lie going to work everyday..

People at school believe using a library == Script Kiddie who can't code.

The icing on the cake is that they call themselves great programmers, and because they are 'superior' they don't use libraries and never will...

I smell bullshit

Oh, you have used the python math library... script kiddie.

You use jQuery, you little script kiddie?

(Because I have taken responsibility for my learning of languages and that is obviously not allowed)

I'm really happy today. I'm not sure why, my life is in ruins on many levels, but at work I'm having fun and getting a lot more responsibility now. I even get to lead a meeting on Monday and be part of the management of a project which means I'll have people reporting to me. I suspect it's a sneaky way to get me more invested in the company so I'll want to stay after my studies but I enjoy it regardless. I finally have enough I need to keep track of to warrant carrying a notebook around and it makes me really happy 😂Hope you're all having a great day too!

This happened via mail thread today.

Boss: we need this new brilliant feature I just made up and running asap! Top priority, it has to be done well, for my reputation is on the line!

Me: *looks at the specifics* 'kay, looks easy enough, this evening max and it will be ready. I just nees some extra info about what kind of data validations (I speak no accountant) are needed, and some other details (a total of 3 questiona).

B: Sure! Remember, it needs to be perfect, as my reputation is at stake. Call me on the phone and I'll give you the details!

M: Can't you answer via mail? Thua way both me and the other devs will have clewr guidelines

B: Just call me! Why do you need it to be written down? It's faster this way!

...Fine. I'll keep asking until you're ready to give me a written answer to my questions. No way I'll take security details via phone for something you want in production this evening. No chance in Hell I'll take responsibility for "misunderstanding" what you said on the phone. Why does it always has to be like that?

Today I learnt never trust a coworker or see them as a friend.

So I have been thinking of quitting my job to further educate myself. The work I sit with is mostly the tiniest CSS changes. Which is frustating and demotivating to work with.

One of my coworkers told me in confidentiality, that he was looking for another job in another company and he only told me. And wanted to keep it secret from everybody else. I felt this gesture of him trusting me meant I had to trust him back with something else. I told him that I am applying for an education for later this year. But I don't want to say anything before it has been approved.

He understood fairly well and we got to be a thing outside work.

Last week I learnt I was seriously underpaid compared to all other coworkers despite me being one of the people with the most responsibility. I felt this wasn't right, so I talked to the pay responsible and said this paygrade isnt substantial, and I felt it was demovating to go to work knowing I was the least paid coworker.

He understood fairly well he said and said he would bring it into management to discuss.

But then he said one last thing. "I have heard something about you applying for another education, is this true? Since I have seen you put your summer vacation really early this year"

I had to lie and say no, that was like before I knew I landed a job here.

I dont wanna say anything to my company before I get the approval from school.

But still now I am in this position of feeling stupid for trusting this coworker, mad that he violated my trust and feeling very guilty for having to lie to this person's face.

"As a team, we have the shared responsibility to ___".

(replace with ALL of the following: resolve bugs, do junior's code reviews, clean up dead code, keep the kitchen clean, improve test coverage, write documentation, order coffee beans, etc)

NO. JUST FUCKING STOP RIGHT THERE. Shared responsibilities do not exist. A single person is responsible, and can optionally delegate tasks.

EITHER I DO IT AND I'LL BE FUCKING AWESOME AT IT, OR SOMEONE ELSE DOES — BUT I'LL SLAP SLACKERS IN THE GENITALS WITH MY KEYBOARD.

Fucking startup hipsters with their community driven attitude, this way no shit gets done, ever.

I told my boss that I felt my job filled the work description of a “senior engineer”. He asked me to write down a few sentences why I thought so, so he could suggest a title change to the board. I did and two months later it went through! Got a 15% increase! :)

I also was kind of “head hunted” for a different job a few weeks before, but hadn’t received any real offer from that company yet. This got known to my bosses boss and he urged me to talk to my boss before making any decision. I think that also helped... :p

I’m now the only senior engineer in my department, just because I take on a little extra responsibility and do a little more than what is expected of us.

me: "Why is the QA guy manually typing JSON into a production environment?"
asshole: "That's not your responsibility."
me: "Why didn't you just migrate data? This is dangerous."
asshole: "You need to go sit down."

Management and other senior leadership have been really shitty recently, I got showed up in a meeting in front of about 20 of my peers and people myself/them and treated like a fucking child.

So I took a week off, uploaded my CV and today, after about 30 calls with offers, I attended two interviews and got two amazing offers of employment!

More money, less responsibility, better career development, modern company and less stress!

I’m so happy and can’t wait to go into work on Monday morning and tell them all to FUCK OFF!

This freaking server migration has been going on since Thursday night (it's now Sunday afternoon, for reference).

I've been on the phone since 1830 last night, which means I'm away about 18 hours in. I'm finally eating dinner, breakfast, and lunch.

People who theoretically should know the environment better than I do argued with me in front of customers and then tried to say she was agreeing with me all along. She tried dropping off the call SHE WAS RUNNING 6 hours before she should have, because I was on and she thought it was becoming my responsibility. HAD SHE LISTENED, we could be done by now.

Some days before my graduation me and my roommate were invited for an interview. We arrived at mutually agreed time.
The interviewer asked nothing about our coding knowledge. just some personal questions. after a brief conversation he started to explain the job responsibility to us. It seemed we were both hired. We were happy that we are getting full time jobs before graduation. And then he asked us if we can commit to stay in the company for year. We both agreed if the terms are good.

After that he tried to hire us for
$125 USD per month.
we did not spent another minute bargaining with him. We just left saying that we will let you know.
We were shocked.

I am DONE with this woman.

Background: we're a team of 3 developers and I'm the junior in this team and I've been in this shit for a year now. 2 months ago the team leader left for another project and I had to stand in for him in every responsibility against the PM and other teams.

Now I not only had to endure this insecure woman but I was also supposed to work with her! Fast-forward to today, the team leader is back and I thought I could put my headphones on and work peacefully at last.

But no!

I've found out she's sent a faulty code to production - no big deal - and said that over chat (although she's sitting right behind me):

Me: We need to fix this.
Her: What?

Me: *giving some details about the issue*
Her: Your attitude is important when you ask me to do something. Whenever you're writing to me you're typing on your keyboard like you're going to break it on my head.

*me not knowing what to say at this point because we had something stupid like this before*

Me: So you're offended by the sound my keyboard makes? (I have mx brown switches by the way and they're not even loud)
Her: No you're typing too fast when you're writing to me. The sound echoes in the office.
...

Can you fucking believe this shit? I hate people that think they can educate me but have no idea how to rationally respond to situations and take responsibility! I didn't even say anything!

And she's been saying to me she hadn't had a problem with any other people for gazillion years who knows how long and why would she cause a problem now! And thinks I am the problem, fuck YOU!

Since you don't like receiving orders why hadn't you taken the place when the fucking guy went for another project but I had to take all the responsibility? I know why you fucking entitled bitch.

Because you HAD NO IDEA AND YOU STILL DON'T.

So shut the fuck up and do as I say.

Kind regards

!(!rant)

So I wanted a raise and the only way was becoming a software lead.

With that title you get more money but also more responsibility, so you have the last word in technical decisions, you review architecture, do tech interviews, guide the less experienced, etc. I can handle that, even as introverted as I am.

What nobody told me was that I was going to spend my whole time on fucking meetings, one after another, I have not touched my IDE in days, I hate this shit already.

Careful what you wish for they say, so true, I'm stuck here and I hate my job now, probably going to quit as soon as I recover my life, if ever.

Building a business can hamper one's development urges!

I have been building stuff since 2008. Took my first job in 2012, won a hackathon at Yahoo right after that. Got an amazing team to work with! Our team converted the hacked product into a proper product using Django and AngularJS. Those were the fun days. At that time AngularJS had just come out and I was under the dilemma to use Angular, Ember or backbone. But with all this came the responsibility to build a business out of our product. It didn't happen eventually though.

So I moved on to cure my entrepreneural itch and went on to start up an e-commerce startup along with my day job. It started getting good traction and I finally left my day job to focus completely on it. It's a sticker marketplace and I had to focus a lot on the actual physical product, improve the quality, tackle business development and stuff etc. In all this, my habit of creating stuff with code kind of got the back seat. Everyday, I see such exciting technologies come up and I want to try them out. I have been itching to create a native app using react native. Try to build a skill for Amazon Alexa.

On one side I am happy that I have been able to build a brand and become the largest sticker marketplace in India providing super awesome reusable stickers, but on the other hand, managing the business on a daily basis is killing the developer in me :(

Does anyone else building a business which involves a physical product also face a similar problem? I think I should just take up weekend hackathon type problems and try to solve them using the technologies I want to learn. Example, I have been meaning to build an app for our company. I think I will start with that!

I have been following devRant for quite sometime now and it has been awesome. Finally, signed up and ranted today! 😊😊

Lets take some responsibility...

DISCLAIMER: I swear to god this is true. This is a completely unfabricated anecdote.

Soon we are moving to a new office space, and my department have been delegated the responsibility of moving all of the computers from the old work space to the new one. I was a little confused at first, because I'm a software developer, not a removalist.
It gets better.

We just had a meeting the other day, and my manager had advised us that we were to be moving the machines on a Saturday. I confirmed whether we were being paid overtime, simply because I had never worked a Saturday before. My manager replied (this is paraphrased but ultimately accurate) - "It's unpaid. Because you get paid a salary, you're expected to do unpaid overtime here and there. We have christmas parties and nights out, all of which come out of the companies pocket. Not all companies do this, so it's only fair you give back".

I honestly couldn't believe it. I was being asked to spend basically the majority of my day off moving computers from one site to another, for free, purely because it's "expected". Am I the only one who thinks this is crazy?

Long story short, I went home and started updating my resume.

Incredible how Git makes you a more responsible developer

Dear fellow mate,

I can't reject your request to leave. You have your right to request casual/medical or any suitable form of leave. It's up to the HR to do their calculation and process your leaves.

All I can do is tell you the overview of our team's tasks status. And status of tasks assigned to you. Then tasks status of possible colleagues who can cover your position.

The reason I shared those with you is that you act like you have no knowledge about them.

That's all I have for you. Decide on your own what to do. But consider with this new information.

Regards,
Cursee

I fucking hate ppl who transferred from business program into the CS program. They are all talk and no action. Literally this girl who claim to be “good at algorithm” doesn’t even know how to write a quick sort. In the past 2 months I have received more request from business program students to “help debug program” than all of the other departments (science, engineering) combined. Worse, some just straight ask for my code so they can copy off my implementation.

Seriously, it’s okay if you don’t know how to do stuff. But it’s not okay if you don’t want to learn AND feel so fucking entitled. I have a lot of homework as well, it’s not my responsibility to **help** you.

Manager: "Hi Almond, how is X going?"

Almond: "...I don't know, Bob is in charge of that."

Manager: "Ok. Do you know the status of Y at all?"

Almond: "Not sure, isn't that Bob's responsibility too?"

Manager: "Well, yeah, but I never seem to be able to get a good answer out of him. Find out on both fronts and let me know ASAP please"

...sure, I know how this goes. I'll stop all the dev work I'm doing, do your job for you, talk to the lazy bonehead that never bothers doing anything, report back that he's done sod all (or still "in a requirements gathering phase" as he puts it), be asked "why is he taking so long", have a bit more back and forth, then decide we'll just leave him be as actually trying to get him to do any work is going to be too much like hassle 😒

Something I can never understand with my boss. This really makes me concerned with the future of the company imo.

I was given a project contract with all of the specifications and how many hours I had to each assignment.

I did my work and I kept myself within the time limit.

Today my boss and I had a status meeting about the project. In which he had an addition to one of my features which would basically require us to start over with it. He started to blame not only me but also my coworker on why we didnt predict that HE would want this addition to the feature. We got into a heated discussion over him putting that blame on us. My point I stuck to, was that the responsibility of specifications lies in the person who briefs a worker, not the worker who is supposed to play guessing game of what the briefer want. He vehemently denied that is how things work.

He basically shushed me and said that is how the order of things go.

Am I in the wrong here?

Let me paint you a picture.

It's the day after code freeze. Code has been branched. It's time once again to verify tickets and run smoke check so we can begin our 3 days of blitz testing before we deploy.

As a team we all have roles to play in this process. Yet, every stinking release it is like pulling teeth to get everyone to take the initiative and verify tickets and run smoke check. Our principled engineer even reached his limit this morning and blew up on everyone.

When you are being paid good money to do a job, you need be an adult, be responsible, step up and do your job!

What really matters about being a developer is how you use your skills, you can know lots but you need to be creative and open-minded.

Don't use your skills for stuff like this, with great power comes great responsibility, don't abuse your powers to give people camcer

One of classmates presented an idea of children tinder as her final project. (To find friends, not...you know..)
So, after a pretty logical question how they're going to prevent it from turning into a platform for kidnappers, they said 'I don't know, not my problem, tinder doesn't do it, Facebook doesn't, it's not my sphere of responsibility. And as a developer I cannot guarantee anything, why are you asking me this you're wrong'
Bravo.

P.s. idk why both of my latest posts are about tinder lol

Best practice of the day:
Single responsibility principle - One class should be responsible for everything!

Either that or someone was payed for LoC. 😁

The best decision I ever made was moving from a big company to a very small one.

I used to work for a large international consulting firm in the model development team. Everything moved so slowly, there were huge amounts of pointless meetings and other time-sinks, we were surrounded by people who were being paid a lot of money but added little or no value, and the general atmosphere of the company was quite depressing. We spent more time having to make PowerPoint presentations for senior management trying to explain why you can't just hire 100 devs and have a product 100 times faster than we actually did developing a product.

I took a bit of a risk and moved to become the fourth person (and second developer) at a niche software producer to take over product innovation and lead product development. Immediately I felt so much happier and realised how much the previous company had worn me down. Everyone works hard and efficiently because your individual output is so much more important to the success of the company and the work you put in comes back to you financially without being syphoned by layers of valueless management levels or time-wasters.

Having responsibility, seeing the impact of your own work and being rewarded accordingly is so important for your sense of well-being. I urge you all to try it if you're stuck in a big company that's wearing you down. And if you're considering moving from a small company to a big one: don't.

Oh I forgot.
Once I got promoted with more responsibility and my pay raised, but since I just passed some tax threshold for few $ my net income was more or less 1 hundred $ lower than before the promotion...

Worst exp. on a collab/group project?

Had a few, here is one.

Worked with a dev team (of two devs) in Norway to begin collaboration on providing a portal into our system (placing orders, retrieving customer info, inventory control, etc)

They spoke very good English, but motivation was the problem. Start the day around 10:00AM...take a two hour lunch...ended the day at, if I was lucky, 4:00PM (relative to Norway time). Response time to questions took days, sometimes weeks. We used Skype, which helped, but everything was "Yea...I'll do that tomorrow...waiting on X....I have a wedding to go to, so I'll finish my part next week."

I didn't care so much, I had other projects to do, but the stakeholders pounded me almost everyday demanding a progress report (why aren't you done yet...etc..etc.)
The badgering got so bad I told the project owner (a VP) if he wanted this project done by the end of the year, the company would have to fly me to Norway so I personally push things along.
When real money was on the line, he decided patience was warranted.

A 3 month project turned into 9, and during a phone meeting with the CEO in December
O: "Thanks guys, this project is going great. We'll talk again in February. Bye."
PM: "Whoa...what! February!"
<sounding puzzled>
O: "Um..yes? It's Christmas time. Don't you Americans take off for Christmas?"
PM: "Yes, but not until Christmas. Its only December 12th. Your taking the whole month of December and January for Christmas?"
O:"Yes, of course. You Americans work too hard. You should come over here and see how we celebrate. Takes about a month so we can ease back into the flow of things."
<Jack is the VP>
PM: "Jack wanted this project completed by the end of the year, that is what everyone agreed to."
O:"Yes, I suppose, but my plane is waiting on me. Not to worry, everything will be fine."
<ceo hangs up>
PM: "Oh shit..oh shit..oh shit. What are you going to do!?"
Me: "Me!?..not a darn thing. Better go talk with Jeff."
<Jeff is the VP>
J: "This is unacceptable. You promised this project would only take a few months. I told you there would be consequences for not meeting the deadline."
PM:"But..but...its not our fault."
J: "I don't care about fault. I care about responsibility. I've never had to fire anyone for not meeting a deadline, but .."
Me: "Jeff, they are in Norway and no one is working this project for the next two months. You've known for months about them dragging their asses on this project. We're ready to go. Services have been tested and deployed. Accounting has all the payment routing ready. Only piece missing is theirs."
J: "Oh. OK. Great job guys. I guess we'll delay this project until February."
<leave the office>
PM: "Holy shit I'm glad you were there. I thought I was fired."
Me: "Yea, and that prick would have done it not giving a crap that it's Christmas."
<fast forward to Feb>
O: "Our service provider fell through, so I'm hosting with another company. You guys know PHP? Perl? I don't know what they called it, but it sounded so cool I bought the company."
PM: "You bought what? Are we still working with Z and B?"
O:"Yea, sort of. How's your German? New guy only speaks German."
PM: "Um, uh... no one here speaks German"
O:"Not to worry, I speak German, French, and Italian. I'll be your translator."
PM: "What? French and Italian?"
O: "On my trip to France I connected with a importer who then got me in touch with international shipper in Italy. I flew over there and met a couple really smart guys than can help us out. My new guy only speaks German, J only speaks French, and R speaks Italian, Russian, and a little English. Not to worry, I'm full time on this project. You have my full attention."

We believe the CEO has/had some serious mental issues, including some ADD. He bailed within the first month (took another vacation to Sweden to do some fishing) and left me using Google Translate to coordinate the project. Luckily, by the end, the Norwegian company hired a contractor from England who spoke German and hobbled together the final integration.

If I hear anyone utter the words "technical debt" one more time, I swear to God, I will fucking kill them :-/

It's your fault your design smells like piss in the first place. It's your responsibility to fucking fix it. You can't just sit on your arse all day, coming up with new, "innovative" ideas that will build up more technical debt :-/ it's making the life of everyone around you, a big, irreparable mess.

devRant is awesome, but Disney also manages to light-up my day.
This is how Wall-E became a beloved member of our team, and helped me put a smile on my face throughout a very frustrating project.

It all started in a company, not so far far away from here, where management decided to open up development to a wider audience in the organization. Instead of continuing the good-old ping-pong between Business and IT...

'not meeting my expectations' - 'not stated in project requirements'
'stuff's not working - 'business is constantly misusing'
'why are they so difficult' - 'why don't they know what they really want'
'Ping, pong, plok... (business loses point) ping, pong'

... the company aimed to increase collaboration between the 2 worlds, and make development more agile.

The close collaboration on development projects is a journey of falling and getting back up again. Which can be energy draining, but to be honest there is also a lot of positive exposure to our team now.
The relevant part for this story is that de incentive of business teams throughout these projects was mainly to deliver 'something' that 'worked'. Where our team was also very keen on delivering functionality that is stable, scalable, properly documented etc. etc.
We managed to get the fundamentals in place, but because the whole idea was to be more agile or less strict throughout the process, we could not safeguard all best-practices were adhered to during each phase of a project. The ratio Business/IT was simply out of balance to control everything, and the whole idea was to go for a shorter development lifecycle.
One thing for sure, we went a lot faster from design through development to deployment, high-fives followed and everybody was happy (for some time).
Well almost everybody, because we knew our responsibility would not end after the collection of credits at deployment, but that an ongoing cycle of maintenance would follow. As expected, after the celebrations also complaints, new requirements and support requests on bug fixes were incoming.
Not too enthusiastic about constantly patching these projects, I proposed to halt new development and to initiate a proper cleaning of all these projects. With the image in mind of a small enthusiastic fellow, dedicated to clean a garbage-strewn wasteland for humanity, I deemed "Wall-E" a very suited project name. With Wall-E on board, focus for the next period was on completely restructuring these projects to make sure all could be properly maintained for the future.
I knew I was in for some support, so I fetched some cool wall papers to kick-start each day with a fresh set of Wall-E's on my monitors. Subsequently I created a Project Wall-E status report, included Wall-E in team-meetings and before I knew it Wall-E was the most frequently mentioned member of the team. I could not stop to chuckle when mails started to fly on whether "Wall-E completed project A" or if we could discuss "Wall-E's status next report-out". I am really happy we put in the effort with the whole team to properly deploy all functionality. Not only the project became a success, also the idea of associating frustrating activities with a beloved digital buddy landed well in our company. A colleagues already kickstarted 'project Doraemon', which is triggering a lot of fun content. Hope it may give you some inspiration, or at least motivate you to watch Wall-E!

PS: I have been enjoying the posts, valuable learnings and fun experiences for some time now. Decided to also share a bit from my side, here goes my first rant!

I finally fucking made it!

Or well, I had a thorough kick in my behind and things kinda fell into place in the end :-D

I dropped out of my non-tech education way too late and almost a decade ago. While I was busy nagging myself about shit, a friend of mine got me an interview for a tech support position and I nailed it, I've been messing with computers since '95 so it comes easy.

For a while I just went with it, started feeling better about myself, moved up from part time to semi to full time, started getting responsibilities. During my time I have had responsibility for every piece of hardware or software we had to deal with. I brushed up documentation, streamlined processes, handled big projects and then passed it on to 'juniors' - people pass through support departments fast I guess.

Anyway, I picked up rexx, PowerShell and brushed up on bash and windows shell scripting so when it felt like there wasn't much left I wanted to optimize that I could easily do with scripting I asked my boss for a programming course and free hands to use it to optimize workflows.

So after talking to programmer friends, you guys and doing some research I settled on C# for it's broad application spectrum and ease of entry.

Some years have passed since. A colleague and I built an application to act as portal for optimizations and went on to automate AD management, varius ssh/ftp jobs and backend jobs with high manual failure rate, hell, towards the end I turned in a hobby project that earned myself in 10 times in saved hours across the organization. I felt pretty good about my skills and decided I'd start looking for something with some more challenge.

A year passed with not much action, in part because I got comfy and didn't send out many applications. Then budget cuts happened half a year ago and our Branch's IT got cut bad - myself included.

I got an outplacement thing with some consultant firm as part of the goodbye package and that was just hold - got control of my CV, hit LinkedIn and got absolutely swarmed by recruiters and companies looking for developers!

So here I am today, working on an AspX webapp with C# backend, living the hell of a codebase left behind by someone with no wish to document or follow any kind of coding standards and you know what? I absolutely fucking love it!

So if you're out there and in doubt, do some competence mapping, find a nice CV template, update your LinkedIn - lots of sources for that available and go search, the truth is out there!

Sometimes, being the only fullstack dev with access to a lot of systems gives you the ability to introduce functionality that:

A) prevents future errors

B) introduces new validations to users to make sure A) is prevented.

C) apply these changes to different projects

But most importantly...

D) without a single person in management getting involved or having to sign it off.

It's like running a company you own, but without owning it.

Granted with such power, comes the trust and responsibility of deploying changes with the adequate testing being done prior and handling change management, but fuck, sometimes I wonder if "god mode" for lack of a better term, is too much, or just enough to get the job done without the politics.

Frontend dev for 10+ years here.

"We can't afford to hire you as a senior, so your job title will be 'Frontend Developer' and your tasks will carry less responsibility than expected from a senior"

One year in, team of 2 handling 3 projects.

After merging with the parent company, we got business cards, mine describe me as a "Senior Frontend UI Engineer".
"Well, our customers only trust seniors, otherwise we can't send you to them".

Meanwhile a former colleague earns >1000€ more a month.

Yeah, fuck you too bosses!

Has it ever happened to anyone that you get hired as a backend java developer without going through any sort of evaluation and for some reason you start getting only design/frontend tasks and you politely complain but the dickhead says "well you should be able to do everything, and I want it before tomorrow" but you kind of need the money so "what the hell" and a couple days later you fully remember again how much you hate spending a whole day trying to get a bloody bar sticked to the bottom of the page while some dickass hits your slack and whatssapp with the nerving "where are my screens?" and start thinking "...do I really need to eat this month..." but anyways you make your research and ask for help and stop sleeping and do as much as you can to get the sh*t done and please the dickhead because you want his money?
...Anyone?
...No?
...Just me?
...Oh well, have a nice day/evening

A pm once told me that the whole point of managing someone was to give them the stuff you don't want to do.

From that project I learned that he didn't like to take responsibility for his own fuck ups.

I was supporting a legacy CRM app which front end used Visual Basic 6 and almost the entire business logic was written on SQL store procedures.

A "feature" of the product was the open code, anyone with admin access could modify forms, code and store procedures.

We also sold "official" (and expensive) consulting services to modify the code.

A long time customer owned this thing and it was heavily customized. They had hired us to change something, hired a third party to make other changes and decided to modify some stuff themselves because, why not?

Suddenly they came to product support asking to fix a bug. The problem happened on a non customized form.

After reviewing, I realized the form used several of the modified store procedures in the business layer. I tried saying we don't support custom code but my boss was being pushed and said "look into it"

All 3 parties denied responsibility and said their changes were NOT the problem (of course). Neither of them commented or documented their changes.

The customer started to threaten to sue us.

I spent 5 full days following every field on the form through the nested and recurrent SQL store procedures and turns out it was a very simple error. A failed insert statement.

I was puzzled of why the thing didn't throw any error even while debugging. Turns out in SQL 2003 (this was a while ago) someone used a print line statement and SQL stopped throwing errors to the console. I can only assume "printing" in SQL empties the buffered error which would be shown in the console.

I removed the print statement and the error showed up, we fixed it and didn't get sued
:)

Should’ve posted this after it happened, but it requires a bit of background anyway.

There’s this guy that oversees our OpenStack environment. My team often make jokes and groan about him in private because he’s so overbearing. A few months back, he had to take us to our data center to show us our new racks, and he kept saying stupid stuff like “you break this and it costs me $30,000” as if he owns everything. He’s just... one of THOSE people. Always speaks in such a condescending way. We make jokes that he is our “best friend”.

Our company is shifting most of our products to the cloud in response to the coronavirus (trying to make it an opportunity for “innovation”). This has involved some structural and responsibility changes in our department, and long story short, I’m now heading the OpenStack environment alongside other projects.

This means going through grueling 1-on-1 meetings with our “best friend”. It’s not too bad, I can be pretty patient with people, so I didn’t mind too much at first. Then a few things happened.

1. He sent a shared folder that he owned containing info related to the environments. Several documents were outdated and incomplete, so I downloaded them, corrected them, and then uploaded the documents to my teams file share, as I was supposed to since we now own the projects.

2. Several files were missing, and when I asked about them, he said “Oh, did you refresh the browser?”. I told him no, that I downloaded them locally and republished them to my teams server, because he was supposed to hand everything off to us at once. He says “Well, silly, how are you going to get updates if you’re looking at them locally?” and kind of chuckles at me like I’m stupid.

3. He insists on training me how to remote into one of the servers to check on cluster space, which in itself is fine. I understand others wanting to make sure things will be done right by the people who come after them. But he tells me to download SuperPutty. I tell him, “oh no, that’s alright. I don’t need putty”. He says “oh cool, what tool do you use for ssh?”. I answer him “Just Git. If I want to I can use a CentOs bash terminal too, because we have WSL installed”. He responds “You can’t ssh through Git”.
I was actually a little shocked. I didn’t know if he was serious or not so I was silent for a few seconds before hesitantly saying “yes you can”. He says “this is news to me” and I so I tell him “every single one of our build jobs fetches code from Git with ssh” and he seemed genuinely shocked and surprised by that.... so then it occurs to me to show him that you can ssh in Powershell and that REALLY blew his mind. He would not shut up about it for several minutes. I was amused until it just got annoying.

Needless to say, my team had been previously teasing me about having to work with him, so they found it hilarious when I told them afterwards.

I got the task to set up an NAS, because "server has too high maintenance costs".
I built two databases for this company and the big boss loved my work. (spoiler:not because my work was outstanding but because I, as a student, am cheap and willing to learn).
And now? Reality hit me for good. I looked for a enterprise worthy NAS solution, sent them the details, they bought it and now it's 00:00 in Germany and I'm sitting in the empty hall, trying to configure the storage to work like they want it. On a friday. Alone. As the only member of the IT-team. With way to much responsibility.

So... Yea, fuck you for good. I hope your backup gets an disk error at the same moment i quit. (but first gimme mah monney)

I had a delivery deadline on the same day when an urgent support request came in. My boss was a stupid sucker who was afraid of taking responsibility, and that's a vice I absolutely hate with bosses.

We had quite a heated argument where he just wanted me to give priority to both things, which I declined because I had no idea how much time the support research would take me.

Finally, he decided that I should work on the support item immediately, but only for up to one hour. He was totally surprised when I accepted that without further argument. I told him that all I had wanted from him had been a priority decision, and that was one.

Felt like explaining to my boss what his fucking job was.

VoIP meeting today lasted 7 minutes.
I have kept the board down to ~5 ticket average for the last 3 months.

Co-worker(jokingly): I guess we don't need you anymore.
CEO: Quite the contrary. @chenb0x may need a promotion.
Me: *smirks*

This is why I like working for this company. Love the culture....no matter how much I may bitch about the clients.

'How did I get here?' a young dev may ask.

1. Delegate where proper
2. Script whatever can be scripted
3. When the board is low in tickets, it becomes a recursive responsibility to keep it low.

Back story
-----------------
When I was hired, the VoIP board was sitting at a ~30-40 ticket average.

This is a story of me trying out maintaining a game server and eventually making a mistake, although I do not regret experiencing it.

A month ago I set up a small modded minecraft server because I wanted to experience a fun modpack together with some people from reddit. Besides this, I also wanted to see if I was capable of setting up a server with systemd and screen running in the background. This went great and I learned a lot.

The very next day I was playing with $annoyingKid on the server and everything was well. However the second day, $annoyingKid started pushing the idea to start up a normal minecraft server to build a playerbase.

I asked $annoyingKid 'What about financing, staff management and marketing?'

$annoyingKid: "I don't know much about that, but you can do that while I build a spawn!"

He also didn't want to reveal his age, which alerted me that he's young and inexperienced. He also considered Discord 'scary' because there were haxors and they would get his location and kidnap him, or something. So if he was supposed to become owner (which he desired), he had no way of communicating with a community outside of the game.

He also considered himself owner, while I was the one who paid for the server. 'Owners should be people who own the server', no matter how many times I told him that.

$annoyingKid also asked if he could install plugins on his own, I asked him if he knew anything about ssh, wget or bash because I used ssh to set up the server (I know rcon exists, but didn't want to deal with that at the time), he had no idea what any of those terms meant and he couldn't give proper arguments as to why he should get console access.

In the end, he did jack shit, he had no chance of becoming co-owner or even head-admin because he had no sense of responsibility or hard work. I kept him around as an admin because he was the one who came up with the idea. I banned him on day one after he started abusing his power when someone tipped him of. Even after me ordering him to ignore an annoying player he kept going, of course I could have prevented all this by kicking him earlier since all the red flags around him had already formed a beacon of light. He tried coming back, complaining that he should at least have his moderator rank back, but he never got in again.

A week later I got bored, I had had enough fun with ssh and the server processes to know that I didn't want to continue the small project, so I shut it down and went on to do stuff on GitHub.

Lesson learned: Don't let annoying kids with no sense of responsibility talk you into doing things you aren't sure you want to be doing. And only give people power after they've proved to you that they are capable of handling it.

Non-dev *random* annoyance:

Today in leave me the fuck alone, establishments have opened but social distancing still applies so don't go around approaching me while I mind my own damn business waiting for a car.

I rarely go out unless I have to pick-up food or buy groceries but there is this place I visit once every few months. I don't loiter in the streets, at the mall, or anywhere. I get out of the apartment, go straight to a specific place, do whatever I went there for (store - buy groceries, salon - get a haircut, etc.) and then go home. In short, I limit my time outside even before this whole pandemic so people don't get a chance to talk to me about shit I don't care about.

I thought it was perfect. I've been to this place a couple of times now but this time, it was different. The car pulls over in front of the salon. I get out and was walking straight towards the door when this random guy in front of the hotel nearby starts talking to me "Hey, where are you going?" Confused, I pointed out to the door in front of me then went in. After an hour, I got out, booked a car, and waited for it to arrive. Same guy approaches me and starts up the shittiest excuse of a small talk.

Guy: "Did you go there?" (points at the salon)

Me: *nods*

Guy: "Did you get a <insert random service that my brain filtered out 'cause I don't care>?"

Me: (no answer but internally, "I got a happy ending and had my balls trimmed, what do you want?")

Guy: "What are you doing here?"

Me: (polite but cold, signalling that there's nothing to talk about) "I'm waiting for a car."

Guy: "What address did you put for this place?" *moves closer and starts looking at my phone screen*

Me: "This building. It's fine. I've been here a couple of times." *walks a couple of feet away*

Guy: "Oh no, you should put this blah blah street instead because that one is on the other side."

The fuck do you mean, man? You saw my fucking pin, it's right there and like I said, I've been here before.

Me: "No, no, it's arriving." *starts ignoring every other attempt he makes to start a conversation*

Guy: *starts mumbling about how I put in the wrong street*

Car arrives, I ignore the guy and walk straight to it.

Guy: "Oh, that's you." *mumbling other shit like we're good friends parting ways*

I know some of you will say that maybe he's just trying to help and I'm being a cunt. First of all, I already told him that I've been to this place several times and I know where I'm going. Second, an old lady got out of a car at the time I said I didn't need help but I didn't see him talk to that woman once or try to help her.

You can say that maybe he's lonely and in desperate need for a conversation. I don't care. It's not my responsibility to talk to random people just because they feel lonely especially when they're hassling me and not following the social distancing rule at all.

You can go ahead and preach that I should be kind but I think I've been kind enough not to lash out and stay polite with this guy even when he was already being rude asking questions that are none of his business. I'm just so stressed out and annoyed that people in general seem to never leave me in peace. It doesn't matter if I go out or not, be on social media or not, nothing works. I just hate people in times like this and wish most of them would turn into cats.

I’m a team lead in the tech team, myself and another team lead manage the on call processes for the department, so when stuff breaks we need to fix it. I assume there is sufficient documentation available for me to fix a process that is not mine.

one of the other managers processes breaks. He’s on annual leave and is away for another week. I attempt to fix the process. No documentation. What do i do?

I go to my manager the next day and tell her the process is broken and I can’t fix it because there’s no documentation and I don’t know what the full impacts are. She agreed we should leave it until he comes back from AL.

He comes back a week later. I tell him the process is broken and it’s been failing since he went on AL.

Him: we had a handover before I went on holiday
Me: no, you showed me where the ‘documentation’ was. Said documentation is not defined enough and is out of date. I didn’t want to break it further by trying to repair it when it’s not completely critical
Him: but it is critical, it has to run every day
Me: so why doesn’t it say that in the documentation?
Him: ............
Me: can you fix it please
Him: no, I’ve got too much to do having just come back from holiday
Me: more critical that a process that has to run EVERY DAY and has been failing for the past 10 DAYS??
Him: I’ll see if I have time

2 hours later...

Him: Lets put in some time for handover so you can understand the process. Is an hour long enough?
Me: I don’t know, you tell me, it’s your process, you know what’s involved and how long it should take to explain
Him: well is an hour long enough?
Me: I don’t know, it takes however long it takes you to explain it
Him: I’m asking you
...........

At this point I’m getting more and more angry, how can you not know how long your process is gonna take to explain when you’re the one that wrote it?! I fully well know that it’s gonna take longer than an hour because it’s an SSIS package that looks like a plate of spaghetti, you spend 15 minutes working out what box flows to where before even looking at any SQL, and he’s still asking me how long it’s gonna take and distracting me from my ACTUAL critical work

Man is a waste of space, so quick to give you work that isn’t his but never takes responsibility for his own... honestly have no clue whatsoever how he became a manager....

This rant doesn’t seem like much reading it back but I swear it’s the last in a looooonnngggg like of his fuck ups that other people have had to deal with 🙄🙄

Before I finally managed to move out of my parents' place, they nonstop kept annoying me by saying I should get a "real job". They thought I was only playing games or browse random unimportant stuff on the computer...

Nowadays they think I "kreate" websites (as Karlie Kloss would pronounce it).
My mother one time was so fucking annoying about my job, I got so pissed off, I threw in her face her that I earn three times what she gets and I have much more responsibility and brain requiring work and that her single-cell brain would never understand what I am doing the whole fucking day.

Since then we dont talk much about work anymore.

Fucking parents... the best thing that happened to me was moving out of their shitty place and their poisonous attitude.

Today somebody claimed they have the "copyright" of responsive websites.

First of all, I'm here for almost a year now, but this is my first rant. Hello guys!
(linuxxx, call me)

This didn't happen to me.

So, it begins like this:
Some client called us and said "[INSERT_COMPANY_NAME] called us and said they have the copyright of all responsive websites, asking money."

I hanged up, laughed hard and visited [INSERT_COMPANY_NAME] website and saw this:

- Each website that uses the solution must report the domain name in order to register it.
- If a company undertakes web site design, it is the company responsibility to inform and record.
- Any unauthorized website will be considered unauthorized and a violation case will be opened.
...

Pricing (Currency Converted to Dollars)
1 Website ~$260
2 - 10 Website ~$1300
...

Well, eventually I reported this to government. I unmasked this fraud.
OR DID I?

Their site is saying this now: "We do not serve this to anyone except government now, you are making nonsense and we do not want nonsense."

So I posted it on a forum, asking what can we do.

We are suing this company now. Yeah, I said "we".

PS: If we cannot win this, I'll get the copyright of subdomains.

A little back story:
A dev who left already implemented a system and modeled the data like he doesn't even care because he was going away in one month anyway.

This sucker here inherited the responsibility to remodel this fucking clusterfuck of data.

I was trying to do a good work here until today but some things came to my mind :
I don't care.
They don't care.
Fuck it.
I'm gonna do the same shit and the next person can suck ma'dick.
I have better things to do.

Look, I'm gonna do a lazy job that is gonna be a million light years better than what this sucker did anyway.

The Interview (Part 2)

I feel like I can make 13 episodes of this shit. I reviewed another resume that has more than ten pages and contains very little useful information. What kind of pain, internal hemorrhage, brain damage, and trauma does one have to endure before he decides:

"I'm gonna make my resume thicker than old school Song Hits magazine. That would be really cool. That would get me hired."

Jesus Christ, I summon you again. I told you dying for these little fucks isn't worth it but nooooo, no one ever listens to me. iM gUnNa DiE aNyWaY, nAiL mE oVa ThErE. Now look at this shit, one "block" per page.

1. Each block contains the position, company, and responsibilities except each block is repeated over and over again for each "project".

2. Each project has no specific name, just numbers but Project 1, 2, 3, and so on just isn't enough so he used roman numerals instead. Roman fucking numerals. I thought that was the name of the project until I scrolled through the different companies he's been in and that format persists starting from Project I to Project XII.

3. Each responsibility starts in a new line, some are not capitalized so you don't even know if it's the continuation of the previous sentence or what except sometimes, there is no previous sentence.

4. The blocks aren't even arranged properly. He has experiences from 2019, 2018, **2015**, and then 2018 again, 2017, 2016, and so on. I know this because I tried to give the guy a chance. Maybe he's one of those good developers who are just absolutely terrible with these things so I tried to "extract" the gist of the resume.

5. The gist is "nothing to see here". He just did all of this to look like he has plenty of experience and the recruiter must have thought "Wow, I bet this guy would pass." He had five years of experience but all I got aside from the giant headers are "joined the project blah blah", "used <something so basic, it's not worth mentioning> to maintain blah blah", and something in the tune of "changed the scrollbar to blah blah".

Example:
Ass Licker - Project VII
Honduras Bitches Inc.
Joined the brothel.
maintained my twerky bitchy assfuck
Used Fontawesome and jQuery shit ass mothafucka some dumb shit here, I don't give a shite anymore, I'm dead inside.

I.. I just.. Why? I don't know anyone who have this kind of resume and yet here I am reviewing this kind of shit from the type of people I didn't know existed. Why do we have to take something so simple and turn it into something that is so difficult to understand or even look at?

!Rant

My boss just gave me a task "deploy this project today".
1. Made by a junior dev, and I have to take responsibility to upload it in this short time (no blame to jun dev, she's new and need to practice)
2. In a crm that I personally never used before, I need to study it and adapt at least the paths
3. Task was given at 13.48 during lunch pause.
But
But
The best is yet to come
Wait

.
.
.
.
.
.
.
.
.
.
Ready?
4. He doesn't know the server where to deploy it!
No one knows.
The IT doesn't answer, but still, I have to deploy a project TODAY (2h and 47 minutes left eob).

Not a hack but more of an orchestrated attack. It was high school and our computer labs ran windows and all of them were connected to a central server. Now i had just learnt about windows api and how it can be used to check the space available on a disk. So i wrote a small script to to write chunks of 5mb files in the directory where TURBO C++ was installed and let it run till the system ran out of space.
Then in the spirit of conspiracy i added the said script to the central node and asked everyone in the lab to copy it locally and execute.
Then a few days later, the poor lab incharge corners me and say who added the ms91.dll file(do not remember the exact name😐). I said that it is a standard Microsoft dll and also how would I know. Then he goes on saying how he had to reinstall windows on all computers. At first I felt sorry but then the spirit of satan rose in me and I denied any responsibility about it and returned back to class where each of my classmates had a good laugh about it. 😂😂

"A comment isn't needed if the name is good and the responsibility is clear" - M.Howell

So I joined this financial institution back in Nov. Selling themselves as looking for a developer to code micro-services for a Spring based project and deploying on Cloud. I packed my stuff, drove and moved to the big city 3500 km away. New start in life I thought!
Turns out that micro-services code is an old outdated 20 year old JBoss code, that was ported over to Spring 10 years ago, then let to rot and fester into a giant undocumented Spaghetti code. Microservices? Forget about that. And whats worse? This code is responsible for processing thousands of transactions every month and is currently deployed in PROD. Now its your responsibility and now you have to get new features complied on the damn thing. Whats even worse? They made 4 replicas of that project with different functionalities and now you're responsible for all. Ma'am, this project needs serious refactoring, if not a total redesign/build. Nope! Not doing this! Now go work at it.
It took me 2-3 months just to wrap my mind around this thing and implement some form of working unit tests. I have to work on all that code base by myself and deliver all by myself! naturally, I was delayed in my delivery but I finally managed to deliver.
Time for relief I thought! I wont be looking at this for a while. So they assign me the next project: Automate environment sync between PROD and QA server that is manually done so far. Easy beans right? And surely enough, the automation process is simple and straightforward...except it isnt! Why? Because I am not allowed access to the user Ids and 3rd party software used in the sync process. Database and Data WareHouse data manipulation part is same story too. I ask for access and I get denied over and over again. I try to think of workarounds and I managed to do two using jenkins pipeline and local scripts. But those processes that need 3rd party software access? I cannot do anything! How am I supposed to automate job schedule import on autosys when I DONT HAVE ACCESS!! But noo! I must think of plan B! There is no plan B! Rather than thinking of workarounds, how about getting your access privileges right and get it right the first time!!
They pay relatively well but damn, you will lose your sanity as a programmer.
God, oh god, please bless me with a better job soon so I can escape this programming hell hole.
I will never work in finance again. I don't recommend it, unless you're on the tail end of your career and you want something stable & don't give a damn about proper software engineering principles anymore.

I have been a frontender for a long time. I recently showed interest in backend development, and said to my boss that that is what I would like to pursue. He said that was never going to happen and I would only be a frontender in this company.

A lot of horrible things happened, some of the Lead Developers bailed and another developer flatly out committed industrial spionage on the company.

Then because of shortage of staff, gave me backend tasks, which all I completed within deadlines with few exceptions of course.

My project manager was very impressed about it.

Then I noticed the project management didn't concern themselves with ongoing projects, they became more focused on customer support and management of unhacking etc.

I noticed a wide gap that made it so all projects went past due the time because lack of coordination and planning

I stepped in because I was annoyed that this was common practice in the company.

While my two bosses were on vacation, they nominated me to be the "boss" of the company.

I earn close to minimum wage, and I felt this wasn't fair if I was to continue to do what I have done. So when our boss called us into a meeting and he said that he was going to move slowly away from the company, he said we should keep the reins of the company.

I didn't say much then, because I didn't feel like taking on so much responsibility I knew I wasn't to gain anything from more than knowledge.

I confronted him today and told him how I have felt throughout a long time. He basically said I hadn't proven myself and because of my young age, I didn't deserve to have more right now.

I was annoyed, he said he expected the same from every coworker and that I wasnt special or unique and that I could easily be replaced.

Not to mention I never got to finish a sentence without him interupting me or raising his voice to deafen out mine.

Have you ever had this experience and how did you feel? I feel terrible to be honest..

C is like an obsidian razor. Extremely sharp tool, immense power with immense responsibility. You can make art and you can make bloody mess.

Clojure is like a magic rainbow mist. You accept it and it's pure chrysalis, everything is good, everything is fine. You feel cared about, you feel like nothing can hurt you.

Bash is like feeling your stepdad's finger inside your asshole. Shame and shame again combined with extreme perception of wrongdoing that lead to nothing but psychological trauma.

I fucked up.

In my career, colleagues always looked up to me to solve everything. From day 1.
Hell, I have nicknames; « The Dad », « Machine », « The Beard »... when I meet a new group of devs at the bar they use those nicknames even if I have no clue who they are.

Result? I'm not allowed to fail and even if I do and try to take responsibility, no one ever blame me.

They see me as a fucking zen programming monk, all wise, patient and kind.

Oh boy here we go. I screw things up all the time and can never let go the guilt since I'm not allowed to take responsibility of my mistakes.

Once again I wake up after a night of stress working, trying to overcome analysis paralysis. I'm late. Supposed to have meetings with some fucking PHDs, fueling my imposter syndrome.

Can't even learn anything in those conditions.

Fuck they should call me the fraud.

We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:

#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.

My job sends out emails with things like "You won a prize!" In the subject line with embarrassingly vague reasons to click the links in the email. If you do, the links take you to a site where they slap your wrists for clicking an unknown link and teach you about the dangers of phishing.

It's fake spam. Ironically enough, though, it's the ONLY spam I ever get. It's more annoying than real spam because it never gets blocked by the system like an actual phishing attack would...

It is driving me crazy having to delete these stupid messages every day and they're clogging up my otherwise clean inbox! I don't even know who to contact about this bullshit because they're so "haha we got you!" about it, there's no department claiming responsibility. They're creating their own spam trying to prevent spam. What the hell?

I just installed Opera Mini on my PSP. That alone isn't very exciting on its own, although I am stoked that my website does in fact render on a device from 2009. With the helpful guidance of a laptop from 2004 that's doing the hotspot duties for this thing.

No, what really got me stoked is that Opera still supports these old platforms, and how small they managed to make it. The .jar file for Opera Mini 4.5 is ~800kB large. There's a .jad file as well but it's negligible in size and seems to be a signature of sorts.

Let that sink in for a moment. This entire web browser is 800kB. Firefox meanwhile consistently consumes 800 MEGABYTES.. in MEMORY. So then, I went to think for a moment, how on earth did they manage to cram an entire functioning web browser in 800kB? Hell, what makes up a web browser anyway?

The answer to that question I got to is as follows. You need an engine to render the web page you receive. You need a UI to make the browser look nice. And finally you need a certificate store to know which TLS certificates to trust. And while probably difficult to make, I think it should be possible to do in 800k. Seriously, think about it. How would you go *make* a web browser? Because I've already done that in the past.

Earlier I heard that you need graphics, audio, wasm, yada yada backends too.. no. Give your head a shake. Graphics are the responsibility of the graphics driver. A web browser shouldn't dabble with those at all. Audio, you connect to PulseAudio (in Linux at least) and you're done. Hell I don't even care about ALSA or OSS here. You just connect to the stuff that does that job for you. And WebAssembly.. God I could rant about that shit all day. How about making it a native application? Not like actual Assembly is used for BIOS and low-level drivers. And that we already have a better language for the more portable stuff called C.

Seriously, think about it. Opera - a reputable browser vendor - managed to do it in 800kB on a 12 year old device. Don't go full wank on your framework shit on the comments. And don't you fucking dare to tell me that there's more to it. They did it for crying out loud. Now you take a look at your shitpile for JS code and refactor that shit already. Thank you.

The first two stories on slashdot's homepage are:
1. Google releases Angular 2, breaks backwards compatibility
2. Apple releases Swift 3, breaks backwards compatibility

If you use either of those tools, why do you put up with this? When did software engineering stop being about building useful or enjoyable things for our customers, and start being about doing thankless make-work for Silicon Valley billionaire companies? Is this the legacy we want to leave to the world?

Teammember left. I did his three tickets yesterday. Before that I created and applied new rescue procedure for broken deploys on production and deployed the app manually. Took me about 6 hours to do this right, find the cause, and solve it, and document what I did. After that my teamleader bought me a launch :)
It wasn't his, my former teammate responsibility to bring back prd to life, it was me being good and engaged employee. His tickets, on the other hand, were his duties. Took me one hour to code them. He was working on them for two weeks. I can't wait for the performance review, im definitely going to ask for a nice rise :)

The feeling when you realize some people on the project are writing legacy code from scratch. Apparently it seems they've never heard of any coding standards, they think clean code and style guidelines are for the weak and single responsibility means one single method is responsible for a bunch of unbelievably diverse things. They are like the Gumbys of the dev realm but it's my brain that hurts every time I have to deal with their code.

"Our central servers firewall has been breached" - Doesn't even work on a server or anything, just his laptop

"How many proxies do we have left?"

"Around 10.200"

I don't take responsibility for any brain damage

So I have been a fly on the "wall" for last couple of months and never signed up, but now here I am!

Rant is about a serious topic - gender gap in tech industry!!
Couple of months ago Stackoverflow announced developer survey results! I was shocked by demographics results! It was disappointing to see biggest gender gap in general tech industry!
I believe tech industry can be the first one to have equal pay for women!

However.... (bad part)
I was going through my twitter feeds and saw this! Many of you have seen this tweet too.

(ohh!fuck I cant attach multiple images here, I should have created Medium post, fuck it!)

"They" continue, quoting from the tweet.
1)"....bias in society is reflected in AI"
2) "However, I do think it is our responsibility as designers/developers/users to be aware of this bias and do our best to correct it."

I want to rant about 2nd one. Some of you may not like it including grammar naziz!
As a developer/programmer I take 2nd one personally! I am currently at denial phase though!
And I have an OCD so gonna make points here!

1) Seriously tell me please, how the fuck you can write gender bias algorithm which can pass a big crazy amount of test suite?

2) Google has done many things for last decade to overcome gender gap related issues. I have met some of the nicest people from Google, and this is really hard for me to believe that google AI or that team has anything to do with the results!

3) Someone suggests use "they" in google translated result, can you fucking imagine how wrong that would be??? If I am developer working on that algo or even in that team and I see this ticket in jira with highest priority where it says, "make all translated results gender neutral using only they" - I would fucking like to die and may be in my next life ask me to do that, when I am a toddler!

4) I am an advocate for equal pay, equal rights and equal opportunities for everyone to "minify" this gender gap in tech, but showing google translate results of a gender natural language to make a point is wrong, it is simply undermining the efforts of something really helpful thing.

5) Moving on to the core point - What can be done to lower down the gender gap? I have seen amazing women who can code/manage far far far better than what I ever could imagine, and they are at really good place and deserve to be there. Are they doing enough to inspire other women to join tech industry?
Collective efforts are very much required. And need to keep in consideration that tech industry is highly competitive roles are also changing rapidly.

6) Many big companies have women at higher positions(CEO, CFO,....) what are their efforts to bring more women in tech industry?
(Some of you may not like this, as this is implying that it isn't only men's job. )

7) Going slightly political here, everyday we see really disappointing news related to women and their rights and health, I strongly believe women don't have to ask for or even have to mention about "equal rights" about anything. Everyone is equal!!!
This is 2017 and still fucked up!

Thats all for today! Heading for breakfast!

Fuck WFH. I'm so tired of kids yelling. people eating, fucking noises and people leaving their desks for hour, and sayigg I'm sorry I was speaking on mute. Fuck WFH. Everybody needs to get their asses back to the office, and actually do the damn work.

WFH only works if you have kickass passionate people who love their job with an ounce of responsibility.

So one of my clients had a different company do a penetrationtest on one of my older projects.

So before hand I checked the old project and upgraded a few things on the server. And I thought to myself lets leave something open and see if they will find it.

So I left jquery 1.11.3 in it with a known xss vulnerability in it. Even chrome gives a warning about this issue if you open the audit tab.

Well first round they found that the site was not using a csrf token. And yeah when I build it 8 years ago to my knowledge that was not really a thing yet.

And who is going to make a fake version of this questionair with 200 questions about their farm and then send it to our server again. That's not going to help any hacker because everything that is entered gets checked on the farm again by an inspector. But well csrf is indeed considered the norm so I took an hour out of my day to build one. Because all the ones I found where to complicated for my taste. And added a little extra love by banning any ip that fails the csrf check.

Submitted the new version and asked if I could get a report on what they checked on. Now today few weeks later after hearing nothing yet. I send my client an email asking for the status.

I get a reaction. Everything is perfect now, good job!

In Dutch they said "goed gedaan" but that's like what I say to my puppy when he pisses outside and not in the house. But that might just be me. Not knowing what to do with remarks like that. I'm doing what I'm getting paid for. Saying, good job, your so great, keep up the good work. Are not things I need to hear. It's my job to do it right. I think it feels a bit like somebody clapping for you because you can walk. I'm getting off topic xD

But the xss vulnerability is still there unnoticed, and I still have no report on what they checked. So I have like zero trust in this penetration test.

And after the first round I already mentioned to the security guy in my clients company and my daily contact that they missed things. But they do not seem to care.

Another thing to check of their to do list and reducing their workload. Who cares if it's done well it's no longer their responsibility.

2018 disclaimer: if you can't walk not trying to offend you and I would applaud for you if you could suddenly walk again.

I'm the only developer here. I'm also pretty bad.

I can't handle all this responsibility, every single fuck up will be my fault.

(I'll give some context before the rant: I'm part if the IT department of a manufacturing company (actually I'm 1/2 of the department), and all the applications (old an new - except the ones used on production line) used in the company are my responsibility, that including most of databases too... Also, English isn't my native language so there will be some words or phrases that I'll probably write wrong... Sorry for that, if there are any corrections, I'll be glad to hear them)

So...

There will be an implementation of new "control point" on the "shipping department" which consists on a electromechanical equipment controlled by a PLC. And despite the original concept was a collaboration between 2 departments (we, IT, and Production Control), I was never taken in consideration about anything of the project... To be fair, I forget about its existence until two weeks ago.

So, a few days I learned that there are a huge delay regarding the original deadline (mainly because the supplier was delayed with the delivery of their system), and since two weeks (less, actually, because some holydays in between) I'm learning how to integrate that "P.o.S" into an existing application on a PC using a serial communication (not the main problem, as I've done that before... With another brand of PLC's) while avoiding buying any additional software (to get the communication done and in a easy way) and that sort of things... But discovering in the process that it will be necessary to acquire such additional SW in order to finish the job ASAP.

When suddenly I get the "news" that it's almost all my duty (and responsibility) to meet the original deadline, because it doesn't matter how the other departments screw all the schedule, it's the job of IT to get the shit done in time... And what is worst: they didn't said that in such straight manner, no, the implied it while making a quick test with the general manager.

I mean, WTF? Besides doing a "respectable" number of "user support" activities in a dialy basis, I also need to manage the activities of other departments? And also fix their screw ups on a schedule that I just learned days before?

And also there is a coworker (one of whom screwed up) that, almost every time she see me, is asking "how much until you'll finish?"

As I read on a meme years ago: "please, give patience, because if you give strength, I'll need bail money too..."

Damn... I don't know of the benefits of this work are worth all this nonsense

Refusing to escape user input in shell commands because "it's the responsibility of the user to insert safe input".

(first post/rant on here)
So I recently started at a new company. I was kinda aware that the project I'm working on would be rather old school (to put it in a nice way :-)).

Part of my job is to 'industrialize' and update/clean up the existing code so there is less time spent on fixing bugs due to bad design.

One of the first things I had to do was to write a new interface to integrate with external software.

I already noticed some rather nasty habits, like prefixing every variable with m (don't know why), private fields for every property (all simple properties) and a whole lot of other stuff that either is obsolete or just bad practice.

Started writing clean code (simple classes with properties only, no m prefixing, making sure everything is single responsibility, unit tests, ...).

So I check in the code, don't hear much from it again besides the original dev/architect that started the project using my code to further work on that integration.

Now recently I started converting everything from TFVC to Git (which is the company standard but wasn't used by our team yet). And I quickly skimmed through my code to check if everything was there before pushing it to the remote repo.

To my surprise, all the code I had written was replaced by m prefixed private variables used in simple properties. BL classes were thrown in together, creating giant monstrosities that did everything. And last but not least, all unit tests were commented out.

Not sure what I got myself into ... but the facepalming has commenced.

I recently finished one year in the industry as a Software Engineer for a solutions development startup. Here are my top 10 learnings:

1. It's okay not to know everything, as long as you're willing to learn passionately.

2. Focusing on the customer experience is the number one priority in software design.

3. Imposter syndrome and fear of failure are real, but a little bit of toughness is all you need.

4. Lack of work is more frustrating than the excess of work. No two days are similar.

5. Working at a startup has taught me more than what my friends at tech giants have learned.

6. The feeling of recognition and appreciation will set your trajectory to constant improvement.

7. Asking for help is completely normal, only if you've exhausted all your research and online resources.

8. Mentoring or generously giving back to the community is super underrated.

9. Taking ownership and responsibility of failures is equally important as for successes.

10. Taking up tasks that interest you - outside your job description - is never a bad idea.

I wish you could order an Emma Watson when you're stressed out on the day.

I just became the maintainer of an open-source repository with about 60k downloads / month.

Does anyone have any general suggestions for me? I feel like it's a big responsibility and it makes me a bit nervous.

I really dislike the company I work at.

I want to say hate, but there are parts that I adore (mostly the people I get to work with).

However, I dislike:
- The management
- The way engineers are treated
- Lack of responsibility for on QA for finding bugs, and it falling solely onto the engineers
- Sales circle jerk every All Hands meeting
- The amount of "ring-around-the-rosy" they played with me for a 10k raise (took 12+ months and not what I was looking for when I first asked)
- They lie

Just a shitty company overall. Interesting product depending on what team you're on, but overall I'd rather dye my hair green and become a talking broccoli stock.

I used to work with a teacher in my last uni year.

The job consisted on doing a kinda-like management system for a business. It all began kinda "right", we agreed upon a price for 6 months of my work (a very lowball price, but it was just right because I was learning stuff that we were going to be using).

Fast-forward first six months, all I do is code frontend, mockup screens and whatsoever because this "business" hadn't give us proper requirements (Yeah, I told him to ask for them, but nothing came through).

So I was like well, I'll keep working in this project because I really want to finish it. Sidenote: I was doing all the "hard work", he didn't know how to code, and he calls himself a teacher... wtf).

Months go by, and a year goes round, in between these months, he spoke to me, that he wanted me that we kept working together, that we could renegotiate the payment (I asked him to give me my payment once the job was done). I agreed, but my uni residence period was coming along and I got an oportunity to go abroad to another country.

So there I was, in the need of money to buy my passport, plane tickets and other stuff, so I asked him for the payment.

Needs to be noted, that the last 6 months work was me doing tutorials on how to fucking use Linux, how to use PostgreSQL, how to fucking use CSS! He told me he would pay me extra for it.

The day came, and I received my payment... the exact amount we talked a year ago, I was like "Seriously dude?", but well, I needed the money and I didn't have time to argue, so we talked a little bit about me helping him and I told him "As long as I have time, I'll help, but remember that I'm going abroad to work for a small startup, so maybe I'll be up to my head with work" he agreed, we nod and then I left.

First week abroad came in and I was doing a shit-ton of stuff, then his first message comes around "Hey, I need more tutorials! ASAP! Before 6PM"

What.The.Fuck. I told you, son of a bitch, that I wouldn't be able to do them until weekend.. and it was monday!

So I ignored it, weeks went throught and my "angry mood" was fading away so I said to myself "Well, it's time to pick up that stuff again", I open Slack and I find a week old message with a document attached, it was a "letter", I just skimmed by it and read some keywords "deceptioned... failed me.."

Sure dude? Was I the failure? Becase, as far as I remember, you were the fucktard that didn't know how to fucking install a VM!

A week went by, and then randomly a friend of mine talks to me through Facebook:

E: Hey, how are you?
M: I'm fine, what's up?
E: What did you do to TEACHER?
M: Nothing, <explains all situation>
E: Well, It seems weird, that's why I wanted to talk with you, I believe in you, because I know you well, but TEACHER it's thrashing shit about you with all his students on all of his classes
M: Seriously?
E: Yeah, he's saying that you are a failure, irresponsible, that you scammed him

That moment, I for sure, lost all moral responsibility with him and thought to myself "He can go fuck himself with my master branch on his ass"

So when I got back to my country, I had to go around in school, avoiding him, not because I was ashamed nor anything by the way, just because I knew that If i ever had the disgrace to meet him face to face, my fists would be deep into his nose before he could say "Hey".

Moral of the story:
If you overheard that a teacher has a bad rep, not by one, nor two, but more than +100 people, maybe it's true.

Good thing my friends and others know me well and I didn't have repercutions on my social status, I'm just the guy that "fucked up TEACHER because I had the right and way to do it"

Who did I piss off in my life to have to deal with this bullshit? First day off of vacation. I am vacation hungover and just regular hungover. Left my Xanax at home. I just sat through a 45 minute meeting that I didn't have to be in for longer than three minutes. I have what my work place calls scrum in 7 minutes, another fucking meeting I don't have to be in cuz vacation. I wasn't even planning on coming in today except for the fact that my fucking boss came in, in the middle of his vacation, to schedule a meeting this afternoon and then go ghost when I try to either reschedule or at least ask what my fucking responsibility in this meeting is this whole thing is making me sick to my stomach because anger triggers my anxiety which triggers my stomach issues which triggers my phobia which triggers more anxiety which then triggers my anxiety. Gods fucking dammit. Why did I come back from vacation just to arrive in meeting hell? Nothing is okay.

Bloody scammers and bloody Paypal.
So I bought echo spot just to see how good it's voice recognition is and also wanted to see what the spot does different. So I found out that it was like hello world for AI. So I wanted to sell it on ebay-kleinanzeigen.de. It's a website from Ebay here in Germany where you can easily sell your stuff that you don't need anymore. I put it there and someone just wanted it so badly and he said that he broke his friends spot and he has no money and he need it very badly cheaper. My price was 98€ and I believed him and sold it for 85€. Now he got the device and wants the refund because the device doesn't match the description and the things he mentioned weren't even in the description. The message you see in the pic it says: It doesn't do skype and it is impossible on that device. First It is his responsibility to inform himself about the device features I'm not Amazon to write something like that in the description I've to just say how the device looks. Second it does skype and it is possible but both partners must have the same device and they should connect it to their smartphones.
But that is not the bad part that my money is ceased and got ownd by a scammer. The bad part is that I wanted to reply his message but the bloody paypal design won't let me do that. Remind me how old is paypal now? It's been there for ages and the footer is just stuck in the middle of the page and won't allow me to click on reply button. Of course I later managed to write a reply but paypal shouldn't have these kind of problems.
I'm so upset right now because these things are wasting my time. I've my final exame in a week and I've to develop a parameter based multilingual CMS, just imagine how long would just data structure take.

My current job at the release & deploy mgmt team:

Basically this is the "theoretically sound flow":

* devs shit code and build stuff => if all tests in pipeline are green, it's eligible for promotion
* devs fill in desired version number build inside an excel sheet, we take this version number and deploy said version into a higher environment
* we deploy all the thingies and we just do ONE spec run for the entire environment
* we validate, and then go home

In the real world however:

* devs build shit and the tests are failed/unstable ===> disable test in the pipeline
* devs write down a version umber but since they disabled the tests they realize it's not working because they forgot thing XYZ, and want us to deploy another version of said application after code-freeze deadline
* deployments fail because said developers don't know jack shit about flyway database migrations, they always fail, we have to point them out where they'd go wrong, we even gave them the tooling to use to check such schema's, but they never use it
* a deploy fails, we send feedback, they request a NEW version, with the same bug still in it, because working with git is waaaaay too progressive
* We enable all the tests again (we basically regenerate all the pipeline jobs) And it turns out some devs have manually modified the pipelines, causing the build/deploy process to fail. We urged Mgmt to seal off the jenkins for devs since we're dealing with this fucking nonsense the whole time, but noooooo , devs are "smart persons that are supposed to have sense of responsibility"...yeah FUCK THAT
* Even after new versions received after deadline, the application still ain't green... What happens is basically doing it all over again the next day...

This is basically what happens when you:=
* have nos tandards and rules inr egards to conventions
* have very poor solution-ed work flow processes that have "grown organically"
* have management that is way too permissive in allowing breaking stuff and pleasing other "team leader" asscracks...
* have a very bad user/rights mgmt on LDAP side (which unfortunately we cannot do anything about it, because that is in the ownership of some dinosaur fossil that strangely enough is alive and walks around in here... If you ask/propose solutions that person goes into sulking mode. He (correctly) fears his only reason for existence (LDAP) will be gone if someone dares to touch it...

This is a government agency mind you!

More and more thinking daily that i really don't want to go to office and make a ton of money.
So the only motivation right now is..the money, which i find abhorrent.

And also more stuff, but now that i am writing this down makes me really really sad. I don't want to feel sad, so i stop being sad and feel awesome instead.

Not really a hack but still worth telling:

I was working in the QA team for a big project. I tried to do some automation when I realized some radio button behaved weird... out of curiosity I checked the source and saw that there was a hidden option for a unimplemented payment option.

I was like: Let’s see how the system behaves if I just submit that form with that hidden value...

Well I was very surprised when I received the email that my order has been processed successfully.

During the investigation we found out that this bug was in prod for over two years. And it requires a one liner executed in the browsers console to skip the payment.

It was kind of a big deal and although I was (and am) still a trainee (in apprenticeship) I got invited to meet up with the client and the bosses.

It was kind of a door opener! After that they trusted me more. I have more responsibility, more interesting tasks and more client contact ever since.

To make a long story short:
Validate everything on the server side ;-)

!dev

Im working with morrons...

So someone had bright idea of having clone setup of our servers in other hosting company (in previous company we have rendundant setup). Whatever, maybe they want to be resistant to thermonuclear war or whatever, like the project wasn't underfunded already... Whatever, fuq it.

And with that, I have like really, really really fucking ABSOLUTELY BULLSHIT STUPID questions thrown at me.

So, this particular instance of bullshit started with trivial, literally "how much storage capacity we will need" I anwsered at least 4TB, preferably on redundant disk array, I've added small table what uses what and how much etc.

Than I got mail back...
"Thats not enough information:
1. What we need to say to company ABC
2. What we need to say to company XYZ
3. (this one actually had sense) Backups conception
4. **WILL WE PAY FOR SERVERS**
5. other important things (literally)"

So let's break it down.
Im backend guy. What the fuck do I know what you gonna say to XYZ or ABC. I dont give a shit, for me it's clicking setup new server and Im done for, you are overcomplicating as shit and require special care from hosting company that you will pay extra.
Next one, the killer one. What the fucking fuck. my anwser was literally "yes, we need to pay for servers, servers arent free."

Now tell me. How the fuck it is possible that someone can be such an idiot to ask questions like that. and I dont mean #3. maybe even #1 and 2 is like looking someone to throw responsibility on. But why the fuck I have to anwser mail that literally asked me if servers are free.

No, fuck off idiot, I have actual work. Take your bullshit and spread it somewhere else.

E:

and before anyone asks. No, Im not working in kindergarden but I often feel like I am indeed working within kindergarden full of 30+ mentally handicapped toddlers.

I have met a game developer today who genuinely browse the internet using MS Edge by choice.
His reason: sine I was little I loved Microsoft, I accept the fact that some websites don't show properly on Microsoft's browser, by using their browser I keep reminding myself that loyalty to what I love is more important than practicality.

My response to him: bbut... As long as you're happy!

As a web developer I feel that myself and other web devs have the responsibility to kick Microsoft in the butt to make their browser good enough for loyal people like that guy!

Instead of accepting reality like a big man and acknowledging that making software with a cargo culted process that has no function in organizing the development work, the boss is insisting I'm to blame and wants me to "take responsibility". Taking responsibility my *****. I slay the dragon in its lair.

Since I'm leaving, I tried to give him some sincere advice, totally flipped him out.

#6 days left.

These are the programmers who I had encountered and detest intensely:

1. Programmers who addicted to take other programmers' failure as an achievement.

2. Programmers who are overly arrogant. (Hey just because you know something , that don't make you a God)

3. Programmers who stealing my code without crediting me, and yet he got paid.

4. Programmers who discourage new developers.

5. Programmers who can't take criticism (Once I told a dev that his code is not clean as he decided to name the variable like __fuckingFuckingFuckningVar = "Fuck"; , he yelled at me that i am a MF. Which it's completely childish in my opinion, as a software engineer, I think programme a clean code for easy maintain and understandable for others, it is a responsibility.)

6. Programmers who compare me with others.

7. Programmers who are not friendly. (Don't be like Stackoverflow).

Being a team leader some times sucks have to take responsibility for everyone's elses functionality that doesn't work or wasn't tested in production. Leads often ends up working overtime fixing everyone elses work :(

Why the fuck don't you provision and configure the cloud virtual machine yourself, "web lead" guy who uses fucking WINDOWS to develop software? Why don't you install Webmin and PHPMyAdmin in the VM yourself if you like GUIs so much? Why do I have to configure Apache and MySQL and fix all sorts of little issues for your project just so you can use some shitty CMS? I'm not your fucking IT support guy. Go learn how to use Unix, take responsibility for your shit, and let me spend my time actually developing software.

After reaching the pinnacle of my latent burnout and mental overload lately I quit and managed to get paid leave for the rest of the notice period through hr as I told them I'm not able to work for them anymore and else had to go on sick leave. My brain just had to have a clean cut and blocked me from
getting into their overcomplex and shitty, unplanned projects as I see no value in doing anything for them anymore. I gave them all my access keys and a small handover, but it was clear that they would run into problems without me, cause I've been doing like 5 jobs there due to developer shortage. Now I still get requests from my manager even though I had an operation and spent last week in the hospital and am still recovering for the next two weeks. He's still trying to build pressure as if it was my fault that we never got time to document stuff properly and automate things that have to be automated. He ignored every recommendation I made in past to ensure that things keep running when I leave, as I always knew that I wouldn't do this shit for long. It was always more important to please bosses ever-changing requests and stupid whims as fast as possible at the cost of quality, pressuring us into putting projects live at 80% to meet random deadlines we had no say on. What a fucking asshole trying to put the responsibility on me now. Not my problem anymore. Have fun finding someone else taking over that shithole of an underengineered software-architecture. I'm out!

Two months ago I started working at a new company, who's system is a huge monolith. The company is a bit over one year old, and the code base is huge. The desire to move to more of a microservices architecture is on the radar, but one of the biggest issues in moving towards it is how we should keep our models. The stack is basically Node.js and Mongoose, where there's about a few dozen mongoose models that the whole system uses, and the issue is that, if we moved to a microservices architecture, how could we keep the models in sync. One idea I had was to keep the models in a separate (node) package that would be shared across all microservices, but then there's the issue that if one model needs changes, all microservices that use that model will need to be updated. Another idea we had was to not share models, but instead let every microservice be in charge of everything to do with a certain type of data (eg. Users are only directly accessed by one microservice, companies by another, and no two microservices share responsibility over data), but that might bring problems when one microservice depends on a certain set of data from another microservice. How do you guys manage all that? Any ideas or tips? Thanks ^^

Yet another school group project where no one is taking responsibility. Great!

I have been a software engineer for about 14 years now, in the beginning, I thought to be smart meant writing methods that do everything and more. however as I matured in the industry, I learned. keep it simple. 1 method 1 responsibility. One should trail my code and never have to find themselves where they were before in the journey. a journey should have one purpose and not pivot (context disclaimer here) as it goes. good programming is simple programming, its a story not a case of multiple endings.

I don't understand how my managers suddenly forgot that my "down weeks" we're due to technical debt I inherited. The whole on boarding hasn't been in my favor. I've stayed at work everyday til long after work hours, digging through code, trying to get JIRA tickets done, encountering issues specific to our code base that no one would ever discover on their own without docs/help from the original dev. The whole time, I was told that they know what's going on and apologize. I constantly expressed that plenty of what we were doing was building on antipatterns. They acknowledged. When a ticket wasn't done, they always knew the very specific reason and I wasn't faulted. 6 months in, I receive a great annual review. 7 months in? I receive an email titled "Performance Discussion," detailing 4 of those incidents where a ticket was pushed back -- with inaccurate depictions of what actually went down. They actually wrote that I didn't communicate. One part of the report expressed that there were "bugs found in production due to inadequate test coverage." WTF!! Everything made it past code review and QA. What are you talking about?? In fact, the person who wrote that merged my code in each time!!!! Insane!! Anyway, Q2 is partly about cleaning up technical debt, which is a responsibility I have been vested (fantastic). I've deleted about 800 lines of code in the last 2 weeks and added plenty of doc strings. Two of the most important modules our application works from are about 1000 lines of JavaScript each without any comments/docs. I'm changing that, but I don't know if my managers truly know the significance. Someone was recently promoted to my position but manually wrote out a sorting algorithm (specified numeric indexes and all); didn't do shit to earn it but breathe. And while they get more and more praise and responsibility, I'm over here stuck trying to prove myself and live up to why I assume they hired me. It's ridiculous. I love the company, but I'm not getting any sleep and I'm stressed out. It's only been about 7 months and I've been doing everything I can. Why is this happening? What am I doing wrong? I've been developing a recurring (physical) headache and ticks. My heart/chest area sometimes feels like it's lifting weights. I sound like an idiot, pushing so hard for a company that isn't mine, but I take so much pride in being in this position, and I'm so set on proving myself this early in my career (I'm 25).

I have just started working in this industry, and so annoyed by the fact that managers are insensitive to the efforts put in by the developers.
1. They ask for estimates, and sometimes consider it to be the hard line for everything and then they make you feel guilty if you are not able to live up to them.

-- I am not asking to be always lenient but they need to understand that this is problem solving and one might not be able to gage the problem at first sight. A problem might have several sub problems or a solution to one issue might raise compatibility issues with other which were tough to foresee .

2. Why do they always want an instant response to their email or query, a developer being online isn't just there to answer your damn obvious and sometimes stupid questions which can be understood just be glancing at the logs once.

-- How annoying would it be if the manager himself is being poked every other minute for trivial things. Does he have the same patience with his/her developers?

3. In tough times the manager easily delegates the responsibility to the developer and instead of standing by his/her side, interrogates them as if we have done some crime.

-- Wasn't this approved by you. Weren't you the one who had these stupid demands before and didn't let me do things the correct or optimized way. I am not saying I am always right, but you can be atleast open for feedback or discussion.

Why are you the first to take credit for the success and yet hold us responsible for any mishaps.

It's sad to see that some of these people have been tech developers.
I can go on ranting for many more things.
I am not saying all those people out there are like this. But trust me many are.

Note: I am not seasoned as you guys out there. I may even be biased by my own experiences. But this is in complete contrast to what I was expecting when I graduated from college and was excited to finally learn by working.

Life lessons learned from programming?

1. Always put things where you look for them
2. You may know better than some people but you never know better than all the people
3. Fuckups happen. Deal with them and move on
4. Take responsibility for your fuckups
5. There is no nice way to tell someone their baby is ugly or that their code is unreadable

Not really Dev advice, but I appreciated it.
"Do your best to take responsibility for everything that happens to you. Even if it's not your fault."
"On the flip side, never apologize for something that isn't your fault. That includes other people's feelings. You're not in control of their emotions."

Fucking telecom and their shady ways of providing "service". Don't even need to consider paying for porn sites when my isp comes along with its own, overpriced service to fuck a customer in every way possible.

Probably other providers as well, but for now I'm fucking pissed at them because they already scammed my grandmother twice, when it comes to internet speed, probably because they thought she wouldn't notice either way.

My grandmother's residence can receive up too 200mbps, so she got a plan according to that. Installation of the router was included as a one time fee.

This is where they first scammed her, imo. They installed a router, that can route 100mbps at max. At first I though she got a plan for that speed.
An elder telecom technician, who was investing a completely irrelevant issue, switched it out for one than can handle uo to 1tbps. He had no obligation to do so and he didn't charge anything.
Seriously, probs to that one guy. He openly stated that telecoms pulls off this scam and switched it for free, since they have many of routers lying around anyways (I wonder why 🤔🤔🤔)

Anyways, guy switched out the router and BAMM! from ~80mbps to ~170, iirc.

Fast forward a couple of months I notice internet speed is capped out at 76mpbs. Capped out way to perfectly, to just blame the cable. But obviously the guys over at customer support do exactly that.

Calls telecom: "yeah, your contact only goes up to 100, 76 because of the cable. You need to pay extra to get up to 176".

Excuse me, what the fuck did you just say, shit nugget? We should pay extra for something you contest from us?

Yo, Mister ChromosomOverflow, don't think that relaying the responsibility to another number to call will put you out of the fucking shit you tried to pull off.

Edit: The contract states up to 1000, 200 or 100mpbs download depending on what the cables allow and in case of 200 there's 100mbps upload, but we also get capped out there at 20. I wish these fucker one gang rape per non-received mpbs

so... while this may not be *my* code, I do have to claim a fair share of the responsibility for allowing it to exist. o.o

I'm busy fixing it now though.

> note: proprietary names have been blurred, naturally.

Applyed for internship for an American company in Japan. Email said I will interview with 3 people at most, 1h each, back to back, and everything will be in English.
But on the day they said I will interview with 4 people, and everything was in Japanese.
They said they will tell me the results within 2 weeks, but got rejected after 3 weeks.

Take responsibility for what you say guys...

1 dept with only 1 staff, well 1 chief to be precise, all employees quit. Another dept with not enough manpower. Requested the dept with highest manpower to help with other depts tasks while struggling and solving the shits out. Thought company is bullying them with extra workload and voice out they are looking for new jobs.

They are not wrong. And that's the bittersweet shit I have to swallow. In the end, it was my responsibility and I'm not doing enough.

Fuck stupid managers.

My current agency tried to create a bundle of generic Microservices with the hope of save time and money on future projects. That was two years ago (i was working here from 4 months ago).

What they have now? well, a sort of distributed monolyth were if one service goes down, everything else fails, infinite technical debt, no security policies (yeah, all the apis are open!!!) Business rules on the frontend . . .

And what the stupid manager say? "Everything must be ok because i designed it very well, i research a lot for this"

Stupid boomer.

PD: Yeah, despite the fact he is judt a manager, he take the responsibility to design the full architecture, idk why no one srops him.

Been working a year and a half on an offer for a client to plan their new system. Today they wanted us to construct the whole system and call it a beta only to pay 10% of the total costs. They said it is our responsibility to make the budget work as they are merely the "end users and not tech people". I am considering to tell them to go f**k themselves tomorrow.

I run update without where on mysql console on production database Today.

CLASSIC

Just because I needed to fix database after bug fix on the backend of the application.
I thought I wrote good sql statement after executing it on my local machine and then everything got bad.

Luckily it was only one column with some cached statistics data and I checked that it was not important data before I actually started fixing stuff but still ...
Almost got hard attack afterwards.
Made a script to fix this column and it took me only 15 minutes but still...

Bug was caused in part I got no unit tests and application grow after 3 years of development from simple one for one customer and volumes of documents around 50k to over 40 customers and volumes over 2mil per month, don’t know how many pages each, just in one year after we completed all needed features.

I have daily backups and logs of every api operation but still.
I think this got to far for one backend developer.

I got scared that I will loose money cause I am contractor and the only backend developer working on it.
I am so tired of this right now I think I need a break from work.

Responsibility is killing me so hard right now.
It will take a week to get back to normal.