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

*sitcom audience cheers*

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

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

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

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

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

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

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

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

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

"DO YOU KNOW ANYONE WHO SELLS POT?"

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

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

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

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

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

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

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

Title: Senior Software Engineer

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

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

Title: Dev Manager

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

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

Title: Product / Product Manager

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

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

Title: Program Lead / Product Owner

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

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

Title: Director of Software Engineering

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

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

My first job: The Mystery of The Powered-Down Server

I paid my way through college by working every-other-semester in the Cooperative-Education Program my school provided. My first job was with a small company (now defunct) which made some of the very first optical-storage robotic storage systems. I honestly forgot what I was "officially" hired for at first, but I quickly moved up into the kernel device-driver team and was quite happy there.

It was primarily a Solaris shop, with a smattering of IBM AIX RS/6000. It was one of these ill-fated RS/6000 machines which (by no fault of its own) plays a major role in this story.

One day, I came to work to find my team-leader in quite a tizzy -- cursing and ranting about our VAR selling us bad equipment; about how IBM just doesn't make good hardware like they did in the good old days; about how back when _he_ was in charge of buying equipment this wouldn't happen, and on and on and on.

Our primary AIX dev server was powered off when he arrived. He booted it up, checked logs and was running self-diagnostics, but absolutely nothing so far indicated why the machine had shut down. We blew a couple of hours trying to figure out what happened, to no avail. Eventually, with other deadlines looming, we just chalked it up be something we'll look into more later.

Several days went by, with the usual day-to-day comings and goings; no surprises.

Then, next week, it happened again.

My team-leader was LIVID. The same server was hard-down again when he came in; no explanation. He opened a ticket with IBM and put in a call to our VAR rep, demanding answers -- how could they sell us bad equipment -- why isn't there any indication of what's failing -- someone must come out here and fix this NOW, and on and on and on.

