Details
Joined devRant on 2/15/2019
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
-
Avoid face to face meetings, have con calls
Avoid con calls, have email chains
Avoid email chains, do one on one mails
Avoid mails, text
Ignore texts -
People here working your own business or side hustle:
1) How long have you been doing it?
2) What kind of tech stack do you use in your product(s)?
3) Are you happy with your business endeavor or has the grass become greener elsewhere?
4) What is the most important thing you have learned from it that you wish you knew when you began?2 -
Recruiter: Hi, i'm recruiting for xyz, your profile looks like a great fit. Would you be interested in discussing further?
Me: Hi, your company website says you only have an office location in Berlin. I've marked my profile as not interested in relocation, only interested in jobs in my country and said the same in my description. Are you expanding to my country?
Recruiter: You are correct, this role is based in AMAZING Berlin. Are you interested in relocating?
Me:19 -
Fucking developers putting emojis in their code!
My terminal (st) doesn't support displaying emojis and it crashes immediately once it read an emoji. I have been chasing crashing bugs for weeks and I just found out where the issue is.19 -
My team handles infrastructure deployment and automation in the cloud for our company, so we don't exactly develop applications ourselves, but we're responsible for building deployment pipelines, provisioning cloud resources, automating their deployments, etc.
I've ranted about this before, but it fits the weekly rant so I'll do it again.
Someone deployed an autoscaling application into our production AWS account, but they set the maximum instance count to 300. The account limit was less than that. So, of course, their application gets stuck and starts scaling out infinitely. Two hundred new servers spun up in an hour before hitting the limit and then throwing errors all over the place. They send me a ticket and I login to AWS to investigate. Not only have they broken their own application, but they've also made it impossible to deploy anything else into prod. Every other autoscaling group is now unable to scale out at all. We had to submit an emergency limit increase request to AWS, spent thousands of dollars on those stupidly-large instances, and yelled at the dev team responsible. Two weeks later, THEY INCREASED THE MAX COUNT TO 500 AND IT HAPPENED AGAIN!
And the whole thing happened because a database filled up the hard drive, so it would spin up a new server, whose hard drive would be full already and thus spin up a new server, and so on into infinity.
Thats probably the only WTF moment that resulted in me actually saying "WTF?!" out loud to the person responsible, but I've had others. One dev team had their code logging to a location they couldn't access, so we got daily requests for two weeks to download and email log files to them. Another dev team refused to believe their server was crashing due to their bad code even after we showed them the logs that demonstrated their application had a massive memory leak. Another team arbitrarily decided that they were going to deploy their code at 4 AM on a Saturday and they wanted a member of my team to be available in case something went wrong. We aren't 24/7 support. We aren't even weekend support. Or any support, technically. Another team told us we had one day to do three weeks' worth of work to deploy their application because they had set a hard deadline and then didn't tell us about it until the day before. We gave them a flat "No" for that request.
I could probably keep going, but you get the gist of it.4 -
As a developer, sometimes you hammer away on some useless solo side project for a few weeks. Maybe a small game, a web interface for your home-built storage server, or an app to turn your living room lights on an off.
I often see these posts and graphs here about motivation, about a desire to conceive perfection. You want to create a self-hosted Spotify clone "but better", or you set out to make the best todo app for iOS ever written.
These rants and memes often highlight how you start with this incredible drive, how your code is perfectly clean when you begin. Then it all oscillates between states of panic and surprise, sweat, tears and euphoria, an end in a disillusioned stare at the tangled mess you created, to gather dust forever in some private repository.
Writing a physics engine from scratch was harder than you expected. You needed a lot of ugly code to get your admin panel working in Safari. Some other shiny idea came along, and you decided to bite, even though you feel a burning guilt about the ever growing pile of unfinished failures.
All I want to say is:
No time was lost.
This is how senior developers are born. You strengthen your brain, the calluses on your mind provide you with perseverance to solve problems. Even if (no, *especially* if) you gave up on your project.
Eventually, giving up is good, it's a sign of wisdom an flexibility to focus on the broader domain again.
One of the things I love about failures is how varied they tend to be, how they force you to start seeing overarching patterns.
You don't notice the things you take back from your failures, they slip back sticking to you, undetected.
You get intuitions for strengths and weaknesses in patterns. Whenever you're matching two sparse ordered indexed lists, there's this corner of your brain lighting up on how to do it efficiently. You realize it's not the ORMs which suck, it's the fundamental object-relational impedance mismatch existing in all languages which causes problems, and you feel your fingers tingling whenever you encounter its effects in the future, ready to dive in ever so slightly deeper.
You notice you can suddenly solve completely abstract data problems using the pathfinding logic from your failed game. You realize you can use vector calculations from your physics engine to compare similarities in psychological behavior. You never understood trigonometry in high school, but while building a a deficient robotic Arduino abomination it suddenly started making sense.
You're building intuitions, continuously. These intuitions are grooves which become deeper each time you encounter fundamental patterns. The more variation in environments and topics you expose yourself to, the more permanent these associations become.
Failure is inconsequential, failure even deserves respect, failure builds intuition about patterns. Every single epiphany about similarity in patterns is an incredible victory.
Please, for the love of code...
Start and fail as many projects as you can.30 -
I think I have accidentally invented the term 'noteporn' the moment a colleague saw my lesson notes taken in LaTeX and said: "Wow, your notes are so beautiful one could fap on those!"4
-
Ok so I'm releasing (in about two weeks) a massive project that my self and other talented people have been working on for about 2 years.
I feel like I want to puke all the time now. God I hope it is okay. 🤢
I'll let you all know what it is if all goes well so I'm not embarrassed if it does not
Wish me luck😐12 -
Heard a CEO say at a conference that they hire the most competent candidate. Unless there is a woman in the candidates. Then they hire the woman.
That seems pretty sexist to me.33 -
There was once a young man who, in his youth, professed his desire to become a great writer. When asked to define "Great" he said: "I want to write stuff that the whole world will read, stuff that people will react to on a truly emotional level, stuff that will make them scream, cry, howl in pain and anger!" He now works for Microsoft, writing error messages.1
-
Wow it's been years since I've been on dev rant. Awesome to see it still going.
I'm a react dev now ... Like all the other JS developers in the world4 -
Explaining to my boss why we can't use the WordPress theme he saw on Theme Forest in an Android app7
-
Best way to handle any exception...
try{
something
} catch(e) {
window.location.href =
"http://stackoverflow.com/search/...]+"
+ e.message;
}joke/meme coding c++ tip of the day tricks stack overflow random rant try catch joke but will be useful 😂😂😂 programmer hacks8 -
Remote manager: Hey, that contractor you are working with that sits with me. We are thinking of sending him over to you guys, get him a visa, pay relocation and all that stuff and have him sit with you guys as a full time employee. What do you think?
Me: .... eh ... look I have to be honest, that guy is awful. He doesn't listen to me, constantly working on other things, and the architecture he forced onto the rest of the team is some of the worst i've ever seen.
RM: hhhmmmm, ok but what if we have him report to you, can you whip him into shape?
Me: Honestly I think theres too much effort involved. We are very short staffed. I'd prefer to hire someone else here who has more experience. Its a firm no from us on this guy.
RM: Ok, understood, thanks.
*2 weeks later*
Contractor: Hey guys, was chatting to my manager last week and he said the company is finally looking to convert me to a full time employee, and best of all he wants to move me over to sit with you guys. Isn't that great?
..... not really no7 -
This happened when I was on third semester of the career at university. I had my first boyfriend, the "Python" guy. He has that nickname because he used Python as his main programming language and nobody on the classroom used it.
In a few words, he was a... horrible human being. He talked down to me almost all the time, saying to me that my country was sh*t (he is from United States, and for a reason he never wanted to told me, he cannot go back to his country), that my university was sh*t and he said "you're will be lucky if you rot programming in a chair".
As you might wondering, yes, unfortunately it was a toxic relationship. Once he said he wanted to kill the teacher because he though that he hacked his laptop D:
He claimed that he was going to teach me python and security stuff, bla bla bla, but nothing. I learned python by my own.
I almost lost my faith in dev future because I though that the only ones that could have a real future in programming where people without ethics and only if they have a friend or a relative on a company.
The saddest part was that I dated him because I love smart boys, but he was just an idiot that, furthermore, wanted to change me (he pressured me to have tattoos, dye my hair and have sex, things that, of course, I didn't do).
I found courage to break up with him. I waited until the semester ends (in order not to lose my programming final projects) and, the day after the last day of class, I broke up with him.
I recovered my faith on programming when, next semester, one of the teachers invited me to give a python programming workshop :D and I gave two python workshops, and two of mobile development.
Now I'm working as a junior .NET developer. Thank God I broke up with him before the relationship became even worse. "Python" wanted to marry me after a year! O_O11