Although sometimes it is not easy to solve problems. And i feel particularly bad (up to the point of hardly getting any sleep) when i made a design error or an error in a library component, i do like my job.
Hate doing that, especially when it's a screw-up that causes problems in the shop, basically rendering many hours of someone else's work useless and costing the company money. (We've got a decent profit sharing program too. Some of the losses do indeed trickle down.)
It never gets boring. And when i am able to understand after measuring and deducing, and to solve the problem it really is a huge braingasm and relief. :awe:
Like wanting the champagne and the women.
I like working on the same location. Locating around i hate.
What kind of stuff do you do? "library" and "component" make me think some kind of electronic design?
I'm in a mix of electrical and mechanical design myself.
I know I've done a good job of designing and drawing something when I send drawings to the shop and the product can be built without hearing a peep from them.
Some older designs that I inherited and had to fight with would result in at least one visit a week from someone in the shop. Something didn't fit, something was difficult to assemble, and so on.
edit :
And it is really nice to be able to discuss with colleagues a problem and solve it.
Not being alone in solving a problem can really help sometimes.
Although, when i am working my way in a methodological manner to a solution... I prefer to work alone.
"You're god damn right."
The brain-train doesn't work well when it's interrupted every 5-10 minutes.
It's nothing short of astonishing how much I can get done when I'm left alone versus having to attempt to remember what I was doing several times an hour, which gets worse when one interrupting task rear-ends another interruption that's been lodged into the queue.
Programming: Discussing it can also be helpful. One of the programmers here will explain his latest projects to me sometimes, and he'll go on for quite a long time, and I sometimes can't follow. But it's very helpful for him: As he's organizing his thoughts to explain it to me, he also figures out problems in the process. And sometimes my occasionally-clueless questions lead to new ideas. I figure that the use of my time in listening results in a net benefit to the company of having better code.
As I'm writing a bit of code myself, sometimes I'll break from it to re-read my own theory of operation writeup to make sure that 1) it's still applicable, and 2) that I didn't forget something or mix up some requirements.
When i run out of ideas, i like to talk to people for fresh input and search the local information library or the internet.
Yeah, I do also have to live with the fact that other people can indeed be useful sometimes.
I have a habit of trying to find elegant and sophisticated solutions to problems...partly so that they aren't as boring. (I do not like to have an idle mind at work. I did that back when I worked at Walmart and at a warehouse. No thank you, not again. Not for me.)
Some people solve problems with a hammer, and if that fails, they use a screwdriver and a much bigger hammer.
Sometimes that approach can be surprisingly effective; I can take that feedback and input and apply it back to the design.
"A cannon is useful and all that, but they're expensive and take specialized ammunition and chemical mixtures. Have you considered tying pointy rocks to sticks and throwing them? I think that'll still get the job done."
.