(As a quick aside, in case it's not clearly coming through between-the-lines, our team leader was always a little bit "over to top" for me. He was the kind of person who "got things done," and as long as you stayed on his good side, you could just watch the fireworks most days - but it became pretty exhausting sometimes).

Back our story -
An IBM CE comes out and does a full on-site hardware diagnostic -- tears the whole server down, runs through everything one part a time. Absolutely. Nothing. Wrong.

I recall, at some point of all this, making the comment "It's almost like someone just pulls the plug on it -- like the power just, poof, goes away."

My team-leader demands the CE replace the power supply, even though it appeared to be operating normally. He does, at our cost, of course.

Another weeks goes by and all is forgotten in the swamp of work we have to do.

Until one day, the next week... Yes, you guessed it... It happens again. The server is down. Heads are exploding (will at least one head we all know by now). With all the screaming going on, the entire office staff should have comped some Advil.

My team-leader demands the facilities team do a full diagnostic on the UPS system and assure we aren't getting drop-outs on the power system. They do the diagnostic. They also review the logs for the power/load distribution to the entire lab and office spaces. Nothing is amiss.

This would also be a good time draw the picture of where this server is -- this particular server is not in the actual server room, it's out in the office area. That's on purpose, since it is connected to a demo robotics cabinet we use for testing and POC work. And customer demos. This will date me, but these were the days when robotic storage was new and VERY exciting to watch...

So, this is basically a couple of big boxes out on the office floor, with power cables running into a special power-drop near the middle of the room. That information might seem superfluous now, but will come into play shortly in our story.

So, we still have no answer to what's causing the server problems, but we all have work to do, so we keep plugging away, hoping for the best.

The team leader is insisting the VAR swap in a new server.

One night, we (the device-driver team) are working late, burning the midnight oil, right there in the office, and we bear witness to something I will never forget.

The cleaning staff came in.

Anxious for a brief distraction from our marathon of debugging, we stopped to watch them set up and start cleaning the office for a bit.

Then, friends, I Am Not Making This Up(tm)... I watched one of the cleaning staff walk right over to that beautiful RS/6000 dev server, dwarfed in shadow beside that huge robotic disc enclosure... and yank the server power cable right out of the dedicated power drop. And plug in their vacuum cleaner. And vacuum the floor.

We each looked at one-another, slowly, in bewilderment... and then went home, after a brief discussion on the way out the door.

You see, our team-leader wasn't with us that night; so before we left, we all agreed to come in late the next day. Very late indeed.

I once had a manager who would, at every stand up, ask everyone if there was a better way to solve their problem. She did this even if the team had already decided on a solution or even if there was no problem at all. She wouldn't let us continue the stand up until we had proposed a new 'solution' that was close to her 'suggestions'.

Some of my favorite suggestions were: "Are you doing everything you can to not make it too 'spiffy' ?". If you said yes the follow up was always: "can you tell me how?"

Then when you said you hit a bit of a bump yesterday due to something unexpected she always demanded that you pair programmed today. Now I don't have anything against pair programming, I even think it's useful from time to time, but being forced to sit next to someone or have someone sit next to me every time someone encountered something unexpected annoyed the shit out of me. Needless to say no one had any problems to speak of during stand ups after a while.

Whenever I was sparring with one of my colleagues she would always join in and start proposing 'solutions' about technical problems she didn't even understand. Again, she wouldn't back down until we had accepted her 'solution'. We would then go to a different room and hope she wouldn't find us there.

This went on for months, until several people had disagreed with her so much that it ended in shouting matches.

It still makes me angry when I think of one person crippling a team that much. I took my issues to her, to HR and finally to the CEO directly, but no one did anything about it.

Finally one of my colleagues decided to quit. After he handed in his two weeks notice our manager came to me and asked if she could talk to me in private.

She told me that she didn't understand why our colleague quit and she thought everything was going great. This was after just about everyone had told her that they hated how she acted and that if she wouldn't stop they'd quit. I had told her that myself twice.

She then proceeded to tell me that I was the most valuable employee and that the company couldn't go on without me. As a gesture of their appreciation for my invaluable effort, she was so generous to offer a salary increase of 50 euro, before taxes.

I laughed, said no and handed in my two week notice the next morning.

I vowed never to work with fucktards again, and I haven't since.

If all you have is a hammer, everything looks like a nail!

This was something which my tech lead used to tell me when I was so obsessed with nosql databases a few years back. I would try to find problems to solve that has a use case for nosql databases or even try to convince me(I didn’t realise it back then) that I need to use nosql db for this new idea that I have, without really thinking deep enough whether the data in question is better represented using an sql schema or not.

Now, leading a team of young developers, I come across similar suggestions from few of my team members who just discovered this new and shiny tech and want to use it in production projects.

While I am not against new and shiny, it’s not a good practice to jump right in to it without exploring it deep enough or considering all the shortcomings. The most important question to ask is, whether some of the problems you are trying to solve can be solved with the current stack.

Modifying your stack requires more than just a week’s experience of playing around with the getting started guide and stack overflow replies. This is something which need to be carefully considered after taking inputs from the people who would be supporting it, that include operations, sysadmins and teams that are gonna interface with your stack indirectly.

I am not talking about delaying adoption by waiting for long list of approvals to get some thing that would bring immediate value, but a carefully orchestrated plan for why and how to migrate to a new stack.

Just because one of the tech giants made a move to a new stack and wrote about it in their engineering blog doesn’t mean that you need to make a switch in the same direction. Take a moment to analyse the possible reasons that motivated them to do it, ask yourself if your organisation is struggling with the exact same problems, observe how others facing the same issue are addressing it, and then make an informed decision.
Collect enough data to support your proposal.
Ask yourself again if you are the one holding the hammer.
If the answer is no, forge ahead!

Good designs solve more problems than you originally intended them to solve.

From my team lead.

What happens when you change the service call center to 100% AI

AI: Hello, this is the After Service center. How may I help you?

Angry customer: Hey! Do you count this as a product? Do you sell this to use it? F*** shit?! Bring the manager now!

AI: Thank you for your response. We will connect you to the Development team.

Angry customer: Uhhhhhh

AI: Hello, this is the development team. Please state your problems.

A bit relaxed customer: Umm, so this product you guys are selling stops working sometimes, so...

AI: We are sorry, but for the product misfunctions, please contact the After Service. We will connect you to After Service.

F***ed out customer: Wait, I just came from the After Service!

AI: Hello, this is the After Service center. How may I help you?

Angry customer who is ready to throw the phone: I said that the product is not working, and I asked to bring the freaking manager in the line!

AI: Thank you for your response. We will connect you to the Development team.

Customer throwing the phone and shouting: F*********************************************************************************************!

Jobless.
Nah, just kidding.

I'm a qualified teacher, so I have that to fall back on.

That or fixing things, I suppose. I would then design something to corrupt that AI and then I can get hired back when the AI starts its reign of terror.

"Oh no! The AI became sentient and started intentionally fucking code up (and then proceeding to manically laugh at it ((ha...ha...ha...)! Who can save us?"

"I have a team of highly skilled devs, programmers, and a dude who works in a cellphone shop at my disposal. devRanters assemble! (then I just fuck up the code I made initially to make them sentient and commit it - problems solved.)

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.

I was messaged on LinkedIn by a recruiter while I was in the UK for my honeymoon. When we got back home to Colorado I called him back and everything went well enough that a tech screen call was set up between four or five guys on the team, and me.

I was expecting to be grilled about various Linux, networking, video transcoding, database, and transaction handling questions and problems, as that was the bulk of the job's description. But instead they just gushed that they'd used software I'd written at previous jobs and loved it.

It was very friendly and they never challenged me (not being arrogant here-- they literally never tested me) and we wound up just talking about, "the job," and about how the work sucked without the tools and apps I'd written.

I got an offer for $30k more than what I asked, the next day.

I was having dinner yesterday and I suddenly get a message from someone from another team.

Them: Hi
Me: Hi

(No response for 20 mins)

Them: I'm having some problem with your service. Its not working when I do <task>
Me: Okay, let me look into that.
Them: Also, <task2> is not working
Them: And <task3> has problems
Them: Could you also look into <task4>?
Me: (visibly sweating) Let's discuss this in detail in the morning.

[Next day, morning]
*convinced that the service has a major bug*
Me: Yeah, show me what is causing the problem.

They show me what they tried. Turns out they made an invalid call and got an error, AS THEY SHOULD, and reported that as a bug. And all the other tasks were because the first call didn't work.

:|

So I'm a entry level female Developer and I started a contract to hire position in July. Its my first job as a developer and I love almost everything about it. Except this..., there is a Senior Female Developer on my team who hates me and isn't shy about it. She goes for the throat man! She magnifies any mistake I make, hell she calls me out on things that people would consider positive. In sprint planning this week she got mad at me for pulling tasks from the backlog after finishing mine early. I've tried to do everything I could to make her like me. I patiently listen when she goes on and on about her damn cats, kids, sports, ah everything, and she is a non stop talker.

Her main problem with me, so she tells the head of engineering, is that I bug her too much. I almost laughed when I heard this was her main issue with me! Sure, I asked her the normal amount of newbie questions but it's not like I don't know how to read code or google! In fact I started avoiding talking to her about a month ago because she was so rude to me. Now getting hired on full time comes down to whether or not she can stand me still if I am working on another team. I'm so frustrated because it's impossible to prove my worth to this company with this crazy lady making me look bad. I have no problems with anyone else at work. In fact a lot of us have become good friends. No one understands why she hates me so much. It feels like middle school all over again.

On top of that there is an even newer hire who she is supposed to help bring on to the team, but because of her horrible management skills, I have become his defecto mentor for learning the project, as well as the technologies we use. The stress of being in an uncertain contract to hire position + tyrant coworker + helping the new guy + still learning and having my own work to do has been overwhelming! I don't know what to do other than hope that she doesn't try to sabotage me moving to a new team.

No, I didn't. Also, beside the point but only guys on that team apart from me.

Why is this such a fucking pressing issue right now? I feel terrible that because of my presence everyone now thinks they have to mind their language. I say 'guys', I will say 'guys', I will be called 'guys' and will always oppose this bullshit agenda of coming up with problems where they don't exist.

In my world suppressing your natural speech is a form of censorship. And where there is censorship there is me in rage, rage FUCKING RAGE!

Just gonna leave this here.

Don't complain if you refuse to speak up. You don't like how something is going? But you don't want to do something about it? Then shut. The. Fuck. Up.

Getting sick of these fucking coworkers who bitch and whine about everything they don't like but when given the opportunity to speak up and voice their shit they just fucking clam up.

Context: nobody was saying anything during today's retrospective but were talking shit about the project the whole sprint. Gee I wonder why NOTHING FUCKING CHANGES. I'm the only one outside of our product owner and tech lead who even speaks out on problems/issues during the sprint. This dev team I'm on is just.. urgh.

They expect me to have their back, but they don't have mine. For months I've been carrying them. Fine. Enough is enough. The next time they need help from me they'll just get the obligatory "have you googled it because I don't have an answer" response.

Adventures in security land, part II:

I’m getting pulled off the security review team and instead relegated to part-time security tickets alongside my usual dev work. (So, someone else finds them, i fix them.)

Guess I found and debated too many problems with the lead dev’s code. 🙄

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

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

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

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

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

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

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

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

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

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

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

I had a huge epiphany on Friday... not all developers enjoy coding.

Discovered when they brought down 2 of our environments, well told them what was wrong with the changes in their code that caused the environments to break, gave them links directly to the file in the gitlab repo that needed to be updated, and...

They fucking went home. The change would’ve taken all of about 30-45 seconds to update and they fucking left.

This person’s team lead come storming in pissed off because her manager is furious about 2 environments going down and preventing everyone else from being able to deploy their changes.

We provide the exact same details to the team lead about what needs to be changed, and advise that her team member took off....

30 mins later, her manager is storming up to us (devops/sre) livid as hell.

Explain the situation for a third time... manager is like, why can’t you guys fix it?

Look here you dense motherfuckers, we can fix the code. We can be the plumbers that clean up your shit. But what value do you gain as a developer if you don’t understand how the systems work and you keep pushing shit in?

Made the changes, fixed the environments, done right? Wrong.

The original developer made more changes not knowing what would happen and thoroughly fucked the environments again.

This dumb-fucking dumpster fire of a dude then sends us a slack message. “It’s down again, can you fix it?”

Our manager steps in and tells us to send him a link to the logs and have him fix it himself!

Thank goodness we have a badass manager.

Send logs, send repo file links (again), and send line numbers in the logs to try and help just a bit more. Dude goes almost the whole day without fixing it, environments are down, other devs are pissed, we throw this dude to the wolves. His manager starts to head over and was about to talk with my team lead when our manager steps out of his office and tells him the in’s and out’s of the situation and that our job isn’t to play log parser/error fixer for the developers. This dude that’s breaking the environments needs to be the one to fix the issue and his team lead should be aware of the problems and should have been able to correct his errors before it ever came to us.

The amount of hand-holding we do is ridiculous.

(Disclaimer, this one guy making some mistakes doesn’t sound too bad, but this is actually a common occurrence for like 40% of all of our developers)

We literally have interns still in college running circles around some of our full time devs. I know I’m not a developer, but for anyone that’s new-ish to developing, when you see shit like that please don’t lose hope. Those ass-hats got into programming purely for a paycheck, not because of passion.

Stick with it and your greatness will know no bounds 👍

As for you craptastic dipstick lickers, FUCK YOU!!! Go back to school and learn how to give a damn.

➡️You Are Not A Software Developer⬅️

When I became a developer, I thought that my job is to write software. When my customer had a problem, I was ready to write software that solves that problem. I was taught to write software.

But what customers need is not software. They need a solution to their problem. Your job is to find the most cost-effective solution, what software often is not.

According to the universal law of software development, more code leads to more bugs:

e = mc²

Or

errors = (more code)²

The number of bugs grows with the amount of code. You have to prioritize, reproduce and fix bugs.

The more code you write, the more your team and the team after it has to maintain. Even if you split the system into micro services, the complexity remains.

Writing well-tested, clean code takes a lot of time. When you’re writing code, other important work is idle. The work that prevents your company from becoming rich.

A for-profit company wants to make money and reduce expenses. Then the company hires you to solve problems that prevent it from becoming rich. Confused by your job title, you take their money and turn it into expensive software.

But business has nothing to do about software. Even software business is not about software. Business is about making money.

Your job is to understand how the company is making money, help make more money and reduce expenses. Once you know that, you will become the most valuable asset in the company.

Stop viewing yourself as a software developer. You are a money maker.

Think about how to save and make money for your customers.

Find the most annoying problem and fix it:

▶️Is adding a new feature too costly? Solve the problem manually.
▶️Is testing slow? Become a tester.
▶️Is hiring not going well? Speak at a meetup and advertise your company.
▶️Is your team not productive enough? Bring them coffee.

Your job title doesn’t matter. Ego doesn’t matter either.

Titles and roles are distracting us from what matters to our customers – money.💸

You are a money maker. Thinking as a money maker can help choose the next skill for development. For example:

Serverless: pay only for resources you consume, spend less time on capacity planning = 💰

Machine Learning: get rid of manual decision-making = 💰

TDD: shorter feedback cycle, fewer bugs = 💰

Soft Skills: inspire teammates, so they are more productive and happy = 💰

If you don’t know what to learn next — answer a simple question:

What skills can help my company make more money and reduce expenses?

Very unlikely it’s another web framework written in JavaScript.

Article by Eduards Sizovs
Sizovs.net

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! 😊😊

So recently we re-orged to a product vs engineering (yes, I meant vs, it’s contentious) organizational structure. One of the former dev leads got picked for product and went on this lovely ass-kissing spiel about how great this was in front of our new bosses. The next day(!) he was telling his old team what to do directly to his buddy the scrum master, who works for me and casually mentioned it. How am I supposed to run engineering and deliver if every P.O. can end run around the structure? I hate all this.

Also, if the new PE tells me one more time all my problems can be solved with SQS, I’m gonna explode. Not all dev problems are a nail to fix with an sns hammer. Asynch comms has its uses, it is not the *only solution.

I feel like I’m over reacting, and yet, I still feel rage…and happy to find an anonymous place to rant about it.

In the last project i worked in, the product owner wouldn't treat people as people but as resources.

The problem with that is you just look at people and their work in terms of a checklist and remain blind about real humans face.

She wouldn't understand the challenges of building something with an absolutely new stack which people needed to learn from scratch and put pieces together. She wouldn't be supportive of people trying out things and fail.

One fine day I told her that I was spending too much time on meetings and i should be excluding that time from available sprint timings.. she made me open my calendar in a screenshare session with all team members. Made me go through go through every meeting invite i had on calender and ordered which ones should i be attending from then and which ones i wont. That was insulting. It broke the trust.

I decided to not work with the project. Stopped putting my heart and soul into it and eventually got out of it in a month time.

Don't put your team into a position like this ever. You have to trust them with the problems they face and try to find a solution. Scrutinizing and micro management will always kill the team.

this is how I destroyed my career in IT and how I'm headed to a bleak future.

I've spent the last 10 years working at a small company developing a web platform. I was the first developer, I covered many roles.
I worked like crazy, often overtime. I hired junior dev, people left and came. We were a small team.
I was able to keep the boat afloat for many years, solving all the technical problems we had. I was adding value to the company, sure, but not to mine professional career.

There was a lot of pressure from young developers, from CEO, from investors. Latent disagreement between the COO and the CEO. I was in between.
Somehow, the trust I built in 10 years, helping people and working hard, was lost.

There was a merge, development was outsourced, the small team I hired was kept for maintenance and I was fired, without obvious explanations.Well, I was the oldest and the most expensive.

Now I'm 53, almost one year unemployed.
I'm a developer at heart, but obsolete. The thing we were doing,
were very naif. I tried to introduce many modern and more sophisticated software concepts. But basically it was still pure java with some jquery. No framework. No persistency layer, no api, no frontend framework. It just worked.

I moved everything to AWS in attempt to use more modern stack, and improving our deployment workflow.
Yes, but I'm no devop. While I know about CD/CI, I didn't set up one.

I know a lot of architectural concepts, but I'm not a solution architect.

I tried to explain to the team agile. But I'm not a scrum master.
I introduced backlog management, story mapping, etc. But I'm not a product manager.

And before that? I led a team once, for one year, part of a bigger project. I can create roadmap, presentations, planning, reports.
But I'm not a project manager.

I worked a lot freelancing.
Now I'll be useless at freelancing. Yes I understand Angular, react, Spring etc, I'm studying a lot. But 0 years of experience.
As a developer, I'm basically a junior developer.

I can't easily "downgrade" my career. I wish. I'll take a smaller salary. I'll be happy as junior dev, I've a lot to learn.
But they'll think I'm overqualified, that I'll leave, so they won't hire me even for senior dev. Or that I won't fit in a 25 y.o. team.

My leadership is more by "example", servant leader or something like that. I build trust when I work with somebody, not during a job interview.

On top of that, due to having worked in many foreign countries, and freelancing, my "pension plan" I won't be able to collect anything. I've just some money saved for one year or so.

I'm 53, unemployed. In few years time, if I don't find anything, it will be even harder to be employed.

I think I'm fucked

Discovered this awesome community some months ago, and I've finally decided to make an account :D

Guess I should write a rant now.

We were initially a team of 2 to do a 'simple' app with AngularJS, NodeJS and Kendo UI in 2 months.

We had some problems with it, mainly because I'm 'in charge' of a big Java web application filled with legacy code and in process of a 'big change that was planned to be deployed for all users yesterday', and my coworker (also the project analyst) was still learning how Node and Angular work. And I'm not going to lie, I'm still learning new things everyday.

Situation 1 month after our start: coworker fired (due to offtopic reasons), replaced by a younger girl, and me still doing changes in the Java webapp.

Thank god I work better when under big pressure :p

Let me share a piece of advice to entry level devs that are getting ready for job interviews that I wish someone gave to me when I was first looking for work straight out of school. Do not focus making yourself look good to this company by trying to make your resume flashy or trying to oversell yourself. Although its important to present yourself sure, but it should not be the foundation for you to base your interview goals around. Rather focus on the company itself. Find out whether the company itself uses modern technology,practices and upholds to project management and the software development cycle, find out how they work,communicate and develop as a team. Simply put focus on whether they are worth working for instead of looking like your worth being hired. Can they collaborate,communicate and solve problems efficiently. Otherwise you may end up getting hired and hating your job. Just a thought and some advice on my own experiences. Hope it helps someone.

i'm feeling so sick right now.

PM invited team for today to present his "vision": "<name of our component>: what it is and what it is not".
but it didn't make sense and showed that he hadn't understood the problem at all. the whole architecture made no sense given the problems that shall be solved. his architecture diagrams missed some essential parts that were actually the giant weak points of his concept. his pseudocode, that should exemplify interactions between components, didn't address the complexity of required interactions at all. it's like he expects some magic to happen and has no fucking clue about the requirements (but acts like it), even though he is the manager of this software project.
and when devs ask really interesting questions that fundamentally question his concept, discussions lead to nowhere and questions are not answered. at some point he literally said "there is no such thing as <name of our component>, i still have to find this out"
really!? after one and a half year, since you sold the idea for this component to upper management, and after half a year of development, you still can't tell what it is what we actually want to build? are you fucking serious?!

at some point in discussion he said that these questions need to be answered but that "there's no time left", and he ended the meeting. although there was still half an hour of meeting time left.

i'm so fucking sick of this, i hate everything right now. i can't listen to this bullshit any longer. in discussions, he contradicts himself all the time, it is so fucking surreal i'm starting to feel like i'm insane.

it makes me really sad and tired. i don't want to care about this shit any longer.

Having a boss that knows nothing related to programming or IT is almost as bad as the fact that I am the 1 man show for all IT and programming.

Biggest challenge I overcame as dev? One of many.

Avoiding a life sentence when the 'powers that be' targeted one of my libraries for the root cause of system performance issues and I didn't correct that accusation with a flame thrower.

What the accusation? What I named the library. Yep. The *name* was causing every single problem in the system.

Panorama (very, very expensive APM system at the time) identified my library in it's analysis, the calls to/from SQLServer was the bottleneck

We had one of Panorama's engineers on-site and he asked what (not the actual name) MyLibrary was and (I'll preface I did not know or involved in any of the so-called 'research') a crack team of developers+managers researched the system thoroughly and found MyLibrary was used in just about every project. I wrote the .Net 1.1 MyLibrary as a mini-ORM to simplify the execution of database code (stored procs, etc) and gracefully handle+log database exceptions (auto-logged details such as the target db, stored procedure name, parameter values, etc, everything you'd need to troubleshoot database errors). This was before Dapper and the other fancy tools used by kids these days.

By the time the news got to me, there was a team cobbled together who's only focus was to remove any/every trace of MyLibrary from the code base. Using Waterfall, they calculated it would take at least a year to remove+replace MyLibrary with the equivalent ADO.Net plumbing.

In a department wide meeting:

DeptMgr: "This day forward, no one is to use MyLibrary to access the database! It's slow, unprofessionally named, and the root cause of all the database issues."
Me: "What about MyLibrary is slow? It's excecuting standard the ADO.Net code. Only extra bit of code is the exception handling to capture the details when the exception is logged."
DeptMgr: "We've spent the last 6 weeks with the Panorama engineer and he's identified MyLibrary as the cause. Company has spent over $100,000 on this software and we have to make fact based decisions. Look at this slide ... "
<DeptMgr shows a histogram of the stacktrace, showing MyLibrary as the slowest>
Me: "You do realize that the execution time is the database call itself, not the code. In that example, the invoice call, it's the stored procedure that taking 5 seconds, not MyLibrary."
<at this point, DeptMgr is getting red-face mad>
AreaMgr: "Yes...yes...but if we stopped using MyLibrary, removing the unnecessary layers, will make the code run faster."
<typical headknodd-ers knod their heads in agreement>
Dev01: "The loading of MyLibrary takes CPU cycles away from code that supports our customers. Every CPU cycle counts."
<headknod-ding continues>
Me: "I'm really confused. Maybe I'm looking at the data wrong. On the slide where you highlighted all the bottlenecks, the histogram shows the latency is the database, I mean...it's right there, in red. Am I looking at it wrong?"
<this was meeting with 20+ other devs, mgrs, a VP, the Panorama engineer>
DeptMgr: "Yes you are! I know MyLibrary is your baby. You need to check your ego at the door and face the facts. Your MyLibrary is a failed experiment and needs to be exterminated from this system!"

Fast forward 9 months, maybe 50% of the projects updated, come across the documentation left from the Panorama. Even after the removal of MyLibrary, there was zero increases in performance. The engineer recommended DBAs start optimizing their indexes and other N+1 problems discovered. I decide to ask the developer who lead the re-write.

Me: "I see that removing MyLibrary did nothing to improve performance."
Dev: "Yes, DeptMgr was pissed. He was ready to throw the Panorama engineer out a window when he said the problems were in the database all along. Didn't you say that?"
Me: "Um, so is this re-write project dead?"
Dev: "No. Removing MyLibrary introduced all kinds of bugs. All the boilerplate ADO.Net code caused a lot of unhandled exceptions, then we had to go back and write exception handling code."
Me: "What a failure. What dipshit would think writing more code leads to less bugs?"
Dev: "I know, I know. We're so far behind schedule. We had to come up with something. I ended up writing a library to make replacing MyLibrary easier. I called it KnightRider. Like the TV show. Everyone is excited to speed up their code with KnightRider. Same method names, same exception handling. All we have to do is replace MyLibrary with KnightRider and we're done."
Me: "Won't the bottlenecks then point to KnightRider?"
Dev: "Meh, not my problem. Panorama meets primarily with the DBAs and the networking team now. I doubt we ever use Panorama to look at our C# code."

Needless to say, I was (still) pissed that they had used MyLibrary as dirty word and a scapegoat for months when they *knew* where the problems were. Pissed enough for a flamethrower? Maybe.

Last week, the team lead told me that he can't merge because my code has code smells and going forward, can't have that. We use Sonar and well the way to "fix it" according to him is to mark the line using //NOSONAR.

Most of the issues are minor like Unused imports and for me incomplete TODOs.

And before the "verbal" rule was only need to fix Major + issues. And well the reason I use TODOs is to mark code that probably needs changing in the future. I know there's going to be some feature that these lines have to be changed. But the requirements are fully defined yet from business.

But I sort of blew up on him. YOU WANT TO ENFORCE ZERO CODE SMELLS NOW?!?!?! AND THESE MINOR ISSUES? MARK THEM WITH NOSONAR?

HERE'S WHAT I THINK FOR THE LAST X YEARS... THE CODE DESIGN IS SHIT, MINOR CODE SMELLS AND MANUALLY MARKING THE ONES U NEED TO KEEP... ARE THE LEAST OF OUR PROBLEMS...

THE OTHER PROBLEMS I'VE MENTIONED BEFORE EVER. MOS YEAR BUT YOU DIMWITS NEVER LISTEN.

YOU THINK MY TODOS ARE BAD... 90% OF THE CODE AND FEATURES (THE ONES NOT DONE BY ME) LOOK AND SMELL LIKE MONKEY SHIT. UNDOCUMENTED, MESSY, FULL OF BUGS.

AND GUESS WHAT? NEW FEATURE, SOME DEV FORGETS TO CHANGE SOME COMPONENT THAT DEPENDS ON IT. WOULDN'T IT BE GREATE IF THERE WERE BOOKMARKS... O WAIT...

i just was catching up on comics again and saw this one... with triggered my memory and this rant... My first thought was to forward it to him...

TeamLeader: I need you to stop disagreeing with the decision of the management, the people in there are taking their decision for a reason.

IHateForALiving: When integration tests were failing, the management decided to comment out the ingration tests; god knows how many bugs slipped by.
When users had problems with the idiotic migration process the management designed, the management decided to remove down migrations; it took two weeks before the QA team started screaming, as all their machines were filled with garbage data.
I was writing type definitions for my code, you removed it. You effectively ensured the only person capable of working on that particular piece of code would be me.
I have been proposing for 8 months to make a unified scheduled jobs system, you all decided to create at least 5 different -and incompatible- implementations, at least 4 of them are total garbage with setTimeout, there's no way to ever unify them and God willing they never break, if they do there's NO WAY to find out even where tf they're hidden in the code.
Every time you were making one of those bad decision I was the only one warning you of the problems you were creating. The idiotic change of the day is going MongoDB+Angular: I can keep a low profile if you want, but when this blows up you can be damn well sure I'll handle my 2 weeks notice because there's no way on earth I'll be stuck with the aftermath of you lot taking technical decisions you are clearly unable to manage.

Finally after one year I understood how to carry out my job. I should do exactly NOTHING. I stopped completely organizing the team, solving bugs, helping the team developing and solving problems, explore and try stupid things said by CEO, PM and consultants.
I stopped for 2 months now and nothing happened.
I work remotely, nobody knows if I'm working or not, because nobody cares really about priorities, bugs, customers or products development.

I gain 10K$ (ten thousand) per month.

I attend skype meeting once per week or less. I say yes to everything, nobody gives a shit to what I say, even if they consider me the technical director. Actually in the meetings I only take care of being considered the technical director.
I achieved the mythical 4 hours working week.

I keep skype open in all my devices in order to answer promptly in case of problem, wherever I'm am, that's the most important thing right now.

I attended some meeting from the toilet or from the bedroom.

It was hard. To understand that the board is only after the next funding and not looking to develop a real product. It's hard to pretend helping people while thinking inside you "fuck you".
You have to let go the "guilt": if you can't login, I KNOW that is my fault, that there is a bug, that is possible to solve it, that resources and planning are needed etc. That's guilt. Just let go and say "next release" and never include it in the next release.
In this way I discovered that some users are paying the application even if they can't login.

The company is not going to disappear in the next 5 years. On the contrary, it's going to receive more money.

So the only "bad" thing is, what will I write in my CV in 5 years?

Today is the real fuckening at work. The worst part is, you are working your ass off and someone started bugging you constantly on chat and blaming it is effecting his "productivity" because tech team doesn't solve his problem.

I have 4 projects under me with doing day to day operations also. But yeah just few more months before I left this shit. I wanted to shout back, but tried to keep my head cool, though I have already kicked his face many times in my mind.

If you cannot help, at least stop being a dick and appreciate someone trying his best to solve problems.

Man, most memorable has to be the lead devops engineer from the first startup I worked at. My immediate team/friends called him Mr. DW - DW being short for Done and Working.

You see, Mr. DW was a brilliant devops engineer. He came up with excellent solutions to a lot of release, deployment, and data storage problems faced at the company (small genetics firm that ships servers with our analysis software on them). I am still very impressed by some of the solutions he came up with, and wish I had more time to study and learn about them before I left that company.

BUT - despite his brilliance, Mr. DW ALWAYS shipped broken stuff. For some reason this guy thinks that only testing a single happiest of happy path scenarios for whatever he is developing constitutes "everything will work as expected!" As soon as he said it was "done", but golly for him was it "done". By fucking God was that never the truth.

So, let me provide a basic example of how things would go:
my team: "Hey DW, we have a problem with X, can you fix this?"
DW: "Oh, sure. I bet it's a problem with <insert long explanations we don't care about we just want it fixed>"
my team: "....uhh, cool! Looking forward to the fix!"
... however long later...
DW: "OK, it's done. Here you go!"
my team: "Thanks! We'll get the fix into the processing pipelines"
... another short time later...
my team: "DW, this thing is broken. Look at all these failures"
DW: "How can that be? It was done! I tested it and it worked!"
my team: "Well, the failures say otherwise. How did you test?"
DW: "I just did <insert super basic thing>"
my team: "...... you know that's, like, not how things actually work for this part of the pipeline. right?"
DW: "..... But I thought it was XYZ?"
my team: "uhhhh, no, not even close. Can you please fix and let us know when it's done and working?"
DW: "... I'll fix it..."

And rinse and repeat the "it's done.. oh wait, it's broken" a good half dozen times on average. But, anyways, the birth of Mr. Done and Working - very often stuff was done, but rarely did it ever work!

I'm still friends with my team mates, and whenever we're talking and someone says something is done, we just have to ask if it's done AND working. We always get a laugh, sadly at the excuse of Mr. DW, but he dug his own hole in this regard.

Little cherry on top: So, the above happened with one of my friends. Mr. DW created installation media for one of our servers that was deployed in China. He tested it and "it was done!" Well, my friend flies out to China for on-site installation. He plugs the install medium in and goes for the install and it crashes and burns in a fire. Thankfully my friend knew the system well enough to be able to get everything installed and configured correctly minus the broken install media, but definitely the most insane example of "it's done!" but sure as he'll "it doesn't work!" we had from Mr. DW.

It was my internship and I've end up working on a law company specializing on Australian construction laws they're working on a website that will take care of all the paperworks for the contractors. They have a dev team who's working on it but they don't have a web designer. I was accepted for the job as an intern/web designer/tester. I was so happy that I've got a really cool internship as a designer but that's only for a second.

The hell starts on day one. They've told me that they're using agile workflow and that they need to make the website responsive. It was based on bootstrap and gosh their code was so broken. HTML tags overlay on each other, some are unclosed. I've tried to fix the problems and did a great job at that. Made the front page responsive and all laid out. When I went to the next php file it has a different header.php and footer.php and same problems apply and we're not even touching the worst.

They didn't use any version management and they're cowboying everything. Now that the website is on the staging server they use Cpanel text editor to edit the code! My headache started to pileup.

The Australian client asked me to provide icons and fix the colors of the website. Also the typography looks great already. I've fixed almost all the problems and I'm satisfied with the design when suddenly a new co-worker from a famous and expensive college was absorbed by the company. He worked as the marketing specialist who has no experience at web design at all. He told me to do this and that and the whole website changed. He bullied me for my skills in design (I'm an intern) and just took over the whole design. Everyone even the boss listen to him as if everything he say is right. He's skilled at design but not web design. He made the website look like a freakin movie poster.

All my works are for nothing, I got headache for nothing and I've got hated for nothing.

It was the day when I finished my internship. It was a long 3 months. After a month I've heard from my co-interns that the whole dev team was fired including the marketing specialist. Also the whole website is scrapped and has been rebuilt by a single guy who used WordPress which he did in only a month.

doNotMessWithITTeamInAFuckingProject();

Last night me with my team have a discussion with my project team. Currently we have a project for our insurance client building a Learning Management System. The project condition already messed up since the first day i join a meeting. Because since its a consortium project with multiple company involved, one of company had a bad experience with another company. It happened few years back when both of company were somehow break up badly because miss communication (i heard this from one of my team).

Skip..skip... And then day to day like another stereotype IT projects when client and business analyst doing requirements gathering, the specs seems unclear and keep changing day by day even when I type this rant I'm sure it will change again.

Then something happened last night when my team leader force our business analyst to re index the use case number (imho) this is no need to be done, and i know the field conditions its so tough for all team members.

So many problems occured, actually this is a boring problem like lack of dev resource, lack of project management and all other stereotype IT projects had. Its sucks why this things is happening again.

Finally my fellow business analyst type a quite long message in our group and said that he maybe quit because its too tired and he felt that the leader only know about push push pushhhhhy fcking pussy, he never go to the client site and look what we've done and what we struggle so far.

I just don't know why, i know this guy earlier was an IT geek also, but when he leading a team he act like he never done IT project before, just know about pushing people without knowing what the context and sound to me like just rage push!

Damnit, i maybe quit also, you know we IT guy never affraid to quit anytime from the messed up condition like this. Even though we were at the bottom level in a project, but we hold the most main key for development.

Hope he (my leader) read this rant. And can realize what happened and fix this broken situation. I don't know what to say again, im in steady mode to quit anytime if something chaos happen nearly in the future.

doNotMessWithITTeamInAFuckingProject();

My colleague is what you would call a cowboy coder. He solves problems with really complex solutions that only he understands and does not seem to care about that the team doesn't understand it. He's super fast and very skilled, but it leaves the rest of the team hanging. He sometimes works at his spare time so things we worked on the previous day can be totally changed the next day without any notice. He has also removed code written by someone else because he did not like it, in secret. I found this while browsing through commits that were committed directly to master without a PR.

We have tried talking to me about this but it doesn't seem to work. He seems to value speed over anything else and doesn't seem to have any respect for other team member's opinions.

What the hell do I do? Has anyone else worked with a similar typed person? He's really making my life hard and I think it's very frustrating. Please help.

Worst collaboration experience story?

I was not directly involved, it was a Delphi -> C# conversion of our customer returns application.

The dev manager was out to prove waterfall was the only development methodology that could make convert the monolith app to a lean, multi-tier, enterprise-worthy application.

Starting out with a team of 7 (3 devs, 2 dbas, team mgr, and the dev department mgr), they spent around 3 months designing, meetings, and more meetings. Armed with 50+ page specification Word document (not counting the countless Visio workflow diagrams and Microsoft Project timeline/ghantt charts), the team was ready to start coding.
The database design, workflow, and UI design (using Visio), was well done/thought out, but problems started on day one.
- Team mgr and Dev mgr split up the 3 devs, 1 dev wrote the database access library tier, 1 wrote the service tier, the other dev wrote the UI (I'll add this was the dev's first experience with WPF).
- Per the specification, all the layers wouldn't be integrated until all of them met the standards (unit tested, free from errors from VS's code analyzer, etc)
- By the time the devs where ready to code, the DBAs were already tasked with other projects, so the Returns app was prioritized to "when we get around to it"

Fast forward 6 months later, all the devs were 'done' coding, having very little/no communication with one another, then the integration. The service and database layers assumed different design patterns and different database relationships and the UI layer required functionality neither layers anticipated (ex. multi-users and the service maintaining some sort of state between them).

Those issues took about a month to work out, then the app began beta testing with real end users. App didn't make it 10 minutes before users gave up. Numerous UI logic errors, runtime errors, and overall app stability. Because the UI was so bad, the dev mgr brought in one of the web developers (she was pretty good at UI design). You might guess how useful someone is being dropped in on complex project , months after-the-fact and being told "Fix it!".

Couple of months of UI re-design and many other changes, the app was ready for beta testing.

In the mean time, the company hired a new customer service manager. When he saw the application, he rejected the app because he re-designed the entire returns process to be more efficient. The application UI was written to the exact step-by-step old returns process with little/no deviation.

With a tremendous amount of push-back (TL;DR), the dev mgr promised to change the app, but only after it was deployed into production (using "we can fix it later" excuse).

Still plagued with numerous bugs, the app was finally deployed. In attempts to save face, there was a company-wide party to celebrate the 'death' of the "old Delphi returns app" and the birth of the new. Cake, drinks, certificates of achievements for the devs, etc.

By the end of the project, the devs hated each other. Finger pointing, petty squabbles, out-right "FU!"s across the cube walls, etc. All the team members were re-assigned to other teams to separate them, leaving a single new hire to fix all the issues.

team downloading a library to solve in 12 hours problems I could code myself out in 15 minutes, complication as a service at its best.

Why the fuck are the setup instructions for the repo for Mac only?!! Oh, because everybody on the previous team used a Mac?!

Have you dick heads ever considered the possibility of new developers for the university module website not having a Mac??

And fuck your documentation too, half the fixes for setup problems mentioned inside the page doesn’t work. CS freshmen can write better documentation than you guys.

PS: that website and db is still not set up and setups should never take more than a day

I love my relationship with the front end team:

—Hey, you have a minute? I need help with some of the endpoints you've created.
—Sure, what's up?
—Nevermind I figure it out.

Solving problems without effort. That's what I call efficiency.

Backstory: A few months ago, I wrote an inventory management web app for internal use by the sales team, logistics, and whoever else might need to use it.

Earlier this week: A few minutes before I usually leave, my phone rings. It's some dude I've never heard of. No idea what his function at the company is, still don't, probably never will, don't care. He's never used the app before, and says he's having problems. His cube's on my way out, so I swing by.

I'm not making this next part up. This dude is probably 60 years old, and he's using a very old looking gateway desktop (with the cow print logo thing on the chassis), running Windows XP (not a typo), using IE7.

I don't know what to say, so I just stare at the desktop, look at dude, laugh, and eventually explain that he's never going to be able to use the system via the web app until his rig is replaced.

What the fucking fuck is this. How could this have happened. How do our it people still fucking have jobs. Better question, how did this thing survive the y2k bug?

Boss: our team in El Salvador is having problems with the app. Look at the email I forwarded you.

Me: oh yes. They are running the wrong ionic commands they need to run these commands.

Boss: okay, and that will fix everything?

Me:...Let's just have them enter the right commands...we can go from there.

A misconception that software engineers just sit in front of their laptops and code 40 hours a week, with no social interaction.

A software engineer’s job is actually pretty social. Personally, I probably spend around half of my time interacting with people. This could be partially due to 1:1, team, and other meetings. But a large part of it is spent in bouncing off ideas about your project with your project mates (especially during the planning phase), chiming in the conversations about some recent or urgent problems to help find or propose solutions, answering others’ questions, organizing some events, etc.

Of course, I do need some dedicated uninterrupted time to focus on programming and to get into the zone, but it’s certainly not the only activity I do at work. The main point to understand is that the software engineering is not a solitary, but a social job.

Overall, I’m very happy with my profession. The enjoyment I get out of my work vastly outweighs all of these points combined.

- Back in October 2019 -

- Me: Hey, these two servers are having weird problems. Several services we use stop functioning every 7-10 days. I can temporarily fix them by taking them off the domain and putting them back on, but I don’t know why they’re happening or what further damage this workaround causes.
- Boss: Thats not good. Well. Keep doing the fix when it’s needed.
- Me: We should really reach out to someone at Microsoft through our support plan. I have no idea how to fix any of this and it’s making our Hyper-V environment very unstable.
- Boss: K. Let’s not worry about that now, let’s just keep working around it.

- In January 2020 -

- Me: Hey boss. More and more errors are generating from these servers. I’ve created a log of everything Ive found to hand off to a support agent. We really need to.
- Boss: Okay. Let’s talk to our internal team that uses Hyper-V and see what they did since they don’t have any problems.
- Me: Its not Hyper-V specific. It’s stemming from AD and authentication. It causes problems even without Hyper-V installed, so I don’t think it will help.
- Boss: K. Let’s just do what we can with what we got.

- Today, May 2020 -

- Me: Hey. The servers no longer work at all, and the workaround has no effect anymore. I’m completely stalled on my project now and have nothing to do.
- Boss: What?? What happened to them?
- Me: *Sends 17 page PDF file documenting all found issues, errors, warnings, and weird anomalies in both servers, as well as troubleshooting steps I’ve already performed*
- Boss: None of this makes any sense. I need you to start troubleshooting right away.
- Me: But... I can’t... *Sends screenshots of errors having no search results on the web, screenshots of Microsoft Support Techs on forums telling me we need to open tickets with Microsoft directly, other reasons why I’m completely blocked*
- Boss: Keep trying to figure it out. We need this resolved as soon as possible and we can’t let it happen again in the future.

Now I’m completely alone in our office, bitterly staring at the servers, trying to force an epiphany on how to fix these dumb boxes.

So I finished my first semester in NYU as a CD master. During the first semester I took a class called heuristic problem solving. Every week a competitive game will be introduced to us, and will be played in two weeks. And trust me, the games aren't easy. I teamed up with another guy who I had no idea was and named our team as we don't know. At the end of the semester we won seven out of nine games, and by won I meant that we beat the whole class in the match. And my teammate became a really good friend.

By telling this story, I want to make a point. I love problem solving, and not problems in a algorithm book where you apply an algorithm and do some trick to solve it, but real world problem where you hope for the best and anticipate, predict your opponent's move. However, American's school system doesn't teach that.

When I applied to graduate school, no school wanted me because I have an average GPA of 3.6, and no outstanding achievements. I can solve problems in my dream becaus I have an active mind, I can propose solution to a project one month before my teammates realized they essentially were doing what I told them the solution should be. But so what, I can't write those on my application.

One of the professor told me that my professor shared the story of my team during a faculty dinner, and they were very impressed by our achievement. So I guess I'm not dumb. But after all, companies and schools will look at your transcript and decide who you are.

I love myself for having random thoughts all the time that can lead to innovative problem solving. But I also hate myself for not able to study like the good kids are.

Ever want to smack someone in the face with a sea bass? Like left out of the water for 3 days with all kinds of juicy and smelly goodness?
When we get an X number system errors, an email is sent to our team. Couple of hours ago I had to move the alerts from one system to another, re-naming some because I suck at naming things. I guess when I copied, I duplicated one. About an hour ago we get a system alert (as it should, there was a server hiccup) and there were two emails with the same data (just named differently)
DevA: “Why are there two emails?”
Me: “Oh, that’s me. I think I copied the alert instead of move. I’ll fix it tomorrow.”
DevA: “Hmm, but the data is the same. It’s a duplicate.”
Me: “Yea, I know. Networking responded and said it’s fixed. We won’t get another email.”
- 15 minutes later
DevA leans over and says to the boss (who was in a meeting and just sat down)…
DevA: “I looked at the alert, it’s duplicated, but the name is different. I don’t understand why.”
Me: “Like I said, the alert is duplicated. When I migrated, I copied instead of moved. No big deal.”
DevA: “Oh …oh ..yea.…OK.”
- 5 minutes later
DevA: “I looked at the query, we might have to add a filter to prevent duplicate emails. Probably some logic problems in the search.”
Me: “I just deleted the duplicate alert.”
DevA: “Oh…OK…that fixes it too.”

Good lord…as I was typing this, he just told another dev the ‘duplicate’ emails were because of a logic bug in the search. I’m getting my fishing pole.

How come it is so hard to find good developers. Have been doing interviews for a couple of weeks now (for a senior PHP developer role).

First round is me talking about the function and company, asking questions about candidates experience, wishes and we usually end in some tech conversations. Most of the resumes I got are pretty fucking good. I mean, experience with low-level languages, experience with the problems we need to solve here, contributions to open-source, experience in R and MathLab etc etc. On paper they look perfect.

For the second round I give them an assessment which they can do at home on their own machine in their own time. It's not a hard one, just some mathmatical problems they need to solve. A quick google GIVES the answer (no joke!!). But that's OK, I look at their code cleanliness, proper use of commenting so I can determine if they are solo-developers or fit good in a team and if they abstract repeated functions and make sure that they take their work seriously, you know the drill.

It pisses me off that I get BROKEN FUCKING CODE WHICH DOES NOT EVEN RUN and that I get code back which I look at and makes me vomit instantly, I mean, DO YOU EVEN TAKE YOUR PROFESSION SERIOUS? How dare you to ask for 50k the year, a lease-car, extra bonusses AND YOUR FUCKING CODE SPITS OUT COMPLETLY WRONG ANSWERS OR DOES NOT EVEN RUN WHAT THE FUCK DUDE GO BACK TO FROM WHICH EVER HOLE YOU CRAWLED OUT AND STOP WASTING OTHER PEOPLES TIME WITH YOUR FUCKING INCOMPENTENCE...

IF YOU UPDATE AN ADM PLATTFORM FOR FUCKS SAKE DON'T DO THE FOLLOWING THINGS:

1. ONLY DOCUMENTATE IT IN A POWERPOINT

2. WRITE DOWN IPs AND PORTS ONLY ON A WHITE-BORD

3. MOVE TOOLS TO OTHER SUBNETS OR DOMAINS WITHOUT PROPERLY KNOWING THE WAYS OF COMMUNICATION BETWEEN THEM

4. USE YOUR PERSONAL EMAIL ADDRESS AS RESET OPTION FOR LICENCE-MANAGEMENT ACCESS IF NO ONE KNOWS THE PW

5. LEAVE THE COMPANY THE DAY AFTER THE UPGRADE IS DONE

Because the guy who has to take care of the upcoming problems is not going to like you!

BUT having to deal with all of this at once would not be a problem if your, so called team (30 People who work with those applications e.g. as test-engineers) would actually work together instead of having that "not my daily business, I am going to drink coffee" attitude.

Apparently I am the only one who has enough balls to see, admit, and report a problem to our leadership.
This always leads to Me fixing the issue...
....that's alright I am learning a lot...
...BUT IF A TEAM-MATE, WHO HAS THE SAME DEGREE AS I AM GOING TO GET, LEAVES EARY BECAUSE: "HE DOES NOT KNOW WHATS WRONG", IT TRIGGERS ME!!!

- The apprenticeship guy

PS Needless to say hundreds of clients have access to those systems and I worked through a shittload of official tool docs just to get to know the tools first...

PM sends email to development team with the whole management team in cc.

"Guys, the data is not updating correctly! Make sure all the updates are being done! If we can't get this right then we can just forget about this whole thing!"

Me: Yes, because making generalized statements and inflammatory remarks actually help in correcting the problems...

Worst thing you've seen another dev do? Here is another.

Early into our eCommerce venture, we experienced the normal growing pains.

Part of the learning process was realizing in web development, you should only access data resources on an as-needed basis.

One business object on it's creation would populate db lookups, initialize business rule engines (calling the db), etc.

Initially, this design was fine, no one noticed anything until business started to grow and started to cause problems in other systems (classic scaling problems)

VP wanted a review of the code and recommendations before throwing hardware at the problem (which they already started to do).

Over a month, I started making some aggressive changes by streamlining SQL, moving initialization, and refactoring like a mad man.

Over all page loads were not really affected, but the back-end resources were almost back to pre-eCommerce levels.

The main web developer at the time was not amused and fought my changes as much as she could.

Couple months later the CEO was speaking to everyone about his experience at a trade show when another CEO was complementing him on the changes to our web site.
The site was must faster, pages loaded without any glitches, checkout actually worked the first time, etc.
CEO wanted to thank everyone involved etc..and so on.

About a week later the VP handed out 'Thank You' certificates for the entire web team (only 4 at the time, I was on another team). I was noticeably excluded (not that I cared about a stupid piece of paper, but they also got a pizza lunch...I was much more pissed about that). My boss went to find out what was going on.

MyBoss: "Well, turned out 'Sally' did make all the web site performance improvements."
Me: "Where have you been the past 3 months? 'Sally' is the one who fought all my improvements. All my improvements are still in the production code."
MyBoss: "I'm just the messenger. What would you like me to do? I can buy you a pizza if you want. The team already reviewed the code and they are the ones who gave her the credit."
Me: "That's crap. My comments are all over that code base. I put my initials, date, what I did, why, and what was improved. I put the actual performance improvement numbers in the code!"
MyBoss: "Yea? Weird. That is what 'Tom' said why 'Sally' was put in for a promotion. For her due diligence for documenting the improvements."
Me:"What!? No. Look...lets look at the code"

Open up the file...there it was...*her* initials...the date, what changed, performance improvement numbers, etc.

WTF!

I opened version control and saw that she made one change, the day *after* the CEO thanked everyone and replaced my initials with hers.

She knew the other devs would only look at the current code to see who made the improvements (not bother to look at the code-differences)

MyBoss: "Wow...that's dirty. Best to move on and forget about it. Let them have their little party. Let us grown ups keeping doing the important things."

Got demoted, got a pay raise and don't know how to feel about it. A story of how not to drink with your coworkers?

The story begins roughly 8-9 months ago. Me and this coworker (let's name him Tim) go out drinking after a Friday party at the office. We do some rounds and we're both smashed. Tim starts telling me how he's happy with life and that he's earning a nice salary right now. He told me his salary. It was the same as mine. Which was weird - He codes in a more hardcore languages than me and has almost double the time in the company as me. I think after some more drinking I've confessed that I make the same as him. This part is sort of a blur (drinking). I've gotten a pay raise(+30-40%) roughly a few months ago from that point backwards because another company gave be a much higher offer. The company I work for matched to keep me. Anyway, 3 months or so after the drinking,Tim is promoted to team lead, and me and a few other people are added to his team. Conversation slips and he told me his new salary - quite a bit more than me.I think it's safe to assume what happened.

The problem with that is that I was a team lead of 1 person (me) at that time, and I was managing my own time and my own tasks, was working with people individually. I was part of the weekly meetings with the CEO and other team leads. Being stripped of this title wasn't a problem at the beginning, as people still contacted me because of their problems, suggestions, whatever. A few more months pass (to now) and less and less people are contacting me - instead they are talking with Tim, and are asking of his opinion on tasks I should do, where he has no experience and roughly 0 lines in the programming language I code in. This is starting to piss me off.

There are a couple other things to take into consideration as well - The company is hiring a lot of people right now. The whole structure for team leads changed a bit, more team leads then ever right now and new roles added pretty fast.

I've gotten a pay raise a few weeks ago though(10%~).

I'm not sure on how to react to this. Should I comply and just keep on working on these tasks? Or should I still keep contacting people directly on their requests and talk to them directly, take credit for the projects I complete publicly and the stuff I do as I was previously doing? Part of me wants to reroute all of the stupids questions people have to Tim, as he is now responsible for these tasks and get this weight off my shoulders.

I'm starting to shift to learning a new programming language and thinking of jumping ship. Thoughts?

Passionate programmer attends one of the toughest interviews ever and solves lot of algorithmic problems coding in different programming languages. Impresses the interview panel providing solutions with as much as efficiency as possible. Gets selected, completes induction and gets a nice Dev machine allocated.

Manager walks in and says we got to work with the production support team on fixing a UI bug.

Rant r = new Rant(Rant.TEAM_PROBLEM);

Three months ago, a senior, one year older than me, decided to join me in doing startups. He said he's good at finance stuff (his parents are fund managers), and he is interested in startups just like I am. He treated me very nicely, so I gladly accepted him.

I'm currently working on many projects, and some of them won me quite a few awards, most notably on the national competition. I also got invited into startup incubator programs, met some awesome people and offered free scholarships at universities in my country.

He frankly said he joined because he wanted to learn about startups and have those "privileges" too, and I'm cool with that.

Anyway, the problem is that I'm the one doing all the work. He's really nice, doesn't claim anything whatsoever, but the thing is he doesn't have any skills whatsoever except soft skills like communicating. So, I'm horribly tired from working alone.

My tasks mostly involves full-stack development, such as planning the specs, designing and developing frontend for mobile apps and progressive webapps, developing microservices for the backend, up to deploying and maintaining the servers. It's a lot of work for a single person to handle in such a short timeframe.

Not only that, but I'm also the one handling the business/marketing part, albeit I'm still learning. From doing paperworks, pitches, business models, up to creating advertising materials for the product.

I'm obviously not the smart ones like the people out there, but I keep focusing on improving my skills.

So, he said he could help me, and I let him try. What did you think he did?

He made pitch decks using default fucking PowerPoint themes, shooted a demo video with his phone cam in 320p potato resolution and expect me to "add some effects", gives me loads of requirements when all we needed was a simple feature, copying and pasting prior documents in my paperworks which doesn't make any fucking sense at all, and quite a lot more.

Also, he said I should stay in the developer zone only while he maintains the business, whilist he obviously can't do much in the business part either. Seriously...?

I'm okay with his lack of experience, considering he's nice and all, unlike the other business guys I've met in the previous rants. However, I keep questioning myself why he is here in the first place when I'm the one doing everything anyway.

What should I do? Maybe just keep him and recruit more experienced people to join us, as he's not that much of a burden? What do you devRanters think?

Thanks for reading, fellow devRanters! 😀

The dev usually sitting next to me is on vacation. Our senior dev is on vacation. Team analist, on a plane to a Greek beach as we speak. Both architects the company employs, gone for another two weeks or so. Lead analist, you guessed it, on vacation.

I'm enjoying the peace & quite for now but god forbid I run into any problems these next coming weeks.

It's sometimes good I work remotely from the rest of my team.... So other can't see how pissed I'm while chatting with them...

Just did an afternoon basically hand holding someone... And well this is the 3rd day... And the original instructions I gave them was: here's the problem, here the code fix, now you need to change it for the other 10 APIs it affects (OS migration).

I have another problem I need to figure out....

Yes I could do it all myself and it would be faster but I don't want to be the only person who can do this stuff either...

But can you just try to use your brain and figure things out before asking how to ....

I don't know am I that much more experienced than everyone else so I just know how to figure things out quickly, know to the learn efficiently? Ask the right questions to Google?

How hard is it to just learn to Google your problems... 80% of the questions u ask me I either tell you to Google it or actually end up googling the answer myself...

I work on a warehouse dev team. One day this past year, I was trying to deploy a new build to a QA server. Earlier that day I had been looking at the logs on the production server and had left the ssh session open. I had been working for less than a year out of college at this point and shouldn't have had access to deploy to the production server.

Long story short I deployed my QA build to the production server and saw there were problems connection to our production database. Then my heart dropped in my chest as I realized I had just brought down our production server.

I managed to get the server back up by rolling back in about 5 minutes and no one ever knew except some people on my team.

I felt horrible for the longest time. Later in the year another guy that joined my team that has about 20 years of experience under his belt did the exact same thing, but needed help rolling it back. Needless to say, that made me feel a lot better. 😂

Definitely the worst moment of my year.

TL;DR:
JuniorDev ignores every advice, writes bad code and complains about other people not working because he does not see their result because he looks at the wrong places.

Okay, so I am really fed up right now.
We have this Junior Dev, who is now with us for circa 8 months, so ca. a year less than me. Our first job for both of us.
He is mostly doing stuff nobody in the team cares about because he is doing his own projects.

But now there's a project where we need to work with him. He got a small part and did implement that. Then parts of the main project got changed and he included stuff which was not there anymore. It was like this for weeks until someone needed to tell him to fix it.
His code is a huge mess (confirmed by senior dev and all the other people working at the project).

Another colleague and me mostly did (mostly) pair programming the past 1-2 weeks because we were fixing and improving (adding functionality) libraries which we are going to use in the project. Furthermore we discussed the overall structure and each of us built some proof-of-concept applications to check if some techniques would work like we planned it.
So in short: We did a lot of preparation to have the project cleaner and faster done in the next few weeks/months and to have our code base updated for the future. Plus there were a few things about technical problems which we need to solve which was already done in that time.
Side note: All of this was done not in the repository of the main project but of side projects, test projects and libraries.

Now it seems that this idiot complained at another coworker (in our team but another project) that we were sitting there for 2 weeks, just talking and that we made no progress in the project as we did not really commit much to the repository.
Side note: My colleague and me are talking in another language when working together and nobody else joins, as we have the same mother tongue, but we switch to the team language as soon as somebody joins, so that other colleague did not even know what we were talking about the whole day.

So, we are nearly the same level experience wise (the other colleague I work with has just one year more professional experience than me) and his work is confirmed to be a mess, ugly and totally bad structured, also not documented. Whereas our code is, at least most of it, there is always space for improvement, clean, readable and re-useable (confirmed by senior and other team members as well).
And this idiot who could implement his (far smaller part) so fast because he does not care about structure or any style convention, pattern or anything complains about us not doing our work.

I just hope, that after this project, I don't have to work with him again soon.
He is also one of those people who think that they know everything because he studied computer science (as everybody in the team, by the way). So he listens to nothing anybody explains to him, not even the senior. You have to explain everything multiple times (which is fine in general) and at some points he just says that he understood, although you can clearly see that he didn't really understand but just wants to go on coding his stuff.
So you explain him stuff and also explain why something does not work or is not a good thing, he just says "yes, okay", changes something completely different and moves on like he used to.

How do you cope with something like this?

Our project at work goes live in 3 weeks.

The code base has no automated tests, breaks very often, has never had any level of manual testing

will not be releasing with any form of enforced roles or permissions in our first release now due to no time to enforce, however there is a whole admin api where you can literally change anything in our database including roles.

We also have teams in various countries all working separately on the same solution using microservices with shared nuget packages and they aren't using them properly.

Our pull requests are so big - as much as, 75 file changes - in our fe app that I can't keep up with it and I honestly have no idea if it even works or not due to no automated tests and no time to manually test.

We have no testing team, or qa team of any sort.

Every request into the system has to hit a minimum of 3 different databases via 3 different microservices so 1 request = 4 requests with the load on the servers.

We don't use any file streams so everything is just shoved in the buffer on the server.

Most of the people working on the angular apps cba to learn angular, no one across 2 teams cba to learn git. We use git so they constantly face problems. The guy in charge has 0 experience in angular but makes me do things how he wants architecturally so half the patterns make no sense.

No one looks at the pull requests, they just click approve so they may as well push directly to master.

Unfinished work gets put in for pull request so we don't know if the app is in a release state since aall teams are working independently, but on the same code base.

I sat down and tested the app myself for an hour and found 25 fe only issues, and 5 breaking cross browser issues.

Most of our databases are not normalised. Most of our databases make no sense. 99% of our tables have no indexing since there is no expertise with free time to do it.

No one there understands css properly. Or javascript.

Our. Net core microservices all directly use ef in the controller actions so there is no shared code there.

Our customer facing fe app is not dry because no tests so it was decided it was better this way.

Management has no idea on code state, it seems team lead is lieing to them about things like having any level of tests.

Management hire devs that claim to be experts but then it turns out they have basically no knowledge of what they were hired to do, even don't know what json is or the framework or language they are hired for, but we just leave them to get on with it and again make prs too big to review.

Honestly I have no hope that this will go well now but I am morbidly curious to watch. I've never seen anything like the train wreck that we are about to get experience.

How do you guys/girls explain to potential new customers that you can perfectly work in a structured business environment and follow the rules, but also that you're assertive enough to oppose desicions being made based on bias, misunderstanding, fanboyism, or grave stupidity.

I just got informed from a freelance position that they would have hired me if it were not for my 'rebellious nature towards customers'

I don't oppose customers, i oppose stupidity unfounded.
Example from experience
> me working in a helodesk support position, all windows computer.
> new mgr comes into office, is a douche and complete mac fanboy
> wants all computers that are FINALLY working decent for some time in the entire department replaced with mac's... Back at 2010.
> whole team, even disliking microsoft themselves, are telling mgr that's a bad, dangerously dumb idea, expensive too, different OS, different software mgmt making, back then integration microsoft and apple was beyond diarhea... Several other issues the senior devs and admins pointed out

>mgr: 'but aple is soh much better, like a billion times better, hurrduurrrrr'
His decision passed somehow to the board..
> All stations from our customers get changed...we don't get a single machine to try out problems because overspending
> we are most of the time unable to help out customers because we still have pc's...
> mgr asks team why performance drops after 1 month
> we compared performance graph with his starting date of mgr, see clear drop after mgr's plan implemented...
> board stilll stands by mgr, gets praise for 'bold changes in the company', but appears to be some associate's son
> two main seniors leave after 15 years of employment, in three months, 80% of staff leaves.
> we canr fix the problems, we are not dev's , we get shit from all sides, i was still a junior in the industry so i worked as a slave inside that job.
> eventually get fired due to 'bad performance'
> mgr loses entire team... 'Hey why don't we outsource this dept to south africa, it's a lot cheaper! '

now that company is an it hellhouse where everyone get clinically depressed from sitting atbtheir station...
This is what i wish to oppose!

How to make that clear!

Fuck my company. Let the technology people work with technology.

I work at a small company who constantly brings in people who are absolutely useless. The project manager requires me to take items out of azure Dev-ops into an excel because he will not take the time to understand how a board works. The business analyst hands bullshit requirements in formats which no one but him can understand under the pretense that the Devs and architect can ask him when they feel like it. The CEO wants a power-point which again the technical teams have to prepare for him because the project manager or BA will not have time for it. However they make sure to gut the estimates handed over by the Dev team and introduce unfeasible deadlines.

Meanwhile the client has zero problems as the work still somehow gets done due to people in the Dev team overextending. Goddam leeches wasting mine and my teams time doing bullshit.

F*CK...that feeling when you were working as a junior UI/UX designer for about 3 weeks in new company, you were on a project which is almost finished and delivered...

1 and half week Later (after technical issues - check my older rants)......

you have noticed one quite importat mistake in the designs, which were done by senior designers, which can lead in future to a huge Ux problems - so huge, that users will probably leave/close the app and will not purchase the product via that app... ( We can say than whole design solution was a waste of money for the client)... On that designes was working a team of 4 people, about 3 Months (and the app (prototype) had to be ready already 2 Months back)...

the deadline was pushed 2x already...

And your boss (senior designer) tell you that this is not such an issue.. But thx for your opinion.....

1 week Later by user testing 4 out of 4 people were asking about that stuff I told to my boss that is missing...

And I was ignored...

In less than 1 week Later after the testing I get fired from the company without no reason...

Or better - the reason was:

I have too little experiences for this job...
Dont know if I should laugh or cry🤦‍♀️🤣/😭

Today I had a meeting...
It was about a Team having problems with our Tool...
All participants where QA professionals...
(at the very least according to their Job title)
The invite said please come prepared!

THEY WHERE NOT ABLE TO DESCRIBE ONE ISSUE ACURRATE ENOUGH TO MAKE IT REPRODUCABLE

It's 0416... Too damn early to fix broken things. This particular team needs to fix their stuff for good, not keep having us out bandaids on their problems

tl;dr - install ‘Pop!_os’ and try it out if you haven’t yet, it’s pretty damn good!

Heavy Micro$haft user here, have tried using ubuntu a bunch of times in the past and fucking regretted it every time. Ran into issues with stupid shit like the apt cache growing exponentially until the drive was full, or something like the the system python getting borked.

To be fair, I’m 120% certain my dumb-assery is what caused the problems. I’m definitely not trying to blame the OS. But my experience was shitty, even if it was at my own hands lol.

Started playing around with Pop!_os from the system76 team. And I’m seriously in freakin’ love with this OS. It’s clean, is performant, feels way less buggy or just feels more stable somehow. I know it’s based on ubuntu, but I’ve had a great time thus far using it. I’ve got ansible, docker, aws toolkit, aws cli, sam-cli, vscode, dynamodb-local, serverless, npm, brew, and working on steam now.

Everything has been a breeze and again the system feels really fast and snappy. It feels a lot like mac on the smoothness scale, but snappy like a windows box with beefy hardware specs.

I’m still just in the testing phase on a VM, but I’m seriously thinking about blowing away my windows install for Pop!_os.

(I’ll try arch someday when I’m up for some hardcore masochism)

A good boss gives you a few clear instructions and then doesn't meddle in your work.
A great boss does that, and also spends most of their time protecting the team from corporate fuckery.

99% of all bosses, though? You can't make heads or tails of their blabber, and the only way they can handle problems is throwing their team under the bus.

My best skill is problem is:
*** problem solving ***
Really, at least in all the teams I've been working until now, I'm always surprised by myself. How fast I am in spotting the problem root and find or suggest a solution. Even on things I have almost no knowledge.

My worst skill is:
*** problem solving ***
Being so effective make me everybody's slave.
Everybody always rely on me for any kind of weird shit. If I try to "outsource" the problem, after one day it will bounce back on me and I solve it in no time.

So I've no time for anything else that solving other people's problems.
Constant interruptions and context switching.
And worst, my bosses don't understand why I don't finish my tasks. And I cannot blame my team.

Several years ago I joined the company I currently work for, as a software support person, with the intention of eventually moving toward the development team.

After a few years doing that, I gradually realised that working in the development team for our products didn't seem that appealing after all, so I went for a more technical support role (essentially debugging all the really complicated problems and reporting the bugs to the devs) which I find fascinating - trying to solve these puzzles is an interesting challenge. It can take days, sometimes weeks to get to the bottom of something really inexplicably weird.

As part of this I get to do some internal dev work on the teams projects (nothing that gets used directly by external users though) and have learned loads of things from my boss over the years (even before I joined this team).

It has its frustrating moments of course but I am definitely glad I didn't follow my original intentions of just being a developer on our main products.

Sometimes what you think you want isn't actually what's ideal for you :)

HR: good news! We're going to be moving your whole floor to a **newly renovated floor** in our main building.

Me (thinking): sounds good! It'll be all new and I'll be reintegrated with the main population, see young ppl (girls) finally.

HR: there will be no assigned seating though. Do you think you will have any problems finding a seat since your deaf?

Me: Hm.... should be fine... (Thinking: so no nobody will care if I work from home or not...yes!)

HR: Actually they said they can give you a fixed seat!

Me: wow thanks!

(Wait... Fuck... Did they actually review my low physical attendance rate so now if I become the only guy with a fixed seat on the floor, I will have to show up more instead of working remotely whenever I want (the rest of my team are in different countries)... I will literally be the center of attention...)

This is long rant/story:

My manager conducts sync-up meetings regularly. The idea is to sync up all developers on current state of work. He does’t conduct stand-ups. He doesn't have time for it. He rather discusses on individual basis if we are blocked. The rule of the sync-up meeting is NOT to discuss any blockers or problems but simply explain each other what we are doing and how we plan next.

Sometime ago, the manager brought up and explained a new way of working in the sync-up meeting. At this point, a new developer in the team was absent due to sickness.

Today, there was a sync-up meeting and the manager started to question the new member about the newly introduced way of working. He was unaware of it and the manager never communicated this important information via email or any mode of communication available.

So, the conversation goes on as follows:

"Manager": — "Why didn’t you complete your task as per the new way of working?"
"Employee": — "Well, I've no idea. Am I supposed to do? I’ve been working as usual like any other"

"Manager": — "We have a new process and you have failed to follow it, so we’re late in delivering your work"
"Employee": — "I’ve already finished my work on time. I've raised a pull-request this morning"

"Manager": — "It doesn’t matter, it is not merged to main branch and so we can’t include your work in the release"
"Employee": — "I’ve no idea about the new process"

"Manager": — "Haven’t you asked around about what happened from previous meeting"
"Employee": — "Yes, I have. I was told which tasks were handled, but nothing about a new process"

"Manager": — "Aren’t you interested to learn it?"
"Employee": — "Why won’t I be interested? I was on a sick leave and I have no clue what happened here"

"Manager": — "What’s happened is past now, let’s not focus on it"
"Employee": — <Dumbfounded>
The Employee felt ashamed in front of everyone. He did his job but it didn’t pay off.

…. After an hour … the Employee had a talk with the Manager

"Employee": — "You shouldn’t have pointed me out in front of everyone. It made me feel real bad. You should have emailed this information if its important for the team."
"Manager": — "I have no idea what you’re talking about. When did I say so? I think you’ve a bright future in the team. You should be focusing on doing better things."

Employee goes back to work. A minute later, the Manager sends a PowerPoint screenshot of the process in the group chat.

**The Process**
It's about delivering release packages based on priorities defined by client. Each release package is a set of work items or requirements. Individual developers are assigned to work items. They are expected to deliver on planned delivery timelines in order to consider a work item into a release package.

!coding

I used to be a sysadmin, which meant I was in charge of quarterly server patching. My team managed about 2500 servers, running various flavors of linux and legacy unix. The vast majority(95% or more) ran Linux(SLES). Our maintenance window was always in the overnight-- 10pm to 6am --so the stroke of 10pm would be a massive cascade of patching commands sent to hundreds of servers.

Before I was brought into the process, it made use of the automation product we were tasked by mgmt to use: Bigfix. It's a real piece of shit. Though we had 2500 or so servers, this environment was dominated by windows. All our vcenter servers ran it, and more importantly, our bigfix nodes were all windows machines. That meant that while we're trying to patch, the bigfix servers would get patched by the windows team. This would cause lots of failed and timed out patching, because the windows admins never quite understood that taking down the automation infrastructure would cause problems.

As such, I got tired of depending on a bunch of button-pushing checkbox-clickers who didn't know shit about shit, so I started writing an ssh-wrapped patching system. By the time I left for my current job, patching had been reduced to a single command to initiate each group's patching and reboots, and an easy check to see when servers come back up. So usually, the way it worked out was that I would send patching orders to 750 machines or so, and within about 5 minutes, they would all be done patching, and within another 20 minutes all the ones that required rebooting but about 5 would be done rebooting.

The "all-nighter" which happened every time was waiting for oracle servers to run timed fscks against a dozen or so large filesystems per server, because they were all on ext3/4, which eats complete shit. Then, several hours later, as they finished, I would have to call the DBAs to tell them to validate their shitty servers.

As a senior engineer/team lead. What would you do if you had an engineer on your team who is very difficult and arrogant but very good at their job?

my job went from being a programmer ==> technical support girl for the whole company D:

its kinda annoying because its mostly about amazon ec2 instances and i have to chat with the support team from amazon when something goes wrong while following the steps (that the others could have followed instead of going to directly to me to make me do it)
now i have to try and fix all the problems occuring in the servers :((

Have you ever argue with a developer who:
+ have the same level as you
+ on the same position in the company
+ in the same team
+ OLDER than you
+ thinks their code is the best

A few years back, a coworker and I argue about how to implement a feature. I proposed an approach. He proposed a different one. I immediately saw some problems and told him. But hell no, he defended his idea so strongly that I just gave up since I will leave the company soon.

2 weeks later, when the sprint was about to end, the whole team had to work overtime to fix the mess because of his terrible approach.

How many of you wear shades at work?

I started doing it after I faced some problems due to the extremely bright lights. It's such a complicated problem that no one in the management or admin team can do anything about it. 🙄

I was hired to a working team that is full of experienced people who know how to code but half the team is awfull at solving problems, and all they do is blame each other... why cant they understand we are one team and rather work on solution for 30 minutes they spent deciding who fucked up...

Around 6 years ago I started at this company. I was really excited, I read all their docs then I started coding. At every code review, I noticed something was a little off. I seemed to get lots of weird nitpicking about code styling. It was strange, I was using a linter, I read their rules but basically every review was filled with random comments. About 3 months in I noticed, "oh! there aren't actually any rules, people are debating them in my code reviews!" A few more reviews went by and then I commented, "ya I'm not doing any of this, code review isn't a place to have philosophical debates." All hell broke loose! I got a few pissed off developers, and I said, listen I don't care what the rules are, you just need to clearly fucking articulate them and if you want to introduce one, I don't care about that either just don't do it in the middle of my review. I pissed off 1 dev real bad. Me and this dev were working together, the QA person on the team stood up and said "hey! you know what I love about your code reviews?!" The other dev and myself looked at each other kind of nervously, "I love that you're both right, these are all problems!"... 1 year later (and until now) me and the other dev are still friends. Leave it to QA to properly identify the bug.

Don't forget to give the developers the opportunity to innovate. Nobody wants to sit and type out the same structures day after day. That's not why we got into this job. We like solving problems. In my current team we set aside some time every sprint to spend on individual innovation. Super useful as it gives us the chance to break out from the standard chugging of the backlog and spend some time trying to solve some of the trickier problems and bringing improvements back to the product that we discovered by messing around with stuff. If you are reading this and you are in charge of a development team, try this out for a sprint or 2.

This is definitely a total first world problem but I am so frustrated.

I am stuck in a team that embodies the Japanese proverb "The nail that sticks out gets hammered down".

The management are there because it is convenient and flexible and have no interest in managing or keeping up with tech.
The lead developers are extremely anti-social and are not approachable and the this stems down to the devs (not all but really most) - all there just to do the bare minimum and spend most of their energies in trying to avoid work or having learn something.

Unfortunately I am passionate about what I do and want to build high-quality products and this has put me at odds with the way things work.

I could fill up alot of time talking about how I was ordered to "cut" images/icons out of PDFs rather just getting them from the branding team, or how I was scolded for having set up logging, detected a problem caused by another developer and fixed it before it cost a big client a massive amount of money... But really the point is that I have never worked somewhere with such an awful attitude to enthusiasm and quite frankly it boggles my mind trying to understand how they rationalise these things but the answer is always laziness.

Obviously there are worse problems in the world than working in a job where you are encouraged to do nothing... But it actually really depresses me and causes anxiety that I am working with people who don't care about testing or monitoring or learning new things or even collaboration.

...sigh...

Hopefully the job market will start opening again soon

Not really a rant but more of a fact kinda thing. Noticed a post earlier about someone ranting about why they code figured I'd do the same...

I code not because I wanted to for say but because my after my uncle's death I needed something that I could feel in complete control of. Coding gave me that ability to control the computer however I want and tell it to do whatever however. At the same time it taught me so much more about myself and the people around me in the process. Today I don't code because I need to control something m today I do it because I can't live with out. It forces me to think critically of everything and everyone. It forces me to learn something new everyday and every night. It requires me to solve complex problems with limited solutions. It allows me to create solutions when everything else has failed and it gives me a drive to complete things. It's the reason I live technology and it's the reason I have the job I do. It's the reason my boss loves my work and it's the reason other people on my team envy me. Code transformed my life into what it is today. And it will forever be my greatest peice of education.

Does anyone work on a team with multiple stacks?

For example we have batch jobs in Java but also have a JS front-end and APIs.

How do you divide the developers and the work across these projects?

Currently everyone does everything but I feel like this is inefficient and hard to develop expertise. And different people or even the same person will make the same mistakes over and over again because they don't know how to do X or they forget or overlook some quirk. When I switched Beck to JS took me like a week to get a Promises nailed down again. And this morning someone else had a production bug and couldn't figure it out. But when I looked at the code I could pretty much see where an issue could be (uncaught exception in a promise)

Also the testing frameworks are very different and there's a lot of infrastructure technical debt, things that really should've been done a long time or fixed but no one had the time or expertise to do it or notice it (until it causes a production issue and then everyone is like WTF is happening??!!!!).

I'm not the manager but I always feel that the team needs to be split along the language lines and specific people need to own these projects to review and code changes for all these common newbie errors. And also developer enough expertise to foresee problems before it becomes a production issue.

I work in a large organization that previously didn't have it's own development team. Therefore various business areas have built their own solutions to solve problems which mostly involve Access and Excel.

Many of these applications still exist and we are expected to resolve any issues with them and update them when necessary performing this support role while still expected to meet our (very tight) development timelines.

I can't tell you how much of a pain in the tits it is to be trying to power through a priority development only to be interrupted with an urgent instruction to fix a 17 year old Access database that's running slow.

Of course it's pissing running slow, it's 17 years old, has nearly a million records and you have multiple users accessing it across the country!! I think it's time to peacefully let it die.

So we've had a new guy on our team for over 6 months now... Been training him up doing shadowing.... Training courses... Study time... The works...

He didn't have the specific skills for our team but had 2 degrees, lectured at uni... Seems VERY smart......

Yet he still has barely grasped the basics..... When experienced people talk about challenges they've had he tries to suggest what they do... Constantly raising 'problems' with ways of working but offers no solutions and never collaborates on how we can fix it......

He avoids doing practical learning and thinks he can learn the job from reading docs... .. Sigh....

Gone almost as far as doing daily check ups on what he's actually doing to make sure he's progressing..... Tough one to crack!

I remember when this person I worked for suggested all the engineers get on a day long call with the product owner pointing out problems and the engineers fixing them on the call. It was absolute chaos when i told my team 😂

Has anyone else ever encountered such??

MOBBING DICTIONARY - 2 -

Sentence
(behind the back)
- he/she has no time, don't tell him/her these problems, don't speak with him/her, just speak with me

(explicitly)
- you have no time do this!. Let me/somebody else do it.

Purpose
- cutting the target out from the rest of the team. Redirect all communication in order to shield the target.

Result
He/she will loose the general vision. He/she will not understand anymore what the problems are. He/she will loose relevance and will not be able to manage his/her own time anymore.

He/she is probably working a lot, and doing a lot of effort. He/she will probably know how to use the time, and he/she needs the team to help with task no take the task out of him/her.

He/she will slowly burn out, specially if he/she discover that such things are happening behind his/her back.
The situation will add psychological problems to technical problems. He/she will be crushed to death.

At work everybody uses Windows 10. We recently switched from Vagrant to Docker. It's bad enough I have to use Windows, it's even worse to use Docker for Windows. If God forbid, you're ever in this situation and have to choose, pick Vagrant. It's way better than whatever Docker is doing... So upon installing version 2.2.0.0 of Docker for Windows I found myself in the situation where my volumes would randomly unmount themselves and I was going crazy as to why my assets were not loading. I tried 'docker-compose restart' or 'down' and 'up -d', I went into Portainer to check and manually start containers and at some point it works again but it doesn't last long before it breaks. I checked my yml config and asked my colleagues to take a look. They also experience different problems but not like mine. There is nothing wrong with the configuration. I went to check their github page and I saw there were a lot of issues opened on the same subject, I also opened one. Its over a week and I found no solution to this problem. I tried installing an older version but it still didn't work. Also I think it might've bricked my computer as today when I turned on my PC I got greeted by a BSOD right at system start up... I tried startup repair, boot into safe mode, system restore, reset PC, nothing works anymore it just doesn't boots into windows... I had to use a live USB with Linux Mint to grab my work files. I was thinking that my SSD might have reached its EoL as it is kinda old but I didn't find any corrupt files, everything is still there. I can't help but point my finger at Docker since I did nothing with this machine except tinkering with Docker and trying to make it work as it should... When we used Vagrant it also had its problems but none were of this magnitude... And I can't really go back to Vagrant unless my team also does so...

F**king hate Windows for its insanely confusing proxy setup required for software development...

> Setup proxy in Windows network settings
> Then, setup HTTP_PROXY & HTTPS_PROXY environment variable at the system/user level.
> Followed by separate proxy settings for java, maven, docker, git, npm, bower, jspm, eclipse, VS Code, every damn IDE/Editor which downloads plugins...
> On top of everything, find out the domains which does not need to go through proxy and add them to NO_PROXY.. at each level..
> It does not end here. Sometimes, I need to setup proxy for SSH connections... like, if I have to use git with SSH and not HTTP/S... Uhhh....

More than half of the problems me and my dev team face is related to setting the right proxy. Why can't it be like, set in one place and everything picks up from there, like in any linux machine or for God's sake, a Mac ?

Worst of all is, my org uses a configuration script, which resolves into a list of proxy servers, from which one of them will be used. So, I need to download that script, find out which is the right proxy server and then, use it in all the aforesaid places... WTH ?????

Is this a common workplace problem for all developers ??? Will this be solved by Windows Subsystem for Linux ???

I am surrounded by incompetent fucking idiots, from the team lead that does a half arsed job at coding and then wonders why nothing further down the chain works to whole component teams that seem to be lagging so far behind they don't even know what the current code base looks like.

And who's in the middle of it all running around fixing all the problems these fucktards create, why yes it's me.

I would leave to let it implode and see what they'd do but I already know, they'd leave it till I got back so I could fix it all for them.

Feel like going around with a rolled up news paper and whacking each of them on the back of the head while screaming "no, bad code monkey, bad, fix your own bugs"

I hate being the go to fix it guy sometimes.

I don't know if this is exactly a rant. But - I am sure somewhere out there has run into this situation before.

I've been a developer (professionally) for a 3 years. And in that time I've stayed with that same company.

Over that time its become incredibly apparent that my boss (senior developer) isn't exactly keen on new technologies, source control (I had to push hard for this. And even then he doesn't use it properly), or any kind of project management. It's only he and I.

I've started interviewing other places and while I have no problems answering their technical questions. I'm worried my lack of experience in a team is becoming a problem.

We don't work on projects together. We don't do code reviews. He does not ask my opinion on anything. We are basically two separate teams. I want to improve as a developer. I love the rest of the company and I enjoy what I'm working on. I just feel I'm hindering my growth as a developer.

Anyone have any advice? I know I can find a project to contribute to on github or something. But honestly that's intimidating to me for some reason. I am self taught. And don't have any experience in working with teams.

Hi guys!

I never thought that this day will come, be here is my first rant with a big dose of frustration.

So, I'm working on the API team of one of ower products and a coworker that works on the webapp has a lot of problems (don't want to be mean, but he has problems like 'i can't catch a 404 http status, please send a 200 with a message' ) and he always go and wines about the API and that he can't do his job because the API is faulty...

But it is not the case, every functionality of the API is well tested and it works as it should.

So, tonight I was the only one left from my team and the project manager comes and
starts asking me about why I am returning http status codes with all my responses, how the login works and other stuff like that...

Just wasted more than an hour to prove that all the code that I wrote works as expected...

Best:
Got a role change to automation engineer, which is sort of a 'just fix problems' position, like with tooling, get rid of manual work, remove as many spreadsheet as we can.
I started looking into rust.

Worst:
People think we depend heavily in javascript because our products are extensions, our golden product is an extension, so a few members of my team insist in depending in our core team and use their javascript stuff, even for string parsing, even if we do have a python package that does rhe same thing that is officially maintained too.
I refuse.

The good again:
My boss let's me refuse, I am not forced into javascript, they let me use whatever I want as long as it is reasonable.

So the company decided to go agile. I am now a scrum master. And we have the local product owners and all. They made us do daily stand-ups.

I don't know what is a scrum master. Nobody knows what the hell is a stand-up. It seems to be an akward 30 minutes every day, when local product owner asks questions and demands status reports.

I did some googling and it seems that the scrum master is supposed to just support the team and solve problems. In our version the scrum master finds out the system architecture and requirements, fills the backlog, does the system design and reports to the project manager(s). Also reports to the clients about the general project status in an executive meetings. I also do the sprint planning, in which we fit the vague features that we are told into time tables with ready told dates.

Oh yeah, the team is just 2 guys. One of them is me. And the other guy relies completely on me to daily tell what to do, review the work and also answer all the project and company level questions that pop into his mind. He gets angry if he doesn't receive ready-thought solutions to all problems, since "you're the boss and it's your job to tell us what to do".

This is going to be a great year.

Our PM just send a mail to our team, that after testing the latest extension we made to the project, he could not find a single issue or bug (usually there are some minor UI problems or some edge case bugs we did not think about or know existed)
and what a incredibly great job we did, and he also forwarded the mail to all our managers up the hierarchy right under the CEO.
The appreciation is a nice change to the self-hatred I feel while coding

one week back from my holidays and so far:
- 3 server outages
- 1 developer will be fired
- 2 new employees (company has around 35 employees)
- 2 employees leaving
- outsourced designs, the designer surely didn't read the feature research doc nor followed style sheet
- a small, easy feature has not yet been finished by the rest of the team
- new devOps engineer wants to rewrite our entire tech stack

But at least the CEO was doing it's best and ran away from the problems & ran 150km

I think a question should be added to tech interviews and maybe the most important one.

How many times in a week do you use Google/internet to look for a solution to/information about ur problems.

Tests for a developers ability to learn or try to figure things out themselves..

Feels like a lot of people on my team just do it the way it's always been done ,. Which is ahitty.. and if they don't know something,.. they need to ask someone instead of trying to figure it out themselves...

Reminds me of that fish adage?

They never learn how to fish....

So I'm working on this prototype of indie game with two friends. Since we are only 3, I can't just stick to coding only... Problem is, I'm the only one realising that and I've ended up doing all the jobs that are missing... Texturing, a bit of modeling, organizing the whole team, shaders, animating and so on... And the two others just stick to their thing and are confident in the fact that I'll be able to handle all the problems. It pisses me off.
But I need the project to have some base experience, and alone, I would probably melt down under the stress. But every time a problem show up I'm basically alone, and my level of stress skyrocket... Not sure if I have the shoulders to finish it, but I have to. In fact I'm not even to the point of ranting anymore I'm just depressed >.>... At least when I'm working on the code and not the rest, I'm really enjoying myself.

Not sure if I should do something about it ._.

[day 1] my team lead insisted that we work "together" on a story. told me to code my approach while he code his then evaluate both once done.
[day 3] we presented our codes to the team but in the end his code got deployed.
[day 4- 7]we got a lot of defects. we did a lot of fixing
[day 8] undeployed his code then deployed mine.
all problems got solved.

Long time no see devRant. This rant is dedicated to an MQTT implementation we use. Mosquitto, mqtt.js - FUCK YOU.

I spent the last fucking 30+ hours trying to find why the bloody fuck the stupid server / client won't connect to the shitty mqtt broker. From changing all possible config, enabling & disabling specific code nothing abso-fucking-lutely works.

But then it will randomly decide to connect to the fucking broker, not causing any issues at all. And each fucking day when I wake up again and think to myself: oh today I can actually leave when it is still somewhat bright outside - NOPE. Because guess what? The fucking shitty abomination doesn't work anymore.

I just love these types of problems that are almost impossible to debug because the only logs you get is: "SERVER disconnected". It's impossible to get a proper reason out of this shit show, it's just turned into randomly guessing what the error could be (and especially where it could be).

And each time I got it to work, tested it and let the testing team know that they can start testing it will just stab me in the back and be like "fuck you, I'm not working any more". Luckily it's not like the deadline is next week... otherwise work is great, trust me.

We use at our company one of the largest Python ORM and dont code ourselfs on it, event tough I can code. Its some special contract which our General Manager made, before we as Devs where in the Project and everything is provided from the external Company as Service. The Servers are in our own Datacenter, but we dont have access.

We have our Consultants (Project Manager) as payd hires and they got their own Devs.

Im in lead of Code Reviews and Interfaces. Also Im in the "Run" Team, which observes, debuggs and keeps the System alive as 3rd-Level (Application Managers).

What Im trying to achieve is going away from legacy .csv/sftp connections to RestAPI and on large Datasets GraphQL. Before I was on the Project, they build really crappy Interfaces.

Before I joined the Project in my Company, I was a Dev for a couple of Finance Applications and Webservices, where I also did coding on Business critical Applications with high demand Scaling.

So forth, I was moved by my Boss over to the Project because it wasn't doing so well and they needed our own Devs on it.

Alot of Issues/Mistakes I identified in the Software:
- Lots of Code Bugs
- Missing Process Logic
- No Lifecycle
- Very fast growing Database
- A lot of Bad Practices

Since my switch I fixed alot of bugs, was the man of the hour for fixing major Incidents and so on so forth. A lot of improvements have been made. Also the Team Spirit of 15+ People inside the Project became better, because they could consult me for solutions/problems.

But damn I hate our Consultants. We pay them and I need to sketch the concepts, they are to dumb for it. They dont understand Rest or APIs in general, I need to teach them alot about Best Practices and how to Code an API. Then they question everything and bring out a crooked flawed prototype back to me.

WE F* PAY THEM FOR BULLCRAP! THEY DONT EVEN WRITE DOCUMENTATION, THEY ARE SO LAZY!

I even had a Meeting with the main Consultant about Performance Problems and how we should approach it from a technical side and Process side. The Software is Core Business relevant and its running over 3 Years. He just argumented around the Problem and didnt provide solutions.

I confronted our General Manager a couple of times with this, but since 3 Years its going on and on.

Im happy with my Team and Boss, they have my back and I love my Job, but dealing with these Nutjobs of Consultants is draining my nerves/energy.

Im really am at my wits end how to deal with this anymore? Been pulling trough since 1 year. I wanna stay at my company because everything else besides the Nutjob Consultants is great.

I told my Boss about it a couple of times and she agrees with me, but the General Manager doesnt let go of these Consultants.

Even when they fuck up hard and crash production, they fucking Bill us... It's their fault :(

This story just left me speechless in any way and i want to share it. tl;dr at the end.
Im studying computer science in germany and in the first of the small classes i noticed... no, i was disturbed by a guy who would just say that the thing we're learning atm were so easy and the teacher shouldn't even bother to explain it to the class. I don't understand why you would spoile a class that hard... I'm here to learn and listen to the teacher, not to you little asshole. (We were doing basic stuff like binary system etc. but still, let us learn)
So he became unpopular pretty fast.
Fast forward, a few weeks of studying later there was a coding competition where you had to solve different algorithmic problems in a team as fast as possible.
I came there, without a team because my friends aren't interested but I enjoy such tournaments. This guy and me were the only ones without a team and we had to work together.
After him being a total dick for hours i had to watch him code a simple for-loop, that iterates through a sorted array. Nothing special, at this point anyone could do that task in our class so it shouldn't be a problem for him.

He made a simple for-loop and it worked fine, but we figured we had to iterate through the array the other way around.
'Alright', I think. 'Just let the index decr..' 'Pssshhh', he interrupted me and said he knows exactly how to do this.
I was quite impressed when he started to type in 'public int backsort..' in a new line. He tried to resort the array backwards with a quicksort that he then struggled to implement. (Of course we had to implement a quick runtime and we needed that quicksort badly)
I was kind of annoyed but impressed at the same time. I mumbled 'Java has an internal sorting algorithm already' just to amuse myself.
He then used that implementation.
After a few minutes of my pleasure and multiple tests without hitting the requested runtime, i tried to explain to him why we wouldn't need to sort that array backwards and he just couldn't believe it.
I hope that he stays more humble after that..
Also we became last place but thats ok :)

tl;dr: Guy spoiles whole class, brags with his untouchable knowledge (when we do things like binary system). In a competition has to iterate through a sorted array backwards - tries to implement a sorting algorithm to sort it backwards first. I tell him, we could use a already implemented java method. Then tell him we could simply iterate through decreasing the index. Mind-Blown

We are researching enhancing our current alerting system (we use Splunk) to be 'smarter' about who is emailed/texted/whatever when there are problems in our applications.

Currently, if there are over 50 errors logged within a 15 minute period, a email/phone/text blast to nearly 100 individuals ranging from developers, network admins, DBAs, and vice presidents.

Our plan is to group errors by team and let each team manage their own applications. Alert on 1 error, 5, 500...we don't care, let the team work out the particulars.

The trick was interfacing with Splunk's API (that's a long rant by itself)

