News for hackers. Stuff that matters.
Re:Red flags I saw while doing technical interviews by _heimdall on Tuesday September 15, 2020 @01:24PM (#24483946)
I worked at Microsoft for a few years and later as a contractor at AT&T for about 2 years. I saw the 2 extremes as far as PMs go.

My PMs at Microsoft were all good at tracking tasks/projects and managing blocking issues. At a minimum they saved me a lot of headache having to answer why a task was late when I was blocked by a dependency. They also had quite a few technical PMs, my brother was actually a PM there before I started after getting his Bachelors and Masters from MIT.

AT&T's PMs were a totally different story. Not only did the PM team outnumber our dev and test teams, most of them were tasked with being product owners for insanely small features. Consider having a PM literally responsible for how a light switch works in home automation, that's the level they broke it down to. Some of the PMs lacked skill or experience, but all were expected to do very little of value and were considered to be successful if they were in meetings nonstop to take notes and give them to the next team in line.

PMs can be vital parts of a tech business, but only when they are given real responsibility and expected to create value rather than countless piles of noted and calendar invites.

Re:Red flags I saw while doing technical interviews by IggleSniggle on Tuesday September 15, 2020 @02:12PM (#24484587)
I had the displeasure of using AT&T's website today and even before I read your comment, I was thinking that AT&T must have a dysfunctional "development by checklists-for-PMs" culture. The site seems like UX appropriate for an SPA, but whenever taking an action, you get redirected 4 or 5 times before landing on the page you intend...only to have some of the elements "lazy" loaded, where "lazy" means "never actually materializes."

And when working through their two-factor-auth process, I kept getting redirected to a version that wouldn't accept my one-time-password because the javascript on the page wouldn't load for some reason. The trick was to switch from Chrome to Firefox.

I wish I didn't understand why it's possible for stuff to exist on big-company websites like AT&T.

Anyway, sounds like an absolute horrorshow for both PMs and devs alike.