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
-
The worst thing about being a dev is after a while your reaction to every problem is this: ¯\_(ツ)_/¯
Or this: ಠ_ಠ7 -
Providing work estimation:
Dev: This should take about 2 weeks
Non dev: Really? But it's so simple. Shouldn't be that long right? I think it can be done in one week.
*After one week*
Non dev: Why is it still not done? I thought you only need one week?9 -
The worst part of being a developer?
So many ideas, so many possibilities... But so little time to do all of it. :'(4 -
When you were growing up to be a developer and your mom brags about what a genius you were and has literally no idea what she was bragging about...
#IJustInstalledLinuxMomChill...
Funny story my step dad was bragging about me hacking Google to a group of his guys a few months ago (mind you I'm 21, he's a roofing contractor) and he calls me over and is like "yo, Jimmy. Tell them how you hacked google. (Obviously I never "hacked google", whatever that means) and this guy he's talking to say:
"Oh shit. You can do that shazz".
For my own amusement I replied:
"Yeah I hacked google last week. I HTML'd into their json databases to pull out an ASP in order to bash attack on their .Net services using only CSS"
Of course the man's only response at this point was to ask me how much it would cost me to build him a site...11 -
How I feel at Christmas time when visiting family and everybody swarms me to set up/fix their new gadgets 😁
4 -
There are a lot of things that could rank up as the worst about being a dev, such as recurring meetings, documentation, shitty requirements, pm gnats, Monday, etc...but something that truly ruins it all is NO INTERNET CONNECTION.
5 -
The worst part of being a Dev? The lonely feeling when you are the only one who likes to develop in your group of friends5
-
1. Do you know why my computer is so slow?
2. What cellphone do you recommend me to buy? (They always end up buying the cheapest)
3. What do you do at work? (Answer: "I create applications". Anything more complex than that is not going to be understood or they will loose interest)
4. Something is wrong with the: [TV, Cellphone, microwave, etc.]. Could you please take a look? (Believe or not, if something works with electricoty, my family thinks I can fix it).
5. Is it true that if I send this WhatsApp message to all my contacts I will have more options?
6. I need to build an application that (pretty much The Matrix), how much time do you need and how much would cost? Don't you dare to give me wrong numbers. (We have to see the future)
7. (Continuing the previous point, a non-technical client) I don't think that would take so much time/money. (Every time)
8. I want to use the latest Front-End frameworks. I want to see all those beautiful animations in my page and that it runs smoothly... I also need that it runs in IE 5.
9. So, you have been working in the back end? If you don't have a screen to show to the client is like you didn't do anything in this sprint.
10. Why haven't you built and million dollar application? Everybody is doing that right now....
Yep, those are only a few downsides of our profession if we count family, friends and even co-workers. But I can't imagine myself doing anything else.6 -
Me: So here's the completed website.
Client: *goes to Google and searches for media agencies india* What the hell is this ? I was told that my name would come on the first page in Google.
Me: Sir, we had quoted to build SEO friendly pages and not for doing SEO.
Client: This is fraud. How the hell could you cheat me by using these technical words. I want my name on the first page in Google.
Me: *types companyname.com in Google* Here Sir, your website is on the first page in Google.
Client: I very well know fraudsters like you. If I wouldn't have checked it then you'd have charged me for this later on. Here's your cheque.
Worst part of being a dev is handling less techy people than you 😫3 -
My neighbor: Hey can you install FIFA 16 on my laptop? I can't seem to have the crack.
Me: I can't do that.
Him: Why not? They teach you that in college, right?
(He's damn serious btw.)3 -
You've spent nearly 5 hours trying to figure out why your app won't work. Only to realize you misspelled a string constant.2
-
No amount of backend code is seen as progress by client.
Have a web store app project that is running and looking beautifully and is currently connected to nothing.
Got scolded this week for not having any new deliverables.
Spent 15 hours on security updates and database architecture.5 -
WORST???
Seeing your code, which you were proud about, now being butchered by some interns/newbies 😲
Just like seeing your X girlfriend after long time 😒10 -
Worst part of being a dev: "we need this done by the end of the week"
Me: "ok what are the specifications?"
PMs: "not sure yet, we have a meeting with the client on Thursday."
Me: "cool, I'll look at it Monday."
Don't come to me with deadlines before you know what I'm building. -
We want a web site.
We're going to want lots of interactive content, which we'll define later.
You need to develop the whole thing in 2 weeks.
We'll give you all the details after you tell us exactly how much it will cost.7 -
When you ask for a screenshot of an error and the client sends you a blurry photo of their screen...4
-
Having to deal with stupid testers who think your app should be resistant to water and black magic and report a bug if it is not5
-
Worst part of being a dev:
Writing down an issue in the ticket system for somebody else took longer then fixing the issue yourself.2 -
Being a developer means...
- Writing code
- Fixing bugs and issues
- Impromptu project manager to current project
- Making coffee
- Seeing unicorns
- Listening to the boss' suggestion that goes horribly wrong
- Contemplate10 -
The relentless feeling that slowly has over taken my waking life. The feeling that if I am not coding, learning or becoming better at coding I am wasting my time. I can't even watch movies anymore without reading articles. This is the worst thing about being a Dev, how when you are a dev you are nothing else.
At least for me, not sure how common this feeling is.10 -
Hearing from friends and some family... "You don't really work. You just sit in front of a computer all day."8
-
People that don't know what you do, think you're just a lazy introvert that sits on the computer all day4
-
Person: Can you hack this person for me?
Me: I don't know how to hack.
Person: C'mon please? I heard you were good with computers.
My face as said person says that: 😑2 -
When everyone ask you to make them a website just because you are programmer... (when you have 0 webdev experience)7
-
Worst thing of being a dev: in family meetings, being asked by EVERYONE to fix their computers or check that weird issue in their smartphones4
-
Worst part of being a dev is the expectation to work whenever / wherever and ultimately cover your bosses ass when they set a ridiculous deadline without consulting you. But if you miss the deadline it's your fault, right.
-
Worst part of being a dev?
The last 10% of a project.
Being in beta, gathering feed back, sorting through opinions and user preferences. All that takes forever compared to the first 90%.
📈🗓❗️❗️❗️2 -
Worst part of being a developer?
Everyone thinks you want to freelance a website for them...
Even when you're not a web developer
What do you do?
I write software.
Oh so you're good with computers and stuff?
Yeah
That's p sweet, can you build me a site?
No. 😃3 -
When folks from other walks of life think we devs have it easy. Cuz "all day we sit infront of computer and get paid for it."
-
Worst thing about being a dev is being interrupted when your in the middle of a lot of mental juggling... "Where was I?... Dammit"2
-
Worst part of being a dev?
THERE'S A NEW FREAKIN FRAMEWORK EVERYDAY.
Where are we supposed to get time to learn everything the job applications require? And even worst, have 2 years of experience with the thing?
And how about when developing a responsive dynamic website? If you are crazy, like me, and you are the kind of dev that always wants to deliver something great, customized to the needs of your client, and that doesn't smell bootstrappy, you probably can't stand too when people ask you about time guesstimates. Especially when you are the ONLY DEV in your company.
Also, our gear is EXPENSIVE.
Sorry, I guess I'm stressed... Had to bring some work home, due to the bosses deciding to deliver a project one week early to the client, without consulting me first.
Still, luckily for me, all this bullshit can't take my love of coding away.
4 -
Worst part of being a dev must be working with people who are not willing to change behavior because of arrogance. Oh - and then the constant OS wars talk. It really needs to stop. Like... Now5
-
The moment when you realize that you have no other conversational topics than technology, programming and how fucking annoying it is, to working with total douchbags :(
-
Having to talk to non technical people and explain them technical things. Painful in every sense of the word. :(1
-
"You've been working on this for 6 weeks, and I don't see any changes. What have you done?"
"I completely overhauled the backend, now everything makes more sense and we're using more modern APIs"
"But nothing's changed at all! The front-end looks exactly the same!!"
"*sigh* The new backend is also more secure.. "
"Oh, so it's a security upgrade, that's good, but why did it take six weeks?"
-_-4 -
Getting told by someone who is almost to stupid to open a word file how easy it would be to develop XYZ.2
-
When teachers expected you to write code for them for free that they didn't even understand and then copy it and claim it as their own....
-
Worst things about being a dev? Boy, this will be a long one!
- Whatever I do, be it hard work or smart work, I feel I am always underpaid.
- Most people who don't know tech feel my job shouldn't take that long. "Oh, a website that should be easy." "Oh, REST services, that's cute!"
- Most people who know a little tech will be like, "Here is the code for this on Google, then why are you charging this much"
- Companies like Microsoft and Apple who are too cool to follow standards.
- Always underpaid!
- The friggin compilers and random environment vars. Sometimes you make no change and the code works on a restart. I mean wtf!
- Having to give/meet deadlines, when we know most of the times things get out of control.
- Having to work for jerks mostly who don't know squat, and can't tell the difference between a CPU and a Wooden box.
- Sometimes I wanna take a break from my laptop(traveling and stuff) , those are the times I get the maximum work load!
- Did I mention we are always underpaid?
- Because of the kind of work I do, finding a girl has been challenging. Where the heck are they!
- We have to stay always updated. Often we deploy something using a framework and the next day we see an update.
- Speaking of updates, I hate having to support for OSes like Microsoft.
- Speaking of OSes, I hate Apple!
- Speaking of Apple, I feel we are underpaid, de javu?
...
How much would you hate me if I wrote "just kidding" ?3 -
Worst part: being everyone else's Search Bitch. Seriously, how the hell do you have a job in the tech industry when you can't use a fucking search engine, whether it's Google, a builtin search facility or, hell, scrolling down the goddamn page?3
-
Worst part of being a dev...working for a company that doesn't understand your potential. Knowing that you can do so much more than they are but being limited due to a myriad of excuses, budget, time, user base, etc.3
-
Worst part of being a web dev is spending the majority of your life making stuff you'll never touch with your hands5
-
The worst part has to be you always compromise on your health just because your brain is telling you to solve a code block. You ignore your basic necessities, resulted in irregular patterns of sleep, skipping food and so much more.
Trying to maintain code which was written long back and alot of it has deprecated.
Yes you need to sit your ass down and write the whole thing again. -
Got a request from a client to remove the dot on the i because umlauts are bad for SEO in URL paths3
-
When people ask you to speed up their old crappy device, whether it's a phone, laptop or tablet (even though I'm a web developer), all I say is:
"Buy a new one, that isn't cheap and nasty"6 -
Worst part:
Either "Can you fix my PC, it won't start"
Or "Can you hack <some instance here> for me because <some stupid reason>1 -
This is just one I had with my cousin who came for a visit.
Cousin: Yo bro, I want you to hack my girlfriend's Facebook?
Me: Lol, and why is that?
Cousin: I think she's cheating on me with this guy. I've seen her replying to him on fb messenger.
Me: Lol, ask her about it then if that's what you think.
Cousin: She won't talk bro. That's why I want you to hack her Facebook or even her phone so I can see who she's talking to.
Me: I can't bro.
Cousin: So you're not going to help me?
Me: Not that bro. I can't hack Facebook. I don't know how to do that stuff.
Cousin: But you have Bachelor's in CS and I've seen you writing those stuff on your computer....uhm, the code thing.
Me: Yeah, but those were school and personal programming projects. Not hacking stuff.. they're not the same.
Cousin: Oh man, what about her phone?
Me: Nope, can't do that either.
Cousin: But I've seen you hacking your Android phone... (*He saw me root my phone*)
Me: *face palm*3 -
The worst part of being a dev is when you realize you have a major design flaw in your architecture at 4:50 PM on a Friday. Goodbye weekend, hello intense thought.2
-
The concept of manhours in our company.
A project that is estimated to take 400 manhours can not be finished by 50 people on 4 hours.4 -
I don't think it's to complicated...
Dumb clients, no matter who they are if they want you to fix their computer ... Create a new Twitter , hack, when you don't hack.
They make our lives hell .. why ? Because ignorance.
My favourite is when they expect you to work for nothing.oh but you can have 2% it's a billion dollar idea you'll make like 20 mill!😒🙄 All I'll do is sit here since i was the genius if the idea you work out the details ? 400 hours you say? I'm sure it'll take 20 don't be silly now.1 -
"Can you fix/update/speed up my pc/laptop/phone/toaster/potato?"
I don't mind too much doing it for my family though, but sometimes it can get a bit annoying.4 -
Worst thing about being a Dev:
Getting forced by a non dev for a timescale without even being allowed to look at the issue. Then being held to that made up deadline!!1 -
Being told the "solution" to a technical problem by a non technical person from a meeting I wasn't even invited to participate in. This middle finger goes out to middle management everywhere.
-
Living in the constant fear of the many threats that only people like us can understand. Even some of our closest friends will poke fun at us for being "paranoid" because they don't know how fucked things really are.1
-
(1) Datetimes. Seriously, fuck 'em.
(2) Everybody always thinking: Come on, that little feature is so simple. It couldn't possibly take a whole week to develop.
(3) Nobody really caring or understanding or forgetting after you've told them that if you cut corners and do something the dirty way, it adds to the effort and time needed to maintain or build new features. -
Worst part of being a dev,
When you find a problem that is very similar to the one you have on stackoverflow, but it's slightly different and the solution doesn't work for you.
So then you ask your specific question and you immediately get some downvotes and comments referring to that solution that didn't work.
And then after weighing all the options, you decide to rewrite the whole program or script or whatever.1 -
Girlfriend, family, relatives, non-coder friends keeps ranting why I don't follow a social convention of attending usual meetings or gatherings and advising I should rather get some time away from a monitor screen.
*Like that's going to happen, getting away from screen, ever, hahahahahhha* -
Worst part of being a dev is that feeling that you're walking up the down escalator. Can't get ahead and if you stop, you're back where you started.
Oh and some punk kids keep passing you on the way! Lol -
When you've got a full time job and you don't have time to update all you personal apps, resulting in 35 emails from Apple saying your apps don't comply *meh*
2 -
Why can we all relate to almost every rant for wk24?
Devs could rule the world! Why do we have to endure all of the same crap from India to the UK?
(The recurring meetings and the 'Dynamic Requisits', as I call it, are what bugs me the most!)5 -
WordPress uses 25+ MySQL connections per person. MySQL limit is set to 100. 4 people can bring down a critical component of the company. Only fix is to write custom MySQL connector using PDO and persistence connections. Added a Resistor cache just for good measure.8
-
Explaining to coworkers that it's not Windows XP on my work computer but Windows 7 with classic theme and that it's the same Visual Studio Version than theirs but with a light theme.
I've quit there btw.1 -
Being treated as some kind of alien, when in fact it's something that can be learnt just as easily as anything else.2
-
"This application has stopped working. Oops, something went wrong." Proprietary software, no error message, only option is to accept your fate or submit a report to your system overlords
-
Searching for a new job in a different language than you have experience in. Seriously, no one seems to really understand that if you can code in one OO language then you can pretty much do them all!
I don't want to do PHP any more you fucks!5 -
People who went to a weekend training course and now believe they are Gods of "the cloud" and "web scale" and "devops".6
-
Trying to understand other people's code like:
- 6 README, in total 7 lines (that's all there is for documentation)
- 40% of code is commentary like (original code, not altered...)
// if(a = b)
// c = d; // this is not working -
The object-oriented model makes it easy to build up programs by accretion. What this often means, in practice, is that it provides a structured way to write spaghetti code.
~Paul Graham -
The worst part of being a dev? Working in teams.
And I don't mean that in the "I'm the best ninja code wizard in the whole world and you're all holding me back" kinda way. I'm thinking more in the lines of someone who has to deal with that kind of attitude on a daily basis. As someone who recently was put in a leading position in a dev team, this is by far one of the worst experiences that came with it.
Some examples?
- One dev completely changed the naming scheme for variables in a class he worked on for one. single. bug fix. His reason? He just didn't like it!
- Another one noticed that data he was supplied with was not in the specified format. Instead of flagging this with the project leads, he just rewrote his parser to fit the data. A couple of weeks later the supplier noticed the error, fixed the format and suddenly everyone wondered why the software failed processing the data.
- Or that one senior dev, that just refuses to accept changes because "it was always done like this and it worked" No, it didn't. That's why it was changed!
Once a dev team reaches a certain size, people need to realize that stuff like coding rules and process guidelines are not there to annoy them but to help the whole team work as efficient as possible. I don't care how good a programmer you are, if you can't check your ego you don't belong in any kind of team-oriented development project! -
Client: we want to double conversions and Facebook likes by end of year.
Dev: (internal: this is impossible) So what's the plan?
Client: *blank stare* ... -
Worst part of being a dev? Probably that there aren't enough hours in the day for me to do all the things i want/need to do...
-
That felling you get when someone cuts you off on the freeway and they are going 10 miles under the speed limit, that same feeling when project requirements change just before the deadline. That is what I hate most about being a dev.
-
If the code is running, then it must be doing what I want. Right guys? Is it normal to be this paranoid even after lots of runs of the code without crashing?2
-
I wonder if being a developer was originally thought of as an undesirable position...
"We need to pay people to sit at a computer all day writing code, sometimes skipping meals, getting less sleep and dealing with all our clients shit"2 -
Worst part of being a dev is no clear career path. I have no idea what I'll be doing in the next 5 years3
-
Boss comes, asks that I make a function in the site. Tell him it's impossible / forbidden, he says okay and goes back. Comes back a week later, asks for the exact same function he asked earlier.
-
"agile" teams, changing scope, unrealistic deadlines, non-tech PMs...
So much fits into this category.2 -
Knowing a lot but getting chewed out over not knowing some obscure thing or others expecting you to be able to read their minds...smh that or then not responding to questions..so tldr; people, people are the worst part about being a dev.
-
Forgetting every day tasks...
So I can use map, reduce, filter in my sleep, have memorised huge chunks of valuable programming information.
Today I went to the gym and laced up my jogging pants, looked at the vogue knot I'm supposed to tie to prevent them from falling down and my brain just said:
"Fucked if I know how to tie that!" -
That feeling when you are about to add a new feature to a project and when you start reading the spaghetti mess the previous developer puked when he/she was monkeying around, your blood pressure goes up, you lose a bit more hope in humanity, you start thinking about buying a gun, and start theorizing how torture could potentially be a valid recourse in some cases.3
-
I could write a book on this (and I am) but long story short: contracts people that have no tech know how, don't get tech inputs, then get mad and convince managers it's all the tech people's fault when the contract bombs.
-
Never getting a straight answer about key aspects of the system, I cringe every time I hear "can you make it configurable"1
-
The stress that comes from meeting deadlines, and always trying to keep the behavior/logic of what your working on straight.
-
Managers that somehow leave projects until the last minute, and then get shitty when you're too busy to do them on the day they're due... Best of all, when it's 4:45pm on a Friday afternoon.
Every. Friday. Afternoon.1 -
Worst part of being a (new) dev, and by new I mean first dev job and I'm a month in, is keeping commit messages from being novels3
-
Another guy who doesn't even fucking know the spec of the device that asshole is holding, acts cool and fucking calls us nerds & losers (the devs due to whom all the coolness is possible with all those techs) and is so fucking dumb but gets the girls!!1
-
Programming languages so rare that they will only help you in your current employment but not in any way or form your future.1
-
The worst part about being a Dev is explaining what exactly that you do to your distant relative who knows nothing about computers 😑
-
Worst part of being a dev is when you need a patch for your sleeping schedule but don't have time for updates
-
Every person who knows that you're a dev thinks that they are a part of a secret circle and you WILL develop apps that would generally cost thousands for free
-
The worst part for me is when I think about fixing an error when I should relax. Like watching a movie and then it comes, you start thinkng about a solution, even pick a paper or notes app aaaand the fun is gone.2
-
Clients asking for features in a prorecord schedule and budget... "Facebook have it. It is not that hard"
-
Internal team changing specs because they don't understand how much work went into the project.
This is generally accompanied by the statement "that shouldn't take you very long." -
Worst part (at least that's on my mind today)? People who don't build the app giving the orders of what needs to be done in it. They never know how possible things are, or expect them in half the time it actually takes.
-
After my Holiday i was totaly rested... But a week ago three collegues and myself started a side project... It is soo hard to get up these days!
Best and worst part of being a dev?
The side projects -
Worst part of being a dev..quite a comprehensive question..i think the most is having to subject yourself to a client's myopic suggestions..which technically makes your job look unprofessional. I end up not leaving my imprint on such jobs..and it feels like a total waste of time.
-
The worst part about being a dev is having to deal with resource allocation of two hands, three keyboards, two mice 😂and a coffee all throughout life1
-
The worst part of being a dev is actually explaining what you do to people with no technical experience.
-
Worst part about being a dev is that feeling like you have missed something before your go live. :/1
-
When the business tries to tell you how you should code the project when they know nothing about coding let alone the actual requirements.1
-
Bad time management habits.
As for me, I've recently changed job and took some side projects and without some tricks (Getting Things Programmed) I would just end up shits creek without a paddle. I feel like I'm already in, but some tricks keep my numbers on the boards and I don't sink yet.
Also bad eating and no sport habits. -
Just because you happen to work with computers a lot everyone that's friends with your mother expects you to fix their malware machine for free and then get indignant when you tell them they where they probably got the virus and how to avoid it.
-
Issues and bugs that neither StackOverflow, Google, DevForums, SeniorDevelopers can figure out and the product should've been piloted a week ago.4
-
Relatives think I'm a graphic designer, i.e. I can do all party invitations for free. I had to create one over the weekend.4
-
The worst part about being a dev is that I regularly feel like I don't fit in and I think it's because I lack the Y chromosome.13
-
For me, developing phone networks, the Client only interacts with me as the front end. If there is a problem with an upstream provider/carrier, the client doesn't know that and we take the brunt of the complaints.
So, what really sucks is when there is a lack of control. -
A majority of the bosses/PMs/supervisors tend to be soo stupid and lack the knowledge of the actual problem's complexity so they expect you to hit keys and voila, project done.. It gets on my nerves big time.
-
Everyone expects you to work your "magic" and get shit done... But nobody thanks you or gives a shit when you do.
-
I work as a developer where I mainly work on internal solutions. The worst fucking part about this, is how we're basically always the fallback for fucking everytging. Sales dept are constantly selling services without knowing if it's even possible, not checking if we need new hardware and shit like that.
Fucknuggets. -
Getting a pretty big project for a new feature on the main site, and getting called to change stuff on the existing features every day....
-
Wanting to work on your side projects but having to do a paper simulating the project management of an assignment you did last year for college.
-
Answering non techie people what my job is. I could say I'm a software engineer, and they would understand because it has the word "engineer". But i prefer to introduce myself as a developer but they give me a confused look.
I think engineer is an overused term and i hate that term, for me, connected to typical asian patents who forces their kids to be an engineer or doctor. -
Sometimes I think computers and the work conspire to make me an alcoholic. Trying to rush the release and thanks to piled up technical debt it's taking ages. And as it is taking ages, other work is piling up so I would have to rush to something else without cleaning it up and will be swearing again next time. That gives me headache. And to cure it I need to drink. And drinking gives me different kind of headache. All those stupid endless circles are ruining my life!1
-
From a meme somewhere, but pretty accurate.
When everything works. Boss:"Why are these guys even here?"
When problems occur. Boss:"Why are these guys even here?" -
Worst part of being a dev is the word 'simple'.. used in the sentence by non devs, " I just have a couple of simple features"...
-
Being asked for computer/device purchase advice! Just because I use a computer on a daily basis, doesn't mean I know what you need. Do your own research, like the rest of us, and learn something in the process! You've heard of the internet right!?
-
Being confused with technical support by everyone. I can guarantee
Even the person who wrote code for computers on board an ICBM would have been asked to help reset email passwords.
We are devs for God's sake. -
Worst part of being a dev?? Having to recompile just because of an error which isnt supposted to happen
-
And one more.
When my senior ask me to rebase the PR, which I submitted f*n one month ago.
Where it was f*n important that time.
And your pull rebase ask you to fix the conflicts.
And you realize you need to reapply the changes again on top of the master.
And you have to run the FTs again.
Damn.... -
Being told all those crazy startup ideas by friends and family with the comment "this is so simple, I'm sure I can learn to code and do it in 2 weeks"
-
The fact that if something doesn't work it's most likely due to my idiocy..
Debugging is quite depressing and awesome at the same time -
Worst part? Hmm.... A lot.
When you your code should be reviewed by an idiot who suppose to put lame comments/corrections for the sake to keep his position. -
Worst part of being a dev?
Tried to explain to das and family what I do and until now, no success!
Not even my wife understands!
And, according to my father in law, I work with "internet". -
The realization that their is no free will, Microsoft rules everything including you.
If for no other reason than that they've claimed every acronym. -
team members that don't want to improve anything or don't want to use tools to improve the work... so annoying... 😔
-
Every time we ask the directors what they think about the design. They introduce a new feature...
Can't you just decide what color will be the plane without changing the maximum speed???? -
Stacktraces of exceptions thrown in async code. When walking up the callchain just gets you in the schedulers dispatch loop...
-
I should check out the latest videos at egghead.io, I should convert to Angular 2, I should start using es2016, I should learn c, I should continue on the cryptopals challenges, I should fully understand floats, I should learn how java works under the hood, I should learn the details of how the drammer exploit were done, I should make a dinner planner, I should continue the Golang tutorial, I should check out the game of my colleague's game attempt, I should engage in an open source project...
Playing cs:go with a nagging bad conscience... Again! -
Worst part of being a dev: have to wait for the compiler to build, then upload to device, then restart the app... A dozen of seconds are enough to lose concentration and wasting time on something else, which lasts much more than a dozen of seconds.
(opening devRant is by far the best of those wastes) -
Separation of duties.
I work in a fairly large IT department for a Healthcare company and for security reasons always having to involve application support or other teams even during development phase can be very aggravating when I have to ask for simple things like server log files. And the process to get to deploy in production is paved with bureaucracy and paperwork and emails that have little to do with anything other than just say, I approve, yet we are supposed to be trying to implement agile. -
That moment just before release to production where you've tested it a thousand times and suddenly encounter a couple of bugs.
-
Today I spend more time writing spaces after commas and between operators while working with legacy code than actually adding new features and fixing Bugs.
-
Feeling terrible for ignoring my family or girlfriend for hours each time when I'm working on an assignment..
-
Helped SO's parents with web dev I'm a bid to get to know them better. Figure the rest. Don't help family. Atleast not for free. Rather, just don't, unless you're okay with multiple change requests.
-
Worst?? When our CTO told us to study the whole template app, and after 1month one dev keep on asking me where he can find those services and function.. -_-
-
"Hey I have this awesome start-up and I need you to built a web app, it's like Facebook but better, we have a month to get the MVP ready and we want to pay you with company actions (none)"
-
Incompetent bosses, open offices, stupid outfitting rules, ie compatibility mode, "fix me this", "explain me how does it work this app you've never used"
-
Writing code and coming back to it later and not knowing what you were thinking so you just rewrite it again1
Top Tags
Weekly Rant
View