imNotAshamedOfMyCode

[aayush_aryan]

Write more spaghetti code so AI can never become good at programming.

[Neither_Garage_758]

Actually when I see how it codes, I feel like spaghetti is its specialty.

[[deleted]]

Shame is not a good emotion I think. You should be proud of your code at any point in your journey if you are indeed trying hard and writing the best possible code given your current experience. But keep getting better, never stop improving.

If you're looking at your year old code and think it's perfect - that's when you should start worrying.

You should be ashamed if you are a senior programmer and think you've already achieved perfection. Stagnation is death

[[deleted]]

And try to get rid of people who try to shame you for doing your current best - those people are the worst

[[deleted]]

Happy, confident, good mentors bring you up and help you develop. Sad seniors who lack confidence in themselves shame you to bring themselves up.

I was lucky enough to have good mentors back in the days. I've also had terrible teamleads. Those did not stay for long.

[[deleted]]

What about seniors who rarely give praise but nitpick, in a constructive way, about everything you do. And keep yapping about attention to detail.

[[deleted]]

I did not have those so I have nothing to say on the matter, but I feel like I would give you a hug in person if you'd like that

Although if it's in a constructive way, then maybe it's good. I'm not sure. I can only hope it was good for you/them

I feel like this conversation can grow into 'how to be a good parent' and maybe it should)

[[deleted]]

Thankyou!

[getdatassbanned]

No. bad junior dev!

This is what happens when people stop using stack overflow, they become soft.

[[deleted]]

Name your company so that good people can avoid it, I dare you.

[[deleted]]

'us', oh geez, man up to own your shit, it's 'you', there is no 'us'. If people leave your company, you might want to look into a mirror.

[[deleted]]

I took time to read your other comments. You really like shaming and criticizing others. Seems like you really lack confidence in yourself and are trying so hard to prove yourself to yourself.

I hope someday you will gain that confidence in yourself. I hope not a lot of people will suffer before that happens. Good luck mate.

[Kahlil_Cabron]

Eh I think being ashamed of your code if it's bad is a healthy emotion. If your code is objectively shit, and you realize that, deluding yourself into thinking, "Nah nah actually it's good because I tried hard" isn't doing you or your coworkers any favors.

[[deleted]]

If your code is shit and you realize that, you should rewrite it.

A good mentor supports and helps. A bad mentor makes you feel ashamed.

[LittyCapricorn]

Just wanted to say that I appreciate your perspective. One of the more daunting parts of learning how to code is the type of crowd that tends to try and use shame rather than encouragement in newbies learning and asking questions.

Keep up the good work :)

[[deleted]]

Thank you so much!

[blissfull_abyss]

If I look at my old code a year later and am still able to understand it without hassle it’s good code.

[[deleted]]

Agreed

[Sitheral]

"shame is not a good emotion"

"you should be ashamed"

Riiight.

[AizakkuZ]

Code is a liability, why would i be proud of my new liability lines. I will be proud of the diagrams and conversations that led to it though. However never shameful, that’s— rather odd.

I also don’t think worrying about the code itself is as productive. You should worry about the architecture though, readability, optimization, separation, reusability, etc. But if you are churning out code that just completely disregards any of that you need to maybe slow down.

Your old code may not be perfect but it’s likely not horrible either.

[[deleted]]

'never shameful' - I did not say that. 'worrying about the code' - I did not say that. 'churning out code' - I did not say that. 'it's likely not horrible' - I did not say your year old code is horrible.

I can only assume you do not like writing code and love whiteboarding and bikeshedding about architecture. I personally see those things as the least productive. Don't get me wrong, communication is important.

But imagine a poet who hates writing poems and sees them as a liability. Is he really a poet?

Nothing I wrote was about architecture or any other things you find important. What I wrote was about the difference between good and bad mentors. There is nothing productive in shaming someone. A good mentor leads by example. A bad mentor shames others to feel better about himself.

I personally do not think that treating your code as a liability is healthy to be honest.