In about a day or so I was able to use Splunk's WebHook feature to notify a WebAPI service I threw together to send myself an email with details about the underlying data (simulating the kind of alert we would send to the team)

I thought ...cool... it worked. Show it off to the team, most thought it was a good start, except one:

Dev: "The errors are not grouped by team."
Me: "No, I threw the webapi service together to demonstrate how we can extract the splunk bits to get access to the teams"
Dev: "Well...this won't work at all."
Me: "Um..what?"
Dev: "The specification c l e a r l y states the email will be team based. This email was only sent to you and has all the teams and their applications"
Me: "Um...uh...the service can, if we want to go using a service route. Grouping by team name is easy using a LINQ query. I just through this service together yesterday."
Dev: "I don't know. Sounds like I need to schedule a meeting to discuss what you are proposing. I don't think emailing all that to everyone is a good idea."

WTF! Did you not listen to what I said?!!!

Oh well..the dev's proposal is to use splunk's email notification and custom Exchange rules with callbacks into splunk that resend...oh good lord ...a fracking rube goldberg of a config nightmare ...

I suspect we'll go the service route once I finish the service before the meeting.

My org (of which i'm basically CTO) has this administrative tool that a team uses to combat spam and scams, which is quite the problem for us.. the tool was written like 9 years ago, by my predecessor, very quick & dirty and unaesthetic and without input from those who would use it as far as interface or UX... it got modded a little a few years later by a kind of amateur coder who was at the time on the spam control team, and now there's this new maybe slightly less amateur coder guy on the team who has written this amateur tool that scrapes data off our site and massages it and stores it on his own server and then provides a better interface, or so they say.... this is all because for a couple of years people didnt want to "bother me" with a request to improve our internal tool, they thought I was "too busy" doing other things... so instead this outsider has built this stupid thing that lives on his own personal server and so now we have these problems to do with performance, security, privacy for user info, etc etc... someone please shoot me....

I can't convince my team that a good database model promotes a good API design and a good UI/UX experience.

Instead, I have to work with a ridiculous table setup.

Imagine, if you will, a table (table B) that references another table (table A) via a foreign key. The FK is a string in both tables. And table A only has one column, which is labeled as "name".

The schema i have to look at it kind of like this:

Table parent
Name varchar(10) primary key

Table child
Name varchar (10),
parent_name varchar(10),
Foreign key (parent_name) references parent (name)

Sorry if the syntax is wrong, a little frustrated having to look at it...

Am I crazy to want to change this table design? Am I missing something? I feel like I'm taking crazy pills, because this is just scratching the surface of the problems I have to deal with.

From perfectly working scrum team to... Don't know what it is now...
Long story short - our SM left company and our team have ongoing "reorganization", our tester leaving at the end of this month, probably we will be out of tester for next month...

I don't mean reorganization, it's normal thing, but... It looks like it's slowly collapsing under bad head decisions (one of them is the reason why our tester is leaving)... Multiple "side" projects / tasks for ppl in team and problems with delivering sprint tasks on time because of it, context switching etc.

I fucking like this project, it gives me much opportunities to learn new things and design new features - it's up to us how we will implement it. Client is satisfied with our work and we worked for their trust for long time. But if things will be going same way as now, we will probably lose it.

How do you think, is it worth to try stay with this project? Or should I update CV just in case?

Stupid fucking client force us to deploy our nodejs codebase on windows server fucking 2016 because that the only version their security team has audited, and in their word: "open source oses like linux are more vulnerable because anyone can contribute????"
I fucking hate digital transformation projects with a passion because of stupid fucking client with their stupid fucking red tape problems

!dev

So last week I sort of unfriended a friend from college that i guess is more like a "chat buddy". After college we've never hung out. Part of it maybe because I'm deaf so there's a communication barrier, I lost most college "friends" after that... but then are they really friends?

The reason was though, he talks to me every night (usually 1-2 hrs online chatting on and off), we do have some laughs but recently he's been complaining about his year end bonus, how it's not enough. And also about how he deserves to match with better girls than the ones he's getting now. He's on those online dating sites and went out with a few. And he's been on a few dates but with my looks and health issues, online dating is pretty much useless. He was the only reason I even tried

He makes twice as much as me already but "he comes from a poor background" so he needs more. Honestly I make enough, but the job isn''t great (not really learning anything new, lot's of things that could be better... obviously) but it's very flexible and near where I now live... should I even choose to go into the office (I sort of work remotely from the rest of the team).

I probably haven't spoken too him for a week now and I don't feel problems, frees up more time but wondering if I sort of withdrawing/unanchored from reality and ignoring problems, settling for less.

Nowadays it really feels like, when I'm in my own apartment or just alone, I'm in my own world, I can do whatever I want... thought most of the time is spent with my devices... so I'm not sure though if that's good or not... Am I a Bachelor or a hermit?

Now i've been rambling for the last 1hr and have no idea what I wanted to say.... guess I just needed to rant...

Ah I remember now sorta... Is this relationship worth keeping or should I find new friends that are more similar to me?

Maybe I've been moving in the wrong direction in life... I shouldn't do things the normal way... Think about what's actually important to me/people like me... not what what everyone normally does...

The irony that goes along with smooth migrations on production is this.

If the migration is smooth, no one knows how much effort, careful planning and execution went into the whole process. They just get a for your information mail that everything went smooth. No one, not involved in the process would know the scale of things; or what could've happened if the transition/migration was screwed up.

On the other hand if there are problems during the process and the tech team fights back, they indeed are the heroes. No one notices the silent crusaders.

No wonder then that all superheroes just smash stuff. Its only then that people notice that they worked so hard. Silent superheroes remain dead.

I’ve had meetings specifically for team A’s problems. Team B gets invited to assist. Within ten minutes the meeting was all about team B and none of team A’s problems were solved. “Team B” is notorious for hijacking meetings. I’m not a psychologist. I don’t feel qualified to speculate about WHY they do this...

One of the most inefficient practices I've seen done in companies is the company housing 50+ devs having to hire an expensive consultant who is only available on a limited time to figure out mysterious or in-depth problems with the company's main application (for example, JavaScript problems).

Then the whole dev team sits on his shoulders and production can't run smoothly until he fixes things. Even worse, him having the so-called qualifications, being the 'expert', but when asked an in-depth JavaScript question, they don't know the answer.
When I suggest to figure out things in-depth so problems like these can be prevented in the future, I'm met with: "Nah bro, we'll just apply quick fix #2" just because I carry the title 'Junior Developer'. Makes me want to hit my head on the wall on how stupid these people are.

This could all be solved if the dev team would be competent in the first place, knows how to read documentation and isn't lazy, most importantly. I hate teams like that.
Grab, the damn, documentation, read W3C, read MDN, get educated, and stop using band-aid solutions! Gah.
Toxic companies like these are what's wrong with some places in the development world.

I'm a proponent of knowledge.
Fellas, know your stuff.

I reported to our team leader (who is not a developer) that me and my colleague has been having problems with our senior developer whose codes are unmaintainable and messy. I told the team lead that I am losing my trust towards my senior developer and that his codes are messy and not following the coding standards. I was nervous at first because this certain team leader is tight with the senior dev. But still, I expected the team lead to be objective.

I was surprised because the team lead asked me if 'I was perfect' and then the team lead continued to shift the conversation towards me. Team lead then started to compare me with the senior dev which is unfair because I've only been working for 2 years whereas the senior developer has been doing this for 6+ years. Team lead said that I was arrogant. Team lead sent our convo to the other teammates and friends. Team lead told me that I am such a baby.

Fast forward, the senior dev talked to me. Told me that he was busy so he didn't get to improve his codes. Which I dont buy because I often see his discord status as playing during work hours. Told me that it wasnt him. Which I dont know if i should believe since he always lies. Told me that his knowledge is outdated. Told me that maybe because I came from a good university and he did not. He apologized and told me he will improve. Sounds good right?

It's a lie. Because then my friend gave me a recording of his voice ranting about me after our talk. In that recording, he said that I have nothing to prove so I dont get a say. He said that he doesnt care about me. He said that I am cocky. Which I dont understand. I only commented abt his work, why is he attacking me personally? Plus, if someone new like me already already noticed the flaws in his work, what does that say about his skill?

My teammates then asked me to just take the fall lol take note that these teammates were also complaining about this senior dev. they asked me to just give them what they wanted to hear. That I am the one who's wrong and the bosses are right. I said I wanted to defend myself but they hated me for that. They told me to think about what would happen to them. They told me I am selfish. Is it selfish for wanting to defend myself?

I defended myself. I told the senior dev that my intentions are for the right reason. He told me he understands. Later that day, a friend told me he talked behind my back again.

Senior dev told me that the team leader cried because of the words I said. Which i found confusing because it was my own feeling, my own opinion that i am losing trust with this certain senior dev so why would the team lead be so affected by that? Also, i showed our convo to the most objective people i know and they said that i didnt say anything that is offensive nor arrogant I have no control as to how people would react to the words I say. It's beyond me.

I feel so helpless. I told those things to the team lead because I think a team should be open to each other but I was blown out of proportion instead. My friend told me that the team lead and the senior dev are still talking behind my back.

If they do this every time someone tries to speak up, will they ever grow?

at one point in time, i had to work with a really junior backend team, they used javascript and neo4j as the database for an in-house developed community forum because "graph databases made sense" in the eyes of their tech lead

turns out that the team struggled quite a bit with it, and had some "unexpected complexity" problems when i asked them to add filters and sorting on the post endpoints

in the end, the "solution" they gave me was an endpoint that spewed ALL the posts so i could sort it in the front end

had they kept the same relational database they were using for the rest of the whole project, i'm quite sure it wouldn't take much to implement that (and their architecture was really performatic)

as a side project i rebuilt the whole forum in a weekend, but using postgresql as database, and it worked nicely, i even added some unit tests just for fun

gave myself a really big slap in the face after that, though

Is it good or bad that the rest of my team is working on the large (shoddilly built) apps but I'm on the side building analytics, reporting, and other tools? (basically telling people why there are so many problems with their app).

How do you deal with a boss that is not very intelligent, but fights you, your team, executive management and project stakeholders on critical system design decisions?

Everyone else is worn out, the project is long overdue and I'm running out of energy, myself. Do I just do what everyone else does and let him have his way and prepare myself to deal with the imminent problems ahead, or do I keep fighting for a well designed system that customers will enjoy using?

I can now leave freely without any regrets!
The slight misgivings I had about leaving this place over the toys they provide, is now gone because I re-realized that while this place adopts new tech, it doesn't adapt to it. So they have shiny tools but the people and processes won't change.
It seems to me that due to pressure to deliver, there is little thought/analysis behind any tech change.

They don't plan to change their wretched delivery pipelines. Everything will be same but on git. So no velocity gains, and same bureaucratic review request process. Such a waste. This attitude applies to their other tools too. They are using a unit test library to write tests that don't use mock. They are using modern languages but without modern idioms. It's like writing C code in C++. And of course theoretically we are agile but actually we're just a waterfall team with managers on our ass everyday and tighter release schedules.

Reminds me of @boombodies recent posts and discussion about business spaghetti reflecting in code.

There are possibly multiple reasons for these problems but I think a large part of it is a lack of empathy/mutual respect. Everyone's too insecure, noone cares for anyone but themselves and people just try to outwit each other.

How do I help my colleague in fighting harrassment?
This is the story of a helpless employee facing everyday harassment. Im trying to help. Seeking for your thoughts

Backstory fast forwarded: My company acquired another company. So we handle all their projects and clients now, but its a completely new domain. So we needed new people. Hired 4 employees + 1 team lead to start with. But the project process got delayed and they were free for a month. So i took 2 of them in my project and gave them some small tasks to help us over. They loved working with my team and were learning new stuff apart from what they usually did. And we were also happy of their contribution. We became good friends. All of this was in March 2020 before covid-19 was taken seriously.

About my company: I love this company. I have been in this company for more than 4 years now. People are really nice. Parties and fun events. Lot of smart and ambitious people. So company and people are awesome.

Coming back to the story. Lets call the team the 4 and team lead T. The 4 were happy that someone like T was in their team. This T had all the best knowledge about stuff and life was going to be awesome for the 4. Or was it?

Story starts: So I talk to one of these 4 on daily basis. Lets call this friend F. F is a real gentle person. Intelligent and dedicated to work. F is awesome to work with. And always enjoyed working. F is a team player and very very soft person. F is fking workoholic. So few days after project starts, F tells me work was not going well. F is getting real frustrated at work and not able to deal with it or find solution.

What happened:
This person T, who was supposed to help these 4, is real piece of shit. He is impatient, arrogant and MFing dick head. Aaaarggggg.
All the good qualities of a leader like supporting the team, boosting confidence, guiding team when they make mistakes, teaching them, were all missing from this person. T was a machine with no emotion and only clock working jerk. I have no idea how T cleared interview process, because one of the interview round is also about cultural fit into company. I know this because i take interviews for other domains. We have rejected lot of such well qualified but arrogant candidates.

So whats the problem now: this team of 4 are learning new tools and taking over the clients requests from old company. Most of the stuff is new for them. So in tat case people need lot of time to understand and figure out shit. people make mistakes while learning and you know have to deal with it. Person T abuses these 4 when something goes wrong. That's one.

Second, the T definitely knows more than these 4. So if these guys dont understand certain stuff they ask T. But T does not help them learn. T will either say busy or run away by saying thats simple and ull know when time comes. REALLY MF???

Third, T does not talk nice. T is rude and does not listen to team members. For eg, If F says some task cannot be done for some reason T will say, "y cant u do it? U r capable of doing it. Tats y u r in this job". And then point number one and two happens. Never responds to emails and messages. But if someone else does the same will not tolerate that and abuses them. List goes on.

So y not escalate and deal with that T:
This person F and other 3 are still under probation and they think complaint or escalation will back fire. These people do not want to lose job in between all this pandemic shit. They are scared.

So this was happening for a while. And i was giving lot of tips on how to handle certain situations. And how one should communicate these.

But being a gentle, soft and workoholic person, F focussed on work and assumed things will get in place as time goes by.

Today, F could not meet a requirement. So T told some shit which got F all sad. and F called up me late night and started crying explaining what happened. I felt real bad. I asked F to file harrassment case. F refused saying it was F's mistake on not completing requirement. WHO THE FK CARES. PEOPLE CANNOT TALK SHIT. I told ill file harrassment case against T. (We have a policy where others can also file if person is not courageous enough). But F did not allow me.

Then after calming down, I told F that telling the problems to me wont solve them. You have to talk to T directly and tell him on face not to talk like this. Or tell the manager about whats happening. Or tell the the HR about this. F said tat cant be done. I was like Y THE FK NOT.

Because the other 3 are not ready to talk about this to anyone as they fear they'll lose job. So if F talks and people question other 3 they might bail out. WAT THE HOLY SPIRIT.

so after lot of convincing F is still not going to
Talk to anyone about this.

So i have decided ill write an anonymous email to HR, the manager and other senior people in the organisation about whats happening.

I really dont know how itll go. Ill keep updating you guys. Feel free to share ur thoughts.

My first dev job :

Do a front-end in Joomla!. As an internship. Without being paid.
(In France, if you are here for >2 months, they can pay you, or not.)

At least, now I know why Joomla is a no-no when you want to do custom things. Heard that the team working on back-end had problems of PHP, like the PHP appearing and the one Joomla uses "is not the same" or something like this.

And now you know if you didn't. No problem.

One responsibility of our team is general code QA for the entire dev department, DevMgr walks in our area yesterday…
DevMgr: “Has anyone reviewed the new WPF threaded model execution code?”
- everyone on the team responds “no”
DevMgr: “Can we get a review on that code ASAP? If it works as well as the developer said, it’s going to solve the lock up problems users are experiencing and automatic logging of errors.”
DevA: “Well, no amount of code is going to stop users from performing bad searches locking up the user-interface. That code is just a band-aid around the real problem. If the developers would write unit tests first …”
- rant about 5 minutes on unit testing that had nothing to do with why the DevMgr was here
DevB: “Yea, the code probably isn’t written to handle threads correctly. All the threading they’ve done so far is –bleep-”
DevMgr: “Oh, I wasn’t aware of that. Get me the results of the code review and if they don’t have unit tests, delete it from source control and let the developer know it’s not up to our standards.”
OMFG!! You have not even seen the code!
OK, DevA ..what the –bleep- does unit testing have anything to do with the user interface! You know the DevMgr is too dim to understand the separation of concerns. Shut your pompous ‘know-it-all’ mouth.
DevB…what the –bleep- have ever done in WPF? You manage the source control and haven’t written any C# in two years and never, ever written code for any significant project. Take that “handle threads correctly” and shove it up your –bleep-. Pompous –bleep-hole. Go back and watch youtube and read your twitter while the grown-ups get the work done.

Idk but i think i have the inability to ask a question on stackoverflow. Whenever i come across a specific problem my first instinct isn't to ask stack. It's to research, research and research. Then i go ahead to ask to those iknowsomuch pricks.
Do i enjoy it? No, i do it because i fucking need to.
So, stop shoving the fucking rules or policies or whatever the fuck it is on my face and answer the damn question if you know it. If not, fuck off. I hate it when they mark it as duplicate. Like are you actually serious. I've gone through the whole fucking internet including stack, searched the damn problem in different keywords, tried all the solutions for the related questions and problems and that's what you come up with. Label it as a duplicate or not descriptive enough. Oh just seriously fuck off with your "oh i have some admin capabilities let me use it on random shit". These are the people where they have no authority on anyone or led anyone or any team in their shitty lives yet act like a dickhead when someone in need of help comes to them. Oh you piece of shit, just fuck off. You miserable cunt.

I really miss having a team. Don't get me wrong, right now I do what I love and I got into a position where I can actually do Quality Assurance instead of just testing and I enjoy being able to actually change things instead of just repeating what problems there are and acting surprised when the same processes produce the same bugs over and over again but I really hope that we'll interview anything else than mouthbreathers soon.

I'm aware of the fact that QA isn't sexy and that few people who could become "Software ninja Rockstars" choose to go into it but can it be that hard to find at least two or three people who can write and read code at least on a junior level and understand how web protocols work? I get the feeling my entire branch is nothing but shit talkers clicking around blindly on pages.

I just want to exchange ideas again, come up with innovative tools, tweaking processes, learning from and teaching each other while we watch the entire operation get more and more efficient.

I was having some trouble accelerating the delivery of a new feature and so my team leader joined me for some pair programming (awesome!). Five minutes later I was selecting some, text while explaining some problems, and he stops me.

Team leader: you know, you can select all that text by double clicking it;
Me: ok (continuing to explain)
Team leader: you have to be faster with that;
Me: That's not the point right now;

Why do people focus so much on these little things?! I really like pair programming, or just pairing to think about a problem, but this kind of things really get under my skin...

(Silver lining: Cool team leader that didn't snap after I told him to focus 😅)

One of our team mates is based out of the US office. We are physically distant, but after our manager's departure, we lost touch because our scope of work was different.

Me and two other team members work closely with each other from India and dude is alone, working out of the US.

Super smart, very polite, and a fun person to work and be with. Even when our interaction was less, I learnt so much from him.

Since, I am facing some challenges, I decide to use it as an excuse to connect with him for a coffee and also seek his guidance because he is senior to me.

Some things he mentioned,

1. Our new line manager asks him to do things on spot with no heads up. He has to drop everything and complete the ask.

2. Often times, poor guy, is asked to join meetings on immediate basis. Even while he is having his lunch.

3. He never got support from our new manager. Infact, based on the conversation, I realised that the manager supports me more.

4. He is facing same, if not more, issues with tech. And he didn't have any guidance on how to handle the issue.

5. A lot of times he is facing process and system problems which he isn't able to solve because the org culture is that of working in Silos. And he doesn't get any support from manager.

6. Tech has clearly pushed him back when he asked for help and other teams never respond to him.

My man was still smiling bright and was looking things from a positive lens that all of this is interesting and adds to the learning experience which will be valued when we decide to move on from this job.

These are the people who inspire me. Smiling in the time of adversity.

Even when he had his own challenges, he was ready to guide me and hear my frustrations. I offered him help and will make sure to stay connected so he doesn't feel left out and alone in the team only because we don't work together in physical space.

One thing I have learned over time is, while I am facing problems, someone out there is facing more and difficult problems then me. I always tend to blow up my problems out of proportion then what they actually are.

I am the dumbest person that I know and mark my words, I'll die because of my empathy. I wish I could help my team mate in any possible way.

CircleCI:
- Ensuring work has meaning: "Let's make yet an other dashboard webapp that going to replace all of our dashboard webapps which we made to replace all of our dashboard webapps"

-Solving interesting problems: "Let's make this with java 15 instead of java 14!!!! Also add graphql to ADD interesting problems nobody had since the nineties!"

- Gain meaningful value from talent: 'Bitbucket and the whole pipeline died fourth time this week, I'm going to drink a coffee or two..."

- Developers in flow: "Joe went to have a lunch around 11:00, you probably should not look for him until 14:30."

- Bring buying decisions closer to the engineering team: "The boss tried to bring up the pros and cons between aws and azure... The police eventually had to break the ensuing fight in the meeting room. The survivors reported things got truly out of hand when someone mentioned line-endings"

- Bring leadership closer to the engineering team: "There was yet an other agile coached hired, when she asked how should we measure velocity one of the lead devs managed to actually wake up and told her that the wifi is still pretty fucking slow"

Well, that's it, folks. Got a job offer, one I might accept, after some tweaks.
I've been a bit more than sixty days unemployed. And in no hurry.
But there is one thing that uneases my mind, though.
I've been a dev, I've been a graduate researcher, I've been a TA and I've been a tech lead, but now the industry wants me in a primarily management position.
I like to code, even if that makes me miserable sometimes. I like to solve problems. Math problems, engineering problems.
But I OOH SOOOO MUCH HATE when I have to deal with leadership who can't tell heads or tails on a coin toss. Who can't make a decision and deal with the consequences. Who can't handle bad times, searching for someone to blame more than searching for a solution. Who can't listen to advice, who thinks a commanding viewpoint is always better than many compiled intelligence reports.
Who don't wanna even think about the possibility that they might not know something, much less that someone on their team might know some subject better than they do.
Frankly, I think might I hate bad leadership more than I like coding.

So if the offer is to have the patent to tell productivity thespians where to shove their stupid spreadsheets, even at the cost of hardly ever issuing a git command, then I think it might be the time.
I hope it is not a mistake, but I can always course-correct my career later. I'm in my late 30s, I still have, like, 40 years of labour ahead of me (assuming medical advancements in the meantime).

So, yeah, I'm joining the other side. But trying not to become them.
May sudo have mercy upon my uid.

this old bitch on my team keeps on taking my food like an elementary school bully and self proclaims herself as my work mom. it's come to a point where she just takes my food off my tray without asking lols
My petty ass has been bringing chocolate and other junk foods because I know she has thyroid problems
she also talks shit to other people when I go on vacation or call in sick so I don't even give a f

The fog of war over all that happened with my change of team is starting to dissipate.
3 people were involved and there were 4 different versions of the whole situtations, but from what I've been able to collect it looks like the company is expanding and one of the mail KPI for the current team leaders is how good they are at creating a NEW generation of team leaders, to take care of the new entries.
My previous team leader told me about all these new growth perspectives and the junior entries I could manage, knowing very well of the desire I have previously expressed of being a senior dev with my small group of juniors to teach.

I declined the offer, stating that this whole year has been exhausting. Every single time I've tried anything (using modules for new components on our old web client, tsdoc to document our types, suggesting technologies like ANYTHING BUT ANGULAR AND MONGO, telling how removing down migrations was a retarded move) my suggestions were either shrugged off or flat out refused. Let alone how every time I was proven right, except for angular but give it time and that will bite their tail as well.
Don't get me wrong: they are well withing their right when they take all those decisions, and more. But I DO NOT PLAN on selling a plethora of bad decisions to a new stack of devs as if they were the gold standard.
"I understand your reasons; you, as a company, need a well coordinated team all running towards a goal; loose cannons are harmful.
But now I need you to understand me: I do not agree with your technical direction. I never lied before and I will not start now. Promotions don't matter nearly as much as my integrity, and integrity in my world means speaking up about problems. Your position is perfectly valid, but mine is as well and they can't be reconciled. If I were you I'd make myself a favor and make sure IHateForALiving doesn't become a team leader; given your direction, I'm not the man you want right now".

As mentioned, one of the KPI for team leaders is how succesfull they are in finding new team leaders, and trying to turn me into one didn't end well; I love sharing knowledge, but being honest to myself is far more important to me. So this meant my previous team leader failed in a very big task, and thus was demoted? At the same time, I've been there for 2 years now so they're not really eager to replace me, but I'm under strict examination too as of now.

I'm studying games development at university and as a course it may not be the best but I enjoy it. With the department courses like Computer Sciences etc run alongside and we're given the choice to swap if we want. At the end of first year a few left the class and a few came in.

Forward to now where we're actually making games. I'm in a team of 4 working on a minecraft clone using Direct X 12 (50% of the module). Immediately one asked "who actually wants to make games?" to which they all said "no... This course is pointless, I don't want to make games" . So now I'm stuck on a team with a group of people who think its all stupid and want to do bare minimum work and want to solve no problems or do anything interesting with the project...

I was just copied on an email that had far to many managers included that basically says 90% of the problems come from an original group that just didn't follow directions.

Now we wait to see if upper management cans the whole team.

!Rant

Tldr: great spike to solve deployment problem may be a wasted effort.

Deployments of an ancient electron application need to be done in CodeDeploy to deploy the latest build. Customer hour restrictions cause this to be done only after midnight, and manually checked.

The whole team knows this is the wrong method of deployment and that there are many other operational problems with the project.

A few other senior team members get together and decide to spike out a way to use electron auto-deployment to accomplish this without using code-deploy at all.

After a shallow dive into this subject, we all get pulled aside to handle a change in another part of the software ecosystem. It happens. We leave the spike behind.

A junior-intermediate developer on the team pics the project up and gets a good spike going in a day and a half! We are all high fives and beers. This is Friday.

By Monday there is a pull request in for code review and it looks solid. Seems like it will make deployments a lot better.

Preparing the last deployment (hopefully) with CodeDeploy ever...

Marketing team members inform us that they are running an add system on the customer devices and to do it they are using Linux.

The current application being deployed is using Windows 10 (yeah, another problem).

They say they have made plans to move our application over to Linux. This means we may not be able to launch the junior devs great spike and the old deployment method may stay for the time being.

Meetings soon to find out how all of this will hash out.

End of rant. I hope I'm doing this right

A long time ago in a decision poorly made:

Past me: hmm we're having trouble getting IT to give us a new build machine with the new compilers.
Past me: I know we'll just use one of the PCs that belongs to a member of the team to tide us over.

[2 months pass]

Present me: that's odd, Jenkins is really slow today.
[Several minutes pass]
Present me: holly shit fuck; it's building the whole weekends worth of builds at 9am on a workday and eating licenses like a cast away that suddenly teleported to an all you can eat buffet.
Present me: [abort, abort, for the love of fuck abort]
Present me: contacts IT, they can't find any problems, wtf happened.

Present me: discovers team member turned off his machine on Friday and builds had been stacking up all weekend.

Lessons learnt: disable power button on team members pc and hire a tazer guy to shoot whenever someone goes near the wall socket.

1 hour lost and no build results for the last 3 days.

It's looking like a bad morning

"I'd prefer a team that commits to solving real customer problems over a team that just commits to finishing user stories." ~@davidjbland

So some big customers are getting problems for a given software project. The relevant dev team, customer support and I, part of another division of QA, need support from a specific QA team. We work for a multinational company employing above a thousand of people around the world.

None of the members are giving signs of life. Nobody from any QA team answers my emails, slack messages or anything. Management does not seem to care either. Did they suddenly die without my knowledge? I am just trying to do my job and find solutions to problems.

I am an inch close to giving no fucks and start playing video games. lol

Took the dive and started learning kubernetes for the last 90 minutes or so. All I can say at this time... is... fuckin' hell m8!

It's some pretty damn cool tech and deconstructing the pieces to understand how to properly build on top of it has been interesting; to say the least.

but shit, man...

the amount of abstractions happening on top of docker/containerd are just asking for tons of problems hahaha. The last place I worked, we had a fair share of devs that either could not or would not bother with trying to understand docker and would constantly push code to the environments, shit would break, and then they'd come to my team and ask us to basically be human log parsers for them... how in the hell my last company is going to fare with trying to roll out kube is beyond me.

tl;dr - kubernetes has a buttload of moving targets and abstracts a metric-fuck-ton of stuff. Last company I worked for is gonna strugglepuff trying to use it.

Is there a team that works truly productive and happy via an agile (scrum) workflow?

Or does it always distill down to an excuse for a chaotic workflow?

My experience and cynic nature has let me to assume the latter.

(That being said, I never had a dedicated scrum master to work with. So that may be the first of many problems.)

Slowly I am strongly considering changing the company. Somehow our management is losing its focus on reality. On the one hand, the management doesn't care one bit about what problems we have, especially when we have issues with other teams, which makes it impossible to finish our (necessary) features. But when the management wants something, everything has to be completed immediately and preferably yesterday.
We work in our team (and in almost the entire development) according to Scrum, so we are organized in sprints. However, our CTO thinks that none of this matters and that the whole planning has to be thrown out just because he wants a small (absolutely stupid) feature.
And then, our supervisor thinks he has to force us to do things that are entirely irrelevant for the team. We wouldn't have any advantage and would just be the henchmen of others.
And then there's a neighboring team that refuses to make any progress and keeps blocking everything. But somehow it's management's favorite team and can simply (unofficially) decide about other teams.
Honestly, I'm pretty pissed off now, and I'm not in the mood for that crap anymore.

There is no such thing as a "Random Error".
Unless you are using rand() to select a random index from an array. And you forget to add - 1 to the generated index.
Now that is one hell of a random error!

Why does everything about Android have to be this verbose, convoluted and complicated?

Why are there no simple solutions to most problems? I have worked with Flutter and Go and none of these have the same level of complexity as Android.

It’s almost as if the Android team lists out the possible solutions to a problem and intentionally pick the hardest and difficult to understand.

Storytime.

once upon a time, there was a dream: we need to test the vagrant setups for our Devs, so that they can run these against the production environment of puppet without problems.

in the year of 2016, the once lone ranger - our team lead - created the ticket. don't. even. ask.

the idea was to build these vagrant setups via bamboo, log the results and fix the setups afterwards.

after weeks of brain fuckery (aka daily business), home office madness, beer, java specs, more beer and many failed builds, I made it.

bamboo now builds the fuckers via a dedicated agent now and I closed the ticket today \o/.

My AP Computer Science teacher changed my life in 2001. Until then, I wasn’t considering a career in development. He challenged me to write a back propagating multi layer perceptron neural network, and an RPN calculator. Every day made me think about how to solve problems at an algorithmic level. He was brutally honest, and one of the reasons why I’m an team manager now. RIP, your legacy won’t be forgotten.

Need some advice here.

So hello everyone! I recently moved abroad for work, for the sake of the experience and the excitement of learning how developers in Latin America tackle specific problems. To my surprise, the dev team is actually composed solely of Europeans and Americans.

I work for a relatively new startup with an ambitious goal. I love the drive everyone has, but my major gripe is with my team lead. He's adverse to any change, and any and all proposals made to improve quality of throughput are shot down in flames. Our stack is a horrendous mess patched together with band-aids, nothing is documented, there are NO unit tests for our backend and the same goes for our frontend. The team has been working on a database/application migration for about a month now, which I find ridiculous because the entire situation could have been avoided by following very rudimentary DevOps practices (which I'm shunned for mentioning). I should also add that for whatever reason containerization and microservices are also taboo, which I find hillarious because of our currently convoluted setup with elastic beanstalk and the the constant complaints between our development environment and production environments differing too much.

I've been tasked with managing a Wordpress site for the past 3 weeks, hardly what I would consider exciting. I've written 6 pages in the past two weeks so our marketing team can move off of squarespace to save some money and allow us more control. Due to the shit show that is our "custom theme" I had to write these pages in a manner that completely disregard existing style rules by disabling them entirely on these pages. Now, ironically they would like to change the blog's base theme but this would invertedly cause other pages created before I arrived to simply not work, which means I would have to rewrite them.

Before I took the role of writing an entire theme from scratch and updating these existing pages to work adequately, I proposed moving to a headless wordpress setup. In which case we could share assets in a much more streamline manner between our application and wordpress site and unify our styles. I was shot down almost immediately. Due to a grave misunderstanding of how wordpress works, no one else on the team seems to understand just how easy it is to fetch data from wordpress's api.

In any event, I also had a tech meeting today with developers from partner companies and realized no one knew what the fuck they were talking about. The greater majority of these self proclaimed senior developers are actually considered junior developers in the United States. I actually recoiled at the thought that I may have made a great mistake leaving the United States to look a great tech gig.

I mean no disrespect to Latin America, or any European countries, I've met some really incredible developers from Russia, the Ukraine, Italy, etc. in the past and I'm certainly not trying to make any blanket statements. I just want to know what everyone thinks, if I should maybe move back to the states and header over to the bay/NY. I'm from the greater Boston area, where some really great stuff is going on but I guess I also wanted a change of scenery.

!rant

Well kinda, more like first world problems.
I started freelancing almost three years ago, it took a lot of hard work, sweat blood and tears to get this whole thing running.
I am currently in a very good place, have a lot of retainer contracts and the awesome freedom that comes with being a freelancer.

Two days ago I got an offer from one of my clients, they really want to have me on board, full time, it's a small, already established startup company, that has big clients, they want me to go into partnership with them, see still haven't talked numbers but they are very "generous".
the idea is to get me ASAP full time on board and start working on a partnership contract specifying all the small details.

I love being a freelancer, the freedom is amazing, client acquisition is Eons away from being a problem, but I miss the team work, and I miss working on products and building teams, freelancers are kind of a lone wolves.

I love working with these clients, there is a lot of mutual respect, they are very transparent and we really are on the same wave.

This could be an amazing opportunity for the next steps in my carrier.
I'm having a hard time making a decision, I'm basically changing my mind about it every two hours...

I mean I guess I'm planning to open my own company at some point anyways... so maybe going into a small but stable company is the way to go..

What would you do?
Would you take the offer? Or would you keep freelancing?

"Hey before we launch, can you reintroduce that bug you fixed on Friday? The other team needs it for debugging."

Why the fuck would you need debugging code in production and why the fuck do we want to readd something that was causing problems? Shaping up to be a great week already.

Not a rant but wanted to get some thoughts from everyone.

I have health problems and unfortunately just had a seizure a few days ago.... Below is directed at my managers. They are nice guys and when I do get back I need them to accommodate although I feel the entire team should be run like this.

Now taking a step back, I see I need to reestablish my way of doing things/mojo. I cannot handle constant chaos and changes. I have to be in a calm, relaxed environment where I can think and enjoy coding: finding and building solutions. That's the summary of how I got into programming and learned to pick things up.

Furthermore, the ideas of the Phoenix Project and what I've shared over the years are actually what I need to be able to perform and excel. Probably the same for everyone and a good way to preempt burnout. It's just in this case, I am the first to go. I cannot be jumping around all the time and need to establish a comfort/expertise zone (but I do and can extend out when given enough time and opportunity).

I'm thinking the EU team probably operates like this, in a calm and orderly environment, less the rare issues.

I'm absolutely sick of my current project. Our client/product owner continues to add (poorly designed) features that require complete back end restructuring and complex data migrations, despite my advice. After my coworker left last week, I'm the only developer willing to work on the model/api for our application. The rest are all frontend.

Everything I work on feels like such a heavy task. No mindless bugs to break it up, because I have no time. I have no one to talk to on my team anymore to help me solve those problems. I feel so alone and burnt out.

Any tips to better my situation here? :/

(Sorry -- this is is my first post here. It's an actually rant. And it's a depressing one at that)

they say i was a natural at programming. i like it, i understand problems easily and im able to find a solution for it. but so was math, and chemistry. basically anything that has problem solving so i wasn't into programming that much.

until i joined my first competition. man that was an eye opener. we had a deadlock tie with the other team, and there was this one problem that was a tie breaker. sure enough we both was able to solve it. but the judges ruled in our favor because of one thing, i used recursion! man that was fun. the looks on their faces.

and i was hooked on that euphoric feeling. that was my drug. now , a decade or so later, im still addicted to that drug

Rant && Question

My asshole manager got me shifted from a better team back to my original team. I didn't have any problems in that.

But now when our QA team has also completely resigned, he wants me to work both as dev as well as QA. I joined at a developer position.
All seniors in my team (Tech lead, product manager) are technichaly incompetent.

I am a fresher and don't have any other offers as of now, don't know what to do?

Have you ever worked for an organization that is not specialized in software development because that is not their main line of business, however, their products are software applications?

If you are, then hi you and me are in the same boat. Currently I have a nice manager and I'm acting as dev lead the strange thing I have a peer that is supposed to be lead as well but I cannot define his position....

In theory he should be scrum master / resource manager which fails at both terribly.

I ended up implementing Agile in the team and deciding what goes and not into the sprint based on quality while this guy just try to squeeze stuff into the sprint, the more the better even with all kinds or problems...

Honestly I'm not sure why he is still in the team since it seems like he only drains the budget, doesn't understand a thing about the products he is working on and every single idea he has is horrible.

Every meeting I have with him I always ended up asking myself "How can somebody be that stupid?" The lack of technical knowledge and even common sense is over 9000 in this one...

It might sound bitter from my end but after two years of dealing with this stupidness of getting people in software development that have no idea what software development is and understand the intricacies of it just because they did an access database or are good at excel is nonsense.

I'm at the verge of quitting and the only thing that is keeping me here is my manager and the fact that the products I am working with are pretty interesting.

Sorry for the long rant but I had to get it out of my chest before it explodes and I directly call out this person.

Not looking for suggestions but if anybody want to chime in go ahead.

How can some developers take a full remote position when they work in a team?

I really appreciate the in real life contact with my team members, to discuss code, solve brain cracking problems together, doing peer programming etc

The days I have worked at home were good for focusing at my own tasks but I missed the team feeling.

Sure with tools you can share screens, collab on code via liveshare in vscode, use Skype to talk and what not but there is no random coworker passing by who takes a look what your doing and helps u with a problem that he knows how to fix

Just a small example why I prefer being at the office

One of the most detrimental things for a developer is having a team who doesn't understand the developer and doesn't fit the developer's personality. This is often overlooked.

Management likes to try and be 'scientific' and start to micromanage, as if the cause of someone's slowness really is their technical skill. No, it's often psychological in nature. A great manager will have a one on one real talk with you. A bad manager will ask you to log every single thing you do on every single day and instead of caring for you they will immediately delegate the issue away without taking into account the psychological conflicts between employees and hidden bullying. You can't solve people problems with business processes.

What doesn't help: ignoring the issue and just softening it with "It's your first time, you will get used to it" or "You will get better at this over time". No, you won't.

One of the sure ways to let a developer spiral down into failure is to not address these kinds of issues. Don't promote a former employee to manager. I think a real manager has to have the personality and studies for it. People aren't cogs and life is not black and white. You are dealing with people. People are infinitely complex. How often they forget this.

Have you ever found a infinite task? Well, I did.

So, the software that I'm working now was under responsibility of another company for development and maintenance (I'll call them X) from 2014 to last month , and the company I work for was handling only with the business part. Now we took all the development for us as well.

This software has a lot of reports , so it has a lot of templates for this reports.

When X was handling the software, they asked the client and the old project manager if they wanted the templates to have the client's products dynamic (no need to change the template when adding a new product) or hardcoded for some products they already had, they choose hardcoded because it would be faster. Butterfly effect.

Fast forward to this week, the team leader designated a task for me, It looked easy at first, just fix 2 templates, easy.

Oh boy, I was so wrong.

I fixed the first template, discovering in the process the hardcoded things, had to add the product reference in a lot of places.

So i went to the second item, a super template that they use to put together some smaller templates.

It was really weird, I couldn't find all the templates that it was supposed to use, and I didn't really know the exact problem, the only thing I knew was that it was not being generated, the reason could be the super template itself or one of the 15 smaller templates, that could happen to have sub templates.

So I called the team leader and explained to him wtf was happening, he called the senior business analyst, that called the PM, we agreed that it would be infinite because of those fucking hardcoded things, they prepared a excel sheet with this and a lot of other problems and will send this to the client, explaining that we'll need a lot of time to put this new product up and running.

Now I'm in the middle of this shit storm seeing a time of darkness in the future.

Ps: This new product was supposed to be inserted in the software since last November, when it was under X responsability, and they analyzed it and said that it would take 190 hours to be completely done, the client refused. It was the first rain drop of what would become a shit storm.

let's call him Richie. Richie doesn't listen in team meetings, does not have any clue of what we are doing and what the important topics are. Richi is hiding between the cars in the parking house to not have to talk to you on the 2min way to the office. Richie is 'done' when he encounters any problems in his work so we have to do it. Yeah, we all love Richie...

When Do You Stop Taking Responsibility?

Let me clarify by describing four scenarios in which you are tasked with some software development. It could be a large or small task. The fourth scenario is the one I'm interested in. The first three are just for contrast.

1. You either decide how to implement the requirements, or you're given directions or constraints you agree with. (If you hadn't been given those specific directions you probably would have done the same thing anyway.) **You feel accountable for the outcome**, such as whether it works correctly or is delivered on time. And, of course, the team feels collectively accountable. (We could call this the "happy path.")

