|
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
| | | | |-- FS @ 2.0.0
| | | | |-- SD @ 2.0.0
| | | | | |-- FS @ 2.0.0
| | | | | |-- SPI @ 2.0.0
| |-- 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
|-- Wire @ 2.0.0
To err is human. Fortune favors the monsters.
|
|
|
|
|
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
|
|
|
|
|
It occurred to me that I feel like one of those crazy bargain hunters sometimes while coding.
"Oh, I can reuse that lexing layer in my markup reader with my CSS reader, no extra cost"
It's not even about the actual savings for me. The joy is in the kill. 
To err is human. Fortune favors the monsters.
|
|
|
|
|
I sometimes start writing it before remembering I've already written it. And more informed than my new attempt. Mixed feeelings.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
|
|
|
|
|
There's joy in discovering code you've written before that lends itself to easy reuse or extension. It means you did something right. 
/ravi
|
|
|
|
|
Well it spent a lot of time in the design phase, as it originally came from a refined C# project that I had reused a bunch, before porting it to C++. =) It was just good fortune all around.
To err is human. Fortune favors the monsters.
|
|
|
|
|
Ravi said it right
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
I had one of those lately.
Wide reaching change impacting hundreds to thousands of disparate modules.
A few lines of change in a key component, Done!
|
|
|
|
|
|
A dual lean-to, how innovative> 
|
|
|
|
|
That must be from a movie directed by David Lean 
|
|
|
|
|
I don't always write robust code, but when I do, it collapses in the middle. 
|
|
|
|
|
PIEBALDconsult wrote: The specs probably said
Specs? What specs?
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
I was being generous, if not outright facetious.
|
|
|
|
|
from this photo cannot tell what sort cover collapsed. was it an A-frame, flat, somewhere in between. No specs provided. Not clear that snow caused collapse or was it wind before the snow?
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
It was not an A-frame, there was no bracing either, no triangles.
Collapse caused purely by the weight of the snow.
Last year they replaced an earlier structure (which had withstood several winters) with this one, I have no pictures of either.
|
|
|
|
|
It's was just a sun shade structure.
With no bracing not much snow is needed to cause problems. Looked it up ranges from 4 lbs per sq ft and up.
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
That's what I love about the South! (Gulf coast)
|
|
|
|
|
But specs (SOW) most definitely did say that it has to cost less than X.
So you get what you pay for.
|
|
|
|
|
Message Closed
modified 15-May-23 19:06pm.
|
|
|
|
|
That's a really sweeping generalization - there are people who don't want to learn in at all ages, from 3 year olds to 100+, just as there are people who do, who can, and who care. The youth of today communicate in different ways from the "generation before them", but that was ever the way.
Attaching labels to groups of people and saying "all these won't / can't fix things" dehumanizes them as well as doing those that do want to learn a major disservice.
But it's easier, because the "won't learns" stick out, they complain instead of investigating - so those that do get on with it get hidden in the noise.
The young are as guilty of this as some of the seniors are - they label all those born before 1990 as "boomers" and insist that none of them can cope with any modern technology. Conveniently ignoring that the basis for that modern tech (and quite a good chunk of the modern tech itself) was invented, developer, and manufactured by those very "boomers" ... But again, the ones that genuinely can't use modern tech stick out more!
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
OriginalGriff wrote: That's a really sweeping generalization
Or an observation, my dear Watson.
A few hundred years ago, there was evolution and a struggle to survive. Now, all survive, regardless of life-choice.
You can say that any child said so during history (which can be easily proven wrong), but things keep changing quicker every month, and so, the outlook for any children. They differ more from the previous generation then then previous ones, because tech and health improvements.
Bastard Programmer from Hell 
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
Dimwits 
ed
|
|
|
|
|
You have to understand the world that they are growing up in. My grandchildren have been watching videos on mobile phones from the age of two. And since the marketing people want you to upgrade on an annual basis, young people see this as the normal way of things, and don't question it.
|
|
|
|
|
Member 14968771 wrote: "get a new one..."?
The answer used to be "did you try rebooting?"
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
