Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
CODE PROJECT For Those Who Code
  • Home
  • Articles
  • FAQ
Community
  1. Home
  2. The Lounge
  3. The joy of NIH syndrome.

The joy of NIH syndrome.

Scheduled Pinned Locked Moved The Lounge
hardwaredata-structuresbusinesstoolsperformance
2 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • honey the codewitchH Offline
    honey the codewitchH Offline
    honey the codewitch
    wrote on last edited by
    #1

    Not invented here - Wikipedia[^] I've posted my dependency trees at the end of this post to give you an idea of my ecosystem, and how much of it is my code. Anything prefixed with "htcw_" is mine I wrote most of the code I touch day to day. That's a good feeling, and it makes me efficient. I think most people here know what a prolific coder I am by this point, and the fact that I'm building with an utterly familiar, self-consistent, and interoperable base is a big part of why that is. I feel like a metal worker who spent a decade putting their own shop together just the way they like it, with the tools, jig tables, hoists, and all that all cut and welded to personal spec, bespoke like, for maximum workflow efficiency. I feel like PIEBALDconsult can appreciate this. I understand all the reasons not to fall into NIH. Intimately, as I've been on sharp business end of trying to get up to speed with a framework developed by someone else on their own over a decade. It's daunting, no matter how well commented it is. But gosh, it makes coding so nice when you've got your own ecosystem to work with. Here's my dependency tree for my current UIX iteration (still in development) Dependency Graph |-- htcw_gfx @ 1.4.1 | |-- htcw_bits @ 1.0.6 | |-- htcw_data @ 1.0.7 | |-- htcw_io @ 1.1.3 | | |-- htcw_bits @ 1.0.6 | |-- htcw_ml And that's just my portable non-hardware specific code. Here's one for an ESP32 under Arduino Dependency Graph |-- htcw_gfx @ 1.4.4 | |-- htcw_bits @ 1.0.6 | |-- htcw_data @ 1.0.7 | |-- htcw_io @ 1.1.4 | | |-- htcw_bits @ 1.0.6 | | |-- FS @ 2.0.0 | | |-- SD @ 2.0.0 | | | |-- FS @ 2.0.0 | | | |-- SPI @ 2.0.0 | |-- htcw_ml @ 0.1.2 | | |-- htcw_io @ 1.1.4 | | | |-- htcw_bits @ 1.0.6 | | | |-- FS @ 2.0.0 | | | |-- SD @ 2.0.0 | | | | |-- FS @ 2.0.0 | | | | |-- SPI @ 2.0.0 |-- htcw_ft6236 @ 0.1.1 |-- lcd_controller (also mine) |-- htcw_uix @ 0.1.0 | |-- htcw_gfx @ 1.4.4 | | |-- htcw_bits @ 1.0.6 | | |-- htcw_data @ 1.0.7 | | |-- htcw_io @ 1.1.4 | | | |-- htcw_bits @ 1.0.6 | | | |-- FS @ 2.0.0 | | | |-- SD @ 2.0.0 | | | | |-- FS @ 2.0.0 | | | | |-- SPI @ 2.0.0 | | |-- htcw_ml @ 0.1.2 | | | |-- htcw_io @ 1.1.4 | | | | |-- htcw_bits @ 1.0.6 |

    J 1 Reply Last reply
    0
    • honey the codewitchH honey the codewitch

      Not invented here - Wikipedia[^] I've posted my dependency trees at the end of this post to give you an idea of my ecosystem, and how much of it is my code. Anything prefixed with "htcw_" is mine I wrote most of the code I touch day to day. That's a good feeling, and it makes me efficient. I think most people here know what a prolific coder I am by this point, and the fact that I'm building with an utterly familiar, self-consistent, and interoperable base is a big part of why that is. I feel like a metal worker who spent a decade putting their own shop together just the way they like it, with the tools, jig tables, hoists, and all that all cut and welded to personal spec, bespoke like, for maximum workflow efficiency. I feel like PIEBALDconsult can appreciate this. I understand all the reasons not to fall into NIH. Intimately, as I've been on sharp business end of trying to get up to speed with a framework developed by someone else on their own over a decade. It's daunting, no matter how well commented it is. But gosh, it makes coding so nice when you've got your own ecosystem to work with. Here's my dependency tree for my current UIX iteration (still in development) Dependency Graph |-- htcw_gfx @ 1.4.1 | |-- htcw_bits @ 1.0.6 | |-- htcw_data @ 1.0.7 | |-- htcw_io @ 1.1.3 | | |-- htcw_bits @ 1.0.6 | |-- htcw_ml And that's just my portable non-hardware specific code. Here's one for an ESP32 under Arduino Dependency Graph |-- htcw_gfx @ 1.4.4 | |-- htcw_bits @ 1.0.6 | |-- htcw_data @ 1.0.7 | |-- htcw_io @ 1.1.4 | | |-- htcw_bits @ 1.0.6 | | |-- FS @ 2.0.0 | | |-- SD @ 2.0.0 | | | |-- FS @ 2.0.0 | | | |-- SPI @ 2.0.0 | |-- htcw_ml @ 0.1.2 | | |-- htcw_io @ 1.1.4 | | | |-- htcw_bits @ 1.0.6 | | | |-- FS @ 2.0.0 | | | |-- SD @ 2.0.0 | | | | |-- FS @ 2.0.0 | | | | |-- SPI @ 2.0.0 |-- htcw_ft6236 @ 0.1.1 |-- lcd_controller (also mine) |-- htcw_uix @ 0.1.0 | |-- htcw_gfx @ 1.4.4 | | |-- htcw_bits @ 1.0.6 | | |-- htcw_data @ 1.0.7 | | |-- htcw_io @ 1.1.4 | | | |-- htcw_bits @ 1.0.6 | | | |-- FS @ 2.0.0 | | | |-- SD @ 2.0.0 | | | | |-- FS @ 2.0.0 | | | | |-- SPI @ 2.0.0 | | |-- htcw_ml @ 0.1.2 | | | |-- htcw_io @ 1.1.4 | | | | |-- htcw_bits @ 1.0.6 |

      J Offline
      J Offline
      jmaida
      wrote on last edited by
      #2

      Busy Lady. I like it. It's good you have a map. It will be more help than you know. I have always had confusion about the "term not invented here". NIH = not invented here OOC = one's own code OBC = one's borrowed code -- NIH <= OOC + OBC NIH ~= OOC + OBC Does this make sense?

      "A little time, a little trouble, your better day" Badfinger

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups