New answers tagged

0

Don't be ashamed of your old code. Be proud that you improved so much in a year that you look back at your old code and are ashamed of it. (Also ask yourself: Could you have written better code a year ago? Does the code look bad because you came to work drunk, or because you were on the internet all the time and spent no time on the code, or does it look ...


0

2 questions you should ask when looking back: 1) did it work? 2) was it stable? If yes is the answer then ok, since then you have progressed along with code etc, so while it can be improved, it may not need it. However, if improving it is a good exercise for a junior or newbie then that is itself a good reason for not worrying about it.


4

This is very very VERY common and nothing to be ashamed of. I cringe when I see some of my old code, and I've been programming for more than four decades. A friend of mine, who is a professor, noted that in IT, you never come across a "201" class. They never teach us anything in depth, we are more or less given the basics, and thrown into the deep end, ...


2

If someone ever tries to "judge", you can say him "Right now I know this code is bad. That's why I was JUNIOR back then."


10

First of all, what you are passing through seems to be some sort of imposter syndrome, so thanks a lot for coming forward. As a junior developer you are following requirements and making sure they are met (and maybe raise some concerns on the way things ought to be implemented?). With that, you don't need to feel ashamed/sad as you are developing what was ...


5

@jackwoods - there is nothing to be ashamed of. In fact, you are realized probable issues of your code is greatly appreciable since many coders still are unable to do self-realization. You shall hurry for corrective changes if this poor code is causing bugs or will become a liability in future. You can try making a list of possible issues you identified ...


8

We all look at our old code and cringe a little. This is completely normal, but what many of us do not experience is the desire to quit over it. Don't quit over something normal, instead focus on the fact that this code which you find undesirable, was seen by the company as good enough to merit a promotion. Learn to laugh at your own code, how noob it was ...


1

I don't know what to do, I'm feeling sad, sometimes I feel so sad that I want to quit my job, but I can't. How can I overcome this? Will people ever judge me because of old code? You have a few choices here: Get a new job and start with a clean slate elsewhere. As drastic as this may seem, if this is substantially hampering your productivity, career (...


1

Why are you sad about your old code? Indeed, for any old code that has been written, it will be seen as a joke, Especially if you've learned a lot of things. Like I did . But you have to take the positive side from here, you have learned a lot of things and from there you should not repeat things that you think are bad. Don't think about things that make ...


72

You’re ashamed because you’re growing as a software engineer? The more you learn, the worse your old code looks... just comes with the territory. Keep looking forward, that “horrible” code you’re referring to helped you get to where you are today. You’ve learned, and that’s nothing to be ashamed of. Worrying about those who are judging you is rarely a ...


Top 50 recent answers are included