It sounds to me like you went into dev chasing a paycheck.

If that's true, it's time for a little introspection. If I were you, figure out what you want to do and study that on the side while you continue in your tech career.

I will add this though, I've experienced the same feelings several times throughout my career, it's usually a precursor to burnout.

Here are some key indicators of burnout:

• Chronic Fatigue and Exhaustion: Feeling tired not just physically, but also mentally and emotionally, even after rest.
• Reduced Performance and Productivity: Struggling to concentrate, make decisions, or be creative, leading to decreased work output and quality.
• Cynicism and Detachment: Feeling disconnected from your work, colleagues, and the goals of the organization. This might manifest as a negative or indifferent attitude towards work.
• Increased Irritability or Impatience: Getting frustrated more easily than usual, especially with colleagues or work-related issues.
• Physical Symptoms: Experiencing physical issues like headaches, stomach problems, or a weakened immune system.
• Lack of Enjoyment: Losing interest in activities that used to be enjoyable, including hobbies and time with family or friends.
• Sleep Disturbances: Experiencing changes in sleep patterns, such as difficulty falling asleep, staying asleep, or restlessness.
• Feelings of Ineffectiveness and Lack of Accomplishment: Doubting the value of your work or feeling like you're not achieving anything significant.
• Escapist Behavior: Engaging in behaviours like excessive gaming, internet surfing, or substance use to avoid work or feelings related to it.
• Isolation: Withdrawing from social interactions both in the workplace and outside.
• Neglecting Personal Needs: Putting off self-care, including exercise, healthy eating, or doctor's appointments.
• Procrastination: Delaying work tasks, often due to a lack of energy or motivation.

If this describes you, it's time to take care of you.

Keep safe! You're not alone in the struggle!

I'm much more passionate about what I cancreate with code vs any part of coding itself. While I wouldn't put too much pressure on it, I think this is the best place to look for if you want to be impassioned by the activity. Of course this is different for everybody, but it's an idea.

I think you also tend to get more passionate about what you're best at — but it's sort of a chicken-egg thing.

Within the craft, I find myself particularly fascinated by matters of latency in Internet-enabled development, i.e. how long it takes for a response to be returned. Based on the speed of light, a response can only be so fast, but there is a lot we can do with infrastructure and code to make things happen faster. I use this idea to try and build services which are globally useful, as opposed to just fast if you happen to live on the east coast of the USA.

I mention that only because it may get your imagination going. Good luck!

Build stuff that helps people. You, your family, friends or colleagues.

Experience how much impact you can make and how easy it is to scale that impact by ex. doing web dev and sharing your work with literally anyone with internet access.

Either you love something or you do not. I do not think you can force it. Learn to like something on the other hand, I believe very much you can but that requires you to think very differently and more positively on the subject in hand.

Hi,
Nandini
Don't worry,
I can help you full time
I'm a full stack developer & software engineer.
I hope to hear from you soon.
Sincerely.

You can't ride that horse far. It's not about loving coding, it's about feeling sense of the code that solves a problem. You may love beautiful clean code, but that's require good craftsmanship. And you'll not get there without practice, mostly for fun.
You can code for money and be mediocre at it - find nine to five programming job and have a good hobby elsewhere. Or you can build software systems for enjoyment of cracking world problems (that's why I refuse cryptocurrency jobs - they create more problems than they solve) and be fulfilled and love coding so much to practice it in own free time for fun and have topics to discuss with others outside your main professional concern.
I compare that with writers. Almost everyone can write. People write for work, but only tiny percentage really enjoy this and are good enough to make serious money by being read by thousands.

Go with the step-by-step approach. Not everyone is comfortable with every other programming language. However, the fire should be there with everyone to work. Depending upon the nature of work, Most likely if it's an official project work, then it's the responsibility of a developer to dig deeper, learn and work with the project. It doesn't matter what technology it is. In the end, it's just a mindset :)

The moment one looks himself or herself as a programmer, things will change. That's the beauty of a programmer, as she/he can work in any programming language.

To add up to@andrewjensentech comment, I would say that your true nature as a human being is also a key factor. We are not all passionate in life and that’s ok. I even think that this passionate stuff is well over made.

Respecting yourself, seeing these persons working way to much putting aside their own life is a good key that you are aware of what could be wrong with to much work. Always put yourself first, otherwise who’s gonna do it if you don’t.

The rest is a question of do you like or not what you do? If not, where would you see yourself?

What I'm enjoying about learning Python now is it keeps me interested or curious to learn more. I want to enjoy my ideal job, not love it. Most of the things I love I use as hobbies and invest time + energy on my terms.

But, I would recommend exploring different job titles or companies to see if that's the missing piece. Sometimes a better environment can make a huge difference. Or even asking yourself what is your ideal job? Or what would you change about your current job?

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.