4 ms·
Wouldn't coding up a prototype be more in line with asking for permission? You code up the prototype to demonstrate your idea then ask your team if you can proc
by weavie 8y ago
Wouldn't coding up a prototype be more in line with asking for permission? You code up the prototype to demonstrate your idea then ask your team if you can proceed with it. I would say that's a solid, proactive way to get your ideas across.
- isostatic 8y agoBetter to spend 4 days working up a prototype than spend 4 days trying to persuade people to let you work up a prototype
- organsnyder 8y agoDepends on your working environment. At my current position, if I code up a prototype during work hours, I'm subverting our EPMO, since it's not an approved project. I've had great success doing various prototypes like this, but I am not waiting for permission to do them. Bringing those prototypes to production is another matter. In any organization, there are processes that need to be followed to onboard a new application, platform, pattern, etc. If those aren't followed, the implementation won't be nearly as effective—especially long-term.
- weavie 8y agoWhat is an EMPO? Indeed production is another matter.. "I'll just slip in this new crypto routine I wrote and ask for forgiveness later..."
- organsnyder 8y agoOops—should have been EPMO (enterprise project management office).
- weavie 8y agoHmmm... What is an enterprise project management office?
- rhapsodic 8y ago> Hmmm... What is an enterprise project management office? It's the office responsible for processing TPS reports.
- 0xfeba 8y agoIt sounds like a normal project manager/owner but with with the bureaucracy turned up to 11.
- organsnyder 8y agoPretty much. They're responsible for managing the project pipeline, prioritizing, sequencing... Basically, they're meta-PMs. This is at a 25,000 employee healthcare system. Bureaucracy is inevitable, but agility is still essential.
- bendixso 8y agoIn some work environments, you are encouraged to get 40 hours a week, regardless of whether those 40 hours are necessarily put towards what are perceived as the "highest value" endeavors. So if you are blocked on everything else, why not take the remaining time and put it towards things you personally believe to be beneficial to the project? It is certainly better than sitting on your thumbs or asking people who are already busy what they think you should be doing.
- JustSomeNobody 8y agoIs this work in lieu of your regular tasks? If not, clearly you don't have enough to do. If so, that's grounds for dismissal. Unless, you got permission...
- matthewmacleod 8y agoYou must work at an awful organisation.
- JustSomeNobody 8y agoWait, there's organizations that let devs spend hours on a prototype in lieu of their normal work?
- Harvey-Specter 8y agoWasn't Google famous for giving devs 20% play time to work on whatever passion project they wanted?
- weavie 8y agoThat is my normal work. Our manager doesn't have a clue how systems work, so it's up to us to find the best way. I know the various areas we need to develop to push the system forward and it is up to me to find the best way to do it. If I learn something new that makes me rethink something, then I am more than welcome to revisit it and try out some new things. If it ends up with a better system then we all benefit. At the end of the day the work that needs to get done does get done. Obviously I do have to use my judgement to allocate time appropriately. If there is a customer screaming at accounts because they were overcharged or whatever, then it is quite obvious I need to resolve that issue rather than work on a new way to style our buttons, but for the majority of the time it is up to me. I do also spend quite a lot of my own time working on various things where it is a bit ambiguous as to whether it is 'proper' work or not. I enjoy the work I do because I don't feel like I am working in a sweat shop.. Maybe I'm just lucky to have always found a job where management trusts the developers.
- 8y ago