I’ve had a good amount of incompetent co-workers in the past. One that stands out was this junior developer who worked at one of my previous companies. He was incompetent, but that wasn’t even his worst attribute. He was incompetent, and worse, he had a piss-poor attitude.

Myself and a few other devs at the company tried to help him, but he would literally get mad when people tried to help him. Sometimes he would even call one of us over and start getting snarky with us as we tried to help him. He was a piece of shit and a shitty developer. I don’t think he built one complete feature or fixed one bug in the year he was at the company before he was eventually fired.

Oh, and aside from his incompetence and shitty attitude, he had no sense of humor. It was so annoying. My friend and I made a little song based on his name and a group that sounded like his name, and he got pissed. We always used to sing it anyway after that and it always riled him up. I feel a bit bad about that now but he pretty much got mad at everything so whatever.

One of my favorite memories of him is when he was leaving one day, my good friend/co-worker and I were having a Nerf gun battle. The junior was leaving the office, and my friend tried to get him involved in the battle and shot him, but accidentally hit him in the back of the head. He said nothing, didn’t turn around, and just walked out lol. He was not happy about it.

So you poor devs... you have to be strong now, hr has a new tool to torture you: Skype has a new coding interview function.
What do you think about that? Good or even more abuse?

My dream is to build a shopping cart for web stores that doesn't fucking suck.

Seriously Bigcommerce, Shopify, Magneto, etc. All of you can eat bag of dicks and burn in hell for ever.

I don't care what languages you fancy, all of their stacks are a pile of shit, monkey patched together with popsicle sticks and duct tape and it all falls apart with high concurrency.

All their greasy haired sales teams will throw all manners of horse shit at the poor bastards who are trying to run a business so they can pad their commission checks... "High availability", "scalable", "reliable", "Increased conversation rate"... Lying dick fucks, all of them! I am calling them the fuck out on that snake oil they're all peddling.

The only thing worse than their shit APIs is the shit documentation and the shit support that accompanies them.

Support of these platforms are pretty much all the same, sure mayhaps one has 24*7 phone support and another closes at 9 or some shit like that, either way the only people they put on the phone are monkeys that will freeze up and say "I'm not a developer so I can't help you"... Guess what, "Eric"! I didn't ask if you're a fucking dev! I'm calling because one of your devs fucked up and I need you to tell him to unfuck it so I can get the fuck on with my day!

Their app/plugin market places are shameful to say the least. The overall quality of software is somewhat dire and it's mostly dominated by oversees developers who speak English about as well as the language they're developing with (not very well usually).

I could go on until I hit the character limit but I'm gonna end it here by saying, all shopping carts suck and they should burn for eternity in the depths of hell so that a savior can free all developers from this agonizing torment.

Starting to wish I never got involved in this industry.

I am working for the most ridiculous, god awful place I have ever had the misfortune of working and I am having a HELL of a time getting out of it because everything wants 5 years fucking exp in some fucking specific framework that is basically the same as every other fucking framework.

Our previous cto was a closeminded totalitarian bully and when she finally left she was replaced by a lecherous fucking dinosaur who has no idea how to code in our code base. He also has barely been showing up to work for the last few months.

For some reason our fucking ceo allows this all to continue and only interjects whenever he can make himself the biggest nuisance (ie design handoffs etc where he has little to no knowledge)

I was already woefully underpaid but was recently 'promoted' to team lead and when I brought up my ridiculous salary (yes I was essentially just funneled into this role) they gave me a neglible raise and ceo told the fucking dinosaur to tell me he 'doesn't like when people ask for raises'

The only reason I am in this position is because we have such ridiculously poor employee retention and I am one of the people after only 2.5 years there that has the ability to provide any kind of knowledge transfer. Most of our dev team consists of people fresh out of school and our code base is just an absolute mess of junior dev spaghetti debauchery.

I have expressed concerns over this and was told that I'm negative and go looking for problems and that 'everywhere is like this'

The ceo has a few people he keeps close because in his words 'they're the only ones who don't disagree with me'

He also refused to hire anyone with experience because they cost too much and he doesn't like people who have opinions.

To make matters worse all the fucking dinosaur does is wander around and talk to the junior devs about video games.

His previous favorite past time was staring at my tits, ranting about his wife and telling me 'he'd offer to give me a back rub but you can't do that now a days'

I caught his fucking wife creeping me on LinkedIn a few months ago for some fucking reason.

Oh and as icing on the cake I had a fucking interview today for an intermediate angular position and a few minutes after I received an email saying that ACCTUALLY they had been informed they were now looking for a senior react dev.

Like seriously what the fuck.

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

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

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

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

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

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

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

WELL FUCK RIGHT OFF

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

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

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

Whether you hated 2017, 2018 will be better, promise.
Wish everyone a happy new year.

Best wishes,
cozyplanes

P.S.1. Thank you everyone for making me the part of devRant!
P.S.2. Thanks David and Tim!
P.S.3. If you need to work todayn and you don't think that it is the right thing to do, think of engineers working in a TV/radio broadcasting company. They should prepare the show! (Poor devs there)

