Details
Joined devRant on 10/31/2021
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
-
SonarQube reduces our code quality through arbitrary nonsense rules, and it's inability to understand perfectly decent Kotlin code. Unfortunately we have a CTO who is completely enamoured with it. I hope someone from Sonar is reading this: You made my pleasurable Dev job a misery, and it may very well be the thing that makes me quit. Fuck your arrogant product. I honestly wouldn't mind it so much if your UX offered a way to discuss each warning and provide affected code snippets so you could argue your case and collaborate on the rule set. But no, you know my code base best right? Fuck you and and your ivory tower.8
-
Iphone autocorrect is truly revolutionary. I truly need these super common words to constantly be changed to complete nonsense.
"in" to "inn"
"an" to "available"
"do" to "doo" or "dou"
"and" to "abs", "ABCs"
Many, many others.
It took over 20 corrections to complete this simple thought.
Soft locks several times a week so I have to hard restart it in the middle of doing things.
$3500 for a VR headset? Where do I sign up?9 -
Interviewer: Welcome, Mr X. Thanks for dropping by. We like to keep our interviews informal. And even though I have all the power here, and you are nothing but a cretin, let’s pretend we are going to have fun here.
Mr X: Sure, man, whatever.
I: Let’s start with the technical stuff, shall we? Do you know what a linked list is?
X: (Tells what it is).
I: Great. Can you tell me where linked lists are used?
X:: Sure. In interview questions.
I: What?
X: The only time linked lists come up is in interview questions.
I:: That’s not true. They have lots of real world applications. Like, like…. (fumbles)
X:: Like to implement memory allocation in operating systems. But you don’t sell operating systems, do you?
I:: Well… moving on. Do you know what the Big O notation is?
X: Sure. It’s another thing used only in interviews.
I: What?! Not true at all. What if you want to sort a billion records a minute, like Google has to?
X: But you are not Google, are you? You are hiring me to work with 5 year old PHP code, and most of the tasks will be hacking HTML/CSS. Why don’t you ask me something I will actually be doing?
I: (Getting a bit frustrated) Fine. How would you do FooBar in version X of PHP?
X: I would, er, Google that.
I: And how do you call library ABC in PHP?
X: Google?
I: (shocked) OMG. You mean you don’t remember all the 97 million PHP functions, and have to actually Google stuff? What if the Internet goes down?
X: Does it? We’re in the 1st world, aren’t we?
I: Tut, tut. Kids these days. Anyway,looking at your resume, we need at least 7 years of ReactJS. You don’t have that.
X: That’s great, because React came out last year.
I: Excuses, excuses. Let’s ask some lateral thinking questions. How would you go about finding how many piano tuners there are in San Francisco?
X: 37.
I: What?!
X: 37. I googled before coming here. Also Googled other puzzle questions. You can fit 7,895,345 balls in a Boeing 747. Manholes covers are round because that is the shape that won’t fall in. You ask the guard what the other guard would say. You then take the fox across the bridge first, and eat the chicken. As for how to move Mount Fuji, you tell it a sad story.
I: Ooooooooookkkkkaaaayyyyyyy. Right, tell me a bit about yourself.
X: Everything is there in the resume.
I: I mean other than that. What sort of a person are you? What are your hobbies?
X: Japanese culture.
I: Interesting. What specifically?
X: Hentai.
I: What’s hentai?
X: It’s an televised art form.
I: Ok. Now, can you give me an example of a time when you were really challenged?
X: Well, just the other day, a few pennies from my pocket fell behind the sofa. Took me an hour to take them out. Boy was it challenging.
I: I meant technical challenge.
X: I once spent 10 hours installing Windows 10 on a Mac.
I: Why did you do that?
X: I had nothing better to do.
I: Why did you decide to apply to us?
X: The voices in my head told me.
I: What?
X: You advertised a job, so I applied.
I: And why do you want to change your job?
X: Money, baby!
I: (shocked)
X: I mean, I am looking for more lateral changes in a fast moving cloud connected social media agile web 2.0 company.
I: Great. That’s the answer we were looking for. What do you feel about constant overtime?
X: I don’t know. What do you feel about overtime pay?
I: What is your biggest weakness?
X: Kryptonite. Also, ice cream.
I: What are your salary expectations?
X: A million dollars a year, three months paid vacation on the beach, stock options, the lot. Failing that, whatever you have.
I: Great. Any questions for me?
X: No.
I: No? You are supposed to ask me a question, to impress me with your knowledge. I’ll ask you one. Where do you see yourself in 5 years?
X: Doing your job, minus the stupid questions.
I: Get out. Don’t call us, we’ll call you.
All Credit to:
http://pythonforengineers.com/the-p...89 -
"Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live" - J.F. Woods5
-
I had a boss I hated. Couldn’t stand him. Then I got a call saying my dad had collapsed and was at the hospital. I went into his office and told him I had to go because my dad was in the hospital.
“Why are you telling me?” he said. “Get the hell out of here.”
I looked at him quite differently after that.3 -
Developer: We have a problem.
Manager: Remember, there are no such things as problems, only opportunities.
Developer: Well then, we have a DDoS opportunity.53 -
!rant
After over 20 years as a Software Engineer, Architect, and Manager, I want to pass along some unsolicited advice to junior developers either because I grew through it, or I've had to deal with developers who behaved poorly:
1) Your ego will hurt you FAR more than your junior coding skills. Nobody expects you to be the best early in your career, so don't act like you are.
2) Working independently is a must. It's okay to ask questions, but ask sparingly. Remember, mid and senior level guys need to focus just as much as you do, so before interrupting them, exhaust your resources (Google, Stack Overflow, books, etc..)
3) Working code != good code. You are an author. Write your code so that it can be read. Accept criticism that may seem trivial such as renaming a variable or method. If someone is suggesting it, it's because they didn't know what it did without further investigation.
4) Ask for peer reviews and LISTEN to the critique. Even after 20+ years, I send my code to more junior developers and often get good corrections sent back. (remember the ego thing from tip #1?) Even if they have no critiques for me, sometimes they will see a technique I used and learn from that. Peer reviews are win-win-win.
5) When in doubt, do NOT BS your way out. Refer to someone who knows, or offer to get back to them. Often times, persons other than engineers will take what you said as gospel. If that later turns out to be wrong, a bunch of people will have to get involved to clean up the expectations.
6) Slow down in order to speed up. Always start a task by thinking about the very high level use cases, then slowly work through your logic to achieve that. Rushing to complete, even for senior engineers, usually means less-than-ideal code that somebody will have to maintain.
7) Write documentation, always! Even if your company doesn't take documentation seriously, other engineers will remember how well documented your code is, and they will appreciate you for it/think of you next time that sweet job opens up.
8) Good code is important, but good impressions are better. I have code that is the most embarrassing crap ever still in production to this day. People don't think of me as "that shitty developer who wrote that ugly ass code that one time a decade ago," They think of me as "that developer who was fun to work with and busted his ass." Because of that, I've never been unemployed for more than a day. It's critical to have a good network and good references.
9) Don't shy away from the unknown. It's easy to hope somebody else picks up that task that you don't understand, but you wont learn it if they do. The daunting, unknown tasks are the most rewarding to complete (and trust me, other devs will notice.)
10) Learning is up to you. I can't tell you the number of engineers I passed on hiring because their answer to what they know about PHP7 was: "Nothing. I haven't learned it yet because my current company is still using PHP5." This is YOUR craft. It's not up to your employer to keep you relevant in the job market, it's up to YOU. You don't always need to be a pro at the latest and greatest, but at least read the changelog. Stay abreast of current technology, security threats, etc...
These are just a few quick tips from my experience. Others may chime in with theirs, and some may dispute mine. I wish you all fruitful careers!221 -
Nothing pisses me off more than a manager that keeps demanding shit but when you ask for support they deny it from you. well guess what? two can play this game, bitch.2
-
Today I quit my job lol.
In my two previous stories I told you guys about a job offering I got, and after a few more incidents in my old job, I decided I take it.
No, this is not an april fools joke, though it felt quite bad to tell my team lead that I quit on april fools day.
Due to notice period I'll begin my new work at first of july this year, can't wait <33 -
Dealing with non-techy people is annoying.
Dealing with non-techy people who THINK they are techy is even worse.5 -
My wife and I have reached the difficult decision that we do not want children.
If anybody does, please just send me your contact details and we can drop them off tomorrow.2 -
I visited my friend at his new house. He told me to make myself at home. So I threw him out. I hate having visitors.
-
You know what, fuck microshit to fuck town and back again.
What part of disabling "allow the computer to turn of this device to save power"
DO YOU NOT FUCKIJG UNDERSTAND!
MY FUCKING USB'S ARE GOING FUCKING MENTAL SWITCHING ON AND OFF LIKE A DRUNKEN HOBO YOU COCK FUCKS.
my week is a complete and utter shit of a week as it is, I don't need this bullshit on top of it too.
#Microsoft, fix your fucking shit already!4 -
OOP is so ass, classes that extend classes that need objects, of classes that extend classes , passend to their constructor which constructs an object to be given to a constructor of a class that extends a class that implements three interfaces. And in the end it all could have been done with a single function and all of these classes get used a single time.19
-
I fucking want to skin alive my engineering senior director and VP.
Fucking piece of shit people. Looking at their faces from behind the screen, I can sense them stink doneky balls.
They have made my life hell.
The entire tech architecture is absolute shit in nature and engineers cannot even build a single blue colour button without creating a major fuss about it.
Every single aspect of product is built kept in my only the engineer persona. Everyone else can go and suck a racoon's dick.
And they have no concept of tech debt. They just keep building and building stuff. And then build some more.
Entire engineering org is in rush to ship shit at the end of sprint and if they don't then VP and Director are pissed. So to keep those two half witted donkeys happy, these people ship garbage. And all they comment is "cool, very cool".
And hence, entire fucking product is built because it's cool irrespective of whether it solves a problem or not.
A single user role authorisation or authentication is so fucking complex that it would take an eternity for even a developer to figure what's happening.
Fucking toxic human wastes.
There's a company wide mandate to use a certain tech stack, design guidelines, and a vision that all teams have to align. But these faggots are going in opposite direction to do what they feel like and forcing everyone else to ignore all other engagements or alignments with other teams.
These two people should be skinned alive in town square during noon and then left there until they dehydrate entirely. Fucking baboons.
I am so fucking pissed with such mindset.9 -
The most disappointing (not so sure about upsetting) rejection was from none other than Google.
I was ecstatic when Google respond to my application by inviting me to an interview. If I recall rightly I had two pre-interview screenings, two technical interviews, and about four interviews with people. The people were great and the HR person I was dealing with was open that the feedback was all good.
And then the rejection came! I called the HR guy and asked what happened. He said there’s a central group somewhere who approve all hiring and they decided I hadn’t worked for a “big enough” company in the past.
Yet - my potential colleagues and manager thought I could do the job, I passed the Google-scale technical tests … and then some faceless person somewhere says “meh” and that’s that.
It’s not like they didn’t have my resume that whole time, or the opportunity to ask any questions they wanted !
So that sucked.10 -
Being told I’m not experienced enough to get a senior dev job I interviewed for.
Even though I aced the first 4 interview rounds, the tech test feedback was “the best solution they had ever seen”, and I’ve been a senior dev for 25 years.
Time wasting assholes.3 -
I wouldn't say it's upsetting but confusing.
I had an interview at a household name where I asked for feedback. They only told me I did well in the technical and every other area, and that I was the first person they interviewed in the last 2 months to make it passed the technical part.
Less than half a day later I got a rejection email.3 -
uSE AnY pRogrAmMinG L@ngu@g3 yOu liKe.
1nTervi3weRs Do N0t CarE aBouT tHe L@nGuAge.
Fuck you. Stop asking time complexity or space complexity of functional code. No one fucking knows.19 -
If you're a recruiter approaching people on linkedin then don't be a fucking idiot and waste their time, get to the fucking point damn it!
No one's interested in going back and forth with you over email especially when you have their number and could be done with it over a phonecall.3 -
To my review of 2021 ... a good lesson was learned.
I was doing so much for my company.. late night workings.. team handling.. client handline.. to name a few.. But in december they broke my heart.. Altough after little negotiation I was able to get a good package but somehow I Realized this is the time to switch.
But am at good position in my current company so I just cant go away for few pennies. I have to check for company's culture.. my tech stack.. etc too..
But I am determined to get a good job and packge with Challeging tech stack in 2022.
Hope this 2022 Bring brighter future to all of you .. Happy New year