|
Another corollary that a comment triggered,
Quote: Create a facade around any API that you are using to protect your code from changes in the API.
|
|
|
|
|
quote Create a facade around any API that you are using to protect your code from changes in the API.
A great idea that no one ever does.
Ok, not no one, but it is done more rarely than it should be.
Also, there are physical limitations to it.
We use a 3rd party component that has 100s methods.
We should wrap the component but it gonna take a while. 
|
|
|
|
|
A 1:1 mapping is not what I was envisioning. (Beginners might miss that joke! What’s the point?)
Facade/Wrapper/Adapter/Proxy/etc
|
|
|
|
|
englebart wrote: Facade/Wrapper/Adapter/Proxy/etc
Yes but then all of those are classes also. And thus those two require an interface...
Myself I am joking but I remember quite a few years ago someone posting somewhere that all the classes in the application were required to have an interface and a factory.
|
|
|
|
|
A facade should be the simplest requirements needed for your code’s clients. If the library I am using has 5 classes and hundreds of methods/properties, my facade could be as simple as one class with 5 properties and 1 method. Since my facade has a hard dependency on the library, I would use an interface so that my consumers do NOT have a compile time dependency on the library.
Like I said earlier, (possibly paraphrased) if you find yourself wrapping everything 1:1, then just accept the hard dependency and ship! ship! The facade might be added later (YAGNI) as well as only if the next major update to the library has breaking changes. Without the facade I would have 70 projects to change. With the facade I have one project to change.
I do agree with the release often philosophy.
A lot of this depends on team size, pace, code stability, etc.
And maybe IDE? Creating an interface from a class or a class from an interface should not take more than a second. Right click…
Someone earlier mentioned they were stuck on VS2013. Yuck!
|
|
|
|
|
Why? How difficult is it to adopt the old semantics of a given dependency, and shim a a new replacement library when it becomes necessary to jump ship. I have done this a few times, though not often. Seems like deferring the pain ('YAGNI') until it becomes necessary is optimal overall.
|
|
|
|
|
hpcoder2 wrote: Seems like deferring the pain ('YAGNI') until it becomes necessary is optimal overall
Yeah, exactly.
You can either have:
1) Pain now (All Interfaces)
2) Pain later (that may never occur)
I figure take the pain later -- cause a lot of software rots for other reasons and is completely re-written anyways. So, you may never reach the "pain later" stage anyways.
As a matter of fact, I've rarely seen it in 35 years of software development.
And, when another manager comes in anyways, they think something totally different and wipe away the "old" code, even if it is extensible from all those Interfaces.
|
|
|
|
|
I program since more than 40 years and develop software since more than 30 years.
15 years ago I heard first time about DI containers, and since 10 years I use IODA as principle to avoid DI containers.
Only integration classes are allowed to call other operations.
If you put the whole logic into operation-classes, with no logic in data-classes and integration-classes (only something like "rail-switches" in integrations),
then separate input- and output- from logical operations,
than you do not need to discuss those things like DI any longer.
I use derivation very rarely, combination of classes is my favorite.
But I use also actions and closures.
You don't have to hide every operation class behind an interface, but it can be helpful.
Consider: By using of interfaces you can not longer jump to the executed code by just pressing "F12" in Developer Studio.
There is no universal answer to this question, it just depends on ...
What is IODA? See here:
https://www.infoq.com/news/2015/05/ioda-architecture/[^]
|
|
|
|
|
Fantastic and interesting reply.
Thanks so much for sharing your experience here.
Interesting that you specifically avoid DI.
Ralf Peine 2023 wrote: By using of interfaces you can not longer jump to the executed code by just pressing "F12" in Developer Studio.
That is definitely one of the problems that I encounter with DI.
It is a pain that the implementation is always somewhere else which you have to track down.
Must say though, that I downloaded VSTudio 2023 to help with this and now it can (as you would hope) navigate to the exact implementation -- even if the code is in another dll it will use reflection to show you the code. Very good.
|
|
|
|
|
Hmmm... once you decide that *all* something must do *something*, before you even know what problem you're about to solve, you've decided that reality takes second place to what you've decided reality should be. "Dijkstra would not like this" <- his immortality, for those who get the reference.
|
|
|
|
|
From CP newsletter
Create AI pro register to uphold ethics, says BCS • The Register[^]
In UK there is a proposal to license/enforce corps when using AI.
Then it uses the problem as an example with the UK government prosecuting post office managers for something that never happened.
Except of course that had nothing to do with AI. And the proposed rules are for corporations. No idea how that is supposed to prevent the government from making false allegations.
Reminds me of the silliness of a case in the US where people were prosecuted due to 'recovered memory' testimony from very young children against a number of people accusing them of satanic rituals. The testimony allowed defied logic.
McMartin preschool trial - Wikipedia[^]
That was far from the only case where recovered memories were allowed.
Unfortunately in the US quite a few people still believe in that nonsense along with so called professionals that keep promoting it.
|
|
|
|
|
So at some point, along with the "harassment training" (which, ironically, is supposed to teach you how to identify and prevent harassment and not be a harasser yourself, rather than training you on how to excel at harassment as the course name would seem to suggest, but I digress) at some point corporations will have an "ethical AI training" class we'll all have to take. Except for management. 
|
|
|
|
|
Hmm. My employer has us do 'business conduct' and other training every year. No one is exempt, including the president. It's not too arduous and can usually be completed in an hour or so. Completing the training is a condition for continued employment. I've never heard of anyone being fired for not completing it, but I wouldn't want to work with anyone who was so argumentative and confrontational that they wouldn't comply with a reasonable request.
I could see the company creating a policy for using AI-generated material on the job. Intellectual property rights are a significant concern for us in places, and given the cloudy (pardon the pun) nature of much AI training data, it's a reasonable response.
As far as governmental regulation goes, I'm sure that's going to be a goat![Elephant | [mastadon]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/elephant.gif) from the word go.
Software Zen: delete this;
|
|
|
|
|
It all boils down to where the spotlight is shining - if it gets too close to home, move the light to something else to divert the attention so we can go on doing the "right thing" irrespective of public view, AI now has the spotlight like any other tech taht were out there before. 
|
|
|
|
|
In absence of hardware, while waiting for it to ship I've taken to producing a starting codebase for my new project.
It's a Cortex-A based CPU, and those are not typically "real time" - for those of you familiar with embedded these work like your smartphone and are complex enough that they generally require an operating system like linux or android in order to function.
The problem with that is boot times. There have been successful efforts to get linux boot times down to less than half a second but it requires so much u-boot hacking and linux kernel hacking that it's not much easier than going bare metal.
I'm going bare metal. I'm terrified that I've accepted a contract for something I've never done before. It has been years since I coded anything in assembly. I read it, but I don't typically write it these days. That's about to change.
I'm dealing with stripped down C and C++, multiple cores but no scheduler, and therefore no synchronization primitives other than say, suspending the other core entirely, if possible? And that's yikes.
I just managed to scrape together enough of the CubeMX HAL under this environment to give me SPI support (I think), but I won't know until I get this board and connect my logic analyzer, and I'm really anxious about it. Lots of moving parts, and I haven't tested a single thing yet.
It's out for delivery now. I was excited yesterday. Right now I'm kinda freaked out. 
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
Ah, the unknown. Exciting, terrifying, challenging, mysterious, bound to be frustrating and also with great successes and stories. It's times like these, if you had a crystal ball to show you the future (in detail!), would you look into it? 
|
|
|
|
|
I bought an old graphic software written in VB6. I paid $30. the author sent me the installer and I can NOT install it on Windows 7 and Windows Vista. The install or continue button does not show up and I can not continue the installation process.
What can I do to make the installer work?
UPDATE:
I just installed VB6 runtime plus and it works now.
diligent hands rule....
modified 18-Feb-24 16:12pm.
|
|
|
|
|
Have you discussed with the author?
"A little song, a little dance, a little seltzer down your pants"
Chuckles the clown
|
|
|
|
|
this professor does not have solution for this. he would like tear my check or send it back to me
diligent hands rule....
|
|
|
|
|
Assuming you haven't tried to run the install as a windows XP or 7 program? Right click the executable, Properties, compatibility and 'Run this program in compatibility mode for' and choose an os.
Edit:
You might make sure that your display is at 100% and not 125%. It is under display properties, you can adjust the scale. Sometimes apps especially older ones don't scale well.
Jack of all trades, master of none, though often times better than master of one.
modified 16-Feb-24 12:38pm.
|
|
|
|
|
thanks for the info![Rose | [Rose]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/rose.gif)
diligent hands rule....
|
|
|
|
|
I bought a 1999 shop manual wrapped in a XP virtual machine. It works.
"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
|
|
|
|
|
Gerry Schmitz wrote: XP virtual machine
I would consider that the best way to try this.
Even if the installer did work in a newer OS, the app might still behave oddly.
|
|
|
|
|
Are you on 64-bit Windows? If so then the issue is that the installer is most likely a 16-bit application, which 64-bit Windows doesn't support.
|
|
|
|
|
You need to look at the files and check which common controls, dll's etc is included. You then need to manually install all if not most of the controls manually to run, still no promises made. It is very old tech, like installing disc brakes on a 1932 Ford, you have to change so many components to make it work, is it really worth the effort begs the question... 
a Solution I posted at the time, not sure it might wotk still - Installing VB6 Applications on VISTA or Windows 7[^]
modified 16-Feb-24 15:31pm.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
