JonnyG
- 233
- 45
I appreciate all of the advice everyone in this thread has given me. Thank you all very much!
The discussion revolves around the design decisions for a program intended to store and retrieve recipes, including the management of ingredient densities for unit conversions. Participants explore various programming paradigms, particularly object-oriented design (OOD), and consider the implications of using classes versus simpler data structures.
Participants express differing views on the necessity and utility of object-oriented design, with some advocating for its use while others suggest simpler alternatives. The discussion remains unresolved regarding the best approach to structuring the program and the choice of programming language.
Participants highlight the need to clarify definitions and relationships within the data structures, such as how recipes and ingredients are defined and how they interact. There is also a recognition of the limitations of C++ for this type of application, suggesting that the choice of language may impact the learning experience.
Individuals interested in programming design principles, particularly in the context of recipe management applications, as well as those learning C++ or exploring object-oriented programming concepts.
Vanadium 50 said:To be clear, I wasn't encouraging subterranean lagomorphic voids. I was encouraging him to think about what he wants this to do before jumping into coding. A simple electronic equivalent index card might be fine. Or it might not. But you don't want to be in the middle of writing and discover you missed a requirement that would cause you to redesign.
I did suggest that it is better to design data structures before leaping into coding. I think this is a good idea, and my experience is that much grief can be avoided by thinking data structures before leaping into coding.
yungman said:[...] My advice to you is find something that you REALLY LOVE, don't look at programming just because of good pay. You literally marry to the job, you better love it. [...]
As an add-on to this good advice, if your wife is going to be the primary user of the program, it helps a lot if the program's data model matches her mental model. For example, what is her mental model of a recipe? Finding that out will require taking some time to ask her questions.Vanadium 50 said:First, I would try and understand the data structures you want.
This is my experience as well. With well-designed data structures, much of the code will more or less write itself. But with a tangle of code that isn't backed by well-designed data structures, it can take forever to find your way out.Vanadium 50 said:my experience is that much grief can be avoided by thinking data structures before leaping into coding
But maybe not two years ...PeterDonis said:Finding that out will require taking some time to ask her questions.

Congrats! Enjoy the rideJonnyG said:I start full time as a software developer in May :)
Yeah, enjoy the ride. In another thread the OP seemed to be lacking some self-confidence. Don't make that mistake. Demand what you and your work are worth (and what your education entitles you to of course).JonnyG said:This thread just got raised from the dead...
I appreciate everybody that helped me out. I start full time as a software developer in May :) (finally)
All time spent with the wife is happy time.DaveC426913 said:But maybe not two years ..
Some of you have never been on a big lake in a small sailboat with my wife and it shows.Vanadium 50 said:All time spent with the wife is happy time.
I REALLY[/size] hope she does not have access to your account here!DaveC426913 said:Some of you have never been on a big lake in a small sailboat with my wife and it shows.