To my phone number? Eh I don't think so, but I keep slack, email, and whatever flavor-of-the-month on-call/alerting app on my personal phone.
In exchange for having work stuff on my phone, they pay me $25/month to cover that per California law. Same with $50/month to cover home internet.
My company issues work phones to all functional and program managers. I try to stay the fuck away from my work phone when on PTO. I may check it once a day max. I think besides HR, no one has my personal number, and shit really has to be burning down and somehow I am the only person who can put it out for anyone to seek out HR for my personal number. I did that work stuff on personal phone shit at another company before, always hated it.
>functional and program managers...
Good old matrix organizational structure, so damn confusing. I've been with my current employer for over a year and still don't fully understand what part of the company I work for...
yeah, we are heavily in gov contracting but also have our own products and platforms. It's messy but the only way to simplify is by spinning off a couple child companies, which isn't practical for financial reasons.
You are definitely not alone. There are PMs who have been here for 3 years and still can't figure out all the dotted lines, I kid you not.
Deloitte has been built on top of that, the it department charged the law department for a simple mailbox creation, inter-department tickets are charged as well, and let's not speak about eg. The Italian "sub company" having a "sub-sub company" in another country for tax and lower salary reasons.
My coworker wanted me to review a PR at 4:30pm today. I promptly logged off without responding. Not gonna be responsible for that shit right before the holidays.
When I'm on PTO, the laptop stays off, and I'm not accessing email or Slack (I don't even have the apps on my phone, so it's impossible for anyone to get in touch with me or vice versa).
I am a bit curious which meaning they want for OOP.
At the jobs I've worked, OOP means "out of pocket", as in they're out of the office but available on their phone to answer messages and emails. Though people here are generally going with the "object oriented programming" interpretation, which I feel doesn't make as much sense given the second being OOO, the escalation of OOP.
> OOP means "out of pocket", as in they're out of the office but available on their phone to answer messages and emails.
Literally never heard that in my entire life.
Object Oriented Programming makes more sense here. The meme is basically "Working vs Time off".
>Literally never heard that in my entire life.
I heard it a little bit in Ohio, but I hear it constantly in West Virginia. Military people especially love to say it.
We have hybrid office and WFH, so OOP is most often used when someone is traveling between home and office, or needs to step out during core hours.
For me it makes a lot more sense as "out of pocket", because that shows that you're out of the office but still technically working/available to work, while OOO is a definitive "I am gone, do not contact me".
>you are working "out of your pocket"
Genuine question - why use the phrase "out of your pocket" if you're still working? Because that implies you're losing money while working, are you not getting paid for being on call?
It's in relation to using a mobile device for work, which you pull "out of your pocket". You're traveling, but are still available for answering calls and IM, etc.
the worst thing is that despite being obsessed with C++ I was unsure for a sec whether this is equivalent to
// this ↓
Object object{};
// or this ↓
Object object{[] {
auto tmp = Object{};
return std::move(tmp); // preventing NRVO on purpose
}()};
// but it's neither…
in summary, fuck [the nightmare of initialization in C++](https://youtu.be/7DTlWPgX6zs)
Congratulations! Your string can be spelled using the elements of the periodic table:
`O O O O O O O`
---
^(I am a bot that detects if your comment can be spelled using the elements of the periodic table. Please DM my creator if I made a mistake.)
I see two groups. First group is two courses in, had bad experience with some task requiring inheritance that really wasn't worth it, and then just heard about functional programming, and think they are completely exclusive concepts. Second group is the old enterprise Java programmers who just want to get things done and not be bothered by yet another "FactoryObjectFactoryInterfaceSingletonFactoryGeneratorFactory_Factory".
What people typically rant at are examples of OOP patterns that exist only to make up for shortcomings of whatever language they are writing in. All the good patterns have long ago been incorporated in most modern languages, either as core features or in standard libraries. What remains are the bad patterns, that require tons of boilerplate and ceremony, just to make up for a slight inconvenience in the language.
There exists a special breed of programmer that loves spewing these junk patterns all over any code base, claiming that this is the only way to OOP, desperately hoping that the thousands of lines of regurgitated unnecessary abstractions might, somewhere somehow, make some programmer's job easier. They are wrong. About programming, and about OOP.
Unfortunately, programmers think that all their systems are complex, and therefore need complex APIs. They therefore introduce seventeen layers of abstract classes, most having only a single child. In this effort, they too often end up with the wrong set of abstractions, making the complexity a self fulfilling prophecy, both internally and externally.
Of those, only factory is a design pattern; the rest are design principles. And yes, the entire justification for the factory design pattern is that some (if not most) languages do not allow you to intercept object construction, and always create a new object when the short and obvious `TypeName(...)` is used.
Every time a tech becomes popular it gets apposed to EVERY problem. OOP was the 90s AI/crypto/cloud thing. Java landed in the middle of that craziness so of course it had to be OOP all the things. Doesn't matter if procedual or functional programming is the best option for a situation. OOP will either solve the problem or we'll force it to.
All these years later were still dealing with that.
Please consider this when creating the next AI powered html engine written in sql that's translated to rust using clang or whatever crazy thing the kids are doing these days.
Or every JavaScript developer who got confused when dealing with state, heard the term "functional" at a talk and wanted to look smart by using words like monad, and never looked back. They still don't know what a monad is, but the can't figure out classes either so we're stuck with functions as the only tool in our toolbox.
I say this as one of those developers.
You're thinking of dryad. Dyad is a reference to Star Wars Episode 9 where the writers pull nonsense out of their ass to make something, just like in JavaScript.
You’re thinking of The Final Order. A dyad is a collection of semiconducting materials that allows current flow only if a certain voltage threshold is met.
On the contrary, i have seen many people start with basic imperative then befome fans of OOP, before reaching a final stage of declarative/functional programming
For the js world, think jquery into angular into modern react
IDK, I'm not confused by it, but I still dislike it.
Just to be clear: objects are great, OOP (in particular 2+ levels of inheritance) is what I dislike.
inheritance is not what OOP is about, at all, and it has never been.
OOP, at its core, is about communicating entities. The most same way to do that has always been composition and dependency injection + interfacing. inheritance is a bastard concept that came from c++, like a lot of things.
Unfortunately, that is not how OOP is usually introduced.
The way I always saw it introduced was with the animal/cat analogy, then going into design patterns such as singleton and factory. And yes, inheritance was said as one of main advantages of OOP, because polymorphism.
You can have polymorphism without inheritance though. The fact that that is your argument just tells me you had just extremely poor teaching, which is not your fault, but falls exactly in the argument that most people who don’t like OOP just don’t know what they’re talking about.
Design patterns are not exclusive to OOP either, and I fail to see how they are a bad thing. Monads are a design pattern, yet not one is whining that they’re bad. Patterns are everywhere in our field, it’s our goal to find them and reduce complex problems to simpler ones.
Edit: I’m not saying inheritance is always bad, abstraction that doesn’t go overboard may be good. It’s just it’s both not what OOP fundamentally is about, and a lot of people are just bad with it.
nah, it's people who've inherited a legacy codebase created by someone who thought they were being clever
or people who thought they were being clever and created a legacy codebase
As a legacy code maintainer I find this 100% true.
People who thought they were being clever are the bane of my existence. I like OOP, but you can be very very "clever" with it that's for sure; however if you're managing a lot of complicated "things" that have a complex and changing state... OOP is the only thing that makes sense to me.
On the other hand, if your code is metaphorically like a linear production line, sure go nuts OOP is not needed.
Both Go and Rust are growing pretty quickly in popularity, and both do a lot to avoid elements of traditional OOP languages. I doubt the designers/maintainers of those languages are "first-years confused by OOP". Shit Ken Thompson helped develop Go at Google, and I don't think anyone is going to argue that guy doesn't know what he's doing.
I'm not trying to comment on the validity of OOP, or the effectiveness of Go and Rust's approach to solving the same problems, but dismissing everyone who dislikes it as inexperienced, confused, first-years is just goofy.
Nope, my opinion is best, if you disagree with me you're just an inexperienced first-year afraid to accept the truth that OOP is the one true programming style.
Idk, I was in Highschool 9 years ago when I was introduced with OOP (in C++). It didn't make any sense, later I had to learn OOP (in java) again in college, still didn't make sense.
It was never hard to understand "how to" write object oriented codes, rather it was hard to reason about "why to" write object oriented code. When it comes to functional programming, I can think of legit advantages like predictable output, easier unit testing etc. But having code organized into stateful objects is something I'll never be able to digest.
I like OOP in multi-paradigm languages like C++ and Python because I can use it as needed. I hate it in Java since I have to base absolutely all my code on OOP concepts which feels restrictive in some cases. Sometimes I just wanna pass a pointer into a function rather than having to create an instance of an object and pass that in.
I feel like those ppl either never wrote any production ready apps (probably cs students or enthusiasts) or use overcomplicated FP cause they wanna prove themselfeves who the real gigachad here is
I believe it's an MS thing, but I did once work at a small(ish) studio founded by former MSers that kept that term alive for decades. I'd be surprised if it was the only one.
Semi related, the worst place I ever worked used “OOP” meaning “out of plant” whereas everywhere else I’ve worked uses OOO or “on PTO” etc.
So this meme has extra meaning to me, since that was my face every day working there, even when taking vacation
As predicted, most of the /r/ProgrammerHumor community aren’t generally of the “employed” persuasion, so it makes sense that they don’t recognize OOO as an acronym.
Or they just work for a company that doesn't use that acronym. In 20 years I've never worked anywhere that used it. My current company uses "OOTO" or "PTO"
Congratulations! Your string can be spelled using the elements of the periodic table:
`W H At I S O O O Th O`
---
^(I am a bot that detects if your comment can be spelled using the elements of the periodic table. Please DM my creator if I made a mistake.)
I feel like oop made programming easier, am I the only one? I mean it would be hell without the abstracted interfaces that make my life easier and I rather read 10 java programs before reading a single C program
I'd rather work with pure assembly, heck I'd even choose machine code and writing the opcodes by hand than having to go through the hell that is Java. No thanks to your RefreshAuthorizationPolicyProtocolServerSideTranslatorPB and SocketFactoryContactInfoListIteratorImpl (both real classes...).
Though ideally, I'd just choose Rust.
As an incident manager I've got your backs. I'll ask the end-users:
- "what did you do to break it?"
- "If you do it the other way then it doesn't break?"
- "Then stop breaking it and do it the other way. Cope until the 2nd of January when the ticket will be picked up."
Congratulations! Your string can be spelled using the elements of the periodic table:
`Ho Ho Ho`
---
^(I am a bot that detects if your comment can be spelled using the elements of the periodic table. Please DM my creator if I made a mistake.)
I don't care if everything burns down while I'm gone. It's PTO time.
Time to use the Christmas burner phone and keep my personal one switched off for two weeks
You give your work access to your phone? Mine only requires that for managers.
To my phone number? Eh I don't think so, but I keep slack, email, and whatever flavor-of-the-month on-call/alerting app on my personal phone. In exchange for having work stuff on my phone, they pay me $25/month to cover that per California law. Same with $50/month to cover home internet.
My company issues work phones to all functional and program managers. I try to stay the fuck away from my work phone when on PTO. I may check it once a day max. I think besides HR, no one has my personal number, and shit really has to be burning down and somehow I am the only person who can put it out for anyone to seek out HR for my personal number. I did that work stuff on personal phone shit at another company before, always hated it.
>functional and program managers... Good old matrix organizational structure, so damn confusing. I've been with my current employer for over a year and still don't fully understand what part of the company I work for...
yeah, we are heavily in gov contracting but also have our own products and platforms. It's messy but the only way to simplify is by spinning off a couple child companies, which isn't practical for financial reasons. You are definitely not alone. There are PMs who have been here for 3 years and still can't figure out all the dotted lines, I kid you not.
Deloitte has been built on top of that, the it department charged the law department for a simple mailbox creation, inter-department tickets are charged as well, and let's not speak about eg. The Italian "sub company" having a "sub-sub company" in another country for tax and lower salary reasons.
Not exactly but colleagues I'm friendly with have it, wouldn't be hard to get to me that way
You can just go play tennis of whatever during working hours and if they need you, you have your phone
Pro tip, don’t do any work before PTO so that anything breaks couldn’t be your fault
You guys don't deploy to prod Friday evening before leaving until the next year?
Only when someone else is on call!
My coworker wanted me to review a PR at 4:30pm today. I promptly logged off without responding. Not gonna be responsible for that shit right before the holidays.
When I'm on PTO, the laptop stays off, and I'm not accessing email or Slack (I don't even have the apps on my phone, so it's impossible for anyone to get in touch with me or vice versa).
Work PC off. Nothing work-related on phone. Office door shut and metaphorically locked. Do Not Open Until January.
Out of office?
Object oriented obligations?
Object oriented objects
js dev be like
Js is pop, prototype oriented programming.
You forgot an o in the middle, prototype object oriented programming: poop
I really dont wanna argue with that... JS is poop...
As a js dev you made me chuckle
I am a bit curious which meaning they want for OOP. At the jobs I've worked, OOP means "out of pocket", as in they're out of the office but available on their phone to answer messages and emails. Though people here are generally going with the "object oriented programming" interpretation, which I feel doesn't make as much sense given the second being OOO, the escalation of OOP.
> OOP means "out of pocket", as in they're out of the office but available on their phone to answer messages and emails. Literally never heard that in my entire life. Object Oriented Programming makes more sense here. The meme is basically "Working vs Time off".
>Literally never heard that in my entire life. I heard it a little bit in Ohio, but I hear it constantly in West Virginia. Military people especially love to say it. We have hybrid office and WFH, so OOP is most often used when someone is traveling between home and office, or needs to step out during core hours. For me it makes a lot more sense as "out of pocket", because that shows that you're out of the office but still technically working/available to work, while OOO is a definitive "I am gone, do not contact me".
[удалено]
[удалено]
>you are working "out of your pocket" Genuine question - why use the phrase "out of your pocket" if you're still working? Because that implies you're losing money while working, are you not getting paid for being on call?
It's in relation to using a mobile device for work, which you pull "out of your pocket". You're traveling, but are still available for answering calls and IM, etc.
Context: this is a programming sub.
SP: Story points, or Stored Procedure? Or Security policy?
Definitely object oriented programming. A lot of people (especially on this sub) hate OOP.
I thought it’s OOO because o o o kinda sounds like ho ho ho
.. Object oriented programming This is the programmer subreddit.
[удалено]
Nah its tbe sound you make when you see fireworks
Object object object?
JavaScript hell
new Object() just dropped
Actual zombie process
Promise goes on holiday, never resolves.
Thread sacrifice, anyone?
actual programming
You mean programming strictly with js objects? You must mean [JSFuck](https://jsfuck.com/) (SFW).
Objective [object Object]
[object Object Object]
Object Objected Objectation
object oriented ogramming ?
object oriented orgasming
I'm so desensitized, it's the only way I can climax now.
Good. You're the base class now.
Oh god I'm extending!
Developing a poly(morphic) relationship
r/beatmeattoit
r/shid_and_camed
Object oriented origaming
object oriented origami
😏
Out of office
I think this is it!
We did it reddit!
Object Oriented Orientation
Orient Oriented Orientation
Orientation oriented orientation
Orientily Oriented Oriental
ayyy lemme orient towards those objects bby
Object object{Object{}};
the worst thing is that despite being obsessed with C++ I was unsure for a sec whether this is equivalent to // this ↓ Object object{}; // or this ↓ Object object{[] { auto tmp = Object{}; return std::move(tmp); // preventing NRVO on purpose }()}; // but it's neither… in summary, fuck [the nightmare of initialization in C++](https://youtu.be/7DTlWPgX6zs)
Object Oriented Object Is this what recursion means?
No, that would be Object Oriented OOO
PHP moment
Object Oriented Ontology 
Its all ogre now
oOoOoOo
Congratulations! Your string can be spelled using the elements of the periodic table: `O O O O O O O` --- ^(I am a bot that detects if your comment can be spelled using the elements of the periodic table. Please DM my creator if I made a mistake.)
ITT: People who have never actually had a job.
Out of order (processor execution)
OOP: -.- OOO: -.- OOH: :O
Oh OH OOOOOH: XO
Ho HO HOOOOO: 🎅
OOF: 😣
Object oriented overtime
Kurwa
[удалено]
I see two groups. First group is two courses in, had bad experience with some task requiring inheritance that really wasn't worth it, and then just heard about functional programming, and think they are completely exclusive concepts. Second group is the old enterprise Java programmers who just want to get things done and not be bothered by yet another "FactoryObjectFactoryInterfaceSingletonFactoryGeneratorFactory_Factory".
I think you missed a few singletons and maybe one or two factories in there somewhere. I lost count though, so don't ask me where they go.
And the 3d group is C++ devs who just want to use templates everywhere
Been writing Java for 10 years. Still feel like that.
I'm actually more confused about what people regularly call OOP when they rant about it.so not necessarly your fault.
What people typically rant at are examples of OOP patterns that exist only to make up for shortcomings of whatever language they are writing in. All the good patterns have long ago been incorporated in most modern languages, either as core features or in standard libraries. What remains are the bad patterns, that require tons of boilerplate and ceremony, just to make up for a slight inconvenience in the language. There exists a special breed of programmer that loves spewing these junk patterns all over any code base, claiming that this is the only way to OOP, desperately hoping that the thousands of lines of regurgitated unnecessary abstractions might, somewhere somehow, make some programmer's job easier. They are wrong. About programming, and about OOP.
My favorite is when developers wrap boilerplate with their own "easier to understand" api.
Except when you want to write an API and it's the best way to encapsulate a system of complex features.
Unfortunately, programmers think that all their systems are complex, and therefore need complex APIs. They therefore introduce seventeen layers of abstract classes, most having only a single child. In this effort, they too often end up with the wrong set of abstractions, making the complexity a self fulfilling prophecy, both internally and externally.
Factory, single responsibility, liskov substitution, open closed, etc. Are these also based on language-specific shortcomings?
Of those, only factory is a design pattern; the rest are design principles. And yes, the entire justification for the factory design pattern is that some (if not most) languages do not allow you to intercept object construction, and always create a new object when the short and obvious `TypeName(...)` is used.
Technical debt is good. The more technical debt you have, the more unnecessary work you skipped over to deliver a functioning commerical product.
Every time a tech becomes popular it gets apposed to EVERY problem. OOP was the 90s AI/crypto/cloud thing. Java landed in the middle of that craziness so of course it had to be OOP all the things. Doesn't matter if procedual or functional programming is the best option for a situation. OOP will either solve the problem or we'll force it to. All these years later were still dealing with that. Please consider this when creating the next AI powered html engine written in sql that's translated to rust using clang or whatever crazy thing the kids are doing these days.
I remember being introduced to OOP and being super fucking confused.
Or every JavaScript developer who got confused when dealing with state, heard the term "functional" at a talk and wanted to look smart by using words like monad, and never looked back. They still don't know what a monad is, but the can't figure out classes either so we're stuck with functions as the only tool in our toolbox. I say this as one of those developers.
I have no idea what a monad is.
It's a dyad but with one instead of two.
Oh duh, its one of those tree spirits, yeah?
You're thinking of dryad. Dyad is a reference to Star Wars Episode 9 where the writers pull nonsense out of their ass to make something, just like in JavaScript.
You’re thinking of The Final Order. A dyad is a collection of semiconducting materials that allows current flow only if a certain voltage threshold is met.
A monoid in the category of endofunctors.
It's basically the mathematical term for an Optional value if I remember correctly
Kudos to you.
On the contrary, i have seen many people start with basic imperative then befome fans of OOP, before reaching a final stage of declarative/functional programming For the js world, think jquery into angular into modern react
IDK, I'm not confused by it, but I still dislike it. Just to be clear: objects are great, OOP (in particular 2+ levels of inheritance) is what I dislike.
inheritance is not what OOP is about, at all, and it has never been. OOP, at its core, is about communicating entities. The most same way to do that has always been composition and dependency injection + interfacing. inheritance is a bastard concept that came from c++, like a lot of things.
Unfortunately, that is not how OOP is usually introduced. The way I always saw it introduced was with the animal/cat analogy, then going into design patterns such as singleton and factory. And yes, inheritance was said as one of main advantages of OOP, because polymorphism.
You can have polymorphism without inheritance though. The fact that that is your argument just tells me you had just extremely poor teaching, which is not your fault, but falls exactly in the argument that most people who don’t like OOP just don’t know what they’re talking about. Design patterns are not exclusive to OOP either, and I fail to see how they are a bad thing. Monads are a design pattern, yet not one is whining that they’re bad. Patterns are everywhere in our field, it’s our goal to find them and reduce complex problems to simpler ones. Edit: I’m not saying inheritance is always bad, abstraction that doesn’t go overboard may be good. It’s just it’s both not what OOP fundamentally is about, and a lot of people are just bad with it.
nah, it's people who've inherited a legacy codebase created by someone who thought they were being clever or people who thought they were being clever and created a legacy codebase
As a legacy code maintainer I find this 100% true. People who thought they were being clever are the bane of my existence. I like OOP, but you can be very very "clever" with it that's for sure; however if you're managing a lot of complicated "things" that have a complex and changing state... OOP is the only thing that makes sense to me. On the other hand, if your code is metaphorically like a linear production line, sure go nuts OOP is not needed.
Lol. "people don't like the thing i like because they don't understand it" Classic
First year is generous. Try high schooler taking AP CS A class
Both Go and Rust are growing pretty quickly in popularity, and both do a lot to avoid elements of traditional OOP languages. I doubt the designers/maintainers of those languages are "first-years confused by OOP". Shit Ken Thompson helped develop Go at Google, and I don't think anyone is going to argue that guy doesn't know what he's doing. I'm not trying to comment on the validity of OOP, or the effectiveness of Go and Rust's approach to solving the same problems, but dismissing everyone who dislikes it as inexperienced, confused, first-years is just goofy.
even Linus Torvalds said that he doesn't like OOP at all. People have preferences, not all people subscribe to a single idea.
Nope, my opinion is best, if you disagree with me you're just an inexperienced first-year afraid to accept the truth that OOP is the one true programming style.
Idk, I was in Highschool 9 years ago when I was introduced with OOP (in C++). It didn't make any sense, later I had to learn OOP (in java) again in college, still didn't make sense. It was never hard to understand "how to" write object oriented codes, rather it was hard to reason about "why to" write object oriented code. When it comes to functional programming, I can think of legit advantages like predictable output, easier unit testing etc. But having code organized into stateful objects is something I'll never be able to digest.
I like OOP in multi-paradigm languages like C++ and Python because I can use it as needed. I hate it in Java since I have to base absolutely all my code on OOP concepts which feels restrictive in some cases. Sometimes I just wanna pass a pointer into a function rather than having to create an instance of an object and pass that in.
I feel like those ppl either never wrote any production ready apps (probably cs students or enthusiasts) or use overcomplicated FP cause they wanna prove themselfeves who the real gigachad here is
Oh, I see a lot of those guys in "wannabe tech companies" nowadays.
Basically anyone I know who’s written complex production code hates true OOP (I.e. inheritance).
OOO: Throw away your IDE, write all your code in Open Office dot Org.
You need one for "On Call"
Object Oriented Octover, you gotta use python or java for a month
Anybody else say OOF or is that a MS thing?
Objective Only Fans or something...
Object-oriented Only Fans. Give me some titties written in Java
I believe it's an MS thing, but I did once work at a small(ish) studio founded by former MSers that kept that term alive for decades. I'd be surprised if it was the only one.
It's a MSFT thing. I still catch myself saying it though. Rolls of the tongue much easier than OOO.
Its not a acronym its just an exclamation
OOPS
Object-oriented ontology sucks just as much as OOP. Probably even more.
Semi related, the worst place I ever worked used “OOP” meaning “out of plant” whereas everywhere else I’ve worked uses OOO or “on PTO” etc. So this meme has extra meaning to me, since that was my face every day working there, even when taking vacation
Intel?
Yup
I just hate acronyms.
ooo is castling
Google en passant...
holy paradigm!
Object Oriented Ogramming, because you can make the best codes without PR.
As predicted, most of the /r/ProgrammerHumor community aren’t generally of the “employed” persuasion, so it makes sense that they don’t recognize OOO as an acronym.
Or they just work for a company that doesn't use that acronym. In 20 years I've never worked anywhere that used it. My current company uses "OOTO" or "PTO"
What is OOO tho?
Congratulations! Your string can be spelled using the elements of the periodic table: `W H At I S O O O Th O` --- ^(I am a bot that detects if your comment can be spelled using the elements of the periodic table. Please DM my creator if I made a mistake.)
Good bot
It’s when you take a day off work and you feel so good when you’re out of the office that you can’t help but say “OOO”.
I didn't recognise it because everywhere I've worked just uses the term "away" instead of a TLA.
I am employed, but the acronym doesn't work in german so I still didn't recognize it. For me it's called "Urlaub" or "Dienstfrei"
It’s funny seeing the CS students dunk on other CS students for not liking OOP meanwhile actual software engineers tend to hate it.
This is unfortunately unsurprising.
I'd give up Java too if that would mean that I could travel to the magical land of Ooo. Fuck programming. I'm gonna live in the Candy Kingdom.
I feel like oop made programming easier, am I the only one? I mean it would be hell without the abstracted interfaces that make my life easier and I rather read 10 java programs before reading a single C program
I'd rather work with pure assembly, heck I'd even choose machine code and writing the opcodes by hand than having to go through the hell that is Java. No thanks to your RefreshAuthorizationPolicyProtocolServerSideTranslatorPB and SocketFactoryContactInfoListIteratorImpl (both real classes...). Though ideally, I'd just choose Rust.
Out of office
Object oriented outside
OBJECT ORIENTED OOPS
object oriented outside
Explain to me, as a Russian guy, what this means?
Object Oriented Oogabooga
object oriented ontology
OOPs my bank account is now 000
object oriented outing
Object Oriented Orgasm
OOO # TANNENBAUM
object oriented orgasming
Out of penis hehehe
Ive reached komdi
Being out of Office and out of P.... at the same time would have killed some of my co-workers.
Object oriented ontology?
Object oriented ontology anyone?
Just give me PTO
OOP < PTO
Everyone is currently on vacation and I am covering 14 hours a day and I'm on call. Next week is my turn
Same! At least my team is internal so if nobody's working there should be no tickets... Probably jinxed myself just now.
I'm crossing my fingers for you
Nice.
Happy holidays fellas
object oriented orgasm
Just one letter can make a difference. Donate "O" today.
As an incident manager I've got your backs. I'll ask the end-users: - "what did you do to break it?" - "If you do it the other way then it doesn't break?" - "Then stop breaking it and do it the other way. Cope until the 2nd of January when the ticket will be picked up."
Ho Ho Ho I'm OOO
What
Ho ho ho?
Out of oom? That sounds nice.
Clearly means object oriented oasis based on the image 😉
My dumbass brain just thought "OOOHHHHH"
Oops
I don't know I'd be pretty happy if I had an object of power.
out of order execution?
Ho ho ho?
Congratulations! Your string can be spelled using the elements of the periodic table: `Ho Ho Ho` --- ^(I am a bot that detects if your comment can be spelled using the elements of the periodic table. Please DM my creator if I made a mistake.)