4 ms·
Hey nobody271 - don’t be so hard on yourself. Working on failed personal projects is a rite of passage for programmers, and believe it or not, failed projects a
by malux85 8y ago
Hey nobody271 - don’t be so hard on yourself. Working on failed personal projects is a rite of passage for programmers, and believe it or not, failed projects are important
They teach you about limits, they teach you where you over abstracted, they make you practice other skills (reading code, debugging, deployment, evaluating libraries, making technical decisions and trade-offs) you might not be fully consciously aware of all of this, but while you were building it, you were improving all of this.
your design on the site is top-notch, really good work. You have something to show for your time.
For us highly ambitious, it’s easy to get caught up in the negative aspects of why something didn’t succeed - but that’s only because the self doubt that us creators have (that is neccisary for us to critique our own work) needs to be kept on a leash.
You’re not one of the 99% of society eating Cheetos and watching TV all night, you’re building your skills. You have come out of this a better developer, and that is success in itself.
- nobody271 8y agoThat's not my design, lol. I just grabbed a template off the internet so that I had something to work with. https://w3layouts.com/grocery-shoppy-ecommerce-bootstrap-responsive-web-template/ https://w3layouts.com/grocery-shoppy-ecommerce-bootstrap-res... I had never got to the point where I focused on making the dialogs themselves look good. I spent all my time fixing the animation not aligning with the actual dialog and not being able to get an image to animate that wasn't blurry. By the end I had tacked on so much temporary code to work around those issues that changing anything was a guessing game. I know you're right. I'm still looking for what I learned though.
- malux85 8y agoDid you learn that getting animations exactly right and pixel perfect is an extremely challenging job, and is almost impossible to get working across all resolutions, all devices and all conditions without an exceptional amount of work? There’s your lesson - in reality is something is not pixel perfect most users won’t notice and most of the ones that do notice won’t care. You took it way too far down the rabbit hole, pushing resources (time etc) into things that don’t matter, you learnt this was a mistake, and you’ll never make that mistake again. I learnt this lesson too - making the same mistakes you did. Every programmer learns this in one way or another. You learnt better resource allocation. Level up!