2. You would prefer to do the work one way, but you're instructed to do it a different way, either by a manager, team lead, or team consensus. You disagree with the approach, but you're not a stubborn know-it-all. You understand that their way is valid, or you don't fully understand it but you trust that someone else does. You're probably going to learn something. **You feel accountable for the outcome** in a normal, non-blaming sort of way.

3. You're instructed to do something so horribly wrong that it's guaranteed to fail badly. You're in a position to refuse or push back, and you do.

4. You're given instructions that you know are bad, you raise your objections, and then you follow them anyway. It could be a really awful technical approach, use of copy-pasted code, the wrong tools, wrong library, no unit testing, or anything similar. The negative consequences you expect could include technical failure, technical debt, or significant delays. **You do not feel accountable for the outcome.** If it doesn't work, takes too long, or the users hate it, you expect the individual(s) who gave you instructions to take full responsibility. It's not that you want to point fingers, but you will if it comes to that.

---

That fourth scenario could provoke all sorts of reactions. I'm interested in it for what you might call research purposes.

The final outcome is irrelevant. If it failed, whether someone else ultimately took responsibility or you were blamed is irrelevant. That it is the opposite of team accountability is obvious and also irrelevant.

Here is the question (finally!)

Have you experienced scenario number four, in which you develop software (big as an application, small as a class or method) in a way you believe to be so incorrect that it will have consequences, because someone required you to do so, and you complied *with the expectation that they, not you, would be accountable for the outcome?*

