Journal Journal: IANAW
It's amazing. I'm sure no one will ever read this, but it might be a good idea to let this out somehow...
How is it possible for such a innovative, technologically advanced, interesting, and exciting company become practically the complete opposite over the last few months?
I love my job. I am challenged by my job. Everytime something new comes out, I always try to pick it apart, see what makes it tick, and fix or any issues found.
Lately, we've been chastized for this type of behavior. Instead of fixing failover LDAP writes, we have to open a ticket. Then someone else decides whether this should be rolled out to every site. Of course it was decided not to be, even though that means that all other sites now have non-working LDAP failovers.
If we want to write tools, even if those tools will not affect our customers usage of our services at all, we have to submit a reason for writing the tool, send it up the chain, and someone who is not even familiar with the situation or possibly even the need for the tool will unilateraly decide if we're even allowed to work on it. Even if they say yes, it's been 3 weeks and we've really lost our interest by now...
It seems like most attempts to standardize, and review changes is done in a manner that stifles innovation, and makes us want to even go above and beyond the call of duty less and less.
The job is becomming less of a mental challenge, and more of a political one.
There are still many benifits to working where I do. And I make it a point to try and involve myself in every project I can to soak up as much information and learn as many things as possible... But it's becomming more and more limiting what we can and can't do.
Inovation is what got us where we are now, what will we be when it's gone?
How is it possible for such a innovative, technologically advanced, interesting, and exciting company become practically the complete opposite over the last few months?
I love my job. I am challenged by my job. Everytime something new comes out, I always try to pick it apart, see what makes it tick, and fix or any issues found.
Lately, we've been chastized for this type of behavior. Instead of fixing failover LDAP writes, we have to open a ticket. Then someone else decides whether this should be rolled out to every site. Of course it was decided not to be, even though that means that all other sites now have non-working LDAP failovers.
If we want to write tools, even if those tools will not affect our customers usage of our services at all, we have to submit a reason for writing the tool, send it up the chain, and someone who is not even familiar with the situation or possibly even the need for the tool will unilateraly decide if we're even allowed to work on it. Even if they say yes, it's been 3 weeks and we've really lost our interest by now...
It seems like most attempts to standardize, and review changes is done in a manner that stifles innovation, and makes us want to even go above and beyond the call of duty less and less.
The job is becomming less of a mental challenge, and more of a political one.
There are still many benifits to working where I do. And I make it a point to try and involve myself in every project I can to soak up as much information and learn as many things as possible... But it's becomming more and more limiting what we can and can't do.
Inovation is what got us where we are now, what will we be when it's gone?
