What to do?
Posted: December 10th, 2019, 4:56 am
Okay, I've run into this problem over and over and it has prevented me from finishing a project for the last time.
One of my biggest road blocks when programming something is design or architecture. I always felt I had a grasp on classes and program structure with the exception of programming patterns like the Observer pattern or ECS, but I always end up running into cases where I have to stop and think about how classes should interact. Should X be a derived class of Y? or should I create a bridge class that communicates between two other different but not entirely unrelated classes? Should I use interfaces?
Well, I can't seem to get anywhere because when I stop and think about it, I usually just drop the project and find something else that interests me.
While I know programming patterns can help make your classes more modular, and interfaces have the same affect and allows for testing different concrete classes, I just can't seem to make it work, so I'm going to do something a little more elementary.
Fuck encapsulation.
Fuck accessor functions
Fuck architecture
It's the easy road for awhile until I get my bearings with structs and functions...like C, but using C++ references, templates, function/operator overloading, namespaces and the STL. Public access all the way.
I did not come to this conclusion lightly, but I need to feel accomplished in something. Right now, I feel defeated and need a pick-me-up. Hopefully, I'll have something to show in a month's time. More realistically by the end of January. The time frame is based on previous experience with the project I'm working on so I have a good starting point and I've rewritten it thrice now.
Anyway, hope everyone enjoys their holidays and new years. I'll still be around for anyone who needs help, but I'm going to have my nose buried in my monitor over the next 6 weeks minus a few days for Christmas and the New Year.
One of my biggest road blocks when programming something is design or architecture. I always felt I had a grasp on classes and program structure with the exception of programming patterns like the Observer pattern or ECS, but I always end up running into cases where I have to stop and think about how classes should interact. Should X be a derived class of Y? or should I create a bridge class that communicates between two other different but not entirely unrelated classes? Should I use interfaces?
Well, I can't seem to get anywhere because when I stop and think about it, I usually just drop the project and find something else that interests me.
While I know programming patterns can help make your classes more modular, and interfaces have the same affect and allows for testing different concrete classes, I just can't seem to make it work, so I'm going to do something a little more elementary.
Fuck encapsulation.
Fuck accessor functions
Fuck architecture
It's the easy road for awhile until I get my bearings with structs and functions...like C, but using C++ references, templates, function/operator overloading, namespaces and the STL. Public access all the way.
I did not come to this conclusion lightly, but I need to feel accomplished in something. Right now, I feel defeated and need a pick-me-up. Hopefully, I'll have something to show in a month's time. More realistically by the end of January. The time frame is based on previous experience with the project I'm working on so I have a good starting point and I've rewritten it thrice now.
Anyway, hope everyone enjoys their holidays and new years. I'll still be around for anyone who needs help, but I'm going to have my nose buried in my monitor over the next 6 weeks minus a few days for Christmas and the New Year.