Emphasis is not on the outcome or who was held accountable, but on whether you *felt* accountable when you developed the software.

If you just want to answer yes or no, or "yes, several times," that's great. If you'd like to describe the scenario with any amount of detail, that's great too. If it's something you'd rather not share publicly you can contact me privately - my profile name at gmail.com.

The point is not judgment. I'll go first. My answer is yes, I have experienced scenario #4. For example, I've been told to copy/paste/edit code which I know will be incomprehensible, unmaintainable, buggy, and give future developers nightmares. I've had to build features I know users will hate. Sometimes I've been wrong. I usually raised objections or shared concerns with the team. Sometimes the environment made that impractical. If the problems persisted I looked for other work. But the point is that sometimes I did what I was told, and I felt that if it went horribly wrong I could say, "Yes, I understand, but this was not my decision." *I did not feel accountable.*.

I plan on writing more about this, but I'd like to start by gathering some perspective and understanding beyond just my own experience.

Thanks

I spent 2 hours fixing eclipse.
I spent another hour getting Java to parse my date and time input.
And I still have to get an SQL query running.

and I need to do 5 more problems like this for a team project.

I seriously detest being dead weight on my team, especially when it is a two person team.

This is friggin bullshit. I'm a 2nd year college CS student! I'd think I'd be a quicker programmer by know! I LEARNED TO PROGRAM IN JAVA FOR TORVALD'S SAKE!

