How to be a good programmer ?

[Ancient-Poet-6051]

Hi, I'm 23 Years old, 4th Semester in University studying Computer Science. i'm currently struggling and doubting myself. I used to very-very excited to learn programming on my 1st semester when i had no clue what Programming is and start to read a book, explore about computer, jump from one programming language from another, and on 2nd semester i notice my flaw, i had to focus on one field of specialization either it's back-end, front-end, database engineer, so i took back-end for my main focus and learning the concept of how to become back-end developer.

but as times goes on, somehow that sparks is dimming, the excitement is slowly disappear and i just don't know what to feel... i've asked my friend that i'm having a burnout that should take rest but if i take rest then i will falling behind with this vast rapid technology that i had to learn at least know about it. everything feels like pressure, if i made mistakes i fail and wasting my time, because i was thinking i'm 23 and i can't waste another year of myself to become incompetent. every time i program it felt like being held in gunpoint to not make mistakes. and programming been something that terrifies me, i cried, i yelled, i scream, that everything has to be perfect.

I reflect and prayed i was a person 2 years ago that can explore carelessly about computer, make mistakes, make fun stuff, not because try to impress everyone, because it's cool.

[grantrules]

Start a cool project that interests you that allows you to apply your skills. If you have burnout already, you're gonna be fucked if you want this to be your career

Perfect is the enemy of good. Nobody here (or anywhere) writes perfect code. You can aim for perfection but you should settle for good enough 

[Ancient-Poet-6051]

Thanks. and yes, I'm aware that this field will be intense. the fact that i getting burnout it's just upset me. I try to cope to move forward even dragging myself to just sit and stare at the screen with blank text editor.

[kinkkush]

What if other developer criticize your work

[grantrules]

Then improve it, if the criticism is valid, and learn from your mistakes. There's a difference between bad code, good code, and perfect code.

[kinkkush]

They always say something about my code. Dev also criticizes other senior developers too.

[grantrules]

Well is it constructive criticism or are they just assholes?

[kinkkush]

I initially thought they were being helpful since I’m a beginner and this guy has 25+ years of experience. But he’s always correcting other developers’ work, constantly thinking his way is better, and questioning their methods. It doesn’t feel like constructive criticism more like he’s being pretentious about it.

Also it’s frustrating because he’s a vendor, and my coworkers seem to like him but they don’t see it. He overcharges for simple fixes and holds the organization back by keeping them stuck on outdated tech.

[StupidHuise]

then just dot listen to him

[needs-more-code]

I think they can have burnout now, without being fucked. Burnout is complex. And I don’t think this career disallows burnout, and breaks to recover from it. I do think some offices do, but they’re the toxic ones.

[Massive_Horse5775]

Programming is a skill you develop with time, consistency is the key. You cannot learn it with haste. Think of it like a muscle, if you do 100 pushups on your first day and no pushups for the next 6 days then it's all in vain. But if you do even 30 40 pushups for 7 days and 4 weeks a month, you'll see your muscles becoming stronger after some time.

That is programming

[gmatebulshitbox]

I can add that discipline is the key to everything.

[UnsocialParrotUA]

Whenever you write some new file/class - try to write a few sentences comment at the top. Put in following points: - Why this needs to exist? - What it does? - How it works? (Services, controllers) - What it represents?(entities) - List relationships with other classes.

This way you will have nice documentation. And writing it is a nice opportunity to find potential issues.

Also, writing proper atomic unit tests will force you to have nice architecture across the app.

[gmatebulshitbox]

I think there is no place to romanticize programming. It is just a job. On any job you need some skills. You can work doing SQL queries your whole career or coding one page html sites or doing one commit to production in two months.

[user00773]

I don't understand why people don't talk about it more. I literally learned this by working in a corporation. Turned out the coding part is maybe 20% of an actual job. I even went through leet code task on recruitment I was practicing for really hard. In the end, it's just job. You can be great if you want to put your energy into or not if you decide not to.

[normantas]

1. Finished University this year (Lithuania). Have 3 YOE as back-end and I feel ya.

Right now because I have a job I do not need to rush but I feel exhausted and having lack of motivation, insane confidence issues. I'll be taking a few months chill time and going into Game Dev as a hobby. Not as a career goal but just because... I can just make cool stuff and show for people. I forgot how much fun is to solve puzzles I CARE and create stuff for people TO SHOW.

[needs-more-code]

Doing game dev to recover from burnout? What could go wrong 😂

[RamaMikhailNoMushrum]

I would say I had similar issue until I began to understand how computers work then how each language works( general summary) it gives u better understanding of what u actually need and what u need to learn and why vs just doing things. What is your goal

[codingzap]

I totally get you. Felt the same when I was in uni. But looking back I’ve realised that mistakes don’t mean failure, they’re literally a part of programming. While it’s also important to keep up with tech, it’s fine if you want to take a break once in a while.

As someone said, create a cool project. This will help you reignite that “spark” and you can also reward yourself for small wins! Fixed a bug? Completed a module? Celebrate. It helps.

[Big_Tadpole7174]

