3 ms·

You don't have to listen to what other people "consider harmful" or think are "anti-patterns" or "clean code". You don't Gotta Catch 'em All the design patterns

You don't have to listen to what other people "consider harmful" or think are "anti-patterns" or "clean code". You don't Gotta Catch 'em All the design patterns or figure out if coffeescript is the flavour of the week or plug in event-sourcing because it was on HN yestreday. You can just solve the problem you have. Nobody will know. I don't why programming is so vulnerable to these memes and false consensus and blog fad driven architecture. I have some styles I like and I use them. Some of them aren't compatible with each other so I don't use them all at the same time. I don't wait for John Carmack or Bob Martin to tell me if it's okay. You shouldn't either.

bodge5000 3y ago
On the front-end you have a new javascript framework every 15 minutes, on the backend you have this. But I'm with you, I'll use what works for me until it no longer works for me
- henry2023 3y ago
  Thankfully everyone decided that react is the final one. Pretty stable over 10+ years. The backend had a lot of this 3 years ago when everything absolutely everything needed to be k8 orchestrated dockerized Microservices
  - aniforprez 3y ago
    There's the new brouhaha over the Server Components thing but it's safe to ignore it completely when even the documentation for it is so poor
- meowtimemania 3y ago
  Meh, it's still 80%+ react and has been for the last 5 years.
  - alex_lav 3y ago
    React Router? React Router Dom? Redux? Rematch? Jotai? MobX? Hooks? Classes? Create react app? Not create react app? Next? Gatsby? Preact?
worik 3y ago
> You don't have to listen to what other people "consider harmful" or think are "anti-patterns" or "clean code". Please do. There is a lot of very bad code doing very important things. Many of us have been around learning for decades, and some of us (not me) are brilliant at writing and communicating Pay attention, please. Do not think "you know better because you are smart". Yu do not, even though you are
- breckenedge 3y ago
  There’s a subtle difference here between ignorance of code smells and cargo-culting “best practices.” Software will never be perfect.
stcroixx 3y ago
Very well said. It wasn’t always this way, but it has been long enough now that I don’t see it changing while I’m still around. I’d do anything else if I could earn even half of what I make.
mekoka 3y ago
Unfortunately, this sentiment can rarely be expressed before someone has come full-circle. An apprentice cannot have that insight. A journeyman is too busy DRYing things up and peppering their code with patterns. It's only once you've felt the pains inflicted upon you by all those "one true ways", when you've survive the betrayals, only then you can finally accept that there are, in fact, no solutions, only trade-offs. Congratulations, you've become a veteran. Despite all the good souls trying to turn programming into a discipline with sharp rules and well defined constraints, it remains a craft. Part prickly, part gooey. As far as I can tell, if it has tenets they sum up to four, in that order: code has to be correct, bug-free, reasonably efficient (i.e. enough for the problem at hand), and maintainable. The last two bits lie in overlapping shades of grey. You either learn to be comfortable with it or you will yourself to make black and white observations, which you turn into rules and patterns (or anti-patterns, as the case may be). Then you write an article or a book about them. And on the wheel goes...

bodge5000 3y ago

On the front-end you have a new javascript framework every 15 minutes, on the backend you have this. But I'm with you, I'll use what works for me until it no longer works for me

henry2023 3y ago
Thankfully everyone decided that react is the final one. Pretty stable over 10+ years. The backend had a lot of this 3 years ago when everything absolutely everything needed to be k8 orchestrated dockerized Microservices
- aniforprez 3y ago
  There's the new brouhaha over the Server Components thing but it's safe to ignore it completely when even the documentation for it is so poor
meowtimemania 3y ago
Meh, it's still 80%+ react and has been for the last 5 years.
- alex_lav 3y ago
  React Router? React Router Dom? Redux? Rematch? Jotai? MobX? Hooks? Classes? Create react app? Not create react app? Next? Gatsby? Preact?

worik 3y ago

> You don't have to listen to what other people "consider harmful" or think are "anti-patterns" or "clean code". Please do. There is a lot of very bad code doing very important things. Many of us have been around learning for decades, and some of us (not me) are brilliant at writing and communicating Pay attention, please. Do not think "you know better because you are smart". Yu do not, even though you are

breckenedge 3y ago
There’s a subtle difference here between ignorance of code smells and cargo-culting “best practices.” Software will never be perfect.

stcroixx 3y ago

Very well said. It wasn’t always this way, but it has been long enough now that I don’t see it changing while I’m still around. I’d do anything else if I could earn even half of what I make.

mekoka 3y ago

Unfortunately, this sentiment can rarely be expressed before someone has come full-circle. An apprentice cannot have that insight. A journeyman is too busy DRYing things up and peppering their code with patterns. It's only once you've felt the pains inflicted upon you by all those "one true ways", when you've survive the betrayals, only then you can finally accept that there are, in fact, no solutions, only trade-offs. Congratulations, you've become a veteran. Despite all the good souls trying to turn programming into a discipline with sharp rules and well defined constraints, it remains a craft. Part prickly, part gooey. As far as I can tell, if it has tenets they sum up to four, in that order: code has to be correct, bug-free, reasonably efficient (i.e. enough for the problem at hand), and maintainable. The last two bits lie in overlapping shades of grey. You either learn to be comfortable with it or you will yourself to make black and white observations, which you turn into rules and patterns (or anti-patterns, as the case may be). Then you write an article or a book about them. And on the wheel goes...