Details
Joined devRant on 1/7/2022
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Not laughing.
Not cursing.
Both for interviewing and being interviewed.
Some interviews could have been taken straight from a mexican telenovela.......
"Yeah, I worked for a year in the Walmart IT administration."
"Ok, what did you do?"
"Oh I had the high responsibility of taking care of swapping printer cartridges, programming the registers, stuff like that..."
"You apply for a senior database management role, you're aware of that?"
"Yeah. I took a bootcamp for 3 months in the evening after work. I'm up for the job and expect a payment of <lol, even having a stroke while writing a payment check that number will never happen>".
I made that up - but we had these cases... The story is just rewritten and mixed up for obvious reasons.
When I'm being interviewed, the same thing can happen by the way, too.
IMHO a interview is made not only for the company, but for me as an employee, too. I don't sugar coat it. I want to know what type of shit I'm getting into and how much I'm drowning in it.
Some "types" of interviewers react kinda funny when I start roasting them with questions...
For example, the authoritarian type usually reacts with disrespect. How dare u piss on my front lawn.... Kind of reaction. Which makes it hard not too laugh, because who wants to work for someone who throws a tamper tantrum during a interview? Even harder when the same guy promised you heaveb before (the flowery kind of bullshit, like everything's peaceful and fine and teams great and they have such a great leadership...)
Even worse is the patsy.
When you're sitting in an interview and the only answers you get are:
- Sorry, I don't know.
- I'm not allowed to ....
- Not in my area of expertise....
All just nice ways of saying: I will say nothing cause then I'd need to take some responsibility.
:)
The most Mexican telenovela stuff though in being interviewed is when I managed to divide a team of interviewers and it starts to become a "Judge Judy" or similar freaked out justice show...
A: "No, our team doesn't work that way".
B: "But you will in the short future, WE committed to it".
C: "Not that I'm aware of".
And me, an obvious sinner and person who enjoys entertainment and schadenfreude, just keeps adding kerosene to the fire.
"So, it seems like the team of A has its own rules which do not apply to B and C, do they also have greater funding?".
Oh it makes just fun to spur a good blood bath. -
Recipe: "baked developer"
you will need:
- 1 day = 1 story point
- 10SP per sprint
- every team member must deliver all the SPs.
Now for every sprint slap on 20+ hours of mandatory meetings, mix with 2-5 days of ad-hoc tasks, which must be addressed, because they are blocking the release/other teams/prod, and make sure all the devs try not to spill no matter what, and you get a perfectly burned out team.
Brittle/crispy on the outside, mashed/soft on the inside
enjoy!26 -
Stop using anal as a variable or function name wherever I look I see anal_this and anal_that please stop. Use analyze, analyzer or whatever and not anal_insert ( ) or anal_check ()13
-
One thing I've learned repeatedly over the last 20 years is that companies are generally not deserving of your loyalty.
By all means, show up, apply yourself, and do your best work, that's just being a professional. But never get emotionally invested in a company you don't own.
There are really only two reasons for staying: earning or learning, ideally both. Once you have exhausted your current employer's limits in this regard, move on, you don't owe them anything.3