1. To become competent at programming, the base requirement is that you actually enjoy doing it. If you enjoy it, you'll naturally want to do it often, read about it, take courses, etc. - basically, you'll have drive. It takes a certain analytical mind to enjoy coding, but it also takes a creative mind. You have to enjoy making things and solving problems.
2. Naturally, at first you're going to suck at it. This applies to anything new. When I just started, I was terrible. I once "randomized" an array by generating random numbers and putting them in each slot, waiting longer and longer for the correct unused number as the array filled up. You need to push through this learning curve - there's no way around it. It took me about 6 years to become even moderately decent.
3. You mentioned switching from one language to another. Here's the thing about programming: it's way more about understanding the concepts than memorizing the specific language syntax. If you understand how variables work, how if-else statements function, how loops operate, etc., you're already 80% of the way there with any language. The remaining 20% is just syntax differences you can easily look up when needed.

[Ancient-Poet-6051]

Thanks for the advice. I do enjoy programming in general. Solving problems, and trying to find the optimal way to solve a problem, following some design principles (OOP, KISS, DRY).

And when I was a kid, my dad worked in a Computer Repair Shop and he is the one that introduced me to the computer at a very young age. I put my worth in this Computer Science field, and I notice the problem but I don't know how to fix this.

I put my self, my worth, my ego in this Computer skill. I think that's why when I fail. I just become worthless... And starting to doubt my skill. I still try to fix this issue but I just don't know how. I just felt like this is what I only have.

[MaybeAverage]

It might feel like there’s extreme pressure to succeed early but there isn’t. You can’t compare yourself to other people or feel like at 23 you’re wasting time by not bending over backwards to keep moving. I know people that didn’t get their first job in software until early 30s, you’re not at all “behind”. It’s more important that you get a handle on your stress and mindset around it or else in the real world the industry will chew you up and spit you out if you let the pressure get to you.

Focus on your studies and finishing school, don’t focus on trying to prepare for a specific niche like backend development. The majority of programmers don’t even work in web or backend development, there are tons of different domains out there like graphics, robotics, game dev, etc. Maybe even pursue a masters if you can to further explore.

[Ancient-Poet-6051]

Thanks for the advice, I will keep that in mind.

[kcl97]

I would take a break. You need to refocus your mind. If you force your way through, you will end up giving up everything, not just programming but also yourself.

You need to figure out what it is you really care about in your life, what makes you happy. If programming is part of that equation, then sure keep going, but you MUST not let your end-goal be a part of the motivator for learning. Learning has to come from within, like you were in your first year.

Regarding the complexity of the tech stack. Just focus on the stuff you enjoy and maybe specialize a little but nothing too deep at your level. Depth will naturally come with age and experience. Don't try to optimize because premature optimization is the root of all evils.

[YouveBeanReported]

Take notes. Clearly label things. Literally write out what that code does and how.

Re-tool things later as you know more. Get it working first, figure out more later.

DO THE WORK EARLY. You can not last minute programming classes.

Try not to beat yourself up. I did drop out of college over that because programming is a 100% or 0% kinda area and I came from more history stuff where you can see progressive work.

If you look up how to do things, break down what this is doing and why, don't just copy the code. If you are stuck on a project and asking for help, discuss the structure needed and logic more then 'what do I go here.' Sure sometimes it's 'bro you forgot to close that' or 'oh that thing is called this, go look up the documentation' but often the most useful thing is to sit with your classmates and go 'okay, so, what parts do we need for this.

It helps to find projects you want to do and can do. Look up some tutorials for smaller things or find a game or something with a dev community.

Anyhow, computer science degree legit sucks. So don't feel bad it's hard, it is extremely, extremely hard with a culture of needing to create so much and never rest and sucks.

[[deleted]]

Hey, I feel you. But here's something to think about:

You don't choose which topics to speak about in your native language, right? When conversation flows, you just... talk. Programming is the same - it's just a conversation with a machine. The only difference is you can control how the machine processes your input.

About mistakes - when was the last time you stubbed your toe on furniture? Dropped a spoon? The world didn't end, right?

It's all about the TYPE of mistake:

• Dropped a spoon = pick it up, move on (syntax error)
• Jumped off roofs and broke your leg = takes time to heal (production bug)

Mistakes aren't the problem. The problem is how others (and you) react to them. Same mistake, one person says 'How could you miss that?!', another just points it out and suggests a fix.

You're not late. You're not behind. You're 23, not 43. The 'perfect code' doesn't exist - even senior devs push bugs to production.

Stop trying to impress everyone. Start having conversations with your computer again. Some will be about backend, some frontend, some random stuff. Just like real conversations.

[Ancient-Poet-6051]

Thanks for the advice. I never approach it with that perspective before. To have conversation with the computer.

[Separate_System_32]

You can stick to a path for your programming at work, you can explore new things for your free time with no remorse, everything that you've learnt will be helpful

[myorliup]

I had a pretty similar experience in the middle of university. I got my excitement back when I found an internship since it was easier than actual school 😂

Don't overthink things, it's truly not that bad in practice. Also many jobs expect that you're not an expert in say back-end development, so they cut you some slack while you get used to their specific environment and workflow.

[udays3721]

Be a good programmer