Grieve (grieve) wrote,

Multiple Data Structures

At work the other day I was talking with my coworker M., and we were discussing good technical questions for experienced hires. He pointed at that the basis for his technical questions were finding a problem that required multiple data structures to solve. He pointed out that novice programmers straight out of college hate solving a problem with multiple data structures. I thought about what he said, and I believe that for the most part he is right.

Then I thought, wait, I hate multiple data structures as well. Have I not grown as a programmer? Then I realized I use multiple data structures all the time. I just think of them as objects/component of the solution which support the main data structure. I admittedly still try to use as few data structures as possible, but I like to think of that as economy of design, which in theory leads to simpler code.
Tags: programming

  • A C++ quiz

    Suppose I gave you the following snippets of code: #include <cstdio> void Class::PrintFoo() { printf("Foo\n"); } int main() { Class13 c13;…

  • Volatile does not thread safe make.

    I keep running across code, some old and some new, that uses the volatile keyword in an attempt to make the code thread "safe". Using that is always…

  • How many Univacs is that?

    Today at work one of my coworkers had a new phone. I flippantly asked him how many Univacs it was? Of course in a room full of geeks once a question…

  • Post a new comment


    default userpic

    Your reply will be screened

    Your IP address will be recorded 

    When you submit the form an invisible reCAPTCHA check will be performed.
    You must follow the Privacy Policy and Google Terms of use.