[Little perspective: For the last 7 months I'm working in a certain project.]
[The project is full of unimaginative, non-creative devs with 0 initiative and poor technical background.]
[And they're almost all from one country which you all can figure out.]
[But I'm not going to mention it here because I don't want to come up as a racist]
[So there's US (Europeans) and THEM. 3 of US and about 10 of THEM. And we're doing 90% of all the heavy lifting]
---
Yesterday
---
D (Dev from THEM): Hi S, I have a problem with my task
Me: (sighing) Ok let's have a call
* on the call with D we were checking some stuff loosely related to task *
* code wouldn't get invoked at all for some reason *
* suddenly I realize that even if the code would invoke, D's probably doing everything wrong in it anyway *
Me (thinking): I need to double check something.
Me: I can't help you now, I'll get back to you later.
* call ended *
---
Me: Hey J, I need your help, I need to clarify the work package in my mind, because I am no longer sure.
J (my European TL): Ok, fire away.
* call started *
Me: Is it true that [blahblahblah] and so D's task depends on me completing first my task, or am I losing my mind?
J: That is correct.
Me: Well she's trying to do this in [that] way, which is completely wrong.
J: You see, that's how it is in this project, you do refinements with them, split these work packages to tasks, mention specifically what depends on what and what order should things be taken in, and in some cases all tasks from given user stories should be done by one person entirely... But they do it their way anyway, assign different people to different interdependent tasks, and these people don't even understand the big picture and they try to do the things the way they think they understand them.
Me: It's a fire in a brothel.
J: Yup.
Me: I fucking love this project.
J: (smiling silently)
* call ended *
---
Me: Ok D, you can't do your task because it's dependant on my task.
D: Oh... so what do I do?
Me: I don't know, do something else until I do my task.
---
A (THEIR TL) (Oh, did I forget to mention that there are 2 TLs in this project? THEY have their own. And there are 2 PMs as well.)
A: Hey S, I need to talk
Me: (sighing, getting distracted from work again) Ok let's have a call
* call started *
A: S, we need this entire work package done by Friday EOD.
Me: I can't promise, especially since there are several people working on its several tasks.
A: D's working on hers for 3 days already, and she's stuck. We want you to take over.
Me: (sighing, thinking "great"): Ok.
* call ended *
---
Me: Hey D, A instructed me to take over your task. This is actually going to be easier since you'd have to wait for mine after all.
D: Oh, ok.
---
* I switched the Assigned Person on D's task to myself on Azure *
---
This morning, email from D.
"Hey, I completed my task and it's on [this] branch, what do I do now?"

........................................
Me, hesitating between 2 ways to reply:
(and take note there are people in CC: A, J, P - the last one is THEIR PM)
1) "Hi, Unfortunately you'd still have to wait for my changes because your task is dependent on my task - the column to be changed is in the table that I am introducing and it's not merged to develop branch yet. By the way I already did your task locally, as I was instructed to do it, I'm wrapping things up now."
(y'know: the response which is kind, professional, understanding; without a slight bit of impatience)
2) WHAT FUCKING PART OF "DON'T DO THIS I WILL FUCKING DO IT MYSELF GO HOME JUST GO HOME" YOU DON'T FUCKING UNDERSTAND

My condolences go out to the 800 or however many amazing employees/devs that were laid off at Activision Blizzard due to poor leadership and guidance. Idk how many were devs were laid off but it’s all a shame. To think that one of the leading AAA companies is so fucking blind to the truth and only go for $$$ is a waste. If they had people in charge whom actually understood why products in the gaming industry are fun and popular and strives to make good games instead of slot machines and didn’t treat their development staff with such disrespect then maybe they’d make good games. Even bringing the great name of blizzard down to shit.. it’s phenomenal how blind they are and where they put their money. They are disgusting and need to get their head out of their ass even though it wouldn’t help anyone. Sorry to anyone that is involved with them

So today, I managed to make one of my colleagues feel like an idiot. In this contract, I work mostly for ui integration, while he build the pages with angular before I add all the html structure and fancy css.

We are building the front-end/ui for an industrial device with a touch screen. For that last 2 days he was blocked on a bug that when you click the confirm button on a delete popup, it would somehow select an input in the page before it was deleted and would lock the ui when showing the virtual keyboard (the poor thing didn't know what to do and wouldn't close).

During those two days, he asked all the other devs for help, trying to find a pattern or anything that could help, while I was focused on writing my css and stuff since it was my priority and I was hired specifically for that (I was aware of the bug and gave my input but I never saw it being reproduced)

So today, he start his new routine of raging at his desk and he decides to show me on my device for some reason. I immediately notice a pattern. It would always select one of the two fields behind the popup, in the click area of the button (it's a big button). Then, I noticed that I could press a random spot on the screen, drag my finger on the button and let go and nothing would happen.

It's at this moment I knew I had found the bug. The button was set to emit an event on mousedown while the inputs behind it were set to emit an event on mouseup (like it should be everywhere). So the popup closed when you placed your finger on the screen and the input was selected immediately after when you removed your finger (which was usually faster than the page code which was not yet optimized)

After that, it was just an easy fix to change the listener and I had a free beer.

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

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

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

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

Dear Product owners / Company Owners / Whoever requesting a feature:

Devs like to know they are adding value to whatever product they are working on. Every time you request a stupid no value added request, you kick the dev's soul.

After several hits the developer will stop caring about the software and eventually will get the job done, but oh boy, the amount of tech debt/trash code the dev is gonna leave behind will be horrendous.

Then the next developer, not only takes the hit from another stupid request, he/she will see the crappy code the past sad developer left and will take a double hit. Of course all of them start proactive and try to fix previous blood trails but sadness will catch them eventually.

If you want you're apps/products/reports to be good in a long run don't make stupid requests.

BAs, Stop being Expensive Email Forwarders and challenge a request, understand the process and then hand it to the developer.

Us developers are sensible cute ponies. Treat us well or expect poor quality projects

The sales and business team at my office really look down at the devs. Just because we don't dress in fancy suits doesn't mean we are any less important that those asshats.

In fact we are probably a hell of a lot more useful since they cant land any sales since they barely have any idea what they are selling and the company is rapidly going under.
To give you an idea :
We recently changed office and one of them asked if they had had to be in the same workspace as the developers again?

Why do we need them?
Cant we outsource their jobs ?

Some of them dont even answer when you bid them good morning

And one douche bag even brought his bluetooth radio and refuses to use headphones , he keeps playing shitty music and disturbing us.

The company is kinda fractured and there is poor chain of command, so there is little we can do, telling dev management is fruitless he has no authority over the guy
And the business manager simply said oh you dont like good music then walked off.

First junior software dev job, asked what I wanted for hourly pay, replied “I need at least $13/hour to survive.” (This is in US, 2007, I was almost done with Bachelor in CS, single mom with two little kids, was also in the army national guard at the time)

I grew up poor, and was very ignorant about salary negotiations. So of course they offered $13/hour. I accepted, thinking it must be fair, and was glad to be making more than minimum wage. Six months in, I’m doing the same work as their devs with 2-4 years experience, find out they are billing clients $100/hour for my work. Then, to top it off, the COO makes a joke in a meeting about how it’s not a big deal for their “technical assistant” to be doing lackey work because he’s only paid $13. Fuuuuuuuuck. That comment still makes my blood boil.

I had a nice manager at the time that explained how salary negotiations worked, but I still think it’s lame as hell. I ended up getting put on salary, $50k/year, after threatening to leave.

Software engineering is becoming main stream.

It will become the average job in the future. Anyone who cant dev is going to be poor and do the dirtiest jobs.

Dev average income is going to drop， mainly because a shit loads of frameworks and dumbification of software and code creation will be set in place to accomodate large population as devs.

The will create a seperation between the normal idiot dev who will be paid minimum wage and the smart ones that create the frameworks and dumbed down code creating tools.

Its oversimplified obviously because im not taking into account sys admin and so on but in general it will follow that trend. Its like this today but because there isnt enough devs， idiots are still revered and payed big bucks.

Give it 50 to 75 years imo.

> Worst work culture you've experienced?

It's a tie between my first to employers.

First: A career's dead end.
Bosses hardly ever said the truth, suger-coated everything and told you just about anything to get what they wanted. E.g. a coworker of mine was sent on a business trip to another company. They had told him this is his big chance! He'd attend a project kick-off meeting, maybe become its lead permanently. When he got there, the other company was like "So you're the temporary first-level supporter? Great! Here's your headset".

And well, devs were worth nothing anyway. For every dev there were 2-3 "consultants" that wrote detailed specifications, including SQL statements and pseudocode. The dev's job was just to translate that to working code. Except for the two highest senior devs, who had perfect job security. They had cooked up a custom Ant-based build system, had forked several high-profile Java projects (e.g. Hibernate) and their code was purposely cryptic and convoluted.
You had no chance to make changes to their projects without involuntarily breaking half of it. And then you'd have to beg for a bit of their time. And doing something they didn't like? Forget it. After I suggested to introduce automated testing I was treated like a heretic. Well of course, that would have threatened their job security. Even managers had no power against them. If these two would quit half a dozen projects would simply be dead.

And finally, the pecking order. Juniors, like me back then, didn't get taught shit. We were just there for the work the seniors didn't want to do. When one of the senior devs had implemented a patch on the master branch, it was the junior's job to apply it to the other branches.

Second: A massive sweatshop, almost like a real-life caricature.
It was a big corporation. Managers acted like kings, always taking the best for themselves while leaving crumbs for the plebs (=devs, operators, etc). They had the spacious single offices, we had the open plan (so awesome for communication and teamwork! synergy effects!). When they got bored, they left meetings just like that. We... well don't even think about being late.
And of course most managers followed the "kiss up, kick down" principle. Boy, was I getting kicked because I dared to question a decision of my boss. He made my life so hard I got sick for a month, being close to burnout. The best part? I gave notice a month later, and _he_still_was_surprised_!
Plebs weren't allowed anything below perfection, bosses on the other hand... so, I got yelled at by some manager. Twice. For essentially nothing, things just bruised his fragile ego. My bosses response? "Oh he's just human". No, the plebs was expected to obey the powers that be. Something you didn't like? That just means your attitude needs adjustment. Like with the open plan offices: I criticized the noise and distraction. Well that's just my _opinion_, right? Anyone else is happily enjoying it! Why can't I just be like the others? And most people really had given up, working like on a production line.

The company itself, while big, was a big ball of small, isolated groups, sticking together by office politics. In your software you'd need to call a service made by a different team, sooner or later. Not documented, noone was ever willing to help. To actually get help, you needed to get your boss to talk to their boss. Then you'd have a chance at all.

Oh, and the red tape. Say you needed a simple cable. You know, like those for $2 on Amazon. You'd open a support ticket and a week later everyone involved had signed it off. Probably. Like your boss, the support's boss, the internal IT services' boss, and maybe some other poor sap who felt important. Or maybe not, because the justification for needing that cable wasn't specific enough. I mean, just imagine the potential damage if our employees owned a cable they shouldn't!

You know, after these two employers I actually needed therapy. Looking back now, hooooly shit... that's why I can't repeat often enough that we devs put up with way too much bullshit.

Read the following in Morgan Freeman’s voice.

Okay everyone sit on down and get ready for story time. There once was a workspace that was a pain in the ass to setup. It often would take an entire day even for the most experienced devs on the team...for it was a workspace perched atop a swamp of shit that would require a whole year to refactor into something that isn’t shit.

It was inherited, passed down, stepped in and scrapped from the boot soles of every programmer that ever touched it. It was an amalgam of old, new, and third party components with a class path a mile long and no package management because the company although physically in the present, somehow maintained a temporal presence in the past. And there was nothing that the team hated more than setting that workspace. In short it was an unholy mess that made Satan cry and Dennis Ritchie spin in his grave so much that the state of California attached magnets and a coil to his body and casket to generate electricity.

Then one day the untalented clowns known as App Group decided that our IDE should be owned and configured strictly through them. They took poor Eclipse and mounted so much silly shit to it that it resembled a riding lawn mower with a fax machine and a blender duct taped to it. Eventually as everything the company touched did, it simply turned into a broken, shitty mess that not even Jesus Titty Fucking Christ could bring back the dead.

And then, every month or so the IDE would break in such a grand way that every developer had to rebuild their workspace...the very same Lovecraftian monster disguised as a code base. It was just too much to bear for old Deus. He was all out of fucks and there wasn’t enough alcohol in the world to quiet his injured soul. So he stood on a chair, carved his name in a rafter and tied a noose to it, put it around his neck and finally kicked the chair out from under himself. I am told he even pooped his pants and the post mortem shit in the seat of his pants was still better than the codebase at work. I’m Morgan Freeman.

Semi rant/ opinion
I have been wondering a bit about what my fellow devs think about adblockers

I have been using an adblocker for years.
I am guessing we got a good mix of both people who are pro and against them

I do get the site's owner point of view wanting to get a little bit of cash out of their site buts its the ad publisher that come in and royally screw things up with their garish flashy shit.

I wouldn't really mind 2-3 small static adverts on a page, little ones that don't disrupt the flow of the page or clash with the page colour scheme (i know that one is a bit far fetched but anyone who loaded up a dark page in the comfort of a darkened room only to have a big bright ad turn up in the middle of the page force them to squint ). Sadly publishers don't give a damn, their only concern is to
GRAB YOUR ATTENTION...

FLASHY FLASH FLASH MOFO!

OH AND HERE IS AN AUDIO ENABLED ONE FOR YA, GOOD LUCK MUTING IT YOU POOR SHMUCK , ONE CLICK ON THE DAMN THING WILL TAKE YOU TO THE LAND OF POP-UPS

AH YOU WANNA DOWNLOAD SOMETHING BUDDY ? AH WELL I HOPE YOU LIKE INDIANA JONES' SCENE WITH HOLY GRAIL
CUZ HERE ARE 10 DOWNLOAD BUTTONS, ONE IS THE REAL THING THE REST WILL ARE TOOLBARS

They are the biggest culprit here yet moan the loudest about adblockers.
Sort yourselves out then complain to us about ad blocking

A morbid realization (I am just wasting your time keep scrolling)

Unless someone takes a stand for the user, and their comfort and requirements, unless someone looks a client straight in the eye and says "no, I will not do that, and neither will my team" and denies them their request, nothing will change, good devs will keep losing their spark to save themselves frustration, good people will walk away and the tyranny that we face daily grows... unless someone stands up, someone who cannot be knocked down, or reprimanded and told they're wrong for fighting for what's right.. unless someone stands up for what is right and fair... nothing changes... and nothing ever will... poor programs, bad games and content, lower standards, frustrated users, annoyance that you don't matter as a user or a dev will never go away... unless someone says enough. But no one will, money is the boss, morality a liability, and people an abundant resource. This world is backwards, devs are carrying the blame and no one who is able, cares enough to say "that's enough!".

PM: this is our super fancy new CI/CD pipeline, it's the greatest. i expect you to learn and understand all this in no time.
devs: so i have to spend some more time on this topic because it's completely new to me and requires some learning...
PM: nooo, that's a super easy task with zero effort, my braindead hamster can do that in no time, so can i, and so can you! let's assign 1 story point for that.

~ 3 months latèr ~

also PM, after he has started developing as well: so i'm realizing there are many things that i have to learn, and it takes me some time. i haven't developed with C++ and <other tool stack> for a longer time. by the way, you guys don't need to check for any quality right now, we need to deliver fast. it's okay, when you have memory overflows, your code is completely crappy, poor architecture or memory overflows, it doesn't matter.

he even has a subtask for migrating his code from VS project to our new project structure, since he refused to learn our pipeline right from the beginning and created VS project instead. シ why is this a subtask? this job can be done in no time, my left vanishing twin named Klaus who has dislexia and hates vim can solve this task in 20 seconds!!!!11

(and still no PR, not even a feature branch in our repo)

Dear Tailwindcss,

Fuck you.

Fuck you and your messy as fuck html files.

Fuck your shitty pseudo 90s 'Let's dump all our shit in a single html file'.

Fuck your claims of being responsive, most of your widths and heights are done in FUCKING PIXELS.

Fuck your claims of being flexible, adding a 10% width class took 20 minutes of scrolling through your shitty docs.

And the worst part is, the poor devs 4 years from now are gonna be stuck maintaining this goddamn shit because shitty enterprise companies desperately trying to stay relevant are treating this shit like the Holy God of Frontend styling, the solution to CSS once and for all

FUCKING IDIOTS CSS ISN'T BROKEN, THIS GARBAGE IS!!!! WE DON'T NEED A SHITTY SOLUTION TO A PROBLEM THAT DOESN'T EXIST

Tailwind can go fuck itself with it's 200 character html lines

Most people I talk to in the industry hate the "puzzle-y" nature of interviews (e.g. coding on a whiteboard, now get it to run in linear time, oh wait there's a trick you don't know but could totally look up if given the chance) and acknowledge that it does a poor job determining the value of the prospective hire.

Why then is there no sign of this changing? I realize it's a hard problem to solve but in theory the entire company is at stake when it comes to hiring good/bad devs. You'd think somebody would have come up with a better way.

Ok so for the first time (doing web dev since a few years) I got this customer who insists to work via TeamViewer on the phone with me doing css edits live. It's a mess and extremely stressful. I told him I don't work like that and today I officially put a stop in this. He's saying that all the other developers are working for him in the same way and that by doing 4 hours sessions of live css edits by the pixel they save time.

Guys, what the fuck are you doing?

So about 3 weeks ago I was laid off from my dream job due to corporate bullshit. From the feedback received since then it is clear that the company made a mistake hiring a brand new React dev while they really needed an experienced one. Because the consultants who were supposed to be weren't. And the other in-house front end dev was an elitist asshole. And I never received proper feedback until it was too late. Actually I still don't have proper feedback save for some vague stuff which really sounds like the kind of feedback you'd give someone in the middle of their learning process. They even said eventually given more time I could have made it. But alas they felt they had to make a call in the best interest of the company.

Things moved fast since then, I took a week to recover and then I spent time updating my resume before getting back in touch with the recruiter who got me my last job. Great guy and he was happy to help me again. Applied to some positions, got some replies, first in person interview I go to they are immediately willing to take me on.

So now I'm supposed to start tomorrow but somehow I'm having my doubts. The company isn't an IT company but rather a fashion company. They believe in developing in house tools because past attempts with external companies resulted in them trying to push their vision through. Knowing who they worked with I agree, they tried to oversell all the time. But after talking with their developers I noticed they are behind on their knowledge. But so am I. So there was no tech interview which means I am getting an easy way in. And if they honour their word I'll be signing tomorrow for around my old wages.

So you'd think that sounds good right? And yet I'm worried it's going to be another shit show working on software without proper analysis or best practices. I mean the devs aren't total idiots, they are mediors like me and I think their heart is in the right place. They want to develop a good project but it will be just us 3 making a modern .net wpf application with the same functionality of the old Access based system currently in use. I was urged by the boss to draw on my experience and I think he wants me to help teach them too. But I'm painfully aware for my decade since graduating I'm a less than average .net dev who struggles with theory and never worked a job where I had someone more experienced to teach me. I coasted most of the time in underpaid jobs due to various reasons. But I'd always get mad over shitty code and practices. Which I realize is hypocritical for someone who couldn't explain what a singleton class is or who still fails at separation of concerns.

So yeah my question for the hivemind is what advice would you give a dev like me? I honestly dislike how poor I perform but it often feels like an insurmountable climb, and being over 30 makes it even more depressing. On the other hand I know I should feel blessed to find a workplace who seems to genuinely believe that people grow and develop and wishes to support me in this. Part of me thinks I should just go in, relax, but also learn till I'm there where I want to be and see if these people are open to improving with me. But part of me also feels I'm rushing into this, picking the first best offer, and it sure feels like a step backwards somehow. And that then makes me feel like an ugly ungrateful person who deserves her bad luck because she expects of others what she can't even do herself :(

My current job at the release & deploy mgmt team:

Basically this is the "theoretically sound flow":

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

In the real world however:

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

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

This is a government agency mind you!

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

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

I want to explain to people like ostream (aka aviophille) why JS is a crap language. Because they apparently don't know (lol).

First I want to say that JS is fine for small things like gluing some parts togeter. Like, you know, the exact thing it was intended for when it was invented: scripting.

So why is it bad as a programming language for whole apps or projects?

No type checks (dynamic typing). This is typical for scripting languages and not neccesarily bad for such a language but it's certainly bad for a programming language.

"truthy" everything. It's bad for readability and it's dangerous because you can accidentaly make unwanted behavior.

The existence of == and ===. The rule for many real life JS projects is to always use === to be more safe.
In general: The correct thing should be the default thing. JS violates that.

Automatic semicolon insertion can cause funny surprises.
If semicolons aren't truly optional, then they should not be allowed to be omitted.

No enums. Do I need to say more?

No generics (of course, lol).

Fucked up implicit type conversions that violate the principle of least surprise (you know those from all the memes).

No integer data types (only floating point). BigInt obviously doesn't count.

No value types and no real concept for immutability. "Const" doesn't count because it only makes the reference immutale (see lack of value types). "Freeze" doesn't count since it's a runtime enforcement and therefore pretty useless.

No algebraic types. That one can be forgiven though, because it's only common in the most modern languages.

The need for null AND undefined.

No concept of non-nullability (values that can not be null).

JS embraces the "fail silently" approach, which means that many bugs remain unnoticed and will be a PITA to find and debug.

Some of the problems can and have been adressed with TypeScript, but most of them are unfixable because it would break backward compatibility.
So JS is truly rotten at the core and can not be fixed in principle.

That doesn't mean that I also hate JS devs. I pity your poor souls for having to deal with this abomination of a language.

It's likely that I fogot to mention many other problems with JS, so feel free to extend the list in the comments :)

Marry Christmas!

i hate linux like a lot , how do you guys use it

like you guys dont want an advertising ID, how the fuck will advertisers know who you are and what you like?

open source , give me a break, you mean your os devs are soo untrustworthy that you just have to see what they wrote in the code, who does that?

free come on, how poor are you linux people, i mean, quality stuff gets paid for, free stuff just means it's trash

and the linux devs , the aint like real coders they are just hobbysts, making your os in their free time

and who wants to install their own software anyway, on other platforms the company curates restricted software that you can use, and i know you'll say its oppressive but its just customer protection.

and i do want my platform to track everything i do, it only helps them build better stuff for me.

and whenever they decide to outdate my hardware and kill support for it, it only means they care and want me to get the latest tech, how considerate.

wait , i hear you say, there are no bugs in linux, my vendor makes sure my os comes with the latest antivirus software, nothing can break my system.

and just because linux runs on servers and most super computers only shows that common users like you and me are ignored, at least my vendor is not a sellout, and still makes stuff for the masses.

you say freedom i say safety i can sleep safe and sound for am protected nutured under one echosystem of software that i can not leave.

!rant

What are people thinking when they are building datepickers (or any type of angular/jQuery plugin for that matter)?

Lets put all of the code in one file, place everything that should be dynamic and optimizable in constants, provide no localization support, finish it all up, publish it to bower and npm (so poor devs won't have to struggle) and last but not least don't accept pull requests with useful features for months!

How to waste money as a dev company, 101:

Give people ton of budget for their education to do whatever they want with it with no oversight at all:
1) Devs go to some shitty confs in places across the world that teaches them nothing (new) so they can visit interesting places on company's money
2) Go to a conf where you learn ton of stuff that can be implemented right away

...Then you come back, no time to do stuff properly, just "make it work" (or make it seem like it works), because of deadlines, poor prioritization, new features, bad planning, vague roadmap and poor client management. And the worst of them all, LGTM code reviews.

Few months later, who the fuck wrote this shit? Oh, dude that left? What about this mess? Oh, he's a goner too. What the fuck should this random undocumented chunk of code do?!

Do that a few times and you've got bunch of pissed off clients with a ton of bug reports nobody can solve without wasting 20x the amount of time it would originally take.. LGTM

RIP project.

Stop whining about slow IDEs. If the IDE is running slow its because your shitbox computer is pissing it's pants. Get rich and buy decent hardware or use notepad and imagine the syntax highlight you cheap hook-nosed fuck. Fucking degenerate.

Google wanted to be politically correct and gave faces different colors. But apparently using "black" or "asian" is a shame too so all of these emojies have same name.

This decision was very poor as it's hard to implement this duplicity in frontend so as always Devs choose easiest choice - just use the first one. And first one is always yellow...

Congrats on making whole lazy Dev world using your "correct" emojies enforcing only one face style.

!!!dev

This is !dev at all, buy I think many devs might share a similar way of thinking.

I just had a discussion with a friend. He told me that he donated 100.- to a poor family he met in Thailand and told me about how good he feels because of that.
I told him that I’ve been donating regularly for the last 8 years and that it’s not about how you feel but about the change you made.

We argued for a while and I realized that I’m using my past donations not only to convince him but to win the argument..

I used my deeds to my own benefit, so I’m no better than the TikTok Bitches showing their bodies for likes..

I’m deeply disappointed in myself.

somewhere in this world this happened..

Company lands huge enterprise project
manager: we have a year to get this done.
poor devs : excited and thinks about so much learning with this project it would be.
manager: Lets get work started with (spits planless jargons)...meanwhile another team is working on SRS.
poor devs: So we are doing R&D right..(excited)
manager: No we have a demo scheduled after 15days.
poor devs: What??
manager: Get on it..we need something to show on demo.
poor devs: no words spoken

...after one year of unplanned demos...
manager: we have to stablize project..UAT is nearing.
one of brave poor devs: No no..lets focus on demo...why do you need a stable product.
manager: instant rage

Many "purists" love to piss on JavaScript and web development. And to an extent I can understand ostream’s frustration with these people.
It’s easy to criticize because yes: many web projects are indeed shit.

But I’d like to argue that the reason why so many of these projects are crappy is because of bad management:
- unrealistic deadlines
- no clear testing strategy
- or no testing at all because of deadlines
- no time allotted to catch up on technical debt
- etc.

This type of management is far more commonplace in web projects because things need to get delivered quickly and if they’re delivered with bugs, it’s no big deal as lives aren’t at stake.

I doubt this type of management is tolerated in projects where you’re working on software for welding machines (for example), where the stakes are that "you’re expected not to kill anyone" (to quote demolishun)

So in these types of projects, management can’t tolerate anything much below perfection and thus has to adapt by setting realistic deadlines that take into account the need for quality processes and thorough testing.

If this type of management was more common in web development, I can guarantee that web applications would be much more reliable and of better quality.
I can also guarantee that poorly managed non-web projects as outlined above would be just shitty as many web products.

My point being that’s it’s really DUMB to criticize fellow devs that work with web technologies on the basis that the state of websites/web apps is a mess. It just so happens that JS is the language of the web and that the web is where things are expected to be delivered quickly (and dirty … but we can fix it later mentality)
Stop acting like you’re the elite. I have no doubt you’re super smart and great at what you do. So be smart all the way and stop criticizing us poor webdevs that have to live with the sad state of affairs. ❤️

Atom editor is not great yet but devs already switches to VScode. Looks familiar? Poor web developers...

The worst co worker I had is actually pretty recent. He joined a well integrated team on what was basically a legacy project. He sounded like a good developer and seemed to know his stuff but it took him ages to push out fixes/features. They were always massively over-engineered, poorly named, partially tested and what documentation he did write still managed to bitch about how poor the project was structured.

He spent most of his time bitching about the general shitty nature of the project (he wasn't wrong) and the lack of interest from other Devs.

He was so unpleasant in interpersonal communication that by the end no one would work with him.

In his last team meeting he basically said he was glad to be going and that we were all lazy, disinterested and shouldn't consider ourselves his peers. The equivalent of storming out of a party after setting the couch on fire and shitting in the sink.

We've since removed all his overcomplicated, not standard, unmaintainable code.

I realized something. No matter what tech i use to code a project there will always be a dev to take a shit on it

someone will recommend to use redis, after i use redis some other dev will trash me for having such a poor choice and recommend me socket.io

Then if i use socket.io some 3rd dev will trash me cause thats not the right way of building stuff and recommend me kafka

If i use kafka some 4th dev will trash me and say why i dont use angular

If I use angular 5th dev will trash me for not using react

If i use react 6th dev will trash me for not using nextjs

Tired of this bullshit

I'll use whatever tech i need. If i dont know what to use ill ask and take the first suggestion. I'll just build a saas and when it starts earning money ill pay other devs to refactor and scale the hell hole (which wont be cause i write good code following solid principles and not spaghetti). Much simpler solution than wrecking my head with decisions of tech stack

There was a big hairy ball of SW mud from another project that a poor coworker had to "reuse". Only that it was impossible because there was no documentation, shit was partly auto-generated with mysterious Excel tables, and the actual code was just as bad. No APIs and nothing, just hacking shit into globals, several nested state machines that were overriding each other's states, and with global side effects. WTF.

Two devs took a look at it - minimum 8 weeks. Schedule was some days, and PM insisted that it was "already working". But the worst thing was that the dev in charge had been looking for another job anyway and quit, so the whole clusterfuck suddenly was on my desk.

The code was so awful that I could only bear it with both eyes closed, so I instead read the spec of this project closely. Turned out that it didn't actually demand this feature, only a small subset of what the ball of mud was supposed to achieve - which I was able to implement from scratch within a day, plus another one for documentation. Phew.

When you login to devrant after couple of years and see it as a mature platform for devs to hangout.

Poor you with low rep points on the platform.

There's too many web apps out there that advertise having great accessibility, but whose only claim to that is that they work okay-ish with screenreaders.

There's more to accessibility, darnit! Not just blind people, also remember people with impaired colour perception, people who have to use increased font sizes, people with poor contrast perception (can we please not do light-gray text, links, or buttons on white background anymore?), and many more.

The amount of apps alone that just are impossible to use properly with increased font sizes due to cut-off unscrollable text or buttons pushed out of the visible part of the page is staggering. Or where you get permanently stuck inside a rich-text editor if you can only navigate by keyboard, or where whole parts of the page are impossible to properly use with background images turned off...

I'm aware this might sound unreasonable and I know it's extra effort to learn all the rules, but once these things are not an afterthought, but rather something to take care of starting even during first implementation, it starts to come naturally.

But would it be unreasonable to ask of an architect to not put the restrooms, conference rooms, managers office, where they can only be reached by stairs? I don't think it would be. Sure it makes placing them more complicated, but excluding people from being able to use the building due to circumstances beyond their control feels a bit elitist and snobby to me.

Saw an app last week where a lot of features were behind click-handlers on elements that are not supposed to be interactive like <div>, <li>, and <span> tags. How's someone who can't use the visual clues even supposed to know that the element is interactive?

And yes, there's some of these points where ensuring accessibility is not just the devs job but also the designer's responsibility (contrast rules for example), but in my experience if the devs notice "oh hey, this could be problematic" then the design people usually listen.

Honestly in the case of accessibility I believe that putting off some features for later to make time to ensure that what's there is accessible, even if it only affects 1% of visitors, belongs into the "social responsibility" category, and most clients I've worked with were open to the subject.

I do believe it's something that everyone should take time to learn.

PS: I don't mean to attack anyone, I just wish it were something that more people watch out for.

Yesterday whole 12 hours we were working on deployment about a feature X that has deadline yesterday itself.
Everything damn perfectly running on Test env but not on Prod.
We made Prod into Dev/Test/Fucking garabage env. Haha.
I was laughing to myself at same time crying hard in my deep heart.

Business guys chasing PM
PM chasing us
And from morning till night we were in same room. Had lunch, and dinner only went out for toilet and to refil water bottles.

And found that feature Y is not working at same time that is related to our feature X. Fucking we have been wasted hours on it.

One of my devs got so fucked up emotionally that he messed up the code (not his fault) he didnt had his lunch and dinner. Had to console him later that its not his fault. Poor guy not sure whether he slept or not; will find out in few hours.

Anyways reported a bug.
But that bug assigned to us for fixing.
Are you fucking kidding me.
Anyways no choice. Had to do it.
Hope today everything goes good or horribly bad. FYI no deployments on Friday damn we are in stalememt till Monday.

Fuck that bug
Or
May be fuck our stupiditiy while makiing mistakes.

I had this boss once who called himself a sitting bull sometimes. He was about 60, an absolute dictator, strong right wing and building an aura of fear around him. He had this emberassing macho attitude which was especially delicate since he was a protective of the female ceo. He talked to everyone, colleagues, customers, partners like they where enemys and was extemely aggressive towards everyone. Meetings where extremly emberassing because he insulted everyone (except us devs), talked much bs an didn't let anyone else speak - including customers.

He was also paranoid af. Once he talked the ceo into firing a team lead he disliked. Before the guy got to know this, he called me, and wanted me to sneak in his office, copy everything from his computer in case he would destroy everything when I realized he's fired. As if everything relevant wasn't on GitHub anyway and is if the poor guy would be uprofessional as sitting bull.

The sitting bull lead the department like a ponzi scheme: He required constantly new projects with funding for some years to maintain the old ones and their piles of tech debt. Dev team grew and grew but every insider knew the bubble will explode at one point. One of the last projects was a partner project with another institution. Naturally he didn't want us to do anything for this project but use our man power to rescue older ones. One pm guy was employed fifty percent as ours and fifty at the partner. So while months passt by and we delivered absolute nothing but lame excuses, his other employer started to ask questions. At one point I told him, and told his other employer afterwards, that the sitting bull never intended to anything for the project. When the sitting bull learned the pm. Guy told them the truth he called him a traitor and fired him instantly.

I left shortly after and the bubble imploded eventually. The sitting bull retired after an heart attack. From over twenty dev positions a single one remains and his main job to shit down one broken service after another...

I was watching a video for some dev related tool.

It noted that "if you connect A and B it will automatically find the most efficient path between A and B".

I couldn't help but think about how that line might trigger a lot of well meaning devs to harass these poor people with tickets about "ackshually if you go through these 400 steps it doesn't always pick the 'most efficient' path!"

As another dev I'd be tempted to say "it does a pretty good job picking a reasonably efficient path... mostly, please don't tell me when it doesn't".

But that's why I'm not in marketing.

Finally, I finally got my dream job, but three weeks after starting, I will say I am going into depression.

First, I have to learn a new language (the lang is less than 7 years old) on the job. The language is so different from the paradigm I am used to-from OOP to functional programming, it has very little confusing documentation and a small but growing community.

Though I have been able to show some work, goddamit, it's taking me blood and sand to adjust and be productive.

My onboarding tasks are fixing bugs and implementing a feature, and it has been like walking in a dark tunnel.

I have to face my problem alone as all the devs in the team have swapped.

I rarely sleep, and I recently started to have an existential crisis!

Also, I work part-time on another project, and my output is so poor due to the fact that I am trying to adjust to the new job. Just this evening, I got a call from the manager who was passively aggressive, complaining and asking me to rethink (a passive way of saying "you are fired, if you do not...").

I am feeling anxious. It is taking so much time daily to adjust to the new job.

Will the depression pass?

Worked as frontend on a company that also had backend devs making frontend work. One day we've received a task of redesigning those screens, since their work were poor. Past half of the work is done, the whole team came onto us saying to pause the task since there would be multiple changes into the informations on the screens. That day we lost something like 4 hours of work. Didn't punched anybody though.

Slowly I'm learning not to give a shit anymore. This project I'm on can burn. I'll make progress and help out my fellow devs, but if it takes me longer than estimated to complete my tasks because of the unforeseen technical debt arising from this piss-poor excuse of an application design (plus we're 13 devs working on like 5 different feature branches - God help us with our merge conflicts) then so be it. If my tech lead complains, he can find someone else to take the wheel.

!rant
Experienced devs please tell help me.

Learning software development has been a challenge. Many times it's frustrating.

I also learn languages and I find them to share one trait with software development, which is complexity.

At first I looked at languages the way I'm currently doing with software. I'd look in a new language and after decided it's cool to learn it, I would stare at it for a few weeks trying to realize what the heck I was going to do. I wouldn't even know how to get started.

Eventually this stage goes away and I think that is about to happen with me with software.

But then a new challenge would come, which is me not making progress as I wanted. That's sort of happening with me by learning software as well, bit in language I now know how to deal with it.
That's because I work full time with something that isn't in my interests and when I arrive home Im tired and want to relax. So I decided my language learning had to go slower as long as I have this job, meaning no hours spent in front of books or a pc studying - that's what I could do with English, I was a teenager and had 12 hours a day to do whatever I wanted.

So I usually spent 5 minutes here and there learning something in my target language when I can, no frustration needed, my only rule is: practice everyday, even if I don't learn anything new.

With software, that doesn't apply though.

So, what I mean by tracing a parallel between these to fields is that I have a strong conviction is that once you get the principles on how a certain kind of learning works, you can apply it everywhere in the field. But with software it's been harder.
Anyways, I see that are some principles that apply, cause trying to learn software is changinge and teaching a lot of things like:

*you have to read a lot (of documentation) . At first I thought all documentation was painful to read and understand, but I found out some software are well documented and one can use those only to get used with it.

*immersion / discipline are important. I'm not very disciplined, I'm better with immersion but both are important if you need to acquire complex subjects/skills

*how to deal with complexity. I installed Arch Linux a few days ago. Just to install it I ended up reading more than 20 pages of documentation (install guide, Wpa supplicant, systemd, networkd, xorg, etc etc). Gradually I'm realizing that when you have to install/tweak something in that distro you necessarily spend a bunch of time trying to understand how it works, otherwise you don't get too far like in Ubuntu or Debian.

*and lastly the one that bothers me. Constantly getting frustrated and feeling crap about my poor skills. No matter how much I progress, it still seems like I'm stuck.
(that's when I ask your help/opinion :) )

A lot of you here rant about devs being arogant or expecting you to think for a little bit with own head and then write a proper string that will help dev answer straightforward without guessing what the author smoked or so for which there's even a tutorial made (wasn't there always). But I don't see any rants about the other side of the coin.

Let's say you are a random dude, not even that arogant type. You see a question, no answers, everyone piss on that question because it's just a mess. Yet you find yourself in a good mood, so let's help the poor soul with th trouble. Answer like from a book for kids, fully explained example and...

No points, no accepted answer, but not even any feedback! Was my answer wrong? Did I miss something? How can I improve it? Was the example too complicated?

This is exactly the type of idiot that deserves a kick in the ass. It's no site, for hanging spam! Why the hell does that kind of idiot think there's even an option for own answer? People will come back to the question eventually and what will they found? An answer, which probably isn't even correct!

(not really talking about a specific answer/question, so no need to search)

So I'm tasked with creating a single sign on link using documentation from the third party we are logging into. So far so good.

Well they don't support some of the fields our users will need--that we don't want to support (otherwise why use a third-party?).

Their solution is to make us the system of record so that when a user goes through the single sign on we pass this info as well. But it needs to be editable on their side well--because they won't give us an API for our system of record to update their side.

That's right only a user signing on from our system will update their side. Tough luck admins on our side. You get double duty due to the poor business decision to work with a company with lazy devs.

Damn, .NET devs are really and I mean really bad at writing documentation. It is either over-engineered (anything from Microsoft) to the point you can't find shit. Or it is almost non existent and you have to study the repo and read classes, etc. (ANY .net core nuget for writing CLI apps, heck I would argue almost any nuget in general)

4 pages on github WIKI + examples that cover 20% of use cases are not a bloody documentation mate!!!

I used to be linux + any of Python/Go/JS/Ruby/Elixir guy and almost never had problems with poor documentation.

Now living in Microsoft world with .net and powershell is terrifying.

i wanted some advice on career progression. I am a CS graduate from 2020, have been a decent mobile dev for last 3 years and switched 2 companies so far. i currently have an average ctc (considering i reside in the world's most populated country) as a junior dev.

i want to grow but don't know the next steps. here are my options:

1. stay in the same company . role growth: senior in 2 years , more senior in 4 years . comp growth : avg 10% every year

>> this feels okay-ish path but 10% growth seems very less

2. switch every x years . role growth : unpredictable. comp growth min 30-50%

>> this has been my approach. as i grow bore of a company, i switch . the first time i got a 200% hike, but at that time, i was already earning very less. however companies do not usually take you for a senior role unles you were a senior before, so i think i am losing something here

3. do a masters in tech . comp growth : ? role growth :0
>> this is an unknown territory for me. i haven't heard of anyone bragging about how they did a masters in some tech field and got a better job/position. most people prefer masters in business or do a masters in tech only if they had a poor bachelors degree

4. do a masters in business. comp growth ? role growth?
>> another unknown territory for me. i really wanna consider a managerial position, just because i want to be leading the action , but that's probably because of being a beta guy in all my life and not just the tech/work.

1. managers have a great comp but they also get fired more often than techies. how do you become a good manager/vp/director etc?

2. what are your goals, how do you improve/work upon the goals as a manager?

3. how do you grow as a manager?

honestly i put a lot of tasks and capabilities into one category : the skills of a manager. but i think there might be different roles for such categories. let me know which one is which and if they are worth going into:

1. an x is a person that researches on market trends, other companies, amtheir audience etc and come up with new ideas to implement and improve growth/business of the company

2. an x is a person that makes sure that devs , qa, designers etc are aligned , knows what to do , clears their doubts and ensure the proper functioni5 of the team and timely releases of new features.

3. an x is an ambitious and curious person who can think of new , original ideas.

4. an x is a person with all knowledge of product features.

-----
in all above statements, is x== junior manager? then what are senior manager, vp, directors, president, tech lead, qa,etc?

also how can one start to become x?