It's interesting that while you describe the reasons that you don't like coding you are at the same time describing the reasons that others love coding.
• when you said: "...something that is so difficult" → I thought: "that's why it's exciting".
• when you said: "Every step has obstacles" → I thought: “and I love surpassing them”.
• when you said: "...not familiar with the codebase..." → I thought: “it’s so cool to research and understand someone else’s code”.
• when you said: "...I don't know the tech stack..." → I thought: "I love to learn new staks".
• when you said: "...don't know to do a particular thing" → I thought: "I love research and learning to do things".
• when you said: "Sometimes I get errors/bugs" → I thought: "I love the feeling when I solve these puzzles".
Many have already contributed to this post. But if I could only advise one thing, it would be:
Most things do not have an intrinsic meaning, we are the ones who give meaning to things. And coding will never stop having all these challenges, but you continue with the expectation that one day you will be able to coding without these obstacles, so when the obstacles appear you give them a negative meaning. Understand once and for all that coding will always be like this, and start looking at the challenges with a positive eye or experience burnout as they said.
I don't have a job in software development yet, but I've been an automation technician for ten years, and what attracted me from an early age to automation and now to study software development is precisely this surprise of challenges and glories in overcoming them.
It's a matter of perspective.
It's interesting that while you describe the reasons that you don't like coding you are at the same time describing the reasons that others love coding.
• when you said: "...something that is so difficult" → I thought: "that's why it's exciting".
• when you said: "Every step has obstacles" → I thought: “and I love surpassing them”.
• when you said: "...not familiar with the codebase..." → I thought: “it’s so cool to research and understand someone else’s code”.
• when you said: "...I don't know the tech stack..." → I thought: "I love to learn new staks".
• when you said: "...don't know to do a particular thing" → I thought: "I love research and learning to do things".
• when you said: "Sometimes I get errors/bugs" → I thought: "I love the feeling when I solve these puzzles".
Many have already contributed to this post. But if I could only advise one thing, it would be:
Most things do not have an intrinsic meaning, we are the ones who give meaning to things. And coding will never stop having all these challenges, but you continue with the expectation that one day you will be able to coding without these obstacles, so when the obstacles appear you give them a negative meaning. Understand once and for all that coding will always be like this, and start looking at the challenges with a positive eye or experience burnout as they said.
I don't have a job in software development yet, but I've been an automation technician for ten years, and what attracted me from an early age to automation and now to study software development is precisely this surprise of challenges and glories in overcoming them.
thanks for your insights!