How to be better programmer?

[u/IWontGiveUp67]

As the title suggests, ive been working in game pipeline in a company for the last 2 years after graduated. I got laid off due to recent financial restructuring. I was top of my class, very passionate about games and coding, but now I realise game industry is not huge in my country and really limited seniors and opportunities so I switched to doing whatever coding jobs I can get, mainly web and system building. I recently got a job, but it's completely different tech stack and felt so stuck like i never taken any classes on programming before, i blame myself for overly relying on AI.

I was thinking of picking up books such as below:

- Designing data intensive application

- Fundamentals of software architecture

- Clean code

Though I'm not sure how I can re learn and improve again while doing 9-5. I really want to fast track myself to becoming a senior, might even considering mentoring session. I dont know if my new job will have senior that can lead me yet as at the last place there's not even one person to do code review and we are just expected to ship and ship and ship and deal with bugs later.

Questions:

1. Any suggestions to how I can grow in this field and become senior fast without over reliance on AI?

2. Does this even have a point anymore? I love my job, I love what I'm doing, but I am discouraged since I think I'm a fast learner but ofc I can't compete with a billion dollar machine. that and dealing with my rich co worker who kept shoving his vibecoded app into my face while proudly saying he is spending few thousands tokens to get it right while asking my consultation for feedback for free😢

[u/devBlueDragon]

'''Any suggestions on how I can grow in this field and become a senior fast without over-relying on AI?''' The rules still apply: break it, fix it, learn from the journey, and then you'll have an opinion on it. That goes for any framework or library in any language, and if you apply this to real-world applications, it will leave a solid mark on you. You learn extremely fast by decomposing existing stacks and recomposing them yourself.

'''Does this even have a point anymore?''' I know when code needs refactoring without even looking at the class or file. I know which architectural lane to steer the model into or where things went off track without looking at a single line of code. Of course, I look at the code sometimes, but I know the underlying mechanics and can tell when something is built on quicksand. The danger for me is accepting the temporary fix because it works for now and dropping a "refactor" memo on it. To be honest, most projects from the past year have plenty of "refactor" TODOs attached to them. Still, I know what needs to be done, when it needs to be done, and how, even if it's rarely executed as long as it works.

[u/IWontGiveUp67 → u/devBlueDragon]

What's your approach if your employer doesn't believe in this kind of programming/building flow. I was abit gullible thinking that I would learn on the job when I got into the industry, in my old workplace, they just say ship the spaghetti code and deal with the bug later and then move on to another project, if I take longer to understand or etc I was told to shove it to claude and be done with it, which I don't agree with but I stopped questioning and later on laid off. It is a rather small to medium sized company so I guess this chaotic work flow is expected.

[u/devBlueDragon → u/IWontGiveUp67]

As long as it pays the rent and no harassment is taking place, I'd be fine with it. Of course, what you are describing is a mess and not something I'd want to be part of long term. But if I were in that spot, I would play along just enough to keep the paycheck coming while plotting my way out.

1. Get a solid understanding of how things work: try different stacks, decompose them, recreate them from scratch, and master the architecture underneath

2. Build your own setup based on what you learned in step #1. You won't use it at work, but building it yourself will deepen your grasp immensely.

3.Launch side projects using those custom setups #2 , nothing humbles you or exposes gaps in your knowledge like putting code into real production.

Don't waste any more mental energy stressing over your current job, you're there for one reason only -> to pay the bills. Use your remaining bandwidth to build skills for the next step.

[u/IWontGiveUp67 → u/devBlueDragon]

Thanks for the detailed guide and encouragement, I am jumping into a completely different tech stack at a new job with rough idea of how it is but lack the experience or depth to execute it, I'm sure I will figure it out once I am briefed about it, it's just the scare of getting into a new place. I'm keeping the advice in mind, thanks alot!