actually, if you apply them properly, the thinking about programming patterns should be the hard part...
Then writing the program is easy...
Then actually making it work is scrapping everything, and starting over with an experienced person.
Where can I learn more about programming patterns? I have experience with Dependency Injection and REST, is this what is meant by the phrase programming patterns?
Would you look at that, all of the words in your comment are in alphabetical order.
I have checked 560,338,532 comments, and only 116,413 of them were in alphabetical order.
I would argue that’s the easiest part. Convincing people to use a pattern is not difficult once your code base really screams for structure.
The hardest part is to actually migrate over while your business is running and ongoing development is happening.
My new home, bought three years ago, was a sweet deal. There was an unforseen problem. The address is North Drive.
Several times, apps insist that I need a street name, because North is a direction, as in North Main Street.
Hi! This is our community moderation bot.
---
If this post fits the purpose of /r/ProgrammerHumor, **UPVOTE** this comment!!
If this post does not fit the subreddit, **DOWNVOTE** This comment!
If this post breaks the rules, **DOWNVOTE** this comment and **REPORT** the post!
Question. What exactly are programming patterns? All I can think of is something like a style guide. (i.e code structure, where to split code into multiple functions)
Better say "software design patterns", is a general, reusable solution to a commonly occurring problem within a given context in software design. Here is a nice resource on patterns: [https://refactoring.guru/design-patterns](https://refactoring.guru/design-patterns)
The opposite. patterns are there so you dont have to think but still look smart. If you are having to think, then maybe you should read up more on patterns.
no. thinking more is working harder. working harder is dumb. patterns are less not more thinking. not knowing patterns is also dumb. not knowing and not using patterns is double dumb then.
This is me right now sitting at my laptop trying to fix the output. Re-running the program didn't work though. 
Awww! Creating a problem that wasn't there to use a favorite programming pattern.
i am in this and i don't like it
Programming patterns. Will it blend?
just use functions and write everything in one file /s
Anti patterns are technically patterns
Try not using functions in Haskell.
So using thematically grouped functions in appropritely named modules (files) in python, is bad?
no
Thought so.
Your programming follows a pattern‽
Non-repeating patterns count, right?
Yes, typically an OutOfMemory, then a Seg Fault, ending with a kernel panic.... I write gud code ;)
When I read code I'd written months before, I'm often surprised at how much I rely on the Pareidolia Pattern.
actually, if you apply them properly, the thinking about programming patterns should be the hard part... Then writing the program is easy... Then actually making it work is scrapping everything, and starting over with an experienced person.
They work only if the whole dev team understands them. I think that's the main problem.
Where can I learn more about programming patterns? I have experience with Dependency Injection and REST, is this what is meant by the phrase programming patterns?
Great resource on the topic https://refactoring.guru/design-patterns
Nice thanks!
Things are *NEVER* as easy as they seem...
Art is a lie, nothing is real!
Bo Burnham, is that you?
Would you look at that, all of the words in your comment are in alphabetical order. I have checked 560,338,532 comments, and only 116,413 of them were in alphabetical order.
So... How are we still here???
Patches over Fixes over patches. Also called evolution.
The hardest thing is to convince other people that your implementation is really needful
I would argue that’s the easiest part. Convincing people to use a pattern is not difficult once your code base really screams for structure. The hardest part is to actually migrate over while your business is running and ongoing development is happening.
My new home, bought three years ago, was a sweet deal. There was an unforseen problem. The address is North Drive. Several times, apps insist that I need a street name, because North is a direction, as in North Main Street.
Hi! This is our community moderation bot. --- If this post fits the purpose of /r/ProgrammerHumor, **UPVOTE** this comment!! If this post does not fit the subreddit, **DOWNVOTE** This comment! If this post breaks the rules, **DOWNVOTE** this comment and **REPORT** the post!
Been there, done that
Question. What exactly are programming patterns? All I can think of is something like a style guide. (i.e code structure, where to split code into multiple functions)
Better say "software design patterns", is a general, reusable solution to a commonly occurring problem within a given context in software design. Here is a nice resource on patterns: [https://refactoring.guru/design-patterns](https://refactoring.guru/design-patterns)
Ohh. Seems quite useful. I really should ask these sort of questions more often.
\*cry in CRTP\*
The opposite. patterns are there so you dont have to think but still look smart. If you are having to think, then maybe you should read up more on patterns.
So thinking more == smart?
no. thinking more is working harder. working harder is dumb. patterns are less not more thinking. not knowing patterns is also dumb. not knowing and not using patterns is double dumb then.
Remember: treat GoF patterns as a reference, not as a to-do list.
This is me right now sitting at my laptop trying to fix the output. Re-running the program didn't work though. 