Looking for a job
-
I just wonder: is there any job post out there in the multiverse that actually omits the bizarre requirement of "being able to work in a fast-paced environment"? Is that really and honestly regarded as a good thing? Also, is the widespread abuse of empty catchy phrases like this one that make them lose their meaning, or is it that they never had one to start with?
Anything that could possibly go wrong in some moment, will definitely go wrong in the worst possible moment...
In the worst way that could be possible!–Finagle's corollary to Murphy's Law (paraphrased).
-
Find a domain where there are long development cycles; not necessarily in the software itself but in the application of the software. Traditional domains ( engineering, aerospace, banking/insurances..) have long cycles. New domains ( mobile apps, games...) have small cycles.
I'd rather be phishing!
-
Leandro Taset wrote:
that actually omits the bizarre requirement of "being able to work in a fast-paced environment"?
Funeral home? Marc
Imperative to Functional Programming Succinctly Contributors Wanted for Higher Order Programming Project! Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
-
fast paced - work overtime no pay team player - no matter what mess you have to clean after someone, you will not piep self motivated - will work for food etc ect
-
Some environments are more fast paced that others; some require the ability to be able to react quickly. Case in point: I was up in the middle of the night with allergies - sneezing and what not. As I didn't want to disturb my wife, I went to the living room. My cell phone received a text message: a high priority ticket had been logged from work for a system - no data was being shown. Normally, tickets are medium priority unless manually elevated. So, I looked at the ticket, opened my laptop and fixed the issue. I wasn't the team member on call, but I saw the issue and decided to react. As a team, if the issue is not resolved in a timely manner, we all get hit with a performance failure. So.. this was 'fast paced', but, generally, it's an easy going environment. Having said that, if you are looking, what field/general area and what region?
That's not "fast paced" it's "bad employer". If you're not on-call you shouldn't be receiving messages or having to cover for people in the middle of the night. This is exactly what the OP is getting at, employers that are stuck in the 90s and take the mick...expecting their employees to sacrifice all of their time and personal life for the company, usually unpaid.
-
I just wonder: is there any job post out there in the multiverse that actually omits the bizarre requirement of "being able to work in a fast-paced environment"? Is that really and honestly regarded as a good thing? Also, is the widespread abuse of empty catchy phrases like this one that make them lose their meaning, or is it that they never had one to start with?
Anything that could possibly go wrong in some moment, will definitely go wrong in the worst possible moment...
In the worst way that could be possible!–Finagle's corollary to Murphy's Law (paraphrased).
Leandro Taset wrote:
being able to work in a fast-paced environment
This is recruiter speak for "The customer's work environment is so screwed up that they change jobs and tasks on you so fast that you can't keep up".
If it's not broken, fix it until it is
-
Banking can be very different these days... ever work in front office trading environment anyone?
dev
trading is not banking.
I'd rather be phishing!
-
That's not "fast paced" it's "bad employer". If you're not on-call you shouldn't be receiving messages or having to cover for people in the middle of the night. This is exactly what the OP is getting at, employers that are stuck in the 90s and take the mick...expecting their employees to sacrifice all of their time and personal life for the company, usually unpaid.
If I'm not on call, I'm not responsible for covering for other people. I CHOSE to assist a colleague... that is my choice. And fast past is always a relative term; it doesn't have to be break neck speed for all tasks.
-
Banking can be very different these days... ever work in front office trading environment anyone?
dev
nope.
I'd rather be phishing!
-
I just wonder: is there any job post out there in the multiverse that actually omits the bizarre requirement of "being able to work in a fast-paced environment"? Is that really and honestly regarded as a good thing? Also, is the widespread abuse of empty catchy phrases like this one that make them lose their meaning, or is it that they never had one to start with?
Anything that could possibly go wrong in some moment, will definitely go wrong in the worst possible moment...
In the worst way that could be possible!–Finagle's corollary to Murphy's Law (paraphrased).
My favorites are "Must be self starter" "Must work with minimal supervision" Then you get in trouble for actually doing both (and not being a team player.)
-
I just wonder: is there any job post out there in the multiverse that actually omits the bizarre requirement of "being able to work in a fast-paced environment"? Is that really and honestly regarded as a good thing? Also, is the widespread abuse of empty catchy phrases like this one that make them lose their meaning, or is it that they never had one to start with?
Anything that could possibly go wrong in some moment, will definitely go wrong in the worst possible moment...
In the worst way that could be possible!–Finagle's corollary to Murphy's Law (paraphrased).
"fast-paced" requirements are often written by people who work at a snail's pace or are cr@p at managing their time, so they think any job that requires a reasonable level of output is way too fast. Either that, or they're added by morons in HR, who took a course that told them to use phrases like that because it makes the company sound cool.
I wanna be a eunuchs developer! Pass me a bread knife!
-
trading is not banking.
I'd rather be phishing!