60+ hours is not that much tho.
> The thing is, it doesn't work
What doesn't work?
Why doesn't it work?
Is the source of the problems in code or in the libraries?
Have you covered all the edge cases and handled all error states?
>and has nasty bugs on slower systems
Due to concurrency issues or?
>it crashes once in a while
That happens! Find/Write a reporting tool and analyse the traces :)
>Sometimes has audio/video synchronization issues
Smells like concurrency issues to me.
Hey,it's all good. You wrote something cool that connects a dozen different technologies, did it all in C++ in a short time frame - and you're just a student! That's great!
You're not a bad programmer - maybe you're just bad at system design/software architecture. And that's not bad - that's great. A lot of folks go into the field and work for a few years until they start learning about architecture and experience what problems it can cause. You just had that experience, now go read up and figure out how to rewrite it into V3. Take some extra time to think about the models, the abstractions, the components, go through edge cases in your head, figuring out if and how your system acccounts for them.
Try not to overengineer it - you probably will - but don't think that means you will suck forever, you will learn with time and experience.
Imagine if Picasso quit after his first sucky drawing. Maybe even HN wouldn't be here.
> The thing is, it doesn't work
What doesn't work? Why doesn't it work? Is the source of the problems in code or in the libraries?
Have you covered all the edge cases and handled all error states?
>and has nasty bugs on slower systems
Due to concurrency issues or?
>it crashes once in a while
That happens! Find/Write a reporting tool and analyse the traces :)
>Sometimes has audio/video synchronization issues
Smells like concurrency issues to me.
Hey,it's all good. You wrote something cool that connects a dozen different technologies, did it all in C++ in a short time frame - and you're just a student! That's great!
You're not a bad programmer - maybe you're just bad at system design/software architecture. And that's not bad - that's great. A lot of folks go into the field and work for a few years until they start learning about architecture and experience what problems it can cause. You just had that experience, now go read up and figure out how to rewrite it into V3. Take some extra time to think about the models, the abstractions, the components, go through edge cases in your head, figuring out if and how your system acccounts for them. Try not to overengineer it - you probably will - but don't think that means you will suck forever, you will learn with time and experience.
Imagine if Picasso quit after his first sucky drawing. Maybe even HN wouldn't be here.