"If you can create technology that solves problems, then you have every right to complain about the problem you solved."
Why complain about something from which you benefited?
Discussion on:
View:
Show:
but then my employer said what we had was good enough..
You might want to get out more.
You might want to get out more.
He wants you to hang out at work, after work, and fix problems you're not getting paid to work on... you know, for shilts and giggles.
Tony has a point, but then again not every company expects miracles with sub-par tools. Our company welcomes innovation and helps innovators get patents or market their project where this is appropriate.
What we don't tolerate is whingeing about an issue without coming up with an alternative. You don't have to code it and commit a 1.0 release; just a concept or napkin drawing will suffice. If we don't engage the company in the solution, we will at least allow you to work on fixing something that bugs you, partially on company time, partially on your own.
Depending on how much personal time was committed and how useful the end project is to the company, we will either:
1) Compensate you and your team for your effort, buying the project outright. We then bring the project into our own offerings or make a subsidiary out of it.
2) Help you through protecting the intellectual property issues with the company owning only the percentage of the project which was done during company time (historically 10-50%).
3) Lay you and your team off and help you spin off your own business to offer your product or service to the world, with our company usually being your first customer.
We have several expressions around here that sum up our culture.
"GOYA" (Acronym for "Get off your a$$")
"Tell me what will work instead of what won't."
"We are about solutions, not problems."
...and my personal favorite, the ten shortest words of greatest power:
"If it is to be, it is up to me."
My point is that corporate culture determines how effectively one is allowed or expected to solve issues. Either way, complaining accomplishes little other than defining the problem. Defining the problem is only the first step in finding and implementing a solution. As with everything else, follow through is everything.
What we don't tolerate is whingeing about an issue without coming up with an alternative. You don't have to code it and commit a 1.0 release; just a concept or napkin drawing will suffice. If we don't engage the company in the solution, we will at least allow you to work on fixing something that bugs you, partially on company time, partially on your own.
Depending on how much personal time was committed and how useful the end project is to the company, we will either:
1) Compensate you and your team for your effort, buying the project outright. We then bring the project into our own offerings or make a subsidiary out of it.
2) Help you through protecting the intellectual property issues with the company owning only the percentage of the project which was done during company time (historically 10-50%).
3) Lay you and your team off and help you spin off your own business to offer your product or service to the world, with our company usually being your first customer.
We have several expressions around here that sum up our culture.
"GOYA" (Acronym for "Get off your a$$")
"Tell me what will work instead of what won't."
"We are about solutions, not problems."
...and my personal favorite, the ten shortest words of greatest power:
"If it is to be, it is up to me."
My point is that corporate culture determines how effectively one is allowed or expected to solve issues. Either way, complaining accomplishes little other than defining the problem. Defining the problem is only the first step in finding and implementing a solution. As with everything else, follow through is everything.
I couldn't always do what was needed but I could always get closer. Writing commercial software for sale, opportunities do not abound.
Not to mention that there are far more problems that can't be solved by coding than can, and of those that are, a horrifying number shouldn't have been...
Not to mention that there are far more problems that can't be solved by coding than can, and of those that are, a horrifying number shouldn't have been...
We cannot instantly transport an object to its destination, and we can't instantly solve all problems or effect drastic change. The concept of mass and inertia apply to organizations as well. While we can't change things instantly, we can move closer by steps, actions, resolutions, projects and influence.
As far as solving issues with pure code, I was always taught that a program is a series of instructions for an adaptable tool. As such, the tool must already be present as well as the process already in place. Software just tweaks and optimizes things to work as good as possible and adapt to changing environments and needs.
As far as solving issues with pure code, I was always taught that a program is a series of instructions for an adaptable tool. As such, the tool must already be present as well as the process already in place. Software just tweaks and optimizes things to work as good as possible and adapt to changing environments and needs.
I agree that coding could save a lot of headaches but 1 doesn't always have time to be coding, which can sometimes be more of a headache
- Keyboard Shortcuts:
- Prev
- Next
- Toggle
