read.engineerscodex.com/p/4-software-design-principles-i-learned/comment/54766923

Preview meta tags from the read.engineerscodex.com website.

Linked Hostnames

2

Thumbnail

Search Engine Appearance

Google

https://read.engineerscodex.com/p/4-software-design-principles-i-learned/comment/54766923

Jay Nabonne on Engineer’s Codex

I think in some ways 1 and 2 are related. You don't want to repeat your sources of truth (or, alternatively, "places where decisions are made"). But you do need to be sure that what you're trying to unify via DRY is actually the same thing. Semantics is key over syntax. Whether code actually looks the same ends up being irrelevant - I have "++i" all over my code. :) And you can have two pieces of code that are doing the same thing that don't actually look alike. (I had a thought relating 1 to 4 - don't store state you can compute = single source of truth - but I went back and realized you had already addressed that.) Great article, by the way!



Bing

Jay Nabonne on Engineer’s Codex

https://read.engineerscodex.com/p/4-software-design-principles-i-learned/comment/54766923

I think in some ways 1 and 2 are related. You don't want to repeat your sources of truth (or, alternatively, "places where decisions are made"). But you do need to be sure that what you're trying to unify via DRY is actually the same thing. Semantics is key over syntax. Whether code actually looks the same ends up being irrelevant - I have "++i" all over my code. :) And you can have two pieces of code that are doing the same thing that don't actually look alike. (I had a thought relating 1 to 4 - don't store state you can compute = single source of truth - but I went back and realized you had already addressed that.) Great article, by the way!



DuckDuckGo

https://read.engineerscodex.com/p/4-software-design-principles-i-learned/comment/54766923

Jay Nabonne on Engineer’s Codex

I think in some ways 1 and 2 are related. You don't want to repeat your sources of truth (or, alternatively, "places where decisions are made"). But you do need to be sure that what you're trying to unify via DRY is actually the same thing. Semantics is key over syntax. Whether code actually looks the same ends up being irrelevant - I have "++i" all over my code. :) And you can have two pieces of code that are doing the same thing that don't actually look alike. (I had a thought relating 1 to 4 - don't store state you can compute = single source of truth - but I went back and realized you had already addressed that.) Great article, by the way!

  • General Meta Tags

    16
    • title
      Comments - 4 Software Design Principles I Learned the Hard Way
    • title
    • title
    • title
    • title

  • Open Graph Meta Tags

    7
    • og:url
      https://read.engineerscodex.com/p/4-software-design-principles-i-learned/comment/54766923
    • og:image
      https://substackcdn.com/image/fetch/$s_!iq1T!,f_auto,q_auto:best,fl_progressive:steep/https%3A%2F%2Fengineercodex.substack.com%2Ftwitter%2Fsubscribe-card.jpg%3Fv%3D-769361568%26version%3D9
    • og:type
      article
    • og:title
      Jay Nabonne on Engineer’s Codex
    • og:description
      I think in some ways 1 and 2 are related. You don't want to repeat your sources of truth (or, alternatively, "places where decisions are made"). But you do need to be sure that what you're trying to unify via DRY is actually the same thing. Semantics is key over syntax. Whether code actually looks the same ends up being irrelevant - I have "++i" all over my code. :) And you can have two pieces of code that are doing the same thing that don't actually look alike. (I had a thought relating 1 to 4 - don't store state you can compute = single source of truth - but I went back and realized you had already addressed that.) Great article, by the way!

  • Twitter Meta Tags

    8
    • twitter:image
      https://substackcdn.com/image/fetch/$s_!iq1T!,f_auto,q_auto:best,fl_progressive:steep/https%3A%2F%2Fengineercodex.substack.com%2Ftwitter%2Fsubscribe-card.jpg%3Fv%3D-769361568%26version%3D9
    • twitter:card
      summary_large_image
    • twitter:label1
      Likes
    • twitter:data1
      0
    • twitter:label2
      Replies

  • Link Tags

    31
    • alternate
      /feed
    • apple-touch-icon
      https://substackcdn.com/image/fetch/$s_!on6a!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F6df5c8bb-6896-426e-92ae-aef74c5cff0a%2Fapple-touch-icon-57x57.png
    • apple-touch-icon
      https://substackcdn.com/image/fetch/$s_!SKfc!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F6df5c8bb-6896-426e-92ae-aef74c5cff0a%2Fapple-touch-icon-60x60.png
    • apple-touch-icon
      https://substackcdn.com/image/fetch/$s_!zC2k!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F6df5c8bb-6896-426e-92ae-aef74c5cff0a%2Fapple-touch-icon-72x72.png
    • apple-touch-icon
      https://substackcdn.com/image/fetch/$s_!V0UK!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F6df5c8bb-6896-426e-92ae-aef74c5cff0a%2Fapple-touch-icon-76x76.png

Links

13