@jestdotty Oh, you're slick, jestdotty!

@cuddlyogre That is evident.

@jestdotty It sparkles like Homer Simpson Sparkles commercial. Although, it doesn't, because it's nicely hidden away on the phone browser.

@Lensflare My idea is not towards memorization, but rather toward finding bugs without the IDE telling me: "hey, here's a syntax error" or "hey, it could be here!".

I was able to successfully find a tricky bug in React using this method, even if it took me 20 minutes.

@int32 Maybe I do, maybe I dooo! He talks bro-speak the whole time and laughs a lot as if everything is dandy and funny... and a fucking smirk on his face too. He's one of those team leads who thinks they can lead but it's all just in their head.

@jestdotty We can talk back but they talk back toxically, which is discouraging.

Hey, well done, Amy.

@jestdotty I used to know someone like that. lol

@jestdotty It's like I'm, paranoid looking over my back, it's like a, whirlwind inside of my head.

It reminds me of what someone told me: at your workplace you must be respected in order to work well.

@kdvps Thrown in the mix.

@BordedDev Yeaaah, stay ahead of the curve, maaan.

@retoor That's usually thrown in the mix, yes.

5. Hotfixes without notice? Kind of red flag. These should always be in careful process and in team agreement. They should remember they are in a team. No respect and poor communication.

6. Poor communication

7. Indeed

8. Liars to keep people from stressing

9. Likely due to too much stress

10. Toxic team

Summary:

Poor team dynamics, power-tripping, poor communication, poor process, poor respect. All signs of toxicity.

1. "stop talking about it" - unnecessarily aggressive and needlessly impersonal. Why not approach you in person; unless they are remote. With the information I have, it sounds narcissistic and power-tripping of him (reminds me of my manager).

2. Yet another toxic behavior, yes. Don't DM things; talk in person, nicely, and don't insult people. This is basics in the company guidelines of any decent company. Things should be evaluated and discussed. The behavior that person shows also reminds me of another colleague of mine who does the same thing. "Hey your code sucks, here take this stfu". I mean, this is not how to work in a team.

3. Not responding; unless too busy for days, then toxic.

4. Overly-encumbered lead or incompetent lead. As a lead, they should be able to manage their time and be responsive to their team.

@retoor Learning.

@jestdotty Itch notchhhhh.

@jestdotty Such foul practices and manipulation! Sounds like your license plate is GORW-1984. lol.

@Lensflare "I poisoned this technology" sounds like a good analogy indeed.

@D-4got10-01 It seems the average has become 1 year. I've been hearing it more and more from people.

@D-4got10-01 That's great to hear!

@jestdotty Employment Disconnect Engineer. jk lol

@retoor Except it makes me fail at projects because I don't master the tech.

@cuddlyogre Something interfering. Hm.

Some guesses: not tested enough/memory set too low in some config.ini

Callback function to escape void hm... so that would mean that function would have to keep bouncing around in memory.

Super relatable.

@Lensflare Interesting. Sounds like some personal problems on their side. Not wanting to cooperate is either a violating of contract terms or violation of agile... though normally the manager should come in between if needed.

@Lensflare Damn straight!

@jestdotty It's still a stochastic system. E-mail management I can understand... but to write an e-mail? Maybe to a super important exec but they don't care anyway. I mean come on, does a person lack the education to write a professional, contextual e-mail? I put too much faith in people. lol