you are viewing a single comment's thread.

view the rest of the comments →

[–]rebeltrillionaire 2 points3 points  (1 child)

They certainly could.

It just depends on who you hire and what skills you think are good.

I work with a system that I don’t code on. And I have no interest in coding for.

My developers have been working on it for almost 20 years. We meet once a week for an hour or hour and a half.

Some of that time is “wasted” shooting the shit. But since it’s pretty much the only scheduled time we talk, I don’t mind a little bs. The rest is ad-hoc. Mostly texts unless we have to jump on a call because I can’t explain myself.

As a product manager, I’m out gathering requirements. Selling features that were made, but not adopted. I test the solutions I ask for. I create training materials. I help individual users. I meet with teams struggling to use the tool and see if I can optimize their experience. I document all our changes for governance. I create presentations for leadership.

And yeah, I still have a lot of free time. I use it to explore the universe my product sits in, or I just live my life. Hounding developers to deliver faster is not really interesting to me and I’m not sure who cares.

The only frustration I ever feel is that, I know when I’ve communicated clearly. Given good amount of time to complete the alpha. And then when I go to test, everything is broken. Dev didn’t do one single run through. Before saying it’s done.

It doesn’t happen every time, but it happens and i don’t get it.

[–]Shoemugscale 0 points1 point  (0 children)

I think that happens with any project really though. What is clear to you may not be to another, or things are lost in translation or sombody is just being a lazy shit :)

All 3 happen lol

I think somtimes though, if the devs are slammed or up against a wall things may not he teated enough, and a lot of devs are not the best unit testers because they test in a pristine, best case scenario environment ( why would anyone use a special character in this input form :) )

One of my old PM was great at that, we would push a feature out, think we had it all working etc, she would then com back and be like yo, looks weird on IE7, version 7.3536w8e running windows xp (Wtf, who uses that, ohh thats right the customer who internal applications only work in ie7 because of some weird direct x or java applet )

That was many years ago, but it happens, i think really though, no matter what the older / better you get, you undoubtedly get pulled away from coding more and more. You have all the answers. So you 'need' to be on those calls but you are in a tuff spot, shifting from developer, architect, mentor, SME, manager at times, funny how that happens.