Still one of my favorite stackexchange question.

One week, and it turned out to be worse than that.

I was put on a project for a COVID-19 program in America (The CARES Act). The financial team came to us on Monday morning and said they need to give away a couple thousand dollars.

No big deal. All they wanted was a single form that people could submit with some critical info. Didn't need a login/ registration flow or anything. You could have basically used Google Forms for this project.

The project landed in my lap just before lunch on Monday morning. I was a junior in a team with a senior and another junior on standby. It was going to go live the next Monday.

The scope of the project made it seem like the one week deadline wasn't too awful. We just had to send some high priority emails to get some prod servers and app keys and we were fine.

Now is the time where I pause the rant to express to you just how fine we were decidedly **not**: we were not fine.

Tuesday rolls around and what a bad Tuesday it was. It was the first of many requirement changes. There was going to need to be a review process. Instead of the team just reading submissions from the site, they needed accept and reject buttons. They needed a way to deny people for specific reasons. Meaning the employee dashboard just got a little more complicated.

Wednesday came around and yeah, we need a registration and login flow. Yikes.

Thursday came and the couple-thousand dollars turned into a tens of millions. The amount of users we expected just blew up.

Friday, and they needed a way for users to edit their submissions and re-submit if they were rejected. And we needed to send out emails for the status of their applications.

Every day, a new meeting. Every meeting, new requirements that were devastating given our timeframe.

We put in overtime. Came in on the weekend. And by Monday, we had a form that users could submit and a registration/ login flow. No reviewer dashboard. We figured we could take in user input on time and then finish the dashboard later.

Well, financial team has some qualms. They wanted a more complicated review process. They wanted roles; managers assign to assistants. Assistants review assigned items.

The deadline that we worked so hard on whizzed by without so much as a thought, much less the funeral it deserved.

Then, they wanted multiple people to review an application before it was final. Then, they needed different landing pages for a few more departments to be able to review different steps of the applications.

Ended up going live on Friday, close to a month after that faithful Monday which disrupted everything else I was working on, effective immediately.

I don't know why, but we always go live on a Friday for some reason. It must be some sort of conspiracy to force overtime out of our managers. I'm baffled.

But I worked support after the launch.

And there's a funny story about support too: we were asked to create a "submit an issue" form. Me and the other junior worked on it on a wednesday three weeks into the project. Finished it. And the next day it was scrapped and moved to another service we already had running. Poor management like that plagued the project and worked in tandem with the dynamic and ridiculous requirements to make this project hell.

Back to support.

Phone calls give me bad anxiety. But Friday, just before lunch, I was put on the support team. Sure, we have a department that makes calls and deal with users. But they can't be trained on this program: it didn't exist just a month ago, and three days ago it worked differently (the slippery requirements never stopped).

So all of Friday and then all of Saturday and all of Monday (...) I had extended panic attacks calling hundreds of people. And the team that was calling people was only two people. We had over 400 tickets in the first two days.

And fuck me, stupid me, for doing a good job. Because I was put on the call team for **another** COVID project afterwards. I knew nothing about this project. I have hated my job recently. But I'm a junior. What am I gonna say, no?

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.

The company I interned at last summer decided to adopt a JS framework a little over a year ago. The managers went with the old Angular 1.x because they didn't want a JS build process. Each page has ~100 script tags on it, and these are manually included in various files (no automated way to include dependencies). None of the CSS/JS files are minified, either.

They really should have chose Angular 2+, or an entirely different framework (React, VueJS). They're also just now upgrading the codebase from PHP 5.6 to PHP 7.2 (5.6 support ended a long time ago, and security support ends this month).

I love the company itself but these practices are poor.