Well. Back to work.

None of my collabs were walk in a park. Some were better, and some worse. Never worked in a team that worked without serius communication problems. Some individuals stuck out as great for me to work with. I guess you can’t have a perfect team.

Hire Cryptic Trace Technologies To Solve Your Marital Problems

Facing betrayal from a loved one is never easy, especially when it involves your own family. As a devoted father, I always cherished my children, but doubts began to creep in when my wife’s pregnancy timeline didn’t make sense. She also maintained a secret relationship with her former boss, someone I had always been wary of. Their private meetings and constant communication behind my back only heightened my suspicions. I knew I needed the truth, no matter how painful it might be. That’s when I turned to Cryptic Trace Technologies, and I can confidently say they exceeded my expectations. Their team worked with the utmost professionalism and discretion, conducting a thorough investigation that revealed the heartbreaking truth—I had been deceived for years. While the discovery was devastating, their help allowed me to confirm my suspicions and take control of my future. Their expertise and efficiency ensured that I had undeniable proof of what had been happening behind my back. Thanks to Cryptic Trace Technologies, I now have the clarity and closure I desperately needed. The truth, though painful, has set me free, allowing me to move forward with my life without the burden of deception. I highly recommend their services to anyone who finds themselves in a similar situation. Their dedication to uncovering the truth with professionalism and care is truly commendable. Contact them through
E m a i l : Cryptictrace (@) technologist (.) com
W e b s i t e :cryptictracetechnologies (.) com

