You ever get into one of these situations?
-
Alice Cooper wrote a song about being "stuck" called Lost in America
Quote:
I can't get a girl 'Cause I ain't got a car I can't get a car 'Cause I ain't got a job I can't get a job 'Cause I ain't got a car So I'm looking for a girl with a job and a car Don't you know where you are
It's not really my cup of tea, and yet the catch 22 situation perfectly describes where I'm at right now. If I incorporate my new font engine into GFX, I break UIX, which I use to send GFX to the screen. Rebuilding UIX is not feasible at this point, as I'll get overloaded with tasks and I can't do that much work in tandem with other open issues on my primary project The whole project is like this. I need to break my pixel class and my draw destinations as well. That breaks thousands and thousands of lines of code, including potentially (but not definitely) my new font classes. I'm absolutely buried right now and considering taking a different approach - ground up rewrite, heavy on the copy and paste from the old codebase. I'm so lost. :(
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
-
Alice Cooper wrote a song about being "stuck" called Lost in America
Quote:
I can't get a girl 'Cause I ain't got a car I can't get a car 'Cause I ain't got a job I can't get a job 'Cause I ain't got a car So I'm looking for a girl with a job and a car Don't you know where you are
It's not really my cup of tea, and yet the catch 22 situation perfectly describes where I'm at right now. If I incorporate my new font engine into GFX, I break UIX, which I use to send GFX to the screen. Rebuilding UIX is not feasible at this point, as I'll get overloaded with tasks and I can't do that much work in tandem with other open issues on my primary project The whole project is like this. I need to break my pixel class and my draw destinations as well. That breaks thousands and thousands of lines of code, including potentially (but not definitely) my new font classes. I'm absolutely buried right now and considering taking a different approach - ground up rewrite, heavy on the copy and paste from the old codebase. I'm so lost. :(
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
You can bewitch a broom to do some of the carrying. Then split it again for added bandwidth. Profit.
-
Alice Cooper wrote a song about being "stuck" called Lost in America
Quote:
I can't get a girl 'Cause I ain't got a car I can't get a car 'Cause I ain't got a job I can't get a job 'Cause I ain't got a car So I'm looking for a girl with a job and a car Don't you know where you are
It's not really my cup of tea, and yet the catch 22 situation perfectly describes where I'm at right now. If I incorporate my new font engine into GFX, I break UIX, which I use to send GFX to the screen. Rebuilding UIX is not feasible at this point, as I'll get overloaded with tasks and I can't do that much work in tandem with other open issues on my primary project The whole project is like this. I need to break my pixel class and my draw destinations as well. That breaks thousands and thousands of lines of code, including potentially (but not definitely) my new font classes. I'm absolutely buried right now and considering taking a different approach - ground up rewrite, heavy on the copy and paste from the old codebase. I'm so lost. :(
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
honey the codewitch wrote:
considering taking a different approach - ground up rewrite, heavy on the copy and paste from the old codebase.
Sounds like it may be the easiest way to approach the situation. Have fun (if possible)! Just think of the limitations with the old approach that you are overcoming! That might bring a smile to your face!
Our Forgotten Astronomy | Object Oriented Programming with C++ | Wordle solver
-
honey the codewitch wrote:
considering taking a different approach - ground up rewrite, heavy on the copy and paste from the old codebase.
Sounds like it may be the easiest way to approach the situation. Have fun (if possible)! Just think of the limitations with the old approach that you are overcoming! That might bring a smile to your face!
Our Forgotten Astronomy | Object Oriented Programming with C++ | Wordle solver
Why does it feel like a failure though? :wtf: Meh. I guess I am just beating myself up over it. If it wasn't maintainable it wouldn't have lasted for as long as it did, I guess, but then other than feature adds and some minor cross platform compatibility fixes I haven't had to do much.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
-
Alice Cooper wrote a song about being "stuck" called Lost in America
Quote:
I can't get a girl 'Cause I ain't got a car I can't get a car 'Cause I ain't got a job I can't get a job 'Cause I ain't got a car So I'm looking for a girl with a job and a car Don't you know where you are
It's not really my cup of tea, and yet the catch 22 situation perfectly describes where I'm at right now. If I incorporate my new font engine into GFX, I break UIX, which I use to send GFX to the screen. Rebuilding UIX is not feasible at this point, as I'll get overloaded with tasks and I can't do that much work in tandem with other open issues on my primary project The whole project is like this. I need to break my pixel class and my draw destinations as well. That breaks thousands and thousands of lines of code, including potentially (but not definitely) my new font classes. I'm absolutely buried right now and considering taking a different approach - ground up rewrite, heavy on the copy and paste from the old codebase. I'm so lost. :(
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
Yep, been there with the editor that fixes warnings found by my C++ static analysis tool. Should each line of code be a separate string, or should the entire file be one big string? This went back and forth a couple of times until I settled on the latter, and each time it caused upheaval in the work that had gone into it before. I had no previous experience to draw on, so I had to play around with both approaches until I could decide which one was better.
Robust Services Core | Software Techniques for Lemmings | Articles
The fox knows many things, but the hedgehog knows one big thing. -
Alice Cooper wrote a song about being "stuck" called Lost in America
Quote:
I can't get a girl 'Cause I ain't got a car I can't get a car 'Cause I ain't got a job I can't get a job 'Cause I ain't got a car So I'm looking for a girl with a job and a car Don't you know where you are
It's not really my cup of tea, and yet the catch 22 situation perfectly describes where I'm at right now. If I incorporate my new font engine into GFX, I break UIX, which I use to send GFX to the screen. Rebuilding UIX is not feasible at this point, as I'll get overloaded with tasks and I can't do that much work in tandem with other open issues on my primary project The whole project is like this. I need to break my pixel class and my draw destinations as well. That breaks thousands and thousands of lines of code, including potentially (but not definitely) my new font classes. I'm absolutely buried right now and considering taking a different approach - ground up rewrite, heavy on the copy and paste from the old codebase. I'm so lost. :(
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
Rich woman, bad cough! Is that to much to ask. :) I actually have a very good mate.
A home without books is a body without soul. Marcus Tullius Cicero PartsBin an Electronics Part Organizer - Release Version 1.4.0 (Many new features) JaxCoder.com Latest Article: EventAggregator
-
Alice Cooper wrote a song about being "stuck" called Lost in America
Quote:
I can't get a girl 'Cause I ain't got a car I can't get a car 'Cause I ain't got a job I can't get a job 'Cause I ain't got a car So I'm looking for a girl with a job and a car Don't you know where you are
It's not really my cup of tea, and yet the catch 22 situation perfectly describes where I'm at right now. If I incorporate my new font engine into GFX, I break UIX, which I use to send GFX to the screen. Rebuilding UIX is not feasible at this point, as I'll get overloaded with tasks and I can't do that much work in tandem with other open issues on my primary project The whole project is like this. I need to break my pixel class and my draw destinations as well. That breaks thousands and thousands of lines of code, including potentially (but not definitely) my new font classes. I'm absolutely buried right now and considering taking a different approach - ground up rewrite, heavy on the copy and paste from the old codebase. I'm so lost. :(
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
Yes. While working in Waco maintaining a large electronic health record code base (This was years before the American Recovery Act mandated it.), Micro$oft Windows was doing a major upgrade from Windows 2000 to Windows 7. Since the code base was built starting in the 1990s and long before I joined the company, there was a fair number of Windows API changes that had to be worked in, and this is the killer, a huge amount of duplicate code and reliance on the side-effects of various subroutine and function calls.
The "common code" was a huge DLL that took forever to load and it contained code that was only occasionally used.
My boss, who learned to program in the Navy over twenty years earlier, was one of the programmers who originally built the program. While he was a good programmer, he moved into management and his skills became very rusty and out of date. He could not see why the existing code had to be changed.
This left me with the dilemma: update it on my own time without telling him or try to patch the code and pray that nothing breaks irrevocably.
I came up with a plan:
- I dropped the duplicate subroutines and functions, then recoded the calls to use the ones that remained. I hunted down all of the dependencies upon side effects and removed them. Many were functions that returned a single value of True or False, but modified other data. These I changed to return a data record with the data changes. I released this update to the huge common code DLL.
- I split the common code DLL into a three level structure with all the non-UI Windows API calls in the bottom layer. Depreciated API calls, of which there were many, were replaced with the current ones. The code to set up for API calls, such as letter generation, print formatting, data base record construction and whatnot in the middle layer as multiple DLLs. The top layer contained the business logic, with separate DLLs for Mental Behavioral Health, Mental Retardation Developmental Disabilities, insurance processing, billing, and client demographics. I released this revised common code as an update. I received praise from the clinicians because the whole program loaded much faster. My boss provided no feedback.
- I split the main UI code removing rarely used paths to separately called programs. The main UI code handled all of the windows that everyone used. The separate programs handled billing and report generation, behavioral health unique logic, and developmental disabilities unique
-
Why does it feel like a failure though? :wtf: Meh. I guess I am just beating myself up over it. If it wasn't maintainable it wouldn't have lasted for as long as it did, I guess, but then other than feature adds and some minor cross platform compatibility fixes I haven't had to do much.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
[???] Maybe because you kick yourself in the butt for not thinking of the constraints you are now facing when you originally designed the project? It is easy to be hard on yourself, from personal experience. [???] Go with the flow. If the easiest thing is to do what you are thinking of, smile, take a break, possibly do something else, then get back at it when the mood strikes. Have fun!, and good luck with it! If I had your skills it wouldn't have taken me so long to do some of my projects!
Our Forgotten Astronomy | Object Oriented Programming with C++ | Wordle solver
-
[???] Maybe because you kick yourself in the butt for not thinking of the constraints you are now facing when you originally designed the project? It is easy to be hard on yourself, from personal experience. [???] Go with the flow. If the easiest thing is to do what you are thinking of, smile, take a break, possibly do something else, then get back at it when the mood strikes. Have fun!, and good luck with it! If I had your skills it wouldn't have taken me so long to do some of my projects!
Our Forgotten Astronomy | Object Oriented Programming with C++ | Wordle solver
I appreciate the vote of confidence. :)
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
