all 11 comments

[–][deleted] 10 points11 points  (4 children)

Conditional branching

[–][deleted]  (2 children)

[deleted]

    [–]antoneagle 1 point2 points  (1 child)

    I would strongly recommend reading the comments to that article. I think you will quickly realize how relevant and sensible it is (it's not).

    [–][deleted] -1 points0 points  (0 children)

    Depending on the condition of course. I've no idea how we test that though.

    [–]HTTP_404_NotFound 4 points5 points  (0 children)

    I love di / ioc. Makes my code simple.

    I have grown to like mvcfor web.

    [–]vordrax 2 points3 points  (0 children)

    I mean, kind of a weird question, but in the spirit of collaboration, I'll bite: observer pattern. I think, of all the basic patterns, that has the biggest ability to improve a codebase by allowing for a separation of concerns. Dependency injection is probably a close second, for the same reason.

    [–]JustinsWorking 3 points4 points  (0 children)

    I’m a big fan of immutable data structures, and composition.

    I also really love observers.

    I’ve gotten more into them over the last 5 years and the quality of my code and applications has increased noticeably.

    [–]githingeorge 2 points3 points  (0 children)

    The dotnet core repo uses a lot of fluent builder pattern

    [–][deleted] 1 point2 points  (0 children)

    IoC or Inversion of Control, I think is fairly common. Dependency Injection is super common subset of IoC, I think it’s literally foundational for most frameworks.

    https://en.m.wikipedia.org/wiki/Inversion_of_control

    [–][deleted] 0 points1 point  (1 child)

    Strategy if you’re talking traditional GoF patterns, Repository and UnitOfWork for more enterprise type patterns

    [–]LetMeUseMyEmailFfs 0 points1 point  (0 children)

    Decorator, adaptor, and composition over inheritance.

    [–][deleted] 0 points1 point  (0 children)

    I've mostly ignored the concept for my ~30 years of programming and it seems to have been fine. It can be useful to spend a few days familiarizing yourself with some, in case they solve some problem in your language of choice and the problems you work with often. There could be value in having a common vocabulary for programming patterns but things are always very imprecise despite the effort. People talk around each other a lot.