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
Search - "rarity"
-
I've been away, lurking at the shadows (aka too lazy to actually log in) but a post from a new member intrigued me; this is dedicated to @devAstated . It is erratic, and VERY boring.
When I resigned from the Navy, I got a flood of questions from EVERY direction, from the lower rank personnel and the higher ups (for some reason, the higher-ups were very interested on what the resignation procedure was...). A very common question was, of course, why I resigned. This requires a bit of explaining (I'll be quick, I promise):
In my country, being in the Navy (or any public sector) means you have a VERY stable job position; you can't be fired unless you do a colossal fuck-up. Reduced to non-existent productivity? No problem. This was one of the reasons for my resignation, actually.
However, this is also used as a deterrent to keep you in, this fear of lack of stability and certainty. And this is the reason why so many asked me why I left, and what was I going to do, how was I going to be sure about my job security.
I have a simple system. It can be abused, but if you are careful, it may do you and your sanity good.
It all begins with your worth, as an employee (I assume you want to go this way, for now). Your worth is determined by the supply of your produced work, versus the demand for it. I work as a network and security engineer. While network engineers are somewhat more common, security engineers are kind of a rarity, and the "network AND security engineer" thing combined those two paths. This makes the supply of my work (network and security work from the same employee) quite limited, but the demand, to my surprise, is actually high.
Of course, this is not something easy to achieve, to be in the superior bargaining position - usually it requires great effort and many, many sleepless nights. Anyway....
Finding a field that has more demand than there is supply is just one part of the equation. You must also keep up with everything (especially with the tech industry, that changes with every second). The same rules apply when deciding on how to develop your skills: develop skills that are in short supply, but high demand. Usually, such skills tend to be very difficult to learn and master, hence the short supply.
You probably got asleep by now.... WAKE UP THIS IS IMPORTANT!
Now, to job security: if you produce, say, 1000$ of work, then know this:
YOU WILL BE PAID LESS THAN THAT. That is how the company makes profit. However, to maximize YOUR profit, and to have a measure of job security, you have to make sure that the value of your produced work is high. This is done by:
- Producing more work by working harder (hard method)
- Producing more work by working smarter (smart method)
- Making your work more valuable by acquiring high demand - low supply skills (economics method)
The hard method is the simplest, but also the most precarious - I'd advise the other two. Now, if you manage to produce, say, 3000$ worth of work, you can demand for 2000$ (numbers are random).
And here is the thing: any serious company wants employees that produce much more than they cost. The company will strive to pay them with as low a salary as it can get away with - after all, a company seeks to maximize its profit. However, if you have high demand - low supply skills, which means that you are more expensive to be replaced than you are to be paid, then guess what? You have unlocked god mode: the company needs you more than you need the company. Don't get me wrong: this is not an excuse to be unprofessional or unreasonable. However, you can look your boss in the eye. Believe me, most people out there can't.
Even if your company fails, an employee with valuable skills that brings profit tends to be snatched very quickly. If a company fires profitable employees, unless it hires more profitable employees to replace them, it has entered the spiral of death and will go bankrupt with mathematical certainty. Also, said fired employees tend to be absorbed quickly; after all, they bring profit, and companies are all about making the most profit.
It was a long post, and somewhat incoherent - the coffee buzz is almost gone, and the coffee crash is almost upon me. I'd like to hear the insight of the veterans; I estimate that it will be beneficial for the people that start out in this industry.2 -
A poor horndog developer started bothering me with useless appreciations like «Oh, a female developer, such a rarity...»
After some chatting he asked me: «How tall are you?»
My answer was: «2FuF8A, find the correct decoding by yourself».
It is "1,67" encoded in Base58 (because Base64 is too mainstream).
He never came back with the solution.9 -
when the moon hits your eye
like a big pizza pie,
that's amore
when a file you don't need
exceeds 50mb,
.gitignore -
My Little Pony, season 1 episode 14, "Suited for Success". Rarity wants to make dresses for her friends, but strives too hard to get it just how they really want it. The project becomes a stressing problem when she tries to make each dress specific to its wearer's taste. Each of her clients has requirements that don't necessarily allign with Rarity's vision, so she has to cope with changing demands and finish them before the Galloping Galla.
Rainbow Dash: I just want my dress to be cool.
Rarity: Do you not like the color?
RD: The color's fine, just make it look cooler.
R: Do you not like the shape?
RD: The shape's fine, just make the whole thing, you know, cooler. It needs to be about 20% cooler.
🎵
All we ever want is indecision.
All we really like is what we know.
[...]
Even if you simply have to fudge it,
make sure it stays within our budget.
🎵
Rarity first makes dresses that she herself loves, but her friends don't, and in the end she makes dresses that her friends love, but she doesn't.
I have sympathy for her.12 -
I think the sleep deprived me is finally cracking under the weight of incompetent assholes.
We just launched a major project in some weird cocktail of Agile slapped with MVP and release to the wild in a waterfall, but it was premature, premature in the sense QA hasn't even finished their side of things, but because some fuck with with "manager" in their title decided they have burnt through the budget with incompetence and scrapped an entire element of the project and outsourced just so they could make a shittier version that doesn't even fucking work.
How hard do you want to fail before you will start listening to the people that now have to work around the fucking clock to clean up this horse shit of a mess.
I'm literally arguing over field mapping with multiple 3rd parties, when the fucking requirements state WTF this is suppose to look like. All because they didn't validate or test their own shit.
Why is EVERY FUCKING cock head in this industry a waste of space and cash! Is it really to much to ask for 1 fucking project to fucking go live that actually fucking works where I don't need to work 2 weeks straight (including weekends) after going live just to be sure that what shit does hit the fan isn't going to create a SEV 1 issue...
Sorry, I'm pissed at the incompetence of others I need to deal with on a daily basis. It's not like this field is insanely hard. A little attention to detail and self validation, verification goes a long way. But clearly that's a rarity.
Once this shit is stable and actually works, I'll be pulling out the mop to clean up half this shit just so it actually works.
Oof, I'm getting to old for this bullshit.4 -
gotta have clear boundaries, specially with phones. I don't even think about code solutions outside of work, i leave that stuff in the office. we're not a "family", I'm not doing anything for love and my extra hours are a rarity.
-
Found my grandmother's Vista laptop from '07. It has 3 problems:
1. Battery lasts 15 seconds at full charge (not a shock)
2. Plastic shell around screen is cracked (not badly, likely fixable with plastic welding)
3. IT'S SLOW AS FUCK
Point 3 is strange, considering the specs:
AMD dual-core CPU at 1600MHz (better than MY laptop...)
Some NVidia onboard GPU thing (no clue)
2x 512MB DDR2-L (immediately swapped out with 1x2GB and 1x1GB, the most we have at the house)
What I noticed, though, is that it's got a SOCKETED CPU (a rarity only like 3 years later), specifically an S1 socket. There's an AMD Phenom quad-core clocked at 1800MHz with that socket, for $16 on eBay no less!
However, it's a different processor family, so I don't know if it'd work in the board...
Anyone think it'd work?9 -
!dev I knew this was true but I'll say it again because I recently was met with this situation again:
Rule: If the interviewer says at the end of your first interview: "We'll see", you didn't get the job.
I'm starting to think that getting a job these days is a rarity..2 -
i am frightened. i have a feeling the only person i can talk about programming stuff twice a year is getting out of touch.
as if the rarity of the talks is not bad enough, our tech stack edges away every time. he is the most intelligent person, yet i see no huge advantages and my strides just raise a shrug. not out of lack of interest but from pure inexperience. we have a long history of joint projects, but i fear the day only he relieves about his webdev experiences with his php-es5-css-stack, while i can not contribute with my knowledge about python- and vba-automation, oop and es6+. as if he would not be able to wrap his head about all this in a blink of an eye.