3 ms·

On another note, how many feel Mr Fowler's notes on software engineering are worth reading?

noelwelsh 3y ago
There is some wisdom in there, but like everything there is a lot of skill in the application of that wisdom. Not all refactorings (to name something for which Martin Fowler is well known) are the same.
- sureglymop 3y ago
  I also feel sometimes there is a tendency to overcomplicate by taking very simple concepts and ideas and assigning a name or almost "field of research" to them. The main example I can think of is "Dependency Injection". The idea to pass an object to another object (for different purposes, e.g. testing) is pretty simple and understandable. But over time the term " dependency injection" has probably confused a whole lot of people but for some reason a term just had to be coined. I do understand that it's probably not on purpose because the author(s) are deeply studying or thinking about what they are describing (probably more so than the readers) and maybe coming up with new terminology does help them to keep making sense of it all.
  - bern4444 3y ago
    I agree. Dependency injection is 'just' passing an argument to a function or method. Whether that happens via the constructor, some method, or a plain ol' function, its very simple. But naming it dependency injection and ascribing terms like setter injection, or constructor injection or discussing dependency injection frameworks with complicated set up instructions, can make this very simple concept seem significantly more complex and difficult for junior and mid level engineers. All my opinion but this was also my experience.
    - megamix 3y ago
      So that's what DI is. Took me 7years. Kidding!
loevborg 3y ago
Martin (and the other contributors to his blog) continue to write insightfully about things that matter. I'm impressed with his continued devotion to topics like Continuous Integration, testing and refactoring.

There is some wisdom in there, but like everything there is a lot of skill in the application of that wisdom. Not all refactorings (to name something for which Martin Fowler is well known) are the same.

sureglymop 3y ago
I also feel sometimes there is a tendency to overcomplicate by taking very simple concepts and ideas and assigning a name or almost "field of research" to them. The main example I can think of is "Dependency Injection". The idea to pass an object to another object (for different purposes, e.g. testing) is pretty simple and understandable. But over time the term " dependency injection" has probably confused a whole lot of people but for some reason a term just had to be coined. I do understand that it's probably not on purpose because the author(s) are deeply studying or thinking about what they are describing (probably more so than the readers) and maybe coming up with new terminology does help them to keep making sense of it all.
- bern4444 3y ago
  I agree. Dependency injection is 'just' passing an argument to a function or method. Whether that happens via the constructor, some method, or a plain ol' function, its very simple. But naming it dependency injection and ascribing terms like setter injection, or constructor injection or discussing dependency injection frameworks with complicated set up instructions, can make this very simple concept seem significantly more complex and difficult for junior and mid level engineers. All my opinion but this was also my experience.
  - megamix 3y ago
    So that's what DI is. Took me 7years. Kidding!

loevborg 3y ago

Martin (and the other contributors to his blog) continue to write insightfully about things that matter. I'm impressed with his continued devotion to topics like Continuous Integration, testing and refactoring.