Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Search - "misunderstood"
Her: Hey, just heard what John did to you.
Me: Yea. I can't believe he screwed me over like that. I thought he was my friend.
Her: Don't worry. Forget about the bustard. You know #FFF
Me: 🙁 #FFF? What does white got to do with all this.
Me: #FFF. This is white.
Her: Nooooo. It means Fuck Fake Friends. As in the G. Eazy song.
I was explaining to my mom how my company is in need of developers and how we'll need more of them in the future - to which she replied:
"oh... what are you going to do? You can't live without a job!"
- erm? What?
"Well - you're not smart like those guys. You'll probably get fired now."
- Wtf mom!? I'm a friggin lead dev and i've been a developer for like 10 years now!? 😳
*silence* "is that what you've been doing? I thought you just kept clicking on stuff"11
So I was with my friends on the subway and we were talking about an assigment we have due this week with trees in Java. I got to say, the face on the old ladie next to us when we said "we must kill all the children left in the tree" was just epic! She must thought we were talking about beating some little kids or something... 😅3
Assembly Programming is a misunderstood and tragically underutilized form of self-abuse.
While the ladies were off reading "50 Shades of Grey," I was reading the ARM ISA documentation.2
How to talk as a dev to a dev:
1.) Talk normally
2.) Start shouting
3.) Slow down but say it more aggressively
4.) Realise you made a mistake and/or misunderstood something
5.) Explain why it's not your fault
6.) Explain why it's someone elses fault
Back in my teenage , a friend of mine asked me «Can you make me a software that guesses the result of a football match ?» I said «Sure, but you have to tell me how to calculate the chances of a team»
«Yeah, use the previous performances in the league»
«Ok, but you have to tell me how to calculate the expected result using previous performances» He laughed at me and said «If i knew how to calculate chances of winning/losing, i would not need a software!»
I tried to explain it simply «Computers can execute basic operations like sums or subtractions, and they know how to follow a list of basic instructions to give you a result»
He looked me like «If computers are so stupid like you are telling me now, are we all crazy idiots trying to learn how to use stupid machines??» and stated that i obviously misunderstood the real power of a computer. I walked back home thinking how funny was my friend believing in some kind of magic inside box called pc.
Few years later, i start studying IT at university. In the free time i look for small jobs like website development, small office network setup, pcs repair.
I continue noticing people believing that pcs knows what to do and how to do it.
«You sure I lost my data ? No i didn't do a backup. You sure my pc didn't do a backup ? No i hadn't a backup software»
«Why antivirus asks me what to do with the viruses it found. It should delete them obviously! Change my antivirus, it's too stupid for my pc»
«I want more people finding my business thanks to my website. How I imagine my website ? Yeah it has to be cool and full of cool stuff»
All that boring stories leads to my final question :
is our job dealing with persons who think we are some kind of wizard, well learned about dominating the pc magic ?
Please answer no.Please.15
I just hate how non-developers can easily conclude that we are drug addicts. Just because we talk to ourselves while coding or always seem off/cranky because of the countless sleepless nights. I mean like, please be a bit more considerate. It may seem like it isn't a big deal since it isn't true anyways but it clearly shows that they can't understand our situation.
Try being in the shoes of the misunderstood for a change. You won't like the feeling since all you ever wanted to do was good.5
!dev !sex I promise this is a good read
I once read the whole bible.
Not in one sitting, ofc. I read it in a period of a year, just 3-4 chapters a day.
Is it something to boast about?
I'm not sure.
I mean, I guess being able to read through it despite not being exactly entertainment material (except some fun parts) kinda is. So I might feel a tad bit proud about that.
But I'm actually more happy that I did instead.
The reason I'm more happy than proud is because I took awareness of the religion I was in.
I became christian when I was an early teen. I grew up in an agnostic family. My dad was kinda hippie and my mom was into leftist ideas.
So me becoming a christian was a bit orthogonal to their philosophies.
I started assisting a church because I was very alone and misunderstood, and found some people there that seemed to get me, and viceversa.
But as time went on and I got more exposed to christian doctrine, my level of commitment grew.
I wanted to save people from going to hell. It sounds funny, maybe egotistical, but it's true.
3, 4 years of being in the church go by. I collaborate in the church, I make some very personal friendships, I was very deep in church by that point.
I then decide that I should take it to the next level and read the bible. So I did. And unknowingly, it started this feeling in me that I didn't liked being a christian at all.
I'm not gonna deny there are some christian values that are still compatible with today's modern society, such as being a good samaritan, working hard, being honest.
But there were too many verses in both old and new testament that I found morally repugnant,
The ones that made me feel the worst about christianity, though, were the ones that condemned homosexuality with death.
Since my dad was a hippie, he used to be in artsy things, like theater or music, and through that he had some gay friends
And for real, I think they were the nicest and most cheerful people I'd met as a kid. So I could not be part of that anymore.
Let me clarify that I didn't stop being a christian immediately after finishing the bible, but it did start a spark "of "what tf do I even believe in...?"
That spark turned into flame when I started the university, a place where people think for a living.
It's no wonder my mind started completing the puzzle, and slowly I started liking church and christianity less and less.
Until one sunday I didn't want to go, and I didn't, and from then on, I pretty much severed ties with that church and christianity.
Which is crazy considering I went every sunday without interruption for 6 years, and several saturdays too.
Anyhow, that's my story of me getting in n out of christianity. Like in the previous post, it sure how to end this, so go fuck a rock or something.12
"You can be misunderstood exactly once. After that, you are not being misunderstood; you are communicating poorly." - Josh Collinsworth5
Basically finished the notification filter script* already, but there's still some small bugs I want to get to first, so in the meanwhile I created a "subscribe" button script**, that simply posts a pin emoji and "Subscribing to the comments".
On desktop I usually used to post a dot to subscribe to rant comments, but with the new people wave, that was often misunderstood (you emoji users won the evolution of comment subscribing, RIP dot) I'm sure some other people that use the webapp more often, will find it useful too.
* notification filter: https://devrant.com/rants/1424435/...
** subscribe button: https://github.com/7twin/...17
Hello, I'm now gonna rant for a bit. I'm usually not a ranty person (wait, why am I on this site again?) , but here we go. I sometimes feel misunderstood about my side projects.
I don't know about you guys, but when I program on my free time, sometimes I just want to grab a glass of wine and explore things I think bout during the day. So, during the start of my CS-education, when I started to get my programming feet a little warm, I wrote this tic-tac-toe game (as you do...), and I thought "Well I know how to play the game. Surely I can program an AI to play against". So I thought hard for an evening or two and came up with something that wasn't too shabby (I can't win).
Then another time when learned about creating GUIs we got to do simple menu based stuff with buttons and pulldown menus following a certain structure, but we also learned that positions of components can be set freely. So I thought "Well, if I can freely change the positions of components, surely I can animate stuff and if I map that to some keys I can create a real time game!". So I wrote a small platformer with two squares that ideally succeed in killing one another. After animation I started fantasising about 3D rendering, so I created a small application which creates the illusion of 3D, which was cool and all, but that got me dreaming of creating a real 3D engine. It became almost like a cause of mine; to understand how it all works and create a 3D engine from scratch.
So now I've written a 3D engine. A simple one, mind you, without all the bells and whistles, but still a 3D engine.
So, after all this rambling, what is this rant about? It's about how people react to all this. The reactions are divided. Some are impressed, mostly people who cannot program, but others are like "hm...". For example, during job interviews, when people ask me if I've done anything on the side and I mention this, people usually go like ".... hm... :| Well that's great. So mostly just done your own stuff?". Well YES! What is that supposed to mean? That I've not created shippable applications? I've explored, which I myself believe is valuable! I believe I've learned something along the way. And most importantly I've enjoyed it. Maybe I'm over interpreting this, but sometimes it feels like people don't even understand the joy in it, like it's illogical. Why create something that in the end won't create any real value?
Am I alone in this? Or perhaps, have I just written far to long and uninteresting a rant for anybody to read this far? I don't know. You tell me.13
I tried writing this rant before, but I was (and still am) in too good of a mood so it was lengthy, meandering, and over-specific. so I'll summarize(ish).
* working weekends
* incompetence and/or screwy integrations
summary of the summary:
* I can't fix someone else's mess if you don't talk to me!
Summary^3: #TODO: learn telepathy
Bossman at work signed up a very lucrative client by promising them something he couldn't deliver because he misunderstood and miscommunicated scope -- anti-fraud, if you've been following my rants.
Their signup (all four...) are screwy and cause issues and nobody knows why. I didn't write the code, have barely even glanced through it, and it uses a third-party (Clover) that's rather screwy.
Bossman has been asking me to do various things concerning the merchant, but has never been around to provide specifics, so I'm left to guess. I've done my best, but due to the aforementioned screwiness, I really have no idea what's going on. I just sort of muddled my way through.
Bossman also asked me, super late on Friday night (after 8:30pm), to rename one of the merchants because there are two with the same name (with different Clover creds, etc.) and that's just confusing. I didn't see the message because late and tired, and he didn't follow up or text/call me until two days later (today, Sunday). I also thought these were strictly for diagnosing and were de-listed. I had no idea the merchant was live and people were actually purchasing things for it. Had I known this I would have freaked out and demanded specifics on Thursday/Friday because wtf? debugging in production? with broken merchants? selling things for real money? scary bad? hello?
Anyway, I didn't see his message until he texted me about it at like 5pm today while I was about 2 hours from my computer. He's understandably frustrated, and I totally don't blame him, but fuck, miscommunication is a serious problem in this company, and that's amazing because it's so freaking small.
But the short version is that I'm likely going to get blamed for all this, Clover screwiness included. Bossman and I set up a call for 10am tomorrow and I'm positive he's going to try pinning it on me. Totally not going to let him, but his social is lv16+ while mine's like. 2 or 3. 😕 I'll see how it goes.
Really though, I should read @rutee07's book and just roast these fuckers.3
TLDR: Ever wondered what your project's intro/theme song would be?!
Share yours if you ever thought about it or some particular song plays in your head while reading this..
Long(er) version + story: project I am currently working on is notorios in our company.. everyone avoids it, parts of code are untouched for 10+ years.. I used to think it was a 'shitty' project, many frameworks, many parts, many coding styles, many bugs... but longer I worked on it, more I came to realisation, it's not the code, it was the coders.. sloppy coders who didn't give a flying f..
Yes, some things are outdated still, and could be rewritten better (hopefully it will start happening soon! Yay!!), some were already rewamped, new things added... but for the time it was going live, it was majestic. I love solving bugs n problems so I must admit it has grown on me.. my little baby/devil..
Anyhu, one day on skype out of the blue I got this pic from my coworker.. made my day, laughed my ass off.. later that day I was debbuging something and youtube started rolling saw theme song (https://youtu.be/9fwWS6Xo1go)...
When I realised what I was listening too, it made perfect sense.. I was relaxed, at peace.. it clicked.. the song, the project, the bug, the code.. it all made chaotic sense..
I want to play a game..
I realised, project wasn't mean, it was just misunderstood and mistreated.. it can be your best friend if you play nice.
I replied to said coworker that I rhink I just found out my project's theme song and pasted the link.. he laughed, I laughed, my project laughed then it killed my test server.. It was a great day!! 🤣🤣🤣🤣
// all true except the project killing server part, that in fact happened on a different occasion
So.. you guys had any moments like this? Any theme songs, intros for your projects?? Or am I the only weirdo who makes associations like this all the time... 🤔🤣😇 ???6
I fucked up !
Please tell me what is going to happen if a pentester fucks up ?
I was just curious about the codes the developer was typing remotely while they were containing important datas :/
Fuck me ! I thought it would be nice if i take some pictures of that amazing code so the other employees misunderstood !!
They think I was stealing data ! 😭
What should I do ?
What can I tell them ?21
Things said at work that would be misunderstood when taken out of context:
client: "I don't like the D"
Boss: "well what if it's a little d"
Client: "I don't think the size of the D matters, do you think people make decisions on the size of a D"
Me: *trying so hard to laugh I spit coffee everywhere*
Boss: "are you working on that sex padding?"
Me: *trying so hard to laugh I spit coffee everywhere*1
Misunderstood badly worded client email -> 4 hours of coding that's actually completely redundant
Everyone talks about crappy categories of user on Stackoverflow - help vampires, rep whores, etc. - but the category of "people who don't care about the stupid mind games, politics or internet points and just want to help others" is so small people apparently don't even think it can exist.
I mean sheesh, I answer on there in my free time to just lend a hand to people, usually in a couple of niche tags that have very little info elsewhere, even for beginners. Of course there's questions that are beyond salvaging and just random homework dumps, but the majority are from genuinely confused users who simply don't know the correct terms to search for.
A question is not inherently evil just because its asker has misunderstood a key concept.
I'm not even asking you to help the poor sods, I'm just asking you to allow me to help without calling me a rep whore or a moron who'd be better talking to bots on reddit 🙄5
This is either a shower thought or a sober weed thought, not really sure which, but I've given some serious consideration to "team composition" and "working condition" as a facet of employment, particularly in regard to how they translate into hiring decisions and team composition.
I've put together a number of teams over the years, and in almost every case I've had to abide by an assemblage of pre-defined contexts that dictated the terms of the team working arrangement:
1. a team structure dictated to me
2. a working temporality scheme dictated to me
3. a geographic region in which I was allowed to hire
4. a headcount, position tuple I was required to abide by
I've come to regard these structures as weaknesses. It's a bit like the project management triangle in which you choose 1-2 from a list of inadequate options. Sometimes this is grounded in business reality, but more often than not it's because the people surrounding the decisions thrive on risk mitigation frameworks that become trickle down failure as they impose themselves on all aspects of the business regardless of compatibility.
At the moment, I'm in another startup that I have significantly more control over and again have found my partners discussing the imposition of structure and framework around how, where, why, who and what work people do before contact with any action. My mind is screaming at me to pull the cord, as much as I hate the expression. This stems from a single thought:
"Hierarchy and structure should arise from an understanding of a problem domain"
As engineers we develop processes based on logic; it's our job, it's what we do. Logic operates on data derived from from experiments, so in the absence of the real we perform thought experiments that attempt to reveal some fundamental fact we can use to make a determination.
In this instance we can ask ourselves the question, "what works?" The question can have a number contexts: people, effort required, time, pay, need, skills, regulation, schedule. These things in isolation all have a relative importance ( a weight ), and they can relatively expose limits of mutual exclusivity (pay > budget, skills < need, schedule < (people * time/effort)). The pre-imposed frameworks in that light are just generic attempts to abstract away those concerns based on pre-existing knowledge. There's a chance they're fine, and just generally misunderstood or misapplied; there's also a chance they're insufficient in the face of change.
Fictional entities like the "A Team," comprise a group of humans whose skills are mutually compatible, and achieve synergy by random chance. Since real life doesn't work on movie/comic book logic, it's easy to dismiss the seed of possibility there, that an organic structure can naturally evolve to function beyond its basic parts due to a natural compatibility that wasn't necessarily statistically quantifiable (par-entropic).
I'm definitely not proposing that, nor do I subscribe to the 10x ninja founders are ideal theory. Moreso, this line of reasoning leads me to the thought that team composition can be grown organically based on an acceptance of a few observed truths about shipping products:
1. demand is constant
2. skills can either be bought or developed
3. the requirement for skills grows linearly
4. hierarchy limits the potential for flexibility
5. a team's technically proficiency over time should lead to a non-linear relationship relationship between headcount and growth
Given that, I can devise a heuristic, organic framework for growing a team:
- Don't impose reporting structure before it has value (you don't have to flatten a hierarchy that doesn't exist)
- crush silos before they arise
- Identify needed skills based on objectives
- base salary projections on need, not available capital
- Hire to fill skills gap, be open to training since you have to pay for it either way
- Timelines should always account for skills gap and training efforts
- Assume churn will happen based on team dynamics
- Where someone is doesn't matter so long as it's legal. Time zones are only a problem if you make them one.
- Understand that the needs of a team are relative to a given project, so cookie cutter team composition and project management won't work in software
- Accept that failure is always a risk
- operate with the assumption that teams that are skilled, empowered and motivated are more likely to succeed.
- Culture fit is a per team thing, if the team hates each other they won't work well no matter how much time and money you throw at it
Last thing isn't derived from the train of thought, just things I feel are true:
- Training and headcount is an investment that grows linearly over time, but can have exponential value. Retain people, not services.
- "you build it, you run it" will result in happier customers, faster pivoting. Don't adopt an application maintenance strategy
Caching is a subject, misunderstood by a lot of developers. Optimize then cache, don't cache to optimize.2
Top 3 misunderstood things:
- The Flat Earth Society
- Pineapple on pizza
- People who code on a white background2
Talking with manager about C++ ...
ME: ... and those are the main differences when coming from C03 to C17.
MGR: OK. I think I got it... are these changes those kind of changes that when we know them we can work in any industry if they use C++?
ME: No they are not, sorry. They are like basic enablers to even start considering entering some industries. What you mean are standards. AUTOSAR standard for example is for automotive industry.
The standard requires some level of C++ standard competency.
MGR: Are these standards like plugins for C++...
ME: ? ... no. They specify rules and architecture, conventions and such.
MGR: ... aah. Architecture, I know that word. So in fact they are plugins....like...like...Eclipse IDE has architecture and it can have plugins....right ? ... and you just plugin that AUTOSAR standard to C++ language.
ME: I think you mixing stuff up on multiple levels here. I think we are not ready to talk C++ competency as a strategic decision yet... lets get some basics down first and discuss this stuff in one month.
MGR: ... ?..but, but I mean it can't be that hard. I think I almost got the gist. I just misunderstood at some point.
ME: Sure, sure. No worries...you almost had it *with deep sarcasm*.5
"You can be misunderstood exactly once. After that, you are not being misunderstood; you are communicating poorly." - Josh Collinsworth6
Fun happy story I thought I'd share with you guys:
I applied to a big tech company for a SWE internship. I was talking with one of my classmate that was usually landing big internship
Friend: good look with your interview, I know people that got it and their salary is x $/h
Me: *getting hype for that huge salary and preparing for the interview*
A few week later, after I was told that they did not have a place for me:
Friend: What ? No it wasn't x$/h I told you they pay, it's (x-10) $/h...
I guess I misunderstood him the first time.. anyways x $ was really a high salary for an intern position
But then, I got a call from the company, saying that they found a place for me at another location but they will pay for relocation and the salary is actually (x+5) $/h
Me telling my friend,
Friend: wth this is impossible
*le friend proceed to send his resume to this company*
PS: for other students out there: don't be afraid to send resumes to big company, they are most likely looking for passionate people like you !3
The thing that is common between my boss and my girlfriend is none of 'em understand what I actually want or want to say and always misunderstood me.5
What about using "$" after punctuation to indicate $ARCASM?
e.g. I barely see people's jokes being misunderstood in devrant!$8
OK, so, did my first 5 hour pre-interview coding test. it wasn't nearly as bad as I expected it to be. now I can't decide whether to be chuffed at myself for not finding the test all that terrible, or beset with anxiety that it was too easy because I misunderstood and just handed in pure crap and I'll never hear from them again.9
- have/share an agenda as soon as possible
- each talking point should identify a problem. Make a list of strategic questions answers to which would make it perfectly clear what and by whom has to be done to resolve them.
- plan meeting duration according to the list of questions. Make sure you meeting room reservation gives you enough time
- take notes
- be prepared for a need for another meeting(s), if during that meeting it comes clear that:
> more/other people need to be engaged
> some things are not clear and need more investigation before going further
> you have run out of time
> there are other problems tgat need to be worked out and it might cobsume too much time to do this in a current meeting
- do not turn the meeting into a chat. It's counter-productive, tiring to the listeners and a waste of time
- do not try to cover many topics. The less, the better. Unless they are very tightly coupled.
- do not invite people you do not need or there is a very slim chance you will need.
- only schedule meetings when the situation needs to be DISCUSSED among multiple parties
- that being said, do not schedule meetings when it's more convenient to communicate otherwise, like email, chat, etc.
- after the meeting make a summary and send it our to all the participants. They might reply and clarify if you have misunderstood smth or missed some important point.
- during the meeting assign tasks to each other. Verbally. Make notes. After the meeting reflect them in jira, rally, wtv.
- while assigning tasks nake sure the assignees have no blockers to work on them and make sure they understand what, when and how should be done. Some tasks might be dependedt on each other, work the sequence out.
- while assigning tasks ask "for ETAs. They might be as silly as 1-hour-to-2-weeks, but they still let you know what to expect.
- offer your assistance to the task assignees if they need any while working on their tasks
- work on your language, grammar, syntax, etc. Reading texts with typos/mistakes is repelling
- be a leader, an authority everyone is looking up to. Not a boss.
- avoid saying NOs. Be more of a "do we really need this; can we do this some other way/time; I can't promise anythibg but I'll see what I can do about it" kind of person.
I eagerly wait for the day some people will realize and believe that Hadoop is a file system and NOT a database!!1
Aggravated after having pointed a remote coworker at documentation that would speed along some development he was assigned to do, only to find weeks later, and several "talking past each other" conversations later, that he had disregarded it or severely misunderstood it and went his own route. Showed him today how something was done under what I supposed he had been doing and he reveals he "didn't know" it was to be done that way.1
"Form follows function – that has been misunderstood. Form and function should be one, joined in a spiritual union. " - Frank Lloyd Wright
It took me 5 hours today to configure some WiFi APs only to find out I'm too stupid for this shit and I misunderstood a setting which broke the whole thing.
After that realization it was done in a few minutes.
When you are proud of your work you have finished today, come home and want to explain it to your non-coding gf...never felt so misunderstood in my life
This place I’m consulting at just had a new Directory of Change, first policy she made for IT is mandatory 3 working days wait for any release in Test and 2 weeks for Prod. That includes application config value update in Test database. We think she might have misunderstood her job title Ms. Director of No Change..2
That it's two parts (pointing and grunting) are generally frowned upon and misunderstood by most people.2
So today I needed produce some files with an unknown file name, not specified by business. I said in the standup that I still don't know what it is supposed to be. BA says they will find out. Speak to them all day discussing it. The architect says its in the documentation. BA and I don't find it. Turns out it isn't. I ask a sister team what they did in a similar situation, they said they named it something arbitrary and moved on. I was like sweet, GG story. Later I'm discussing work with my tech lead. Email pops up look at that and read. Look back at tech leads screen. What do I see, file names. At this point I'm frustrated because all I see is file names that look similar. My senior then speaks and says 'Yeah we've seen them for X days now' I'm like really? He says yeah and I hope we don't get anymore people like you. At this point my colleague dev bursts out laughing and I feel humiliated. Only to realise they are the names of other files. Try to explain myself but my senior is already looking at his PC doing sweet fa.
I'm now raging a bit inside and want to leave but can't because I'm tied into a horrible contract.
So Today I realised I'm might be being bullied by my senior dev.1
"Her complexity is a glorious fire that consumes, while her simplicity goes unapproachable. But if one takes time to understand her, there is something beautiful to find, something simple to be loved. But she goes unloved, for being misunderstood." - Anthony Liccione
I realized i cant communicate well with human sometime, is it a symptoms that i too addicted in coding until my brain only know how to communicate with machine instead of human?
My frds even laugh me when i trying to explain something but they totally misunderstood my meaning, thats very annoying, fuck them!!!
I've ran into some problems because I misunderstood iOS `Decodable` protocol. After a while I've compiled some utility classes to transform it into something more expected.
I've written a short post about it here and I don't have any place to share for feedback. So I thought I would post it here.
- - -
Thanks for reading. (I cannot post an URL yet... So I guess I can only attach a screenshot of the title...)2
"Her complexity is a glorious fire that consumes, while her simplicity goes unapproachable. But if one takes time to understand her, there is something beautiful to find, something simple to be loved. But she goes unloved, for being misunderstood." - Anthony Liccione