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
-
Dev: Microsoft is shit
VS Code: (ಥ⌣ಥ)
Dev: Oh not you dear! You're not like the other guys
VS Code: (｡◕‿◕｡)45 -
Sometimes I feel frontend development is like ancient magic:
Backend Dev: Oh no, I can't align this DIV properly.
FE Dev: No worries!
* Casts Flexius Boxius on the DIV *
* Div aligns slightly better *
BE Dev: But it's not centered!
FE Dev: No worries!
* Casts Marginis Automaticus! *
* Rolls natural 1 *
* Everything collapses *
* Website is on fire *
* Product owner cries *
FE Dev: No worries!
* Casts Flexius Boxius level 5 on the parent div *
* Everything looks beautiful *
* People are in awe *
FE Dev: You are welcome!
* Adjusts his robe and leaves *8 -
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 -
Non dev co-workers: Dude add us on Facebook.
Me: I don't have Facebook.
Non dev co-workers: Instagram?
Me: I don't use Instagram.
Non dev co-workers: Oook, what about Twitter?
Me: I deactivated my account permanently long ago.
Non dev co-workers: Huh? So what the heck are you always looking at on your phone laughing and stuff?
Me: devRant!
Non dev co-workers: Huh?
Me: DEVRANT!! (*shows them devRant*)
Non dev co-workers: What the heck is that?
One of the co-workers: guys, he's a hacker.
Me: *face palm*5 -
*Battle music*
Wild customer appeared!
dev used Ubuntu
It's not very effective...
Foe customer used Stupid Feature-Request
It's super effective!
dev is confused!
dev hurt itself in its confusion!
dev used Reasoning
dev's attack missed!
Foe customer used Ridiculous Feature-Request
It's super effective!
dev used Rage Quit
dev fled using its Rage Quit
...
2 -
Non dev friend: Do you know “hatamal”?
Me: wtf is hatamal?
Non dev friend: hatamal. Spelled as HTML.
Me: T.T12 -
Manager: This button is too dark, you need to lighten it. Have you no sense of design?
Dev: …
Dev: Hows this for an adjustment?
Manager: Wayyyyy too light now, jesus you need glasses if you think that’s good.
Dev: …
Dev: How about now?
Manager: It’s close, make it just a little more dark. God why does this have to take so long, do I have to hold your hand through this entire process!
Dev: …
Dev: There that good?
Manager: Yes that’s perfect! Send me a PR immediately so I can approve, we need to get this out ASAP, it’s critical!!
Dev: I can’t.
Manager: ????
Dev: There’s no diff, you had me gradually adjust the colour back to exactly what it was originally.
Manager: THAT’S IMPOSSIBLE IT LOOKS COMPLETELY DIFFERENT. HOW DARE YOU INSULT ME LIKE THIS, I HAVE A MEETING I NEED TO GET OFF TO BUT WE WILL BE HAVING WORDS LATER ABOUT THIS INAPPROPRIATE BEHAVIOUR.
Dev: …16 -
Recruiter: This is a 100% remote position
Dev: Good! That’s what I’m looking for.
Recruiter: But the company does require you to come into the office “on occasion”
Dev: I live 5 hours away from your office so that would be not a good fit
Recruiter: And once covid is over the ability to work remotely will be getting reconsidered. You’ll likely need to move cities in order to continue your employment with them.
Dev: Yeah I’m looking for 100% remote work
Recruit: This is 100% remote! Just with the need to come into the office sometimes now and potentially more later.
Dev: …15 -
Manager: Feature C doesn’t work
Dev: We never built feature C
Manager: Nonsense, I remember feature C clearly!
Dev: It’s still in the backlog
Manager: But we had many meetings about it
Dev: Never got put on the board
Manager: Feature C is very important!
Dev: It was never assigned to anyone
Manager: What could possibly be more important than Feature C?
Dev: All the other features you placed on the board and assigned up until now
Manager: Well I need Feature C done asap! It should be top priority!
Dev: Ok then next sprint add feature C to the board and assign it to someone
*Next planning session manager leaves feature C in backlog in favour of other tickets*
*2 days later*
Manager: What is the status of feature C?
Dev: You opted to leave it in the backlog
Manager: BUT IT SHOULD BE TOP PRIORITY!
Dev: …9 -
Dev: Hey, do we have a Google cloud machine running?
Me: No we have AWS remember?
Dev: Okay..
Me: Why do you want a gCloud?
Dev: I had this large stack of files and want to put them somewhere, off of my laptop. I just feel comfortable using Google than AWS.
Me: Umm.. there is Dropbox for that sort of stuff. Not high performance servers running our services.
Dev: ...
Dev: (After a moment) Yeah, why didn't I think of that? :/
Me: Seriously???
I think he forgot to have breakfast today.18 -
Dev: Ok issue fixed, you just need to log out and back in again on your end to receive the fix
User: It’s still not working
Dev: Did you log out and in again?
User: No why would I want to do that?
Dev: It’ll reset your locally saved login information which is causing the issue
User: I thought you said the issue was fixed?
Dev: On our end yes, we just need you to reset your end in order to receive the fixed version
User: Look I have been dealing with this issue for 6 months. Fixing bugs are your responsibility. I have too much to do, you have to get this fixed. *click*.
Dev: Yeah you submitted the bug ticket yesterday night though
Email from users manager later that day: <User> is saying you are refusing to fix this bug. This is unacceptable. Fix it or else I will escalate this. Also there are other bugs we noticed today too, fixing them is absolutely critical!
Dev: …
Dev: What other bugs did you notice?
*no response for 2 weeks and then:
User: Hey you can close this ticket, the issue seems to have resolved itself.
Dev: ….muppet.17 -
Manager: *taps dev on shoulder* We need to do B
Dev: I know, you created a ticket for it yesterday
Manager: Yeah but it hasn’t been done yet. It needs to get done.
Dev: I’m currently working on A which is higher priority
Manager: Ok but B needs to be done too
Dev: I know, it’s next on my board
Manager: I’m just making sure you are aware of it
Dev: I am aware of it, it’s next on the board
Manager: Ok but make sure you do it after A
Dev: Yup it’s next up
Manager: Ok, don’t let anyone distract you
Dev: …9 -
Interviewer: So are you familiar with our company and what we do?
Dev: I looked at your website, looks like you build tools for managing restaurants.
Interviewer: No. That’s not even close.
Dev: ?
Interviewer: What we do is create an ecosystem of integrated data centres all orchestrated for immediate stakeholder utilization.
Dev: But the product itself…. it’s a user interface for tracking inventory. Of like…. burgers…. and bottles of wine.
Interviewer: It’s not a product! It’s a data……habitat!!
Dev: …
Dev: So does that make your users animals?
Interviewer: 😡. Unfortunately it looks like you do not see our vision and would not be a good fit for this role.
Dev: Agreed.27 -
Dev: Sam’s a little nervous about taking his paid leave. I guess it’s not common in Nigeria. He needs to hear from the company that taking time off like that is acceptable.
HR: THAT’S SO INAPPROPRIATE! YOU CAN’T ASSUME HE’S FRON NIGERIA JUST BECAUSE HE’S BLACK. BLACK PEOPLE HAVE A VERY RICH AND DIVERSE CULTURE, THEY ARE NOT ALL FROM NIGERIA!!!
Dev: Sam is from Nigeria. He told me so. He tells me a lot of stories from there.
HR: …
Dev: Can you tell me something about Sam besides his skin colour?
HR: …
Dev: …13 -
Dev submitting PR: “Testing instructions: Self explanatory”
Dev reviewing PR: You need to be a bit more verbose than that.
Dev submitting PR: “Testing instruction: Feature should work as expected”
Dev reviewing PR: *sigh*… Feature doesn’t work as expected
Dev submitting PR: WHAT IS NOT WORKING AS EXPECTED??? I NEED MORE DETAIL THAN THAT!!
Dev reviewing PR: …….So do I you muppet5 -
Interviewer: Do you know what Kubernetes is?
Dev: Yeah, that’s the greek god of spending money in the cloud.
Interviewer: Actually Kubernetes is an orchestration tool. Have you not been on a project that uses it yet?
Dev: …9 -
Dev: So we’ve been working on X for about 2 weeks now, it’s about halfway do—
Manager: Btw what is the status of X?
Dev: I was just telling you
Manager: Oh, I wasn’t listening.
Dev: …
Dev: So as I was saying, we’re ab—
Manager: Oh and where are we at with Y?
Dev: …10 -
Dev: So how do you want this feature fixed?
Manager: It should work how it worked before.
Dev: I'm new to this feature, I don't know how it worked before or what is broken about it.
Manager: Well just make it work like it worked before.
Dev: I DONT KNOW HOW IT WORKED BEFORE THAT IS WHY I AM ASKING YOU. PLEASE TELL ME SO I CAN DO MY JOB.
Manager: Just how it worked before!
Dev: ...
Manager: ...
Dev: fuck you17 -
Real conversation:
dev 1: so what are you working on these days?
dev 2: some wordpress project.
dev1: hahaha. wordpress is shit. are you a real developer?
dev 2: have you ever used wordpress?
dev1: no.
dev2: okay.26 -
After 1 year I have finally quit my sysadmin job!
Got my first dev job as a fullstack node.js dev!!!!
4 years of IT boredom is finally over!
WOOHOOO!
😎😁9 -
I like it when a boss is a Dev (or a former Dev). Makes them a bit more sympathetic towards us i think :)2
-
So I’m working on an app with a friend who is designing it and I spent a week building a custom segment control as a menu bar. He said that it looked nice but he got inspiration to make a tab bar instead 😑
Cheers to the dev life
2 -
dev A: is everything operative?
dev B: yeah, sure
dev A: how do you know?
dev B: log service doesn't show anything wrong
dev A: does the log service work?
dev B: why shouldn't it? It's its job
dev A: *sips tea*8 -
**at daily standup
Dev: and along with a push to production that is what I’ll be doing today
Manager: Good good, alright, nice….. ok who else hasn’t gone yet? Dev how about you go next
Dev: …I literally just went
Manager: What? Well what did you say then? Hey when is that push to prod happening? I feel like there should be one happening sometime soon.
Dev: …8 -
Interviewer: Hello my name is Alyssa from Sheeple and my pronouns are she/her
Dev: Oh yeah I saw that in your email
Interviewer: Ok well I am just letting you know they are still the same
Dev: Thanks for that.
Interviewer: What are your pronouns?
Dev: div/span
Interviewer: Sorry?
Dev: he/him
Interviewer: Oh…ok. Let me know if that changes.
Dev: I promise you it won’t
Interviewer: Well you never know!
Dev: …46 -
Today @ 4pm:
New dev: I need help with this issue, i've been stuck on it all day.
Me: ok let's look ...... ok, and did you try google this?
New dev: ... no
Me: ... why?
New dev: well this is clearly my issue, why would I google it? I only google for things I don't know
Me: ... ok ... we'll do you know what this bug is then?
New dev: haha ok, fair point, I'll give that a try. Thanks for the tip.
Seriously, should I be worried? I feel worried13 -
Dev: Hey, I need you to see something.
Client: ok
Dev: this is the models of those reports you need
Client: ok, wait, what is that number? This is wrong, we can't...
Dev: hey, calm down, this is not the production, it's just fake database!
Client: ah, ok.
(5 minutes of explantion)
Dev: so, what do you think?
Client: just one point, that data is very very wrong, we need to change this ASAP!7 -
Recruiter Email: We need experience in Doker!
Dev: I could potentially be interested, what is this new technology? I've never heard of Doker!
Recruiter: It's not super new, it's the traditional Doker! You know, good ol' Doker!
Dev: Like Poker? Or Joker? 🤡
Recruiter: What?
Dev: What?9 -
Project Manager: Hey Gid, we need to start migrating project-A to the new Server.
Me: Okay, I will inform Dev-Q.
Project Manager: Please do and treat as top priority!
Me: Hey Dev-Q, we need to migrate project-A to the new Server and we need to get it done asap.
Dev-Q: But I'm currently working on some critical bug XYZ which PM wants fixed before COB.
Me: I dunno maybe you want to speak with him.
Dev-Q: I was told to...
Project Manager: Yes! we need that done right away.
Dev-Q: What about the critical...
Project Manager: No! treat this as top priority the client just called.
Dev-Q: Okay.
Me: Any update yet?
Dev-Q: Yep but it seems like the database is quite large and the migration may take a while.
Me: Okay take your time.
Dev-Q: {hours later} Pheww done! All files and database migrated successfully.
Project Manager: Good good. So the critical bug XYZ was also completed and migrated to the new server right?
Dev-Q:
5 -
I hope they make an anime about being a dev and the enemy is the deadline.
Dev: ill use this coding technique number 111
Deadline: impossible
Insert explosion effect here9 -
Dev: Your PR only addresses a quarter of the ticket
Dev2: *limps a commit so that now 1/2 of the ticket is addressed and creates a new PR for a separate ticket*
Dev: Your original PR only addresses half of the ticket
Dev2: *limps a commit so that now 3/4 of the ticket is addressed and creates a new PR for ANOTHER new ticket*
Dev: Your original PR only addresses 3/4 of the ticket
Dev2: *limps a commit so that now all of the ticket is addressed but two new bugs are introduced and creates a new PR for ANOTHER new ticket*
Dev: Your original PR introduces 2 new bugs
Dev2: *limps a commit addressing one of the two new bugs and creates a new PR for ANOTHER new ticket*
Dev: Your original PR still has one bu—
Manager: WOW GOOD JOB DEV2 THAT’S 5 PRs TODAY AMAZING! Dev you need to pickup the pace, you only have 2 PRs so far today. And get these PRs from Dev2 QA’d fast. He’s a rockstar!
Dev: …
*The 4 other PRs turned out to be equally dogshit*
Manager: Hey hurry up with QA, you’re holding Dev2 back!
Dev: …7 -
Manager: Hey Dev I need to do QA on this PR.
Dev: That PR is not finished yet
Manager: Well do QA now anyway, that way when it is finished it can be merged in right away since QA has already been done on it. It’s a project management technique called “fast-tracking” and it improves efficiency.
Dev: …9 -
Manager: That last dev you hired is working out well. Where did you get him from?
Dev: *Looking at new hire’s resume which only contains a single bootcamp and nothing else*
Dev: He’s a rescue.11 -
True web dev power is using the dev console to get rid of modal boxes so you can see the content underneath7
-
Shared devRant to some of my Chinese speaking dev partners.
Partner: It is interesting to know that dev rants are language independent.
Me: Developers talk in programming languages, which are the same throughout the world. -
Dropbox TLS 1.0 & 1.1 is deprecated
Dev: we need to upgrade our projects
Manager: we don't have time for that. can you call to their helpdesk, so we can keep using our projects w/o upgrading?
Dev: ....
Manager: call them!
Dev: ...9 -
PM: hows the android app going?
Android Dev: gradle downloading... blocked by network admin.
PM: anyway how is the iOS app going?
iOS Dev: cocoapods downloading... blocked by network admin.
PM: ... i guess the only thing running now is the web admin right?
Laravel/VueJS Dev: composer nodejs/npm/yarn downloading... blocked by network admin.
PM: team lets retest the api endponts
Team: Postman downloading... blocked by network admin.
Team: -_- Insomnia REST Client downloading... blocked by network admin.
PM: code study?
Team: even visual studio code/android studio/xcode is blocked. :(
.... sad dev life
anyone here with the same problem?14 -
Boss : Need very very little change on our project
Dev : Ok, what is the change?
Boss : This, this, this, this and just this one.
Dev : Really very very little.1 -
Jr. Dev: We got an issue in prod.
Sr. dev: Okay, what is the issue?
Jr. dev: Don't know, just got an email.
Sr. dev: Did you check the service?
Jr. dev: Which service?
Sr. dev: What have you debugged so far?
Jr. dev: I explained you the issue and waiting for your inputs.
😑😑😑😑😑6 -
Me: I prefer to make sure dev is fully separated from prod, that way if we fuck up, it doesn't matter.
Manager: It's fine, the service isn't fully deployed and dev/prod are named differently.
Me: runs ansible script to stop dev
*prod breaks*
Me: Huh. Wonder why that happened.2 -
When the last dev wrote code and you dared to read it....switch on a Boolean, what even is your life legacy dev?
2 -
Manager: You know you really shouldn’t pay off your mortgage faster than you absolutely have to. It’s the cheapest money you’ll ever get!
Dev: I’d rather work towards being debt free. Besides my RRSP (401k) is already maxed out
Manager: RRSPs are a scam! TFSAs (Roth IRAs) are way better
Dev: My TFSA is maxed out too
Manager: 😡 You still shouldn’t pay off your mortgage!
Dev: …16 -
~ 10yrs ago, Dad: I'm a dev, your mom's a dev. I paid for you to go-to business school... But you still became a dev. And your brother also wants to be a dev
Now after me and bro moved back with then bc of COVID. The house is basically WeWork on weekdays.
Good thing we're all devs so can with remotely.9 -
HR: I’m sure you know what this meeting is about
Dev: My script that converts the name of our 3rd party IT provider in any email thread I reply to with “PooPoo Inc.”?
HR: No, that is a separate meeting
Dev: Ah.4 -
Dev: My VM is not working. Something is wrong with VM.
Me: Have you made any changes to the code?
Dev: It shouldn't matter my VM is not working.
[I go and check the Dev's VM.]
Me: ಠ_ಠ The build output literally states your unit tests failed -
I'm so close to giving up. Yesterday, I travelled 4 hours in one direction for a job interview for a graduate position as a web developer. As I arrived at the interview, I was welcomed by a senior dev and one of the HR people.
I sit down and they start explaining how everything will commence(standard procedure stuff) and afterwards hand me the technical test. At this time I am super calm cause I did my homework, checked out their products, their websites and knew right away what I was going to work on. As I turn the page, I see at the top with huge fucking capital letters "JAVA OOP test".
I take a minute and look back at them, like wtf is happening. Turns out that they are looking for a java dev. They picked me for the role because I had literally 1 fucking sentence in my CV and where I have said that I studied java in one semester of uni. FYI my entire portfolio, cv and cover letter are focused on JS, html, css both for client and server side.
As the fucking HR guy stood there and asked me "is there something wrong", I felt broken inside. For the first time in my fucking life I felt like I was done and couldn't continue anymore. I felt like this is some bitch-slap from karma about something but I still can't figure out what. I just walked out of there being unable to realize what happened.
I just feel like I should end my developer career before it has even started, just go do business analysis or something. Why the fuck would someone put a job description entirely talking about Angular, Less/SASS, bootstrap and jQuery and then say that is a Java dev OOP role. Who the fuck allows those people to take good salaries yet still deliver the up most shittiest quality service.
Before the interview, I checked out their websites which are simply horrendous with the comparability of a fucking baked potato. Idk really what to do, I don't mean to sound as a whiny little b.... but as I walked out of their office, I felt broken inside. Sorry for the long rant.8 -
Slack Boss: hey, could you check work of dev that is okey, we want this update fast.
Me: hey, just tell him to open PR and assign me, I will check and merge changes.
Slack notification: Dev: Hey, could you please merge Pull request on the project ?
Me thinking, hmm weird, I didn't get email.
Checking github, 0 pull request.
Me: hey, I don't see any pull request open, and when you make pr, just assign me I will merge it right away.
Dev: takes half a day
Dev: Makes pr and assign correctly me.
Dev on slack: HERE is PR open now @me.
I get 3 notification to see this PR, sure at least it is there.
I check this PR, 50 commits, X conflicts, cannot merge this.
Me: Hey, @dev please fix conflicts in your PR.
DEV: takes another 2 days to respond.
Boss in the meantime: hey, have you pushed those new changes ?
Me: I am waiting for conflicts to resolve.
Dev: I fixed the conflicts @me.
I check the PR conflicts are there.
Me: are you sure you pushed your changes @dev ? I don't see them resolved
Dev: takes another day and pushes changes to resolve conflicts.
Me: merges PR to master becaus he based it on master, I will sync the developer branch myself.
All good, everybody happy.
I write to dev: Next time base your changes on develop branch and resolve conflicts before making PR.
Two weeks later new PR From this dev.
Based on Master, conflicts everywhere.8 -
Dev: There’s a file in your PR with over 1000 lines of code, I think it should be broken apart into a couple smaller pieces to be a little more in line with the single responsibility principle
Muppet Dev: That file only has one responsibility! It can’t be broken apart!
Dev: How’s that?
Muppets: It’s single responsibility is managing that group of functionality
Dev: …3 -
Sales: "There is a problem in complicated feature A, in a client system!
Dev: "What is the problem"
Sales: "I don't know exactly"
Dev: "which client system? What version is installed?"
Sales: crickets.
Dev: "Do you a Jira ticket, or an email with more details?"
Sales: "It is urgent that we fix the problem ASAP!"
Dev: "what problem"
Sales: "The problem! I talked to the VP RnD, So he can make sure you are on it!"
Dev: "What exactly do you me to fix"
Sales: "The Problem!"8 -
Remember to regularly defragment your drives on linux. use this handy command.
dd if=/dev/zero of=/dev/sdX bs=1M
Terminology:
dd: Disk defragment
if: input file (the pattern to search for, and should always be /dev/zero)
of: output file (your disk, /dev/sda for instance)
bs: blocsize 1M is fine here16 -
After 'Dev' deployed a service using Azure ServiceBus, a particular queue/client was receiving errors.
Dev: "Looking at the logs, client is getting faulted."
Me: 'What is the error being logged?'
Dev: 'Client is faulted'
Me: 'No, that is our error when the client is either unable to connect or there is an exception in the middle of sending a message. What is the exception from Azure?'
Dev: 'Client is faulted. That's it. I'm going to have to re-engineer the code to implement a retry policy.'
<OK, I smell someone cooking up some solution finding, so I dig into the logs a little further>
Me: "Looks like an invalid connection string. The actual exception being thrown and logged is from the Azure client connection string builder. The value cannot be null."
Dev: "No, I'm looking right at the connection string in the config. Looks fine."
Me: "Looks correct on your machine, but what is actually being deployed to the server?"
<I could tell he was getting agitated>
<Dev clicks around, about 10 min. later>
Dev: "Aha!..I found it. The connection string in the config on the main branch is wrong, in fact, the entry is missing."
<dev fixes, re-deploys, life is good, I document the error and the root cause>
Boss: "Great job Dev."
*sigh* ..go teamwork?3 -
Let junior dev design module.
Make code review.
What junior dev says: "It is a totally flexible concept!"
What junior dev means: "It is extremely shitty to use for the one use case it was meant to do, but it will be equally shitty to use for all the use cases we will never have."
Back to square one.9 -
Dev: I think I just deleted data I shouldn't have. Can you do a rollback?
Me: No, I'm a DBA, I don't touch data. Did you commit?
Dev: Yes, I committed.
Me: Your data is gone.
Dev: But don't you guys do backups?
Me: We backup the Prod servers. We only back up Dev on request. Did you request a backup in Dev?
Dev: No.
Me: ...
Dev: The Testers are going to be pissed.1 -
team lead: what is the minimum lenght validation on the first name field?
dev: i decided to put minlenhgt 3
team lead: why? did you tests it
Dev: i tested it. 3 makes sense to me
Team lead: isint your first name 2 letters long?
Dev: oh i dodth think about that4 -
One thing I've noticed about devRant is the ratio of web dev/mobile dev posts to database/architecture/big data dev posts. There's A LOT of you web peeps out there, and not enough data dudes, which I guess justifies my constant demand, salary and lack of competition. Just an observation.9
-
"This pub is famous for its pork dishes. And I usually buy liquor from that stop, quality approved."
- one dev friend
// said "best advice"
// not "best dev advice"2 -
preface context: I was recently asked to make a website for an event I participated in before
client: okay I heard you can make a website for our event? that’s great!
me (dev): yeah, do you have any requests or expectations for me?
.
client: not really, but I was a developer before and I can code a bit so I’m wondering in what language would you code or develop our website in?
me: oh I would be using JavaScript, specifically nodeJS
.
client: oh really? i’m not really familiar with that language, so is it okay if you code it in a language I understand and used before?
me: sure, what is it?
.
(lol I wonder if you can guess already what it is at this point)
client: HTML
me: ... (*uh oh* html isn’t a markup language *sigh*) :——) -
Because DevOps in a lot of organizations is really “help desk for clueless developers”, conversations like this happen a lot:
Dev “hey the thing seems to be not working right”
Me “what does that even mean? I need you to be a good deal more specific. What thing. What isn’t working?”
Dev “I dunno”
Me “Are there error messages?”
Dev “yes”
Me “….would you like to share them with me?”
Dev *sends error*
Me “ok did you actually read this error message?”
Dev “yes”
Me “…so you’re good then? It says you’re trying to use a variable that hasn’t been declared yet. You should fix that. “
Dev “…”
Me “good luck”13 -
I've finished all my work. The Dev life is definitely for me. I love being a Dev. I am going to continue being a Dev. Ignore my previous rant.12
-
RETARD MASTER: So how did you feel about this sprint DEV?
*nothing is planned, new tickets added each day and old ones removed - inconsistent sprint*
DEV: Well, it’s a bit chaotic, but it’s understandable. I’m used to it. Nothing’s to blame here. Client can’t produce their end of the bargain on time.
*3 week later*
DEV MANAGER: So RETARD MASTER gave a feedback. He told me you insulted him.
DEV: Can I please die now? Not funny.12 -
Interviewer: Yeah so we're hiring you as the person who would build out and own our client-facing web application and related stack.
Dev: Perfect, that's what I've been doing for the past 10 years, I'm your guy.
Interviewer: GREAT SO WHAT IS THE DIFFERENCE BETWEEN FORK AND EXEC ON A PROCESS ON A LINUX MACHINE!?!?!?!?
Dev: I don't... know immediately at this moment?
Dev: Sigh
Dev: I hate my life
Dev: Somebody please help me18 -
Boss tells senior dev to show junior dev how to do something. Senior dev says okay. Get back to desks - senior dev refuses to show junior dev because 'if you fuck it up, everything'll break'... How exactly is a person supposed to learn if you won't even let them observe?!13
-
Client: we want X.
Dev: Quote for X.
Client: We only want to pay x.
Dev: Requote for x.
Client: approved x.
Dev: Deliver x.
Client: where is X we asked for X.
... perspective of project scope matters.1 -
Just over heard, Dev A was reviewing another team's code ...
Senior Dev A: "I don't understand this teams code. I hate WebAPI. Wish we could use X."
Senior Dev B: "Why can't we use X?"
Senior Dev A: "It's frowned upon."
Senior Dev B: "By whom?"
- couple of seconds of silence -
Senior Dev A: "X is not a Microsoft technology"
- few more seconds of awkward silence -
Senior Dev A: "X is magnitudes slower than WebAPI anyway."
Senior Dev C: "What? How much slower?"
- caught off guard..didn't know Senior Dev C didn't have his headphones on -
Senior Dev A: "Um...I don't know, that is what you told me."
Senior Dev C: "I never said that. I've never used X. I prefer WebAPI anyway, but both WebAPI and X use REST based protocols, I doubt X is magnitudes slower. Actually, I think you told me WebAPI was slower."
Senior Dev A: "Different paradigm."
- second or two of silence -
Senior Dev B: "What?"
Senior Dev A: "Hey, did you see on twitter ..."
Have no idea where he thought that conversation was going. Maybe he was hoping the other devs would dog-pile/attack the code. Pretty funny it backfired. His face when Dev C said 'I never said that' was priceless. Like "Oh -bleep- ..how do I lie out of this one? ...quick, distract with random words or a twitter post" -
At what point do I stop being a Jr dev? Is it a time spent in the field type of thing?
Or is everyone a Jr dev and titles are pointless.15 -
*Senior Dev:* Ah yes, we need to put try-catch in every function to handle errors and Logger.Log() at the beginning.
*Me:* Is not better to define a global error handler and use the stacktrace instead of doing all that?
*Senior Dev*: ...
*Senior Dev*: Is a rule here, do what I'm telling you.3 -
Serious question, what's so great about using Macs for programming and dev work? Junior dev here and all my colleagues and superiors can't stand them.
Is there actually a technic benefit that I'm missing?59 -
Junior Dev me: ok boss, coding is basically done, just need to do some more system testing.
Senior Dev: fantastic let me take a look.
(3 hours later)
Senior Dev: ok so I've made some small changes and pushed, could you pull my edits.
me: sure
(pulls changes)
(EVERYTHING Is changed)
(try to compile)
(doesn't compile)
Me: sorry, it doesn't seem to compile for me
Senior Dev: I never tried to actually build it, it's only a small change
me:
7 -
!rant
My laptop is 8 years old this year. She’s still going strong but her Core 2 Duo is starting to show. I need a new dev laptop so I can put all my cool dev stickers on. Sponsorships? 😬23 -
tfw...
• the new "sr dev" asks what the point of TDD is
• being polite, I answer in an ELI5 format
• rest of the room nods head in agreement
• new "sr dev" still has baffled look on face -
The worst dev I’ve interviewed is the only dev I’ve interviewed.. Which is probably one of the best colleagues I’ve ever worked with, and a really good dev.2
-
Conversation between a developer and admin team to change configuration in higher environment.
Dev: Please change these config parameters.
Admin: What is environment url
Dev: 😑. Gives the url
Admin: How to change?
Dev: 😑. Gives all the details
Admin: I am unable to perform as server is slow.
Dev: Whom will you report the slowness of server as you are the admin?😵
Admin shocked developer rocked -
Probably gonna quit dev and get a job outdoors. Dev sucks dick, is too boring, and it is too political for me23
-
Extract from a quite old recruiter email (excluding the formalities):
Position: junior dev
Workplace: office for first year, can be changed to remote after (salary will be 50% lower if you go remote though) *suspicion levels starts raising*
Payment: 1€ per line of code (empty lines/comments excluded) or page of documentation *alarms start ringing*
Additional info: on high alert for 4 weeks every 6 weeks *wtf is going on*, salary bonus is 10€ per week *I stopped reading here and moved the email directly to the spam folder*6 -
Lead-Dev: "These links don't work as they should, I'm having you fix them, 'kay?"
Me: "I'll have a look."
> The link doesn't do anything when you click on it.
My internal monologue: (The href is probably just wrong)
> It's not wrong.
Me: "What the fuck?"
Lead-Dev: "Can you fix it?"
Me: "I don't think I can."
Lead-Dev: "Why don't you try looking in thisScript.js?"
Me: "Oh, you think the click event got prevented or something?"
Lead-Dev: "No, I think something went wrong with what that script is doing with the jQuery library this site uses."
Me: "..."
Lead-Dev: "..."
Me: "jQuery... library...?"3 -
Never had the situation to give advice to a new dev. But I have an idea anyways: Give that dev a problem, which is above beginner level and watch the dev. If the dev rage quits and doesn't want to try again, then the new dev will not be happy with the job. But if the dev achieves to collect all knowledge to handle the problem, even if the solution is not the most elegant way, then the dev will have fun with the profession.2
-
The `sed` command skills of my senior dev (team lead) is equal to every skill I (junior dev) have ever acquired until now as a programmer.
Just amazing !1 -
My dad let me use how computer and have me a VB6 book when I was like 5.
I took it from there though it seems it tube in the family.
Dad's a Dev
I'm a Dev
My younger brother is also a Dev
My mom is QA, though used to be maintenance dev I think2 -
Not my rant, but this person can probably use some devRant in his/her life. Go read the full tweet and his/her replies here.
Buck up for a very very long read.
https://twitter.com/gravislizard/...
There was quite the argument storm in (a) similar rant(s) here, so hope peeps don’t mind how this is just adding to the pile. The tweet uses a lot of web examples and bashed really hard on them.
PS: I do web dev myself, but I have to agree to certain nasty things about it.
9 -
Conversation in a debug meeting, after a series of confusing failures:
Senior dev: “This is stupid”
Junior dev: “Me too” -
Student dev : "C++ is C but with OOP features"
Teacher dev : "C++ is a OOP language, you'll loose points if you don't use OOP"
Me: "Time to leave this school"3 -
*literally any arithmetic operation which is hideously wrong*
Almost every JS dev : Is this JavaScript?1 -
First dev job is my current one.
I'm a software engineer in test, writing automated UI tests for web and mobile apps.
Its pretty great. I work from home with flexible hours. I have a boss but he doesnt manage my dev team, he just checks in to make sure I'm getting support, training and have all my questions answered. My dev team is myself and 2 other people, both of which are cool, and all the work is dev-driven.
Might just stay here until retirement, that sounds easy.2 -
Starting my first real dev position Monday. Scared about using a windows computer for dev for the first time but stoked.
My rant is against myself that I didn't switch jobs earlier.6 -
A friend of mine and I are about to open a company and we're hiring a developer to develop websites, no specific needs, it literally just have to work.
We found this guy, who develops goodlooking websites, but isn't really a developer, meaning that he just uses visual composers. (which doesn't differ too much from what we want).
Well this guy kinda loves us because we're actual developers who know how to code "properly".
It's the first time someone likes me just bc I'm a developer and I'm already superhappy!
Hope it will get good soon enough! -
Dev: Woah look at this code! I might be a genius!
Also dev a few months later: Woah WTH is this shit? Was I totally dumb or what?2 -
Got a ****ing blocked nose. ****ing irritating. ****. Sick dev is a bad dev. Zero productivity. Tons of things to finish before Saturday. ****.4
-
IE's dev tools is the web-dev equivalent to a broken Mad Catz controller. Literally fucking unusable.
-
Be me
Newb Ui dev
New job , learn c#
Become xaml pro first
Newb ui dev
Today building menu
It's breaking ree.
Ok I go through an fix
Part fixed
No reee
Commit build for other my senior dev
We have online compiler
Receive build fail
Reeee
My code is good
I'm sweating bullets
I call other dev
Yo I f***** up
Help me
Go figure it out ... reeee
I go spend 40 mins
Don't know what is killing build
Reeee intensifies.
Going to shit diamonds
Reeeeeee
Other dev, lol my bad I turned on somethin that break ur build. Your not fired congrats.
Reeeeeeeeeeeeee3 -
I started iOS app dev thinking there’s good scope in the future,now I hear people saying app dev is gonna die switch to data science. Tf6
-
Happy!
Being an Android Dev myself, I bought my first app in Play Store!
Nova Launcher Prime was offered @ ₹10 (~0.15$). No matter how small the contribution is, it's quite a special joy to support another dev!
4 -
In all seriousness, the best part of being a dev is that you learn something new every day. That serves me personally as motivation. There are so many fields of study that embody what a dev is, and because of this, there are a LOT of things that you can do and create. On the other hand, the worst part of being a dev is the fact that we can't do it forever.
-
the two code review personality types
review activity:
- dev A: requests code review, sets dev B and dev c (myself) as reviewers
- dev C comments: this review is marked with a complexity > 9000, touches > 20 files and has zero comments... also there's a lot of refactoring going on, making it hard for me to tell what the actual relevant changes are. can you please add more comments to this review?
- dev B (10 mins later): approved review6 -
Packt.com (dev education books) is doing a survey of their readers. I don't fit into any of their boxes, closest one is data scientist.
I think I might really be a mathematician rather than a dev...
I hated maths at high-school.1 -
*Dev is non-native english speaker
Dev: we need the VPN ip.
Me: the server ip or the connected device ip.
Dev: the server.
Me: gets the ip.
Dev: this doesn't work, is this the VPN ip ?
Me: Gives the device ip. Works.
Dev: OK. Works now.
Could have just asked for the client IP in the first place but s/he didn't know how to.
I have been trying to freelance for people who don't speak english as a first language and getting the Requirements is the hardest part of the job. 😫 .
P.S. Suggestions needed from remote freelancers. What's your workflow like.6 -
Every Node.js dev today - Deno is awesome! Much better than Node. Let's use Deno.
Still every Node.js dev - Why can't Deno run my simple code? Why can't they make Deno work exactly like Node?6 -
The best dev advice a dev has given me is to write clean and structured code from the very start of every project. Changed my life in general.
"How you do one thing is how you do everything." -
When people ask me what I do for a living I reply : "I'm dev" (Which is "Je suis dev" in french) and people always think I'm called Dave4
-
> be me, associate dev
> slack mid-level dev 40 lines of code
> I have never written a REST api before
> his response is "lol"3 -
Me: Where is your unit tests?
Dev: I tested manually and it worked.
Me: What if there are changes to the code in future?
Dev: We'll manually retest the implementation. It'll be fine.
*flip table*1 -
A non dev has no right to pass judgement whether a dev is good or not. Be it engg manager or a product manager or any other manager6
-
the look and chat project managers give right before they tell you the specs changed.
pm: heyyy
dev: what is it?
pm: how are you?
dev :{realising the spec changed}
-
Web development is a fucking mess. Why is there hundreds of things to download, manage, and all of them depend on another tool? Framework dev teams, can you stop creating dev tools for dev tools that is intended to alter development? How the fuck do people even handle this pile of mess? They must be superhumans.1
-
As a dev (all kind of dev ) what is something you struggle with in a work environment? Or at home?8
-
Joined dev rant yesterday. First thing I do today after reaching office is open dev rant and scroll through... really loving it...1
-
I overheard this mid level dev discussing a new task with a senior dev. They're discussing compile error in cmake. I realized that the mid level dev asked so many basic stuff that are easily google-able. Mind you, our codebase is cmake based, how come she didn't know even the basics and yet survive in our company for years?
I felt bad for the senior dev, as I knew he's busy with his work. He couldn't do his job because he had to do hand-holding with this dev.
My biggest mistake is often trying to solve things by myself which will take hours instead of just asking a senior. But asking other dev for every little things are also annoying. Why can't you just google shit up or RTFM?1 -
C/C++ - complex, very fast, used for OS dev
Java - Comparatively easy, fast, used app dev
Python - very easy, comparitively slow, used for app dev
Then there is this boy
Rust - Just fucks you up10 -
This dude is a casual dev. You know it just by looking at the repo name. He probably likes other stuff like burning stupid people in the mind or throwing chairs. Casual dev..
https://github.com/nvbn/thefuck -
Promoted this last Tuesday. Went from hourly associate app Dev to application analyst. Apparently I skipped app Dev and Sr app Dev. Not the raise I wanted but still substantial. No change in responsibilities with high probability of substantial raise next year on the next budget. Curious though. Is app analyst always above developer? Titles confuse me.3
-
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
-
(Sr. Dev) Oh right, you can't do that in the controller.
(Me) I can't do what?
(Sr. Dev) That thing.
(Me) Call another controller from the controller?
(Sr. Dev) Yep.
(Me) Where is supposed to be called?
(Sr. Dev) From the view.
(Me) But what is supposed the controller to be used for?
(Me) What is supposed to do the controller?
(Sr. Dev) The controller pass data to the inner classes. (Controller > Manager > Domain Object > DAO)
I ended calling 3 controllers methods from the view in 4 different views everytime...3 -
Going from web dev on Mac to web dev on Windows. Any advice?
What is you favourite JS IDE on Windows? Any software that will make my life easier? Any other things I need to know?
All and any advice is welcomed.11 -
This is an actual transcript...
Since it's way too long for the normal 5000 characters, hence splitting it up...
Infra Guy: mr Dev, could you please give some rational for update of jjb?
Dev: sparse checkout support is missing
Infra Guy: is this support mandatory to achive whatever you trying to do?
Dev: yes
Infra Guy: u trying to get set of specific folder for set of specific components?
Dev: yes
Infra Guy: bash script with cp or mv will not work for you?
Dev: no
Infra Guy: ?
Dev: when you have already present functionality why reinvent the wheel
Dev: jenkins has support for it
Dev: the jjb is the bottle neck
Infra Guy: getting this functionality onto our infra would have some implications
Dev: why should I write bash script if jenkins allows me to do that
Dev: what implications ??
Infra Guy: will you commit to solve all the issues caused by new jjb?
Dev: you show me the implications first
Infra Guy: like a year ago i have tried to get new jjb <commit_url>
Infra Guy: no, the implications is a grey area
Infra Guy: i cant show all of them and they may hit like in week or eve month
Dev: then why was it not tackled
Dev: and why was it kept like that
Infra Guy: few jobs got broken on something
Dev: it will crop up some time later
Dev: if jobs get broken because of syntax
Dev: then jobs can be fixed
Dev: is it not ???
Infra Guy: ofc
Infra Guy: its just a question who will fix them
Dev: follow the syntax and follow the guidelines
Dev: put up a test server and try and lets see
Dev: you have a dev server
Dev: why not try on that one and see what all jobs fails
Dev: and why they fail
Dev: rather than saying it will fail and who will fix
Dev: let them fail and then lets find why
Dev: I manually define a job
Dev: I get it done
Infra Guy: i dont think we have test server which have the same workload and same attention as our prod
Dev: unless you test how would you know ??
Dev: and just saying that it broke one with a version hence I wont do it
Infra Guy: and im not sure if thats fair for us to deal with implication of upgrading of the major components just cause bash script is not good enough for u
Dev: its pretty bad
Infra Guy: i do agree
Infra TL Guy: Dev, what Infra Guy is saying is that its not possible to upgrade without downtime
Infra Guy: no
Dev: how long a downtime are we looking at ??
Infra Guy: im saying that after this upgrade we will have deal with consequences for long time
Infra Guy-2: No this is not testing the upgrade is the huge effort as we dont have dev resources to handle each job to run
Dev: if your jjb compiles all the yaml without error
Dev: I am not sure what consequences are we talking of
Infra Guy: so you think there will be no consequences, right?
Dev: unless you take the plunge will you know ??
Dev: you have a dev server running at port 9000
Infra Guy: this servers runs nothing
Dev: that is good
Dev: there you can take the risk
Infra Guy: and the fack we have managed to put something onto api doesnt mean it works
Dev: what API ?
Infra Guy: jenkins api
Infra Guy: hmmm
Dev: what have you put on Jenkins API ??
Infra Guy: (
Dev: jjb is a CLI
Infra Guy: ((
Dev: is what I understand
Dev: not a Jenkins API
Infra Guy: (((
Dev: (((((
Infra Guy: jjb build xmls and push them onto api
Infra Guy: and its doent matter
Dev: so you mean to say upgrading a CLI is goig to upgrade your core jenkisn API
Dev: give me a break
Infra Guy: the matter is that even if have managed to build something and put it onto api
Infra Guy: doesnt mean it will work
Dev: the API consumes the xml file and creates a job
Infra Guy: right
Dev: if it confirms to the options which it understands
Dev: then everything will work
Dev: I am actually not getting your point Infra Guy
Infra Guy: i do agree mr Dev
Dev: we are beating around the bush
Infra Guy: just want to be sure that if this upgrade will break something
Infra Guy: we will have a person who will fix it
Dev: that is what CICD is supposed to let me know with valid reasons
Dev: why can't that upgrade be done
Infra Guy: it can be done
Infra Guy: i even have commit in place3 -
Today, my co-workers went nuts about the fact their version of our product doesn't work on the pre-production since everything is fine on their local dev machines ^^
After a quick sighting, I figured out what was going on.
There was a package called from non-dev code which was required as a package for development.
The build plan of the application consists of a task which purges dev-packages within the vendor folder, using composer install --no-dev ^^
So the build plan runs perfectly fine, without a single error, but runtime was yelling about a missing class.
It's a delight to be one of the only guys with dev-ops experience in the whole damn building.
xD -
NPC stereotypical dev: "I self identify as socially awkward."
NPC stereotypical dev: <Gets irrationally angry about friendly banter.>
NPC stereotypical dev: "I hate people who try to interact with me socially."
And knowing is half the battle. GI Joe!1 -
It's part of me, there's nothing special for me known as Dev days. Everyday is Dev day, for me Dev day basically means my life. If you ask for normal day, where I don't have to do something techy, well, then it's a different story.
-
is it possible to get remote job for junior java - android dev? I'm php dev, but thinking about moving to android1
-
is it just me or
<job ad>
...
min 1 year experience with web dev
min 5 years experience with web dev in JS
...
</job ad>
does not make much sense4 -
don't you just hate, when this happens? translated from Slovak we call this "the system of the falling shit" you know this under "hot potato"
email:
from: marketing coworker
to: senior dev 1
* asks for a lot of stuff, deadline yesterday, high priority, on a site for which the jenkins build is crashing every once in a while, because we are migrating all the time so some folders are already deleted or not created yet and the build config is really strict *
forwarded from: senior dev 1
@senior dev 2
forwarded from: senior dev 2
@senior dev 3
forwarded from: senior dev 3
@junior me
ಠ_ಠ fuck me i guess ¯\_(ツ)_/¯1 -
Business: The feature is not as aspected.
Dev: This is what you asked for.
Business: I ask for something else.
Dev: Please refer to the documentation.
Business: F**k with document.
Dev: You only the documentation. -
Be clear on your aim as a dev.
Be truthful of wat u know.
DONT DONT ever try to outsmart a interviewer who himself is a dev for many years.
Lastly keep cool and backup ur skills. -
New job, strict devops role. I asked the devs they're painpoints, no mention of local dev stack.
Spin up a local dev stack and it's a garbage fire. No feature flags, env vars, docker. Have to be careful due to devs using staging databases for dev work.
This is going to be a problem...3 -
My advice from a very beginner dev myself is to take walks and use some fresh air. Dev outside your job on techs and frameworks that aren't use by your company. Sleep. Stackoverflow.
-
Sigh, what is it with these cowboy SQL Devs? Why the fuck is this a pattern for anything?
New contract, new idiots, sigh.
EDIT: Had to change picture because Prod is different to Dev (but no dev has been done since release....smh)
4 -
In my dev travels and dev journeys, i have learnt nothing but one thing. The secret of life. I will share with you devs today.
"Life is a free form jazz odyssey of mastubatory bullshit" -
If all dev job were taken by AI, I'll probably go back to making dolls and fabric jewelry. Is not as good a source of income as being a dev but you can survive off it.
-
It took a front end dev (me), a backend dev and the founder to figure out some Apache rewrite rules. Why is server management so stupidly complex?2
-
Not dev related, assuming that here is a lot of people interested in history , philosophy, books I would like to ask for recommendations for:
YouTube channels or site related to history, books reviews/recommendations (dev and non-dev related), philosophy.
Thanks. :)6 -
!dev-related
Before I start this is a community of dev-minded people so this question should be here.
Anyway, how much money will the person that invented and mass-produced teleporters make?3 -
Quand ta MOA te demande de réaliser des action en recette, que tu les fait sur l'environnement nommé REC mais qu'en fait, il fallait le faire sur DEV1...
sorry i don't know how to translate this... -
QA: Finds and reports Critical Bug
Dev: Hotfix 2 days before next scheduled deploy, NP!
After Scheduled Deploy...
QA: Critical Bug is back
Dev: Oops, overwrote hotfix during Scheduled Deploy -
!dev
Currently, cause holiday camp for the children
Probably a good idea to collect some social skills there, as that's nothing that is required or learned with my dev job -
Dev and QA environments are housed on AWS servers, both sharing the same API code. Dev API is unable to connect, while QA is able to connect just fine. How does this happen 😱
-
Now I didn't become a dev solei to avoid paperwork but the lack of paper was appealing...
I'm stuck in a support gig because it pays more than any of the dev jobs I got offered and I do is write is docs on Confluence.
Please no "Money isn't everything" comments. I agree but the dev offers I got, I couldn't live on
Top Tags
Weekly Rant
View