Hacker News new | ask | show | jobs
by thecupisblue 2200 days ago
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.

1 comments

Thanks for your answer, I think I want to address a few points.

>What doesn't work? Why doesn't it work? Is the source of the problems in code or in the libraries?

>Due to concurrency issues or?

It's difficult to name one but probably the biggest issue at the moment is frame rates randomly drop at some point the the resultant video is garbled (1 minute is played in a few seconds, etc.)

Possibly concurrency is one of the reasons. The Media Foundation encoder expects video and audio frames at regular intervals and if because of performance issues, some frames drop, it gets into a vicious cycle and frame drops accelerate until it comes to stand still.

>You're not a bad programmer - maybe you're just bad at system design/software architecture.

<rant> Unfortunately, I think I am because I suck at algorithmic challenges (competitive programming), system design, reading documentation for external APIs, in short nearly everything that is to programming. I learned programming at 13, it goes to show I have been programming for quite some time and others who started it in university went to do amazing things while I suck at basics. I dreamed of starting a tech startup someday but it seems unlikely now.</rant>

>figure out how to rewrite it into V3

My client is a SOB and doesn't appreciate my efforts nor rewards them, so it's unlikely. Besides, I have signed NDA so starting open source project is out of the question. I'm thinking of starting some other projects, though.

>Imagine if Picasso quit after his first sucky drawing. Maybe even HN wouldn't be here.

I liked that lowkey compliment but I doubt I am worthy of this.