4 ms·

I think I overused every single pattern, method, or framework I happened to learn until maybe after 15 years of coding. Probably still do to some extent. Nice

by kpil 10y ago

I think I overused every single pattern, method, or framework I happened to learn until maybe after 15 years of coding. Probably still do to some extent. Nice read, and something to reflect upon for all young "fundamentalist". It takes some experience to learn when to bend the rules...

stinos 10y ago
I think I overused exactly. But, imo, you should do that in one point. Only then you can learn from mistakes, and learning from mistakes is the best learning. At least for me. Same in real life. Many examples, here's one: I'm confident and careful with ultrasharp cutting tools. But only because I cut myself bad a couple of times: before that I was more reckless even though I thought I was doing ok. Also others telling me to be careful had no effect whatsoever.
retox 10y ago
If you think of patterns and frameworks as tools, when you're a beginner the only way to master and ultimately discover the limitations of those tools is to use them everyday.
- AstralStorm 10y ago
  However you shouldn't release a training prototype. Artists do not release sketches. Architects do not sell concept drawings.
  - TeMPOraL 10y ago
    You'd be surprised. (Looks at the artbook from collectioner's edition of StarCraft 2.)
  - coldtea 10y ago
    Actually artists do both of those things. And some artists even specialize in sketches and concept drawings.
    - cestith 10y ago
      Sometimes professional graphic designers end up selling one of their concept pieces to a customer with a request of "no changes". Sometimes it's even the one the designer least liked and produced as number six of the minimum four concepts just to show the customer more options.
- coldtea 10y ago
  Patterns maybe, but you shouldn't think of frameworks as tools. In the sense of tools in the real world (like hammers, etc) which are fundamental and basic to the task, used by everybody in the profession, and have staying power. Frameworks on the other hand, are just some code some random guy (or random community) put together. Some are just awfully coded, despite their popularity. They are frequently rewritten. And they get out of fashion every few years.
  - retox 10y ago
    I get where you're coming from, it wasn't a particularly good metaphor I put forward. I would argue that there's some legitimacy in claiming that frameworks are just prepackaged collections of tools. It's funny you mentioned hammers actually, the movie playing in my head when I was writing that post was of a neophyte hammering nails in all day, struggling to remove nails with some contraption, eventually deciding that there must be a better way to remove nails and inventing the hammer with nail extractor head.
cestith 10y ago
Beware the factory factory.

by kpil 10y ago

stinos 10y ago

I think I overused exactly. But, imo, you should do that in one point. Only then you can learn from mistakes, and learning from mistakes is the best learning. At least for me. Same in real life. Many examples, here's one: I'm confident and careful with ultrasharp cutting tools. But only because I cut myself bad a couple of times: before that I was more reckless even though I thought I was doing ok. Also others telling me to be careful had no effect whatsoever.

retox 10y ago

If you think of patterns and frameworks as tools, when you're a beginner the only way to master and ultimately discover the limitations of those tools is to use them everyday.

AstralStorm 10y ago
However you shouldn't release a training prototype. Artists do not release sketches. Architects do not sell concept drawings.
- TeMPOraL 10y ago
  You'd be surprised. (Looks at the artbook from collectioner's edition of StarCraft 2.)
- coldtea 10y ago
  Actually artists do both of those things. And some artists even specialize in sketches and concept drawings.
  - cestith 10y ago
    Sometimes professional graphic designers end up selling one of their concept pieces to a customer with a request of "no changes". Sometimes it's even the one the designer least liked and produced as number six of the minimum four concepts just to show the customer more options.
coldtea 10y ago
Patterns maybe, but you shouldn't think of frameworks as tools. In the sense of tools in the real world (like hammers, etc) which are fundamental and basic to the task, used by everybody in the profession, and have staying power. Frameworks on the other hand, are just some code some random guy (or random community) put together. Some are just awfully coded, despite their popularity. They are frequently rewritten. And they get out of fashion every few years.
- retox 10y ago
  I get where you're coming from, it wasn't a particularly good metaphor I put forward. I would argue that there's some legitimacy in claiming that frameworks are just prepackaged collections of tools. It's funny you mentioned hammers actually, the movie playing in my head when I was writing that post was of a neophyte hammering nails in all day, struggling to remove nails with some contraption, eventually deciding that there must be a better way to remove nails and inventing the hammer with nail extractor head.

cestith 10y ago

Beware the factory factory.