[tamarind8]

What I did say was that I rarely use browser debuggers, because I've just never felt the need to. The console.log and a good mental image of what the code is doing has got me this far.

I asked my boss, that as a senior dev with over 15 proven experience, he should not stress to much about HOW I do it, just WHAT I deliver, and WHEN it is delivered. I guess that was asking for to much? Or being insubordinate? Anyways, I was told my skills, abilities or personality was not the problem, am just not "a good fit". Why? Because I like firefox, and using text editors (vs code) over IDES (visual studio).

[mikro2nd]

It sounds like the tooling was just being used as an excuse, that they'd decided to fire you regardless for reasons that they wouldn't want to articulate because they'd be grounds for legal action. Just guessing, of course, but don't believe ~everything~ anything you've been told. I believe you've already made good choices in this: take a deep breath and move on, having "dodged a bullet" as others have commented. Good luck with your next gig.

[tamarind8]

You get it. I will not be surprised at all if the move to React never happened, and everything is still on angular8 one year from now. So why hire me in the fast place? Because they think they can just hire and then fire someone on a whim? If I don't do something about this, they will do it to someone else.

[Toutouxc]

> If I don't do something about this, they will do it to someone else.

Name and shame then? Don’t know how well this goes with the suing that everyone’s proposing though.

[tamarind8]

Have I named anyone here? Have I shamed anyone here?

All I have said, is I'm going to look into my rights as an employee, and question whether I was treated fairly. Why do you have a problem with that?

[Toutouxc]

You misunderstood my post, that was also a proposal. Like “maybe you should name and shame then?”.

[TylerE]

Console.log and a prayer isn’t exactly the kind of thing I’d like to hear from a dev I’d just hired, tbh.

[tamarind8]

And is that a front end dev? So please tell me exactly, HOW you want your senior front end devs to solve the problems you assign to them. Lets forget about the WHEN and WHAT for now. Just let us know the HOW. Specifically, I mean the IDES or editors you expect them to use, the browsers you want them to test in, the static analysis tools you expect them to use, to unit testing libraries you want them to use, the e2e tools you want them to use, the plugins you expect them to install into there IDEs or editors, the OS they must use, what tools and apps they must use, what must be open in screen one, and what must be open in screen two, what keyboard shortcuts they must use, what snytax highlighting themes they should use dark or light, ... etc

Please, let me know how you micro-manage your senior devs.

[TylerE]

Yeah, you weren't fired for using Firefox. You were fired for acting dickish about it.

[whiddershins]

Honestly: are you a bit argumentative?

If I was in the first few weeks of a job I would try to be receptive to what my coworkers suggest, not win any arguments.

[tamarind8]

> Honestly: are you a bit argumentative?

Not at all. I pick my battles. Some things are worth fighting for, others can be ignored. Not all conflict is bad. Every manager reading this should google "form norm storm perform"

Any senior dev worth their salt should have, and be allowed to have a "storm". We all have our experience, and the paths we followed to get that experience. If a companty thinks your experience and path is useless to them, why would they hire you in the first place?

[tamarind8]

Actually, I think I was a bit too accommodating.

I let a fellow dev fully set up my dev box twice. The second time I did tell him lets do this later, I really want to work on that first ticket but he just kept on typing, ignoring me. I shoudld have grabbed the keyboard from him the moment I realized he was deleting my current ubuntu WSL setup. Guess I just kept silent in the spirit of "being receptive to what my coworkers suggest". Little did I know that my boss would decide that this means i don't know anything.

[quickthrower2]

I sort of agree with you: if I am reaching for the debugger I know I am in trouble! It is good for ... well ... bugs - things that got past QA and are hard to pin down. It is also good for CSS "hacking", as in why won't it work so let's play with different CSS settings.

[tamarind8]

I most definitely use the browser dev tools extensively. The debugger is just one of those tools, and it simply does not apply when it comes to CSS. The debugger is for JS bugs.

[bombolo]

Some bosses want to control which fingers you use when typing.