BROADCASTS.com

b'

In this episode, Dave and Jamison answer these questions:

\\n
1. \\n

   \\u200cAbout a year ago I joined what it seemed to be the best company ever.

   \\n\\n

   It\\u2019s a pretty big, pretty successful company which has been fully remote for decades. They have a great work culture where async written communication is the norm. There\\u2019s no scrum, no micro management, no crazy and absurd planning/guessing meetings, etc. Of course we also have some pressure to ship product, but nothing out of the ordinary. Salary is good, work life balance is awesome, I like my team a lot and overall people are awesome too, so this sounds like paradise to me.

   \\n\\n

   However, on the technical side, this is the worst careless outdated bug-ridden untested unmaintainable inscrutable ide-freezing mindblowing terrible wordpress codebase I\\u2019ve ever seen in my life.

   \\n\\n

   No linters, no formatters, the repository is so big you can\\u2019t even open the entire thing on your editor and you need to open just the folders you\\u2019re touching. The development environment is \\u201cscp files to a production server taken out of the load balancer\\u201d. Zero tests, manual QA by a team mate before merging, outdated tooling, outdated processes, css overriden 10 times because nobody wants to modify any existing rule, security incidents hidden under the rug every now and then and the worst part: any attempt to improve this gets rejected. My team laughed at me when I tried to write an acceptance test in my early days. Months later I can see how ridiculous it looks now I have a better grasp of the technical culture over here.

   \\n\\n

   I\\u2019m towards the second half of my career. So \\u201clearning\\u201d and \\u201cstaying up to date\\u201d with the trends is not my priority. I really enjoy this company and love working here until the moment I open my code editor.

   \\n\\n

   I\\u2019m seriously thinking on starting to look for another job, but I have this feeling that wherever I go the code might be slightly better but the perks will be worse. Now I understand why we have these perks, otherwise nobody would be here I guess.

   \\n\\n

   Have you been in this situation, or maybe the opposite one? Not sure what to do at this point.

   \\n\\n

   Thanks!

   \\n
\\n
2. \\n

   My team got a new manager about 6 months ago. While I\\u2019ve had managers all across the spectrum of weird quirks in my time as an engineer, this person has one that\\u2019s new for me, and I\\u2019m not sure how to handle it. He operates in a very top-down fashion, which isn\\u2019t unusual. What is unusual, however, is that he will insist that everyone on the team give him feedback on a given issue\\u2026and then inevitably just proceed with whatever he had decided beforehand.

   \\n\\n

   I take giving feedback very seriously, and spend a lot of time getting my thoughts in order when I\\u2019m asked to give input on something. Having someone request that and then immediately throw my input in the proverbial paper shredder is frustrating and a waste of my time, especially since the team and company are growing rapidly and there are a lot of these kinds of decisions that have to be made. How should I approach this? I don\\u2019t want to keep spending time and effort on feedback that\\u2019s going to be ignored, but I also don\\u2019t know a polite corporate-speak equivalent of \\u201cplease don\\u2019t ask my opinion on this when we both know you\\u2019ve already made up your mind\\u201d.

   \\n
\\n