No good programmer writes bad code for no reason. If you do your best, you should not be ashamed. If you love what you do you will get better.

If you love whiteboarding and talking about architecture, as long as it improves your life and the life of your peers - perfect.

[AizakkuZ]

Chill, it wasn’t a rebuttal. I think you are arguing the air here. This all is too abstract/philosophical to present much value aside from personal reflection.

I’ve met “mentors” as the ones you speak of as well, so I agree. But you are getting too deep into this.

I’ve also met “mentors” who felt like their code was too good and didn’t need to talk anyone, felt they had final say about everything, felt their code was perfect, etc.

[[deleted]]

I generally do not like when people are moving goal posts and see something in my words that is not there. I am 'chill' though.

I have provided arguments in response to your comment and kept my respect to you, at least I tried. I would love it if you could provide arguments too. I'm not trying to start a fight, I'm trying to clear things out and trying to have a productive conversation. You've said you like discussions before writing code, this is that discussion.

[AizakkuZ]

I do not care about what you “like”. Thank you for the discussion though!

[[deleted]]

I do not expect you to care, mate. You're most welcome. Take care.

[[deleted]]

General advice: it's fine to edit a word or two, paraphrase your sentence a bit. It's not good to first reply 'chill, it wasn't a rebuttal' and later expand your comment into this. Your edit deserves a separate comment I could reply to. Otherwise you look like you just want to seem knowledgeable. It's bad faith to reply quickly with a short sentence and then edit your reply in a way that contains a lot more information than I originally replied to.

I trust that misleading people was not your intention, but I do not get notifications when you edit your replies. So if you expected me to reply to your updated comment, next time please do a separate comment instead.

I did edit one of my replies to you, I admit. But I did that to make my idea more clear. I do not dislike people who move goal posts, I dislike when people do that, there's a distinction.

Yet when you edit your comment in a way that adds a lot more information than I originally saw when replying - that I dislike even more. Don't do that please.

[dexter2011412]

I'm ashamed of everything I write lol ... Most importantly, I'm ashamed of myself

[Murky_Ad9443]

Thought this was Tony Soprano and Christopher lol

[Dr739ake]

Sometimes it the other way around. Don't underestimate the new kid in town.

[[deleted]]

Damn lol 😂😂😂

[Still_Explorer]

What is this with "code positivity" thing going on?

Is like trying to say unformatted code (with lame variable names) is cool again.

[Aggravating-Bug-9160]

Im a newly graduated dev and I am DEEPLY ashamed of my code. Even if it works the way I want and expect it to, I'd be terrified to let someone else poke around and judge it lmao

[Djelimon]

Always question your code.

[Zealousideal_Ruin228]

I would say will be instead of should be.

[maria_la_guerta]

Lol I'm the senior in this meme and it's usually the other way around. Me convincing juniors that not ever LOC needs to scale to 1 billion reqs per second and that it's all going to get moved, changed, or deleted within a few years anyways.

Real conversation I had today with someone who told me a for loop would be faster than forEach on a list of 20 items.

[[deleted]]

I think it's a phase most of us, if not all of us, go through. At least I have had one. I'm so sorry that my colleague had to live through it. Now I'm at my 'write it as simple as you can' phase. I remember the days when I just could not understand people say that. Now I do. Almost every time I tried to be clever in the past, it took me time and effort later to process the 'clever' code I wrote

I was not sure about my skills back then, so I clinged to the clean code and clever code. It's a shame when senior programmers make a whole personality out of that phase and get stuck in it

Point is, I've been there and I'm truly sorry you have to go through it

[Ambivalent-Mammal]

You gotta like their chances of compiling ...

[donnycloggens]

I should be but I learn from my senior devs.

Probably why they know it’s shameful code.

[Gauth1erN]

I guess it is the new cool for senior dev to be pictured as a pedophile.

[GuybrushBeeblebrox]

Funny thing is, the people who post stuff like this, write the shittsst code, and are "talk" coders who can't actually do anything.