Actually my degree helped me a lot, I owe my teachers most of what I know, I learned so much, I even learned to love programming with one of my teachers and now I can't think of myself doing anything apart from programming. It got me my first job, and soon I realized my formation (and my college partner's) was among the best in my country, I was soon able to solve problems that no one else in the team could, and could learn new stuff faster than them, all the graduated from my same college usually had better projects and instant good reputation because they knew we were well prepared.

So YES, my degree helped me and my friends a LOT and I feel I couldn't have chosen a better thing to study or a better place to do it.

I'm starting to realize that maybe the issue with my team is that they don't know how to break down complex problems into smaller parts that can be completed, tested one by one, allowing you to create save points.

To them it's either all or nothing... And once they're done, they cannot explain what they did other than it works..

Who doesn't love customer support?

So anyway, I'm the point-of-contact at our company for a specific tool we use, sold by an external vendor, whose yearly licenses cost five-digits per user. I've been the point of contact for around three years now, and most of the time it's people way more senior than me asking for help with [specific edge case] and I send them on their way with the solution. Sometimes that isn't the case though, and I need to send an email off to [vendor]'s support team.

Good support is lovely. Our go-to guy on their support team was great. Timely responses, thorough, and always willing to dig to the bottom of the case. Sometimes it's us being stupid and not knowing what the [obscure feature] toggle does, sometimes it's just a mis-match between what we're trying to do and how the tool was designed, and sometimes it's a sneaky, devious bug in their product. I still remember the pride I felt when we got an email notification for the latest release of the tool that contained a bugfix that I had gone over with their dev team on call to figure out how to reproduce.

However, just over a year ago they changed our go-to guy. It started off small. The new guy was more terse in his responses. Less attentive to the little details in the message. Gather as much information as possible first, deal with the actual problem we were having second. He'd fix the immediate problem, but more open-ended questions about best practices to avoid another mess in the future would be ignored.

But slowly it got worse. Less responsive. Entire paragraphs of context would be ignored and had to be repeated to him. More generic responses. The odd case got dropped entirely. Last time I opened a support ticket, when I asked for additional clarification I got a ChatGPT-ass response only tangentially related to the actual context of my question (you could tell it was copy-pasted because he didn't even bother to paste without formatting).

Now upper management is unhappy with [tool] and are on my ass to get them to solve all our problems with it. What does new support guy reply with to my ticket with clearly bulleted questions, written in bold to separate them for clarity from the surrounding context? A two-line, nonspecific request for information entirely unrelated to the issue at hand, to the point that me and everybody from my company in cc privately went "why the fuck would we even send that??".

These next few weeks are going to be fucking rough, dear god may this be over soon.