I may be working there full time eventually. I hope to eventually help with the inevitable transition to a newer framework once Angular 1.x is dead since I am an avid user of newer JS technologies. Any tips on convincing manager(s) towards newer technology? (Or at least convincing them to combine+minify these files in production to reduce # of requests and bandwidth.)

Also this company's product has millions of active users.

Got it in WhatsApp...😃😂😂
I am sure you will have a laugh too

A wealthy manager was driving in his car when he saw two men along the roadside eating grass. Disturbed by the sight, he ordered his driver to stop and he got out to investigate. He asked one man "Why are you eating grass?"

"We don't have any money for food," the poor man replied. "We have to eat grass." "Well, then, you can come with me to my house and I'll feed you" the manager said.

"But sir, I have a wife and five children with me. They are over there, under that tree".

"Bring them along," the manager replied. Turning to the other poor man he stated, "You come with us also."

The second man, in a pitiful voice then said, "But sir, I also have a wife and seven children with me!"

"Bring them all, as well," the manager answered.
They all entered the car, which was no easy task, even for a car as large as it was.

One of the poor fellows turned to mr. Manager and said, "Sir, you are too kind. Thank you for taking all of us with you."

The manager replied, "Glad to do it. You'll really love my place; the grass is almost 1 meter high!"

Lesson: Never trust managers... They will take u to any extreme to finish their job.

And there is nothing like KIND MANAGERS 😜

Dedicated to all managers and upcoming managers 😂😂😂😂😂😂😂😂😂LOL😜😡😡

All the noob jokes about "tee hee I write such bad code exdee" fucking drive me nuts.

There are absolutely such things as good codebases, in any language. By posting "tee hee funny relatable" "memes" about your shitass code you just make yourself look like a fucking idiot who excuses poor quality with "haha so relatable!" bullshit excuses.

Thank you for being the literal cancer of the industry, oversaturating the markets and making all of our managers think we're fucking idiot babies that have to be wrangled like cats in order to get a single feature out the door, devoid of rational thought or a modicum of expertise.

Fuck you. You're the problem. Be better or find another profession where slacking off is acceptable.

> 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.

Junior engineer asking managers on Slack about prioritisation..

Junior eng: Hey managers, I have these tasks A & B lined up and some other type of work... Is it ok if I finish A by Weds and B by the end of week or should it be done sooner? Also, is the order fine or should I prio B first?

*silence for hours*

Random dev feeling bad for junior getting no response chips in: Hey, you are doing great, that order makes sense to me and let me know if you need any guidance or have questions!

Junior dev: Thaanks and will do!

*another hour goes by*

Manager: Hi team. I have asked other engineer X to do task B tomorrow.

what the fuck. at least answer the fucking question and say it needs to be done sooner. felt bad for poor junior here. :/

I no longer work for a startup company. On Monday I’ll start work for a real company, one that values project managers and their infrastructure. As a DevOps engineer, I value the IT resources that power my old companies SaaS platform. My old position is not being back filled and they’re hiring a full time dev instead of and Ops engineer. They have chosen to proceed with zero employees who know Azure or the platform their own software runs on.

Word to the wise when choosing to work for a startup. Ask these questions:

- Do they have a dedicated product manager/owner , who isn’t also the CFO?

- Do they value infrastructure and their IT resources ?

- Do they have decent powered laptops to work with?

- Do they have too much technical debt because they’re always building new features ?

- Do they work 18 hour days because they set poor work/life boundaries ?

- Who handles Support tickets , and what’s a typical support issue like?

- Do they have a branching and merging strategy? Don’t accept “we’re too small” as an answer! It’s a trap that they don’t want one.

What are the chances that you get busted by your manager and 3 team leaders you personally know when you are going to a job interview?

We have poor men’s silicon valley near universities. Our company’s one office moves to another university. By the one in a million luck, interview takes at the same building where our next office of my current company will be. Managers and team leaders are there to inspect the new office. I enter the building, see them near elevator. One of them see me, with panic i wave my hand to him. There is a distance of ten meters, I hide behind a column. The team leader who sees me waving thinks I am with them to inspect new office. He asks others why am I not coming with them as I learn later. I can not pretend to play along and catch up with them, due to panic and time of interview is soon already. They get into elevator and finally I dont have to hide anymore 😂.

I got into interview and c++ exam with that physcology. Little did they knew that I just completed CPP PRIMER book. I both rock interview and exam but lets see if they will return with a job offer. What a rollercoaster of emotions.
Note: I am on mobile now so can not give more juicy details for now, fingers are tired.

2 hour meeting to brainstorm ideas to improve our system health monitoring (logging, alerting, monitoring, and metrics)

Never got past the alerting part. Piss poor excuses for human being managers kept 'blaming' our logging infrastructure for allowing them to log exceptions as 'Warnings', purposely by-passing the alerting system.

Then the d-head tried to 'educate' everyone the difference between error and exception …frack-wad…the difference isn't philosophical…shut up.

The B manager kept referring to our old logging system (like we stopped using it 5 years ago) and if it were written correctly, the legacy code would be easier to migrate. Fracking lying B….shut the frack up.

The fracking idiots then wanted to add direct-bypass of the alerting system (I purposely made the code to bypass alerting painful to write)

Mgr1: "The only way this will work is if you, by default, allow errors to bypass the alerting system. When all of our code is migrated, we'll change a config or something to enable alerting. That shouldn't be too hard."
Me: "Not going to happen. I made by-passing the alert system painful on purpose. If I make it easy, you'll never go back and change code."
Mgr2: "Oh, yes we will. Just mark that method as obsolete. That way, it will force us to fix the code."
Me: "The by-pass method is already obsolete and the teams are already ignoring the build warnings."
Mgr1: "No, that is not correct. We have a process to fix all build warnings related to obsolete methods."
Mgr2: "Yes. It won't be like the old system. We just never had time to go back and fix that code."
Me: "The method has been obsolete for almost a year. If your teams haven't fixed their code by now, it's not going to be fixed."
Mgr1: "You're expecting everything to be changed in one day. Our code base is way too big and there are too many changes to make. All we are asking for is a simple change that will give us the time we need to make the system better. We all want to make the system better…right?"
Me: "We made the changes to the core system over two years ago, and we had this same conversation, remember? If your team hasn't made any changes by now, they aren't going to. The only way they will change code to the new standard is if we make the old way painful. Sorry, that's the truth."
Mgr2: "Why did we make changes to the logging system? Why weren't any of us involved? If there were going to be all these changes, our team should have been part of the process."
Me: "You were and declined every meeting and every attempt to include your area. Considering the massive amount of infrastructure changes there was zero code changes required by your team. The new system simply worked. You can't take advantage of the new features which is why we're here today. I'm here to offer my help in any way I can with the transition."
Mgr1: "The new logging doesn't support logging of the different web page areas. Until you can make that change, we can't begin changing our code."
Me: "Logging properties is just a name+value pair dictionary. All you need to do is standardize on a name and how you add it to the collection."
Mgr2: "So, it's not a standard field? How difficult would it be to change the core assembly? This has to be standard across all our areas and shouldn't be up to the developers to type in anything they want."
- Frack wads smile and nod to each other like fracking chickens in a feeding frenzy
Me: "It can, but what will you call this property? What controls its value?"
- The look I got from both the d-bags I could tell a blood vessel popped.
Mgr1: "Oh…um….I don't know…Area? Yea … Area."
Mgr2: "Um…that's not specific enough. How about Page?"
Mgr1: "Well, pages can cross different areas, and areas cross different pages…what do you think?"
Me: "Don't know, don't care. It's up to you. I just need a name."
Mgr2: "Modules! Our MVC framework is broken up in Modules."
DevMgr: "We already have a field for Module. It's how we're segmenting the different business processes"
Mgr1: "Doesn't matter, we'll come up with a name later. Until then, we won't make any changes until there is a name."
DevMgr: "So what did we accomplish?"
Me: "That we need to review the web's logging and alerting process and make sure we're capturing errors being hidden as warnings."
Mgr1: "Nooo….we didn't accomplish anything. This meeting had no agenda and no purpose. We should have been included in the logging process changes from day one."
Mgr2: "I agree, I'm not sure why we're here"
Me: "This was a brainstorming meeting as listed in the agenda. We've accomplished 2 of the 4 items. I think we've established your commitment to making the system better. Thank you all for coming."

- Mgr1 and 2 left without looking at me or saying a word.

I worked with this hack of a backend dev that was too lazy to add a complex(ish) object to our CMS tool. His solution?

One giant-ass text box with the label "put JSON here".

If tech people were using it I wouldn't mind, but our poor content managers have no idea what json is. Plus like... no examples, no schema... they would have to change shit then go look at the website to see if it worked. Fucking asshole.

Plus.. I mean SHIT, MAN! This was in a Node.js tool... if you have the Json parser you could just GENERATE the respective form fields. DO YOUR JOB

It's funny how you start feeling bad for the next dev taking over your project because it turned into a total spaghetti code shit show that will be impossible to maintain in the future with new features coming in.

Honestly... if a projects starts out with a certain scope which then gets extended EVERY FUCKING WEEK with requirements that can't even be met in the initial timeframe it's no wonder the code quality will decrease over time.

This just reminds me daily how important good project management (and I'm not talking about suit wearing pain-in-the-ass-managers) and the inclusion of devs in the planning process really is.

It's so fucking crazy that companies run like that with people up front that have NO FUCKING CLUE what they are doing, nor do they understand the mechanics, tech and effort that go into certain features. They're like "beep, boop, it's done by Friday you fuck!".

The funniest part of this stupid charade is that the closer we get to a new "deadline" (we will not meet the deadline anyways) the more nervous the "managers" get. WHY didn't you properly plan this shit in the first place? WHY didn't you care for the last six months where all this fucking bullshit could still have been prevented?

Meanwhile I'm just so sick and tired of this shitty project and this sucky company that I just don't have any motivation left to keep on working. It's so fucking hard and painful to work on projects that suck ass, are poorly designed. I just got to the point where coding is no fun any more. Thank god I'm out of here soon... fml

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

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.

I just got scammed in web3. Again. Luckily by following an extremely strict risk management i lost $25.

But apparently now i have to be even more strict and be rigorous to the extremes.

"Pay me up front payment and ill start" Fuck you. Fuck all of you requesting for an upfront payment.

Do you think in the real world when you get hired at ANY job, do you think you're paid up front even a fucking dime? NO. You start working and get paid 1 whole ass Fucking month LATER. But only in web3 do these shitholes ask for an "uP fRoNt pAyMenT s0 i cAn StaRt wOrkiNg". No. Fuck you. I hope you get a fucking cancer and choke on a dead ape's dick.

How Fucking PATHETIC does your poor miserable waste of life have to be to scam someone for just $25? What the fuck?

Web3 is FULL, actually full is a compliment so I'll say it this way: Web3 is OVERLOADED AND OVERFILLED WITH FUCKING SCAMMERS. They're dripping EVERYWHERE. DMs. Discord. Twitter. Fake profiles. Fake messages. Fake cloned websites. Fake scam influencers. Fake marketers. Fake collab managers. Lies deception and exaggeration of results. Or even if it's the original collection, it's probably still a scam.

I don't know what to fucking do no more.

OH have i mentioned Web3 influencers? Oh my fucking god. These influencers on twitter for web3 are the most narcissistic, egocentric, arrogant, RUDE and EXTREMELY disrespectful as fucking pricks they are. I can not lead a normal conversation with ANY of them without them offending me because i dont want to give them my hard earned money right away. Fuck you. FUCK YOU. I HOPE YOUR WHOLE FAMILY DIES IN CAR CRASH FUCKING LOSERS.

Instead of focusing on building in web3 and developing software im now stressing 90% of the time about potential scammers and focus on being careful not to get scammed......

The amount of TOXICITY in Web3 is EXTREME. This is so Fucking ANNOYING and mentally EXHAUSTING

Oh here's a good one. When the managers realised one of our apps is a giant hunk of crap that wasnt thought through at all and was lazily thrown together, and their solution is "meh let's just rewrite it in Swift on our new platform. And those other guys can maintain the old one and continue to do hotfixes for it until we are done".
I've been telling them for the past year that its the worst codebase I have ever seen and the lack of tests is disgusting and not something we should dare to release to paying customers (especially when those customers work in healthcare!!!). The best part was when one of them promised we would all be working on the new shiny platform by Christmas. That was last year. And I'm currently the poor bugger doing the legacy maintenance and in the process of trying to get moved to a new project. So much for managers promises amirite...

Recently I stumbled upon some articles on the internet claiming you could use window managers on the windows subsystem for Linux. I got a tad too excited, left what I was studying (today I regret it, I just finished a test I didn't know shit about), and started sudoing apt-get install the fuck out of my terminal. Downloaded an X server for Windows and pressed i3 on the terminal.

The server's window was black, but I knew everything was ok, so I pressed alt+enter. My poor eyes melted on the presence of the brightest, whitest terminal window I've ever seen. I must admit I felt really disgusted by the white, but that didn't matter, I had fucking i3 running on my windows laptop. Now when I get home I'll try to fix the dbus problem that prevents gui programs from starting and make everything look pretty. I hope it works!

tldr: I burned my eyes with a white terminal.

It's the small things. Chronos task run syntax:

- P10M = 10 months
- PT10M = 10 minutes

And for some reason, lots of our task are defined to only run every 10 months, should be run every 10 minutes though.

Even weirder: Why do most of our tasks run daily? Either we have some cron job task firing curl requests at chronos rest api, or some poor content managers clicks a button daily.

Why do they demand 12-month goals when we use Agile Methodologies?
If we do it right, we don't know what we are working on next sprint, let alone 12 months.
Our goals are to work on the highest priority stories. We are not to work on stuff "in the background", so how can we have any long-term goals?
The only things we can plan are outside of our actual jobs (like conferences, training, pilot programs/hackathon projects, etc.) So the only things we can review at the end of the year are not the most important things we do.
Poor managers love numbers and checklists to hide behind.

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?