290 karma · joined April 6, 2015
This portal is really nice compared to the previous system, which was send an email to someone and wait for them to get to it. :)
On my projects that have been open sourced, we mostly open sourced to make debugging easier and make extension authoring easier. I've gotten comments from people that that makes them feel easier about vendor lock in, but honestly, I haven't seen many people try and stand up their own service. Would you say that matches your own expectations?
Prohibition didn't end because people missed the taste of alcohol; it was because people kept on drinking (and the illicit nature brought with it the trappings of criminality - corruption, violence, and murder).
Gay marriage bans were hard to "ignore" because it requires cooperation with the government, but anti-sodomy laws were generally ignored until it became comical they were still on the books.
And in general, these kinds of things are the way change happens. The first people at my work switched to git on their own discretion and against the "rules", but it caught on and was productive/popular enough that it's now common practice and no managers ruffle their feathers at the thought.
The phrase is something like - "It's better to ask for forgiveness than for permission". That's because it's easy to say no when asked for permission ("The rules are there for a reason! Tradition!"); if someone has to think about why what you did was wrong, they may come to the conclusion that you were right.
[1] http://blogs.msdn.com/b/techtalk/archive/2005/12/16/504872.a... [2] http://microsoftjobsblog.com/zen-of-pm/
Why do I still do the role? Well, it kind of fits what I wanted to do for a living. I always enjoyed doing lots of diversity in my job and trying all kinds of new technologies out. I get to be a customer for a living. I try out our product and think about where I want it to go. I can be annoying (a real customer would probably be a bit annoying sometimes too, they challenge your product and your hard worked design). I get to care for a living. As an engineer, I could see myself needing to let things go because it's gotta get out the door. As a PM, I know a customer is going to hit that issue and I need to get it in front of people so we can fix it. I'm building applications using our technology and competitors and technology not obviously related just to see if could be relevant.
The problems with PMs vs Engineers is that it is super hard to tell a good PM from a bad PM who is good at politics; but I'm still super happy the role exists. I'd likely have to become an evangelist to do the things I do everyday still, but I'd have less influence with the engineers and it'd often be reactive if I wasn't on the product team. To any people considering a job as a PM, do me and your other future customers a favor and ask if you can care more about your customer than having your job or being promoted? I've held fast to the notion that customers are why I'm here and my career hasn't been too bad so far, management still recognizes good work with customers. But if it all goes to hell, I can always find some other job and be happy with myself.
While, I think there is room to fund content producers in alternate means, I don't think advertising needs to be written out of the playbook. It's just a matter of properly recognizing the cost of violating privacy and the alternatives. I think society as a whole has a bit to learn about the price of privacy.