Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Search - "underestimate"
The first time I realized I wasn't as good as I thought I was when I met the smartest dev I've ever known (to this day).
I was hired to manage his team but was just immediately floored by the sheer knowledge and skills this guy displayed.
I started to wonder why they hired outside of the team instead of promoting him when I found that he just didn't mesh well with others.
He was very blunt about everything he says. Especially when it comes to code reviews. Man, he did /not/ mince words. And, of course, everyone took this as him just being an asshole.
But being an expert asshole myself, I could tell he wasn't really trying to be one and he was just quirky. He was really good and I really liked hanging out with him. I learned A LOT of things.
Can you imagine coming into a lead position, with years of experience in the role backing your confidence and then be told that your code is bad and then, systematically, very precisely, and very clearly be told why? That shit is humbling.
But it was the good kind of humbling, you know? I really liked that I had someone who could actually teach me new things.
So we hung out a lot and later on I got to meet his daughter and wife who told me that he had slight autism which is why he talked the way he did. He simply doesn't know how to talk any other way.
I explained it to the rest of the team (after getting permission) and once they understood that they started to take his criticism more seriously. He also started to learn to be less harsh with his words.
We developed some really nice friendships and our team was becoming a little family.
Year and a half later I had to leave the company for personal reasons. But before I did I convinced our boss to get him to replace me. The team was behind him now and he easily handled it like a pro.
That was 5 years ago. I moved out of the city, moved back, and got a job at another company.
Four months ago, he called me up and said he had three reasons for us to meet up.
1. He was making me god father of his new baby boy
2. That they created a new position for him at the company; VP of Engineering
3. He wanted to hang out
So we did and turns out he had a 4th reason; He had a nice job offer for me.
I'm telling this story now because I wanted to remind everyone of the lesson that every mainstream anime tells us:
Never underestimate the power of friendship.21
A common mistake that people make when trying to design something completely foolproof is to underestimate the ingenuity of complete fools.
Product manager: build us a recently viewed and bookmark feature!
Younger-Me: But every browser already has a bookmark feature and a recently viewed (history) feature and its much better implemented with much less overhead.
Product manager: I don't care. Give me this feature, you are supposed to do as i say and bow.
Younger-Me: I'll take it as a challenge.
--- two weeks after feature is deployed ---
Product Manager: 😁 See! Many users are using the feature we built *shows me messages from subscribed customers*
Me: 😨 I'll never underestimate user's stupidity again.3
Been reading devrant posts for a month or so, this is my first actual post. I'm hoping it will be therapeutic. ☺️ I need something to keep me from killing my boss when I see him again tomorrow..
Some backstory: Currently working in HR for the last 7 or so years with complete shit for brains boss, even worse when it comes to anything related to technology. For almost two years I've been working to get another bachelor's degree. This time in computer sciences, to make a career switch to systems and software engineer. Last week I roughly had the following wonderful conversation:
Boss: we've needed new Recruitment software for a while now. Can't you make us one as a school project?
Me: 'Make us one?' It's not really that simple.. I'm barely halfway through my education, maybe I could do it, but it would take me quite a long time even if I could work on it fulltime.. Combining a halftime job with a fulltime education is taking up enough of my time as it is and I have more than enough school projects btw..
Boss: it would be a win-win. Work a little harder in your spare time and when you graduate you have a real-life project on your resume.
Me: I'm sorry, i'm failing to see the 'win' for me here.. I work 10 hours a day, 7 days a week on average, trying to combine work and studies. I'm pretty much maxed out..
Boss: Your coworker(also extreme dumbass) told me you wrote some quick code the other day that helped him out. Don't underestimate yourself, I'm sure you can do this.
Me(in complete disbelief by now): I wrote him an Excel-macro! They don't even teach me that at school. It's a very very very long way from actual software development! I'm sorry, it just can't be done.
Boss: Thats too bad. I expected you to welcome an opportunity like this and be more motivated towards this company..
Me: ***more disbelief and silence, just staring at him***
I'm sorry you feel that way.
WTF, I work my ass off for 7 years for this fucking shithead.. Even before I started this bachelors degree I had at least some understanding of the work developers put in their software. It blows my mind, no, it fucking angers me how people think making software is so simple.. Why do you think it's a 3-year education you fucking cunt?
Please, someone tell me how I can keep myself from ramming his fucking head through a wall tomorrow...6
Never underestimate the power of a decent chair!
Was staying at friend's for a couple weeks with a horrible chair - my back just spasmed so hard that I am physically unable to get up from bed. Thank god for devRant to keep me occupied throughout the night.
Stay safe kids3
A quick advice to new developers. Never and I mean NEVER do a "quick edit" or "beautification" extremely close to a deadline. You should not underestimate the power of bugs.3
Never underestimate the power of developers on stackoverflow.
If you forget a single restriction they will find solutions that perfectly match your question but not your problem.3
Story #1: So I took a month of parental leave. And was planning to extend it a little longer to deal with my final exams. I was planning to spend lots of quality time with my wife and newborn son. Little did I know... It turns out that out of 5 OoO weeks I was looking forward I actually had 3 at most. The rest I've spent working remotely as I was insisted to deploy a brand new and poorly tested feature to PROD 2 days before my paternity leave. So I spent 2 weeks debugging things in PROD. Remotely. Needless to say that did suck.
Story #2: After story #1 I've learnt my lesson. This summer I took 3 weeks annual leave to renovate my apartment. I asked to not to be disturbed unless there's an emergency. And an emergency it was. One of our app users had a planned hi-load batch job lasting for 2-3 months. Hundreds of thousands of items had to be created and processed. It turns out the _processing_ algo had some flaws and was acting out. I was called out and asked to assist. I knew this sort of debugging is going to take a lot of my time so this time I put my conditions on the table: I will assist but I'll extend my leave by 1.5 the time I spend working now. They took the deal. Instead of 3 weeks I had 5 weeks of vacation!
I don't care that much about my salary. I prefer to exchange it for my time off hence I didn't ask for compensations.
Bottom line: NEVER EVER underestimate or undersell your time and effort. You are a valuable asset and if the team/client needs you on your day off -- make it count. Your time off is YOUR time. Never forget it.3
Tl;dr younger people on here, especially passionate ones, don't worry about comparing yourself to people who appear to have tremendous laurels, those people are probably completely full of shit.
I say kids because you may be like me and more likely to underestimate your ability or more likely to be modest about your accomplishments, and you're too young to know you're doing that.
Either way. I've been doing a web development boot camp the last six months. It's been quite good with the teachers, and some of the classmates. Hell career services is now run by this woman who really actually seems like she knows what she's doing. It's pretty awesome.
That said, my teammates on the group projects have been a different story. I've primarily stuck with some of them out of loyalty and friendship. But one guy in particular has pissed me off to no end. He said he was a computer scientist going for masters. I thought I could learn from this guy. Now I wonder if he's a pathological liar.
Our first project he made one commit. Ripped straight from the homework. It was a simple api mash-up so alright. Fair enough. Next project was when he really started to piss me off.
He didn't do shit the first week and a half. No PM, no design, no programming. Nothing. Comes in two days before project is due, and me one other guy are fucking scrambling. Because of course no one else is there.
I live significantly further than my teammates mind you. We're busting ass. This fucking guy, this dumbass pick who is convinced he's a genius that will work in higher academia clobbers our whole fucking repo.
Why you ask? To put in an unrelated commit that replicated homework from the week before. Why you ask, again? Because this person is a borderline sociopath trying to appear busy in the commit logs.
We're onto the third project now. I spend days designing something original. Side note: I fucking hate design.
So I design my heart out come up with something awesome. This fuck ass, disappears. And another group member. This was the end of November, I hear from this prick last week about refactoring to ES6. But here's the kicker-fucker, our shit ALREADY WAS IN ES6!
I go in Saturday, slack a message I'll be late. I see this fucking "genius dedicated computer scientist" leaving the fucking university shadily checking to see who was watching. He saw me see him. Coward tried to shrug it off.
Here we are, end of semester. He gets the same certification as I do. The difference? I actually know what I'm taking about, I haven't paid in full to fail.
So never, ever fucking ever take what someone says on their resume or LinkedIn as truth. The better it sounds, the more full of shit they may very well be.
And as for our presentation on Saturday? I plan on handling that but letting him do all of the talking. Let's even see if he knows what the project is about :).6
I feel all of us here could use this brilliant quote by Douglas Adams.
A common mistake that people make when trying to design something completely foolproof is to underestimate the ingenuity of complete fools.1
Never underestimate users disability to follow guidance .
Showed me a screenshot where he started the script immediately and entered another command afterwards. Was kinda confused, since the script runs in an endless loop.
Then he showed me his version of the file...3
TL;DR: a dude thinks good graphics make a game good.
so every day when the school ends, me, a dude and another girl walk home. as expected we have lots of time to talk about anything. I wanted that day to tell that dude about what I am going to buy on steam summer sales with just 15$.
me: I am going for this summer to play lots of games so I saved some money for this summer sale. do you want to hear what awesome games I am about to buy with just 15$?
dude: yeah, sure thing.
he wasn't expecting much
M: this summer I am going to buy 5 games and maybe keep more for some others. they are so awesome!
D: ok, let's hear those 'awesome' games!
M: the first game is devil daggers, maybe you don't kno...
D: of course I do. is that game
M: I want to get that game just to improve my aim, but maybe I will have some fun.
D: yeah yeah, I know that game
M: *poker face*
I KNEW he doesn't know this game and anything about pc games because of the followings...
M: ok then... I also want to get Half-Life 2 : Episode 1 & 2. they have pretty rich story and I already have both Half-Lives.
D: holy shit but the graphics... ok, one more 'awesome' game of yours.
M: there are 2 episodes, 2 separate games. I really don't care about the graphics, I love the story.
D: continue with your 'awesom' games...
that dude didn't even knew about half-life and said that game is bad.
M: another game I want to get is Battlefront 2, the one from 2005 and...
M: yeah, the new one sucks, and the gameplay in the original is way better and...
D: *starts laughing* 2005!? I thought you were getting the new one. I imagine the graphics being like this car. *points to a fucking car, yeah that kind of comparasion, I know*
after this I was so fucking pissed off. he doesn't even know about some cult classics that are meant to be played. he doesn't even have a pc nor console and he is stating his opinion on fine air for fucks sake!
M: ok, what about getting the facts and then make an opinon.
D: yeah yeah *making fun of me at that point*
I didn't tell him that I wanted to buy the binding of isaac, cause it was enough for me. I told him to watch some reviews on these games and blog posts about them and I am sure tomorrow he will say that he 'wathced' the reviews and that those games are garbage. it's his style to underestimate things. I fucking hate him, not becuase of the games, but because he underestimates everything that is not on his list of 'good games'. that list consists of new games with great graphics(3D only).
sorry if I exaggerate saying that those games are cult classics but I really look forward into buying them.
if you have another indie game to run on this potato machine(2gb ram, pentium dual-core 2.1ghz, gtx 525m) that I should or at least try comment, I am open to suggestions!11
When i ask you a question through skype or mail, I expect a fucking answer.
You might just say that you don't know. That is okay.
But we all fucking work from home and I can see you're there. FUCKING ANSWER YOU INCOMPETENT, USELESS, UNPROFESSIONAL SACK OF SHIT.
It is so fucking counterproductive. I fucking hope all the chocolate chips in your life turns out to be raisins.
It is fucking impossible to underestimate these people.
I am seriously jealous of all of you here on devrant, for not having met these washed up twats.10
Applies to: instructions, signs, traveling to new locations, arriving on time, etc.
1. Always read the documentation before asking questions.
2. Ask for clarifications as soon as possible.
3. Never underestimate the complexity of a task even when it looks simple. (traffic)
4. Always test the current application before adding a new feature. (shortcuts, baggage, companions)
5. Never trust everything the previous developers say about their code. People forget. See for yourself.
6. No, you will not remember what this part does. Take notes, write comments, docstrings, and give objects reasonable names. (that hookup has a name and is someone's child)
7. Get things working way before the deadline. (check-ins)
Applies to: talking to people, being precise, etc.
8. Don't turn the method definition into an essay.
9. Break things down into smaller pieces, if possible.
10. Avoid misspellings. The computer may not get confused but the next developers will.
Applies to: communication, relationships, etc.
11. Be considerate.
12. People in higher positions make mistakes too.
13. Communicate. Don't expect people to read your mind and don't assume you have all the information you need.
Applies to: utensils, sex toys, compatibility, sexual preferences, etc.
14. Don't do random hacks just to make something work. If it's not the tool for the job, use something else. Wasabi doesn't make a good lube.
15. Product owners and users don't always know what they want. ;)
16. Stop being an asshole unless you have lubes and da hole tyt.
17. Be assertive, not aggressive but spank and choke me anyway.
18. Consider each sprint as a sport. You may have almost killed each other during the game but keep it civil after. (violent love-making)
19. Don't burn the bridge when leaving. Someday, they can refer you to a better job or you can refer them and get money out it. (hookups and prostitutes)
Applies to: beliefs, religion, obsessions, hobbies, etc.
20. Programming languages are not cults. Same with IDEs, tech stacks, etc.
21. Use linters. (check yourself)
22. Be aware of your own bias especially when testing and debugging your own code. (reflect)
23. Being antisocial does not make you a better developer. Stop romanticizing it. (delusions)
Applies to: life in general
24. Be patient. You'll get out of the maze. You always do.
25. Stop blaming inanimate objects for your code not working. Behind every inanimate object is a person responsible for the failure. Most of the time, that person is you. If not, talk to the person and solve the issue.
26. Take breaks.
27. Keep learning new things.
Applies to: negotiation, transactions, relationships, etc.
28. Always send documented proof of requirement changes. (50 shades of grey contract, ew)
Applies to: sex
29. Write tests. Test your tests. Testes. Testicles. Tentacles. Testicular cancer.
30. Hostility never results to productivity. Wank it out, get back to work, and stay calm. (doms in BDSMs are gentle creatures)5
Sometimes I feel people underestimate us.
During all my life, people has asked me if I can fix their *any device* because it goes slowly/something doesn't work.
But, of course, for free. Because they think the only thing we do is pushing 3 buttons and everything is done. They think everything solves itself easily.
Then is the fact that we should be able to fix everything always. Even if the hardware is broken. Even if there isn't any way to solve the problem.
I think we deserve a little bit more from society. I don't expect people to understand what we do but at least something better than the guy who formats your computer when it starts to go slow.
(Maybe I'm the only one who feels that way or it's just where I live, idk)2
3 days ago, I started thinking in a new functionallity for my app, spend 2 days thinking the best way to update the database and thinking about the "shitty" code I wrote 3 months ago, I think it will take me lot of time, but it just take me 1 hour to hace everything working perfectly, never underestimate your code.
Don't underestimate the power of good nights sleep. Was stuck on a bug most of yesterday, decided to go bed early as I wasn't getting anywhere... Woke up, did my morning routine, within 20 mins the bug was fixed. Such a great feeling! :D
I gave my project manager a prototype of the ocr app we're developing to play with, just for fun. The next morning, I enter the office to see this along with a well structure spreadsheet with some 40 columns.
Never underestimate the seriousness of a project manager.3
Now i was thinking that wooble on printing bad isnt that bad but well my prints were good but not exactly perfect.
Today i printed a replacment over the fucking acrylic pieces and the holes were now closer to each other so that the wheels were closer to the rails.
And WOW did that make a difference on the bed. Its much much less wooble on it.
What does this have to do with programming ?
Nothing but it gives a lesson.
Never ever underestimate a small problem !4
So I finished all my tasks for the sprint (3-weeks long) in the first 2 days.
Shit that happens when senior team members underestimate your abilities...4
I love to program — I discovered that about myself a few years ago. Beforehand, I only KNEW how to program. But then I discovered the power programming gives you to create things, and even help your surroundings. So now, I can surely say, that I love programming. Heck, I am even dating a very talented programmer.
But despite all the pleasure I derive from it, I feel lonely sometimes. True, there are millions of programmers all over the world. I also know I am not the only one who prefers coding over going to the movies, taking a walk, eating or sleeping.
Why do I feel this way?
My loneliness is a gendered loneliness, as there are not many women in my field. For sure, there are women who study computer science in high school or at the university, and some even work as programmers. But they are very, very few!
I often underestimate my abilities and feel intimated for no apparent reason
If you have some troubles with some errors/bugs:
Never underestimate the power that a short break from coding can give you1
I'm not here to underestimate the design of a government app on Android.
I hope the developer considered the UI itself as user-friendly and not the default button from android studio. he just simply copies the contents(text & images) from the government web page and paste it to its application.
He/she got paid well to make that app. well, although the information is correct for the users.
It's not much that users are even enthusiastic of the design. they simply read the guidelines inside the app and no more fancy animation.1
If there was an anime Based on developers.
Dev : here comes my favorite browser.
Mouse : No, not until I'm here.
Hand : whattttt? What's happening??
Mind : oh NO!! I why's Internet Explorer is loading?!?
Faster Mind : it's mouse, he's behind all this. Only he's powerful enough to pull off something like this.
Time : Developer-san SAVE me!!
IE : it's too late now, if you do anything it will just slow everything down!!! Hahahah
Dev : No it won't, don't ever underestimate a true developer. It's not over yet!!
*Some keyboard key combination
Time : *screams* developerrr-saaaan!!
Hand : wait, I know it, it's happening. We can still save Time-chan.
IE : WHAT!! No, it can't be!!
Dev : here comes Ctrl+Alt+Del. Be gone....
IE : Nooooooooooooo, this isn't happening, Aaaaaa *dead*
Hand : we did it!!!10
Dear bluetooth headset,
I know your battery is low, thanks for the notice. I have 1 hour work left, after that you will get your charge. I also know you underestimate your own power and can do more than an hour on reserve.
So suck it up and stop being a whiny bitch blaring your damn "battery low"-beeps into my ears. It's way too loud and beeping every 10 seconds will only strain your power reserves and my nerves.
The more I work on the backend forms validation side of my .NET Core project the more I understand how to fuck up web forms in general... 😈
Never underestimate the necessity of a backend validation other then the frontend one. 👿4
Don't refractor for fun!
An anecdote from my previous company. A developer had written a shitty java console app for fetching stock prices. About 3000 LOC. just one java GOD class. So, when me and my friend looked at it, we were amazed how that code works with all that if conditions spanning 100LOC. so. My dear friend underestimated the complexity. Since it just fetches stock price and puts in database right. I can write it in few days and much better one. So, he started writing code in an OO way. Three days later I see he still working on it. Having a glimpse at code. The app is now Object oriented shitty and ugly.
Guess what new code never goes in prod too.
Don't underestimate complexity of app.
Be empathic about fellow developer. Don't think he has written a shitty code. Think why he had to do so.
Don't work on refractors if there is no one to guide you.3
Friend : Have you take a look at this part? We will discuss it this Friday.
What I want to say :
"Don't underestimate my ability to procrastinate, sleep on my problem, run away from my responsibilities, and don't give a sh*t about everything."
What I actually said:
"Of course but I will look at it again thoroughly."
Maybe my frustration and depression are not showing enough on my face.
Suppossing that you're a very capable professional my advice is to NOT UNDERESTIMATE YOU. There are a lot of crappy programmers that feels like an expert because they did a hello world.
As a following to my previous rant
I ended up staying because because the outsourced company(where I’m hired) got called out by the company we’re providing devices for letting me leave and underpaying me
As it it was not enough they also threatened them to stop outsourcing with their company.
At the end I got a 2x salary rise, way better benefits and the promise(still to see) of getting hired directly on the company I’m working in.
So yeah, don’t underestimate your value.3
Never underestimate the power of a misplaced static in your Java to totally fuck you over.
I was busy with my computer science project for the semester where we have to implement a Sudoku solver without backtracking by using graph theory.
So there I was writing my data structure for the grid when for some reason all the cells were initialized with the value 8.
After a whole night of debugging I was about to start over when I realized I had made my array static.
And boom, it works. WTF!!!!!!!3
I see a lot of people ranting about programming exams on paper. I acknowledged that not having a texteditor is not ideal. But not having a compiler is essential in testing the students programming skills in the first few courses.To many students are completely dependent on the compiler.
Some students writing C++ code have to try to build their program as many times they have lines because of all the syntax errors they make. Why think about all the ; if your compiler will tell you where they are missing?
As a programmer you should be able to look at (your own) code and be able to tell what the result should be. Of course this has its limits, but in the small exam questions they get in the first few courses they should be able to do that. To many first year students write a for loop without thinking about the starting value and the end condition. With the repeated process of running the program, changing the starting value or the end condition randomly they eventually get to the loop they need.
I think people underestimate the value of an exam without being able to compile or run your program. But I like to hear your reactions.
QOTD: "We tend to overestimate the effect of a technology in the short run and underestimate the effect in the long run."
I either underestimate or overestimate my deadlines...There hasn't been a single time when I have stated deadline in a standup for a feature and finished it on that day...It's either days before deadline or mostly few days or even weeks past it😓4
Don't underestimate the powers of adding comments here and there. Your future self (or other devs) will be thankful.
It's something that comes with practice, but in general it's much better to overestimate than underestimate.
- Always take your time. Don't be rushed into plucking a number out of thin air.
- Break the task down into really small, atomic chunks.
- Each of those chunks will take at least twice as long as you think it does - nothing goes to plan 100% the first time!
- Make sure you add contingency at the end.
Back to work from a week on holiday. Find out that both mine and my girlfriends companies have announced redundancies on the same day (completely unrelated companies in different fields). We've both made it through the first round ok (which is more than some so massively grateful) but we are still at risk of loosing our jobs. We have some savings to fall back on but that will only cover rent for so long. Never underestimate how quickly things can go to shit.
I hate it when I'm knee deep in projects that need to be done before the new CI strategy starts two avoid a three week long full test every two weeks and then my dear boss comes up with having me do the planning for the next testphase while my coworker is scrolling through 9gag. I mean, sorry old man but either I automate this monstrosity of thirty million layers of 'naturally grown', ill documented, identifier lackimg piece of shit or I can do the fucking schedule. My mother isn't an octopus, i've got only two arms...
Tl;dr: Why do non programmers always heavily underestimate the time shit needs to get done?