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
-
I was explaining git and Github to one of my friends during our boring maths class when he asked : "What is the difference between git and Github?". Just then another friend of mine sitting in front turns out and said : "It's like the difference between porn and Pornhub".17
-
Had my first 'mentor' moment at work today!
Newest guy couldn't figure something out and asked me, slightly nervously, for help.
Suddenly I went into mentorish state, explaining stuff I was doing while fixing it in under a minute!
Felt good 😃8 -
* phone conversation with Dad*
Dad: What are you doing?
Me: Busy creating website.
Dad: So, if I type " www", will I be able to see it?
Me: *explaining website hosting and servers for 15mins straight*
Dad: Huh. You do learn something in college then.
Me:🤐23 -
*Me Coding with a laptop and desktop when friends enter *
Friends : u r a coder right? Hack something in front of me.
Me : *sick of explaining ppl*
*SSHs into lap from desktop and shuts it down*
See. I hacked my lap
Friends : whoa! Cool man8 -
Rule 34 ½: For every programming problem, there is already related XKCD, StackOverflow question and indian guy explaining it on YouTube. <3
23 -
The most detailed error report I've ever had from a client. He couldn't login to his email, I asked him to send an email explaining what was going wrong, attach error messages, etc.
I got this from him:
"I can't login to my email, why"
Really?! 😑8 -
When someone, after explaining it for 10 FUCKING TIMES, still doesn't get that WE ARE NOT HOSTING HIS MOTHERFUCKING SERVER SO WE CAN'T FIX HIS FATHERFUCKING COCKSUCKING EMAIL ISSUES.
FUCKING HELL.13 -
iOS: Hey, human wanna hear a joke?
Me: Sure.
iOS: Out of Memory.
Me: What?
iOS: I ain't explaining shit.2 -
Programmer boyfriend: *explaining his work and code and how things work*
PBF: does that make sense?
Me: of course
Narrator: it did not make sense7 -
For fuck's sake,if you are teaching "Machine Learning For Developers",you don't have to waste a whole hour explaining what the fuck a variable is or what is an if statement.Developers know what that is....aaargh.Off to sleep.13
-
Parents who, despite clearly seeing a code on my monitor think that I'm playing games, and need to nag me to study cause they "rarely see me with the textbook".
I'm in an IT university and explaining that everything's in PDF or just online doesn't help9 -
I thought I knew English until I heard my neighbour explaining the difference between Email and Gmail,
(1)Email - the mails which are sent using Electricity
(2)Gmail -the mails which are sent using a Generator11 -
So I found myself explaining to my rubber duck all the things I've done wrong in my past relationships...
What? It's a great guy, I shouldn't limit it just to code issues, I have a life it could fix too4 -
I know pretty much everyone here understands the importance of net neutrality, but here’s a nice chart you can share with all your non tech friends explaining the importance of it in terms they understand
24 -
I have spent 20 minutes explaining to a contractor how to stage a file in git and what a filepath is.
It's moments like this where I stop worrying about my job security9 -
People who ask a question on the interwebs, solves it by themselves and just say "It's OK. I've solved it" without explaining how should have their Internet removed (maybe some light torture too).2
-
7th feb : Spend rose day by explaining my 10th grade nephew how to draw "rose" in c++.
8th Feb: nephew calls me and said thank you, his classmate agreed to go on a date with him.
When i was in 10, i was busy watching micky mouse and all.
Sigh.6 -
introducing my classmates to git and how it can help us.
*explaining scm, git, github and bitbucket, and conflict resolving*
"why don't we just use google drive ?"6 -
Introducing my parents/sister to devRant. This is way more explaining then I thought but very funny 😅.
Especially explaining the word devRant, the principle of comments and rants and how mentions and tags work is a challenge 😆13 -
Me doing monday morning Support because all of our fucking support members were not available.
Me: Can you navigate to the Installation path of our Software.
Customer: how?
Me: with the Windows File explorer
Customer: i dont have That
me: Explaining how to navigate to the install location (thinking: fuck my life)8 -
Fixed this guy's code and he spent the whole day thanking and explaining to me how sad and depressed the bug had left him. I felt really sorry for the poor dude. Lol.
1 -
Today six friends of mine were fired, they didn't know about it, while they were working HR called them and fired them, CEO talked to me explaining reasons of their decision, trying to convince me. I don't care about reasons, its not about reasons, its about behaviors, people are not resources.17
-
Explaining my mom about my job as backend developer... She couldn't understand what is there behind the website. She was like "u designed the website. It's done. What u do full day?"
Finally I gave an example of restaurant... I am the cook(backend developer). Front-end is waiter. Finally she understood....6 -
One day at a doctor who started a small conversation:
Doc: What is your job?
Me: I am a software developer, I write computer programs basically.
Doc: Interesting. How does it work?
Me: Oversimplified you have special languages to tell the computer what to do and then this is converted into a program you can start on your PC. The languages are a bit like basic english (thought of Pascal at this moment).
Doc: So then it is a pretty simple job.
Me thinking: OMFG yes that's why I studied it 6 years, because it's soo easy.
Me thinking at home: Next time tell them that you are a computer scientist and that it is applied mathematics basically. Maybe then they will get a clue of the complexity. 🤔14 -
Just finished explaining to my 13 year old brother that the monitor wasn't the computer... 😧
This is what happens when you get married and leave the house. Your family become technologically illiterate 😔12 -
Explaining to the client that you can't push untested changes to production and expect it to be bug free.
3 -
Online course with ASP.NET 4.
Professor is a loser, convincing students into using shitty 2010 software which will not install and is no longer supported.
>> Sends mass email explaining how to use VS2017
Met with praise. Fuck outdated teachers and technology, truly a shame.5 -
!rant
http://www.howmuchtomakeanapp.com
This site will save you hours of explaining how you can't make every "awesome app idé" that people have!
(Thank me with a stress ball of stress I just saved you 😇)9 -
Had a couple of beers with some non-terminal friends, started talking about devRant.conf.
Started explaining why some post was funny.
Don't make that mistake, friends.5 -
Me, explaining to my wife the difference between WiFi and Cellular as I explain why I need put the Pi from that other thread between our modem and router (and take our WiFi down) all so I can finally answer her repeated questions of "Where is all our data going???"
8 -
so heres to all the fucking programming teachers who use incorrectly terminology when explaining shit. now i gotta go tell my friend that he should ignore what the teacher said and ill tell her how to myself. also fuck javascript and code.org's terrible implementation of an environment for it.
4 -
Had a great time yesterday explaining a C++ dev on a UNIX box that yes, he actually has to shut down his machine before adding this new extra 8gb memory...4
-
Lately, I see a lot of rants/comments/jokes about WinRAR and its eternal trial (algorithm, is that you?). Here's a nice video explaining why WinRAR chose it as its business model and how it works: https://youtu.be/fTgZRVVr3_Y
Spoiler alert: WinRAR is brilliant.
But use 7-zip or be a command line ninja.
6 -
Client: "Help me I can't find my programs"
Me: "Have you installed them right?"
Client: "Yes, I have"
Basically I spent an hour explaining him that dragging an installer from the download folder to program folder isn't actually installing...6 -
First year at uni, during c++ basis.
The professor has just finished explaining the while cycle.
Professor: We want the code to print all numbers from 0 to 40 using a counter. How would you do?
Classmate puts up his hand: we do 40 if statements and when we reach the 40th one we stop.
Professor: *face palm*9 -
My Professor today, explaining data distribution in distributed systems:
"Imagine distributing Username data in subsets, such as A-C, D-F, G-I, J-L etc... And we have a lot of users with A .... *long pause* A bunch of assholes basically .."1 -
I don't know about you, but our fellow Indian colleagues doing YouTube videos explaining programming concepts and whatnot have got me through college and many of my projects.
Cheers for the Indian superheroes in our line of work! Keep doing what you're doing, you are making the world a better place.5 -
Today i had to set my theme to white for my listeners to see clearly what i was explaining.
My eyes hurt😭😭
Please make it stop😭3 -
How I spend my days at work working with legacy code:
* Writing tests before I do anything
* Noticing that i cannot write tests because of antipatterns. Lots of them.
* Refactoring to make at least a tiny bit testable.
* Then writing tests.
* More rewriting and refactoring
* Finally adding that one feature my boss asked me for
* Writing tests for that new feature (my do that before implementing)
* Explaining to my boss why it took me so long and agreeing on stopping writing tests.
* 2 days later: explaining why i still broke something.
But in the end my code works just fine.
my colleagues handle things differently. They just ignore problems as long as at least one feature works a bit.13 -
When you're used to hanging out with developers and you hang out with non developers and get a little comfortable and tell a technical joke then spend an hour explaining the joke1
-
yo guys! im making a raspberry pi claw machine and thought it would be fun to log my progress as i go along, so i made a blog post explaining how to build one! if anyone wants to check it out, you can find it at http://www.alexdovzhanyn.com/blog/1
10 -
Being rejected as "unprofessional" for explaining that I don't want to rush a decision 2 days before Christmas. By the guy who, I kid you not, showed their EKS credentials on screen during a recorded online interview. Kinda glad I dodged that one now that I'm looking back...6
-
Sometimes, when I write scripts to scan random IP addresses for an unsecure VNC server or develop my own NES emulator and someone asks me "Whatcha doin'?", it's just easier to lie rather than start explaining, so I reply:
- Nothing... Just some web dev.2 -
Biggest problem I've encountered as a 100% self-taught programmer in an internship: Having no idea the meaning of half the words my boss uses when explaining my assignment... I always called most of them "that thingy that does the thing" XD3
-
If someone asks me how to hack software, I answer:
'Well, basically it's just like searching for open doors of a unknown house you want to get in.' 😎
Usually the answer disappoints everyone. Then I add:
'Why so surprised? Would you leave your main door open, if you want to store something securely in your house?'
I love those disappointed faces from time to time. 😋1 -
analysing a database problem and writing a 4-line fix: 5 minutes.
preparing a foolproof manual for the manager on how to apply the fix: 15 minutes
writing a manager-level explanation what the fix does: 30 minutes.
explaining it to the manager: 30 minutes.
writing a _detailled_ explanation why we need the fix: 60 minutes.
explaining it to the manager again: 30 minutes.
figuring out why our progress is slow:
_priceless_6 -
- git commit -m "well described comment explaining addition"
oh crap forgot to take out this one thing
- ctrl-S
- git commit -m "ahskdbejjeebdosjeb"3 -
2 days ago: *rants about HP's design choices on a laptop*
22 hours ago: *new video from GreatScott comes out, explaining all about voltage tolerances for the charger etc*
Coincidence? Maybe not 🤔4 -
What do you guys tell your friends when they ask what you're doing on the computer? My wife asks all the time and I usually give a generic answer like "writing code" but lately that's not good enough. Today I had browser dev tools open along with vim because I was building a web scraper in python and I needed the structure of a certain site. I tried actually explaining it but got nowhere so I ended saying I was just downloading content from a site. Do you just give generic answers to people or try to get more technical? She seems unhappy with both approaches but maybe I'm just bad at explaining.12
-
OK I live in lithuania, small country, my grandparents live in silute, super small city, the internet is shit here, I need to use my mobile data to program, next day I wake up to this graph explaining me how I lost all of my fucking data😤
41 -
I'm in internship, why the fuck am I the one explaining them how to use git, Android studio????? Why am I the project manager?????? I'm supposed to learn from you not the opposite. Fuck this monkey.15
-
Ran couple of interviews today I don't think I'm ever gonna forget this guy: He was explaining a time he worked in a team and used version control. I asked how he handled merge conflicts his response:
'If there are merge conflicts I delete their work and use mine, my code is probably better anyway'.4 -
The worst thing about being a dev is explaining to these fucktards that facebook can't be hacked.
But what is even worse, is when these dipshits say that i am a bad dev for not hacking facebook for them.
Use that big stupid head to sometimes think straight and stop being a little twat.3 -
Do you know what's better than getting work done. HAVING ANOTHER F****ING MEETING ABOUT WHAT WORK NEEDS TO BE DONE!
I COULD'VE HAD MOST OF THIS SHIT DONE BY NOW BUT I HAVE TO SPEND 1/2 OF EVERY DAY JUST EXPLAINING WHAT THE F***K I'M DOING, WHAT THE F**K EVERYONE ELSE IS DOING, AND THEN EXPLAINING WHY IT HASN"T BEEN F***ING DONE!
YOU WANT TO KNOW WHY EVERYONE IS LEAVING WHY YOU CAN'T RETAIN ANYONE? YOU HIRED THEM AS FREAKING ENGINEERS PROMISING THEM THEY WOULD BE ABLE TO DO THINGS AND THEY SPEND ALL DAY IN F***ING MEETINGS WASTING THEIR IQ AND WISHING FOR DEATH!
GGAAAHHHHH! BY THE EMPEROR PLEASE COMMISSAR END ME!4 -
Explaining to my boss why we can't use the WordPress theme he saw on Theme Forest in an Android app7
-
Friend: I really dont see how Java and JavaScript are different
Me: *Several minutes explaining the differences
Friend: Ok, ok, but if i write 'JAVA' scripts, im a JavaScript programmer right?
Me: No, you're an asshole3 -
Me: explaining the FOSS project I'm trying to get started, to my parents.
My dad: So how do you get paid?
Me: what? No....2 -
when u want to explain something to a collegue and u use all your mind in explaining it by words and he doesn't get it.
draw it! haha! even my flowcharts doesnt look like flowcharts, he got what i meant..XD
2 -
Merry Christmas everyone! 🎄
If you are home with family, hope you enjoy solving their problems or explaining Bitcoin!1 -
Explaining what a method does:
"""Python has docstrings"""
/** Java has javadocs */
SwiftHasSuperFreakinLongMethodNames()
Seriously Apple...7 -
Nothing irks me more than when I sit down with a fellow student and try to help them with a programming assignment that I’ve already completed and after clearly explaining everything to them they just say “Can I take a picture of your code?”. Uhm... no. Fuck you.1
-
The thing is that I have told my family a few times what I really do at work. But I have to be honest: explaining what a backend dev does is hard without showing a GUI 😂
Sometimes I even think for myself: wtf am I doing here... 😁1 -
I hate it when my manager lurks around when i am debugging and keeps giving random unsolicited advices. I spend more time explaining him why what he is saying does not make any sense than debugging.3
-
fucking hosting company...
Just got a ticket back explaining that "the settings you want to make to your mysql database aren't possible with our hosting products". While they state in their FAQ that there are no restrictions applied. (We are talking about to possibility of using JOIN here!)
Ducking fuck.11 -
Instead of investing in a rubber ducky for explaining my coding bugs I decided to have Alan Turing be my listener. At least he'll be more understanding than a pretentious biased rubber duck!
2 -
fuuuccckkk stackoverflow.
q: "why doesn't python do this like i want:
me: "Here's an answer that quotes an article and links out explaining with Python 3.6.x doesn't allow that."
every fucker: "downvote, doesn't answer why it isn't allowed"
FUCK YOU, PROVIDE AN ANSWER THAT DOESN'T SAY WHAT I SAID5 -
A cs degree without indians explaining concepts on Youtube would be much harder.These guys savede so many times.5
-
That moment when the instructor is explaining array in Java, and you are the only one in the batch having 4 Years of Experience, and Certification by Oracle4
-
"While the number of rabbits grows, the rabbits will grow in number."
Teacher explaining the Fibonacci sequence.2 -
When I get stuck I usually try a variant of the duck method. I find someone not involved the project and explain my problem to them. I always figure it out before I finish explaining3
-
!rant
Just wrote my first piece of code using neural networks. Even explaining it to people is fun: "So you wrote a program that writes code?" "Exactly!"3 -
My company don't trust the employees to the point, we have nearly meetings every 13 minutes explaining what we do.
I just wasted one week of implementing the features due to unnecessary meetings.7 -
Fuck group projects/labs. I hate them. I typically find myself explaining basic shit that was covered in previous lectures, or just doing all the work myself because they could care less.4
-
I just corrected my CS teacher about 5 times while explaining generic classes.
WHAT THE FUCK, EDUCATIONAL SYSTEM?!7 -
Me @40 explaining to my parents why am not married yet.
"Well, see, I prefer short commits,
(I mean everybody does)
And then I require at least two peer reviews and approval before pushing.
So she really needs to be perfect to merge"1 -
When your client asks you if slow pageload can be fixed in a half an hour, after you've spent 5 minutes explaining over the phone how you're currently driving to another country.2
-
Dad showed me how to build a computer when I was three. Then he spent the next ten years explaining how variables work over and over.
Then I freaked out about being poor forever, applied to one of the cheapest 4-year colleges in state, and am doing my best to do that whole Computer Science thing.1 -
Be us
Be pair devs
Be doing PHP
Be explaining code to each other to find bug.
Be confused. Code checks out.
Be laughing asses off
Be realise the filename had a m instead of n
@TheCapeGreek -
11.1/11.4 GB of RAM is being eaten open on boot, even though I just rebooted. Almost half of my swap is in use too. WTF! Windows is no help in explaining it either...SO ANNOYING!
15 -
currently in a hackaton right now and I really hate my self for being so dumb in presenting/explaining my idea. oh well, better luck next time.2
-
Today I spent 25 minutes explaining to this dev that there’s no way that a http request can access directly to an ftp server and retrieve a file.
A dev with 4 years of experience...17 -
Have you ever talk with client and start coding and ui design in your mind while client explaining the requirements?4
-
*Explaining over the phone how to connect an iPad to the internet
Me: "Select the wifi network and put the password in"
Them: "It says here something about the IP Address - is that the postcode?"
😩2 -
That thing we all tried - explaining to project managers what the difference is between back and frontend,
Today i got 23 backend bugs assigned to me as a frontend 💩 -
I hate looking stupid when I have to ask clarifying questions after the person explaining something to me has left out a ton of information. People assume way too often that I can “fill in the details” from a vague description that they think is complete.
4 -
Me explaining my project to my teacher -
Me: So all these functions are carried out asynchronously so the user doesn't have to wait much and the whole thing is placed in a web server.
Teacher: Where is the web server located?2 -
What is starting out progaming without explaining to your parents why you making an object move when you press a key, is not only impressive but also took you 15 hours to learn?4
-
Explaining why I need something installed on my work laptop in a request ticket: BECAUSE IT LOOKS COOL1
-
At the University, Algorithms class, exercises lesson..the assistant explaining the results of an assignment:
"Because here..if we use a classic 'if-else' loop..."
😳1 -
We've been using a recruiter who works out of the same business park as us. They purport to be "specialists in technology".
Somehow a conversation got started and I ended up explaining how we make use of open source software, where possible.
Their response: "That's the free one, right?".3 -
I lost points for not including the following comment:
//Declaring variables
int foo, bar;
I already knew how to code, and I completed the assignment in the fewest number of lines needed while still being well commented explaining my logic. I lost points because I didn't say what everyone understood.4 -
You know what’s more annoying than someone downvoting your answer on Stack Overflow without leaving a comment explaining why?
When it’s your own answer to your own question... -
Manager: You can ask the Level 1 team in India to assist you, they can take take some load of you.
Me: *spends 30 minutes explaining a 5 minute job, several times, each day*
Manager, after noticing my stress: Really, just ask the Level 1 team to assist you!1 -
*Writes something I think is clever
*Write like a 3 sentence comment explaining why it's clever.
*Smugly run.
*Doesn't work.
*Quietly erase line and comment.
*Repeat -
Good god. In an entry level CIS course, the teacher is literally explaining binary as slowly as possible and then spouting misinformation about sound waves and telephone stuff. Ugh.2
-
When you survive WannaCry but now your email inbox is full of spam from antivirus companies explaining how they could've helped you.
Nobody was ever safe. -
I'm reading (deciphering) the clients notes for modifications to their app and explaining to my PM what they want. At one point, he stopped me and said "How the fuck are you doing that? I don't understand how you can make those connections. Brilliant." 😂
-
Update to: https://devrant.com/rants/1573298/
So I just had the interview. It wasn't too bad, but I caught myself stuttering and saying "uhh" way too frequently. I also kind of stumped my toe on a question about explaining a computer virus to someone.
Hopefully it'll go well in the end.4 -
Is it normal that IT support of a multinational bigass corporate drops the "we may need to change your PC because maybe your network card is defective" after explaining over and over that you have problems with HTTPS only when using the corporate network (whether onsite or via VPN) and not in external connections?3
-
Having to explain to non-programmers why devrant uses ++ and -- for invited and down votes....Same as explaining why they named it C++
-
Me: Explaining what I do for a living (strip's title)
So true though as most of the workday is not coding...
Or is that how you explain all that typing (coding) to a layman?
3 -
Is it just me or do any of you people also hate asking for help with understanding other devs code?
At the same time I also hate explaining my code to other devs, like I have to justify I'm not an imbecile.6 -
*Me explaining how the modules were planed out*
Me: Did you all understand how we are going to proceed?
Coworker 1: yes!
Coworker 2: easy!
Narrator: An epic story about a group of software developers, that build walls instead of modules, is about to unfold. -
Rubber duck debugging. When you find that explaining your problem to another person helps you come up with the answer but you hate people and/or have no friends. Yay for rubber ducks3
-
Clients expecting quotes before explaining the full extent of the work and then getting mad when I change it after they add a billion more features.
Also, cross-browser testing 😫🔫1 -
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 -
If you ever thought hell didn't exist...
I just spent the day explaining cryptocurrencies to a room of social sciences and law students.
I really need to get drunk, but it's only Thursday 😫3 -
1. using "if... then... else..." When explaining something tru slack to non tech people
2. buying lamps i can program
3. dreaming abt my code
4. dreaming abt the solution
5. trying to make bot to send happy birthday msg -
Every time I talk about a bug/error in my code with my colleague, I end up coming up with the fix myself while explaining it. I accidentally use him as my rubber duck...3
-
I didn't know "bandwidth" can be so hard to understand even after 2 hrs explaining..client still wants widgets with autoplay videos..God why?4
-
I’m not a native english speaker.. had lots of interviews but all rejected me... I guess I was not good at delivering or explaining things... is this language barrier really is important.. working in canada11
-
Tried to write a short article about Javascript IIFE modules, ended up explaining about function block scoping all the way to closures before I eventually get to the IIFE module explanation itself...
I'm really bad at this 😓1 -
My programming teacher is explaining functions in C++ as if they were rocket science... Complicating things when they're easy5
-
when your family comes to you to fix every problem with their computer and you're too tired of explaining what you actually do, so you put on your most professional look and hope for the best
2 -
Was explaining the usage of   and white space in HTML to a confused nondev colleague. He later asked how come there is white space, when this program you use to code is a black..while pointing to my dark themed text editor.
-
Working on this bug for a day. Frustrated Friday afternoon. Decided to explain to my manager and senior why I can't find a fix and while explaining it to them, I eventually figured out the problem and fixed it.
I just realized I used my manager and senior as rubber ducks. -
Explaining to the new team, all with experience, how to compile and what to do with errors. 😓
What are they teaching in school these days?1 -
Explaining difficult things in a way that they are understandable by non-expert audiences.
This helps a lot to focus on simplicity when programming. And simple means it'll get understood by your peer programmers, it is simpler to test and it will be easier to maintain, and so on... -
Reviewing and explaining 1 year old bad application logic to your client because he asked for it and now he can't remember how the application work.
-
Presenters, please. Do not name your presentations "Advanced X" if you spend 75% time on explaining every detail of basic software usage. DO NOT WASTE MY TIME LIKE THAT
-
Cross time-zone design reviews are brutal! Feeling super exhausted, explaining shit I designed feels like torture! I mean, just get it!
-
I've spent the past few months working on creating a decentralized application network built for developers. Here's a link to a quick blog post I made explaining the idea. I'd love to get some of you on board! https://dev.to/alexdovzhanyn/...2
-
Another project, another team, another shitshow in codebase.
Now instead of doing work and implementing long awaited features... few weeks of minor refactorings ahead, untangling unnecessary complexities...
... but mostly - explaining the team why their 12-months work is pile of shitty spaghetti, and how it should really be done.
Explaining basics to "seniors" is the most exhausting thing.3 -
I have a very annoying person in my team, who thinks he is the leader and is so full of himself that once he gets some idea he makes it final without listening to other's opinion, kinda anti-humble.
Today he was explaining that we are going to implement this feature and one of the member had a doubt which was legit so that guy started explaining it, but didn't really understood what the question was ( as he always does) he was heated up already as he was explaining the same thing again and again but it was nowhere near what the exact question was, by mistake I entered the conversation and tried to explain the question to him, he became so annoyed that he lost all his patient and shouted at me to shut up. Not only I felt bad but also found myself helpless in such situation i didn't know what to do, I was annoyed like anything, and now I think that I don't really know how to deal with annoying people such annoying and toxic people..6 -
Why commenting is important?
If you are commenting a variable or method and you can't find the right way of explaining it, there's a problem with your code6 -
Guy wrote a whole ass thread explaining how to fix it and its not a big issue but the manchild elon musk's ego couldn't handle being wrong so he fired him
39 -
Looks like using another language to develop a separate process on the system is too much of a mind blow to my boss.
The look on his face when I tried to suggest such thing made me realize it will not be worth the time explaining the benefits of using the right tool for the job.1 -
"Where an expression’s main job is to produce a value, a statement’s job is to produce an effect."
That's the cleanest way of explaining the difference between expressions and statements I've ever seen. Kudos to you, Bob.
craftinginterpreters.com if anyone's interested.2 -
When you say to a non-techy: "This is complex."
Meaning: "I don't want to spend my time explaining this to you" / "I don't care".
1 -
When you have an error and you search for the solution on Google a video pops up a there is a kid maybe 10 years old explaining the problem. 😥1
-
I guess talking to a duck helps after all although my duck was actually writing an email to business explaining an issue I am having in a requested change.
Right before I hit send, I go... Ah I get it now!
That saved me from some embarrassment :) -
during a programming introduction course on loops my pals started writing `for` loops instead of `while` loops like so:
`for (;expression;) {}`
spent weeks explaining why it's wrong. needless to say, they still do it. had to hinder myself from ripping my hair off my head11 -
At my workplace a while back we got some new interns.
I had been explaining how to use the commands on our Linux server. While I was in mid-sentence talking about what shutdown does, the intern inputs the shutdown command; shutting down everything... not shortly after, I start getting bombarded with emails and calls...4 -
Yesterday I was doing amazing coding, making big things happen, today I'm explaining how the internet works so a customer who doesn't care this job is so bipolar.1
-
When explaining unit testing:
"We tried but every time someone changes something in the database all the tests fail."
*facepalm*5 -
Final year of my diploma in Information Tech, I overhear a coursemate, well-known know-it-all, explaining what Javascript is:
"It's somewhat like Java but it's used for scripting purposes."
I swear to the Lord Almighty, I wish I could drive my palm through my face.1 -
On my first day at new job, a non-technical person used CQRS word while explaining the system. When I asked what's need of such a complex pattern for simple query type service, he simply backed off. 😝
-
The awkward moment when you name your dictionary "dic" and realize that while explaining a piece of code to a female colleague. 😳1
-
(Fyi: I was an intern.)
It took me hours of time to recognize, that one of the necessary tables just used an oracleDB Date as a timestamp, which lead to a violation of the primary key constraint on interactions taken place in less than one second.
Me: (explaining the problem to CW)
CW: "Yup, we know."
Me: ...2 -
UGH! Wasting time explaining to the client why you are not adding information/functionality to a page since a separate software will do it all (and better than what you would do).
-
Taking notes or explaining mathematical,/physical concepts by writing I'm C++ syntax.
It's pretty good because all my other chemical engineering classmates stopped asking for my notes.2 -
Every person project cycle.
1.thinking 2.making bitbucket private repo 3.Making slack channel for contributors.4 Explaining the idea 5.the end.
I seriously need to work after step 5 -
stop teaching language syntax and start explaining the ideas and the concepts in computer science.1
-
Nothing worse that watching a tech talk where the presenter is accidentally condescending.
It's definitely a "know your audience" situation, but it's cringe worthy when explaining a really valuable topic. -
Ever tried explaining GitHub to someone? I swear it's like trying to teach a dog to ride a bike. You can try, but it's probably not going to end well.
Okay, rant over. Back to coding... and dealing with merge conflicts... and pull requests... and GitHub issues... sigh.4 -
when you spend more time in JIRA explaining the client that their bug is not a bug but misconfiguration on their side than actual programming. :-/
error between chair and keyboard.1 -
Got a Dec duck for Christmas from my brother in law.
Funniest part was explaining to the rest of the family why I got a rubber duck...
3 -
- git => did you use sourcesafe anytime?
- VS Code => because everyone is against MS ;-)
- hammer (for keyboard) => self explaining -
I get it you don't know anything. You are not paying me to be your teacher.
Let me do my job!
At what point can we stop explaining ourselves and every little detail of the job.1 -
I dunno if any of my choices have been "bad". Humans are great at explaining things to themselves to feel better. Narratives is our strength and we love them.
In hindsight everything seems to be a correct choice and kinda makes sense. For everything else is just a lesson to learn from.2 -
When the technically inept PM wants to be included on every single email thread. So then you have to waste even more time explaining.
-
So tired of explaining other stupid developers that POST is not more secure than GET in a ReST api. I have heard many times if you use GET you will be hacked :|
-
Have you ever had a subject in university that is very interesting but the lecturer has such a way of explaining things that you begin to wonder that he is a robot trying to imitate humans? Really nice guy in person though.1
-
I'm not explaining why I am saying this, but,
Fuck AI, Fuck OpenAI, Fuck Sora, Fuck Sam Altman and especially, wait for it, especially, Fuck Devin.7 -
Today I felt like the grinch explaining to my team that you can have memory leaks in a garbage collected language if they keep leaving live references.
-
Boss explaining a bug found in my senior developer's (yes, that one) application...
Boss: "This shouldn't happen, this presents a security issue since these records should not be visible at this point."
"Senior" Developer: "You're right. Hmm, what should I do about that?"
Me: *face palm*2 -
Being a scout.
It allows me to practice leadership, patience and explaining and it forces me to be outside and active every now and then.
The fresh air really helps, and I always bring a notebook 🤓3 -
Since CS is about the science of computers and not about a particular programming language, it would be nice if assignments were accepted in any non-esoteric language, as long as it can demonstrate that the student has learned whatever he was supposed to learn.
Bonus points for explaining well why that language was chosen.1 -
Dad: what do you do in IT classes
Me: mostly, learning new languages!
I'll never forget that confused face of his. Of course I explained him there were languages in informatics to. Still, it was pretty funny explaining it all. I'm happy he really thinks informatics is the future! -
I made the perfect situational joke:
I was explaining physics to a coworker and stating that the only particles that are important for everyday life are protons, electrons and neutrons.
CW:" What about neutrinos? You don't care about them?"
Me:" No, I don't. Wanna know why?"
CW:"Yes, tell me."
ME:" Because, they don't matter!"1 -
Fucking hate explaining and convincing people why Linux is better.. The least the can do is give it a shot and experience themselves.20
-
When you hear a conversation where a developer tries to explain difference between JavaScript spread operator and an ellipsis to a random person they walked past.
20min now... (Ellipsis is intentional here) -
Anyone else ever not feel like explaining something technical to someone in a different non-technical department or position, so you use a lot of techy terms and make it sound really confusing so you can move on with your life?
-
As the only developer in the startup team. I am really sick of explaining "how it works" and "how to execute"...
-
Me, explaining once again that a webserver needs to be thread safe:
"I have nothing to learn from my colleagues".2 -
Project/Middleware/APIs website about section- Writes a lot of things which is hard to get for many, than explaining exactly what it does
-
3ds Max Python API Documentation.
No function has a single word explaining what it does.
The Documentation seems like it is completely auto generated and while writing the API they forgot to add Docstrings....2 -
When you're explaining your app to a non-dev, don't. Use. Technical. Terms. It's not that fucking hard. Don't talk _down_ to them, but use terms they fucking understand.4
-
When I was at my previous sales job, explaining the same sales pitch for the 987345284th time, listening to my customers' every irrational need, I suddenly realised I wanted to work with something rational and logical. Best insight of my life!
-
The time it takes to develop a feature is the square root of the time it takes explaining it to the PM1
-
I bet jake wharton is going to post his cat pics in a repo someday and that would also get a 1000 stars, 350 forks 80 issues, 4 prs and 30 medium articles explaining/suggesting/worshipping/debating on it XD5
-
The worst part about being a Dev is explaining what exactly that you do to your distant relative who knows nothing about computers 😑
-
"For Product projects *company name omitted* uses a combination of Waterfall and Agile methodologies".
Wow. Nice they're actually admitting they're doing it. But the paper that explained what Waterfall was spent most of the time explaining why it was a bad idea. -
Spending hours in conference explaining app to customer and the only question you get afterwards is: when will it be finished ?
-
I come to check in to the office during my vacation to see how the project is going. I find a colleague from a vendor explaining it all to business and pushing over CSS changes to the next release. Current release is MVP1 and is set to release 3 months for now. *facepalm*2
-
Are there any other devs out there whose minds go blank when they try to teach coding?
Whenever my friends ask me coding related questions, I just cannot explain it to them. I cannot think of any examples even. And when it comes to explaining the method used by the program, I just end up confusing them even more.
I feel so bad when I cannot help them understand.3 -
After inputting all of the defect info into the bug tracking tool, QA writes a quick summary of their findings and goes home.
Love explaining to mgmt why developers could not fix bugs because they had no access to the bug tracking software.
1 day.... X number of bugs... 0 progress -
"Write a tech tutorial without explaining something via a fucking stupid as hell analogy" challenge IMPOSSIBLE.5
-
I wish Docker had docs explaining how to migrate EXISTING projects. The pros better outweigh the cons after all this time...5
-
Working with a manager who thinks they know how development works but doesn't actually know is the worst. At times your better off fixing the issue versus explaining it to them. Fix it then explain it.2
-
Today my project manager called Hadoop a data warehouse and a Big Data lake in a meeting. I couldn't decide whether to laugh my ass off or spend the next 30 mins explaining to her what Hadoop actually is.2
-
Paraphrased wise words from lecture by the one and only Donald Knuth:
If you want to learn something new, don't try to learn by explaining it to another human. Make a computer do it instead because then you'll have to truly understand how something works for all cases.1 -
Explaining !IT people my job...trying to sound more professional as possible so they don't think that I just "play with computer" :)1
-
Explaining to my Scrum Master EVERY morning from scratch the technical details of the story so that he can give his blessing to why the story is still In Progress column!
-
The worst part of being a dev is actually explaining what you do to people with no technical experience.
-
I got more interested about the technical side of bugs in video games.
Really didn't understand the Pokémon hype as a kid, few months ago watched an entire YouTube series explaining the Old Man Glitch and ACE exploits in the game. 🤷♂️1 -
If you want this app better, stop posting crappy content or content you have to end up explaining.
Simple, isn't it?
3 -
Currently being a TA for the software development course in my college, spent an hour on a stupid student for explaining what is a constructor.
-
when your coworker wants help on something but they can't seem to explain the problem or you fail to understand them explaining the problem
also not sure if i had to show them how to set a debugger breakpoint in the web browser debugger
fml1 -
As much as I hate writing documentation, I agree that it's a necessary evil. I also try to be as descriptive as possible where it makes sense. But, do we really need a 6-page document explaining how to run a query that updates a user's role?1
-
Hey guys,
do u know a simple and well designed program, that's suitable for a presentation about design? I am explaining UX, UI, IA and IxD and I need a simple example to show my class the components of a program that represent these.
Thanks a lot :)6 -
A colleague and I joined a couple of friends for dinner and my colleague was explaining how our company reacted to him showing them another offer he got. Just by thinking I am being too slow at looking for another job (even if it's to negotiate better conditions) my back got so tense is hurting...
-
In the last couple of years I've only really had 2 kinds of meetings, weekly stand-up or me explaining something to someone. So they're usually pretty productive.
-
- devRant
- reddit
- people asking me how to solve a problem in their code and me explaining it to them -
!rant
If you're into compilers AND AI, check out Glow Compiler.
https://arxiv.org/pdf/...
Explains the idea well, casual read, almost no math just clean code examples and lots of easy reading explaining the ideas and theory behind it.
You can find the project at https://github.com/pytorch/glow and and also https://ai.facebook.com/tools/glow/1 -
Hello guys, i need some advice:
Our school is having a "auto-management" (idk how to translate) period, it lasts 3 or 4 days just before christmas vacation, and in those days students get to organize courses about pretty much everything to teach stuff to other students (exept stuff like video games cuz the principal is closed-minded), some friends asked me to make a course about programming in c# because they are interested, i thought it was cool so i said OK.
Now i'm thinking how to structure it, it's going to be 2 "lessons" of 2 hours each, and it's open to everyone in the school.
I don't want to do a full blown course explaining everything, i just want to give them a kick start and point them to the right direction, I thought about explaining some "theory" in the first lesson, I'm assuming almost everyone that will come never did programming stuff, so i'm thinking of explaining stuff like how a computer works, why you need a compiler, etc.. maybe based on the introduction from learncpp.com without getting to much into the details and then explaining how c# works and its grammar.
Then in the second lesson i'll try to code togheter some stuff (We'll have just one pc attached to a projector).
So, how would you do this ? I mean i never tried explaining programming to someone else and i'm self-taught i looked at the guide on msdn but it starts directly by giving you an hello world, should i follow it ? I fear i'd get too thecnical and they wouldn't understand me, do you know some good guide i can use as a reference ?
ps: there's going to be max 30 people1 -
today I was explaining a non tech guy , how 2 mobiles communicate with each other via a server. It started of really good. Then I got to know that what I was speaking was looking like Greek to him. This made it very clear that explaining things are also a difficult job1
-
If you have a template of what you're expecting me to make, don't bullshit around for 2 weeks explaining what you think you want. Just give me the template and I'll make what you actually want.
-
I am going to school for a BS in computer science and the other day my dad tagged me in a job for IT. Spent the next couple hours explaining what my job actually is.1
-
Someone just spent an evening with me explaining how to use Ember and *not* fuck it up.
Ember is actually quite nice if you know how to use it :)1 -
I work in such specific domain that most of my daiky issues would require too much explaining to rant about them...
-
Mess up explaining a pull request working backwards from the why of the issue, instead of explaining what my code changes would do in the order the machine would execute
welp
should've clarified on what/how they wanted me to clarify what I did -
Fighting for an hour explaining how a query wouldn't return the data he wanted...turns out it did...but really not sure how... FU Access!
-
The constant re-explanation of how stuff should be done, whether it's business logic or even in simple programming itself. When it comes to developers, I find myself repeating myself a lot simply because they can't be bothered to understand what business rules are needed as all they want to do is just code a solution and get it over and done with.
-
Every week you meet with the loneliest dumb person explaining what you had already explained the last week.
Even now I remember the week that it all started. It all happened when I got the job 😅 -
I'm currently refactoring some Fastlane code at work, and I'm wondering what is the fundamental difference between a "lane" and an "action"? I can't really find anything in their documentation explaining the difference.7
-
kudos for the tech-staff of the digital congress ot-world.connect for explaining how things work to all the non-tech speakers over and over again.
Top Tags
Weekly Rant
View