Quote:
Originally Posted by Katsunami
Indeed. I've often been asked: "Do you have a portfolio?"
A what? Do you think companies are going to GIVE ME code that runs a €100.000+ machine to show to competitors when applying for a job?
|
A chap I ran across elsewhere jumped ship from his previous employer to a competitor. The first thing his new manager asked for was a copy of the source code he'd worked on at his previous employer. Apparently, the rationale for hiring him wasn't to get
him, it was to get access to the competitor's code. When he told the new manager that would be theft and he didn't
do stuff like that, she was displeased...
On a different line, another chap I ran across had a contrarian approach to applying for tech jobs. His application lists capabilities, with a line saying "This is what I can do. I you would like me to do it for you, let's talk." He does
not provide job history or references. If the prospective employer wants those, they can be provided, but they aren't offered up front.
Other folks who hear are horrified at the way he doesn't follow accepted procedure. He just smiles and says "I get two to three sit down with the hiring manager interviews a
week doing it my way."
Quote:
It's embedded software. Apart from a few hardware switches and/or a touch panel on a somewhat bigger machine, you won't ever see this thing. (If a very big machine has an interface on a computer, I probably won't be the one writing that interface; except for maybe the low level code to interface to the machine.)
As you said: if it works, it's invisible. If you're seeing the embedded software somewhere, something has crashed.
|
Yep. Another thing I made a point of doing was to try to identify stakeholders and sit down with them and say "I'll be your sysadmin today. Tell me what you do and what support you
need so I can do a better job of support you.
Sometimes it even works.
______
Dennis