How to fall in love with coding?

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 can create 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.

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.

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.

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.

You need to first understand and acknowledge what made you start with software development. Please note that coding is just one of the tasks done in software development.

You will also agree that software development is all about people and solving the issues faced by people using software. So obviously we need to be people-person and possess skills like problem-solving, logical thinking, analytical thinking, interpersonal skills and empathy.

Before you love coding, you need to love people and problem-solving to tackle their issues with software solutions.

We cannot start with coding and then hope to start linking it someday.

And we should have our why. Why are we doing coding?
I think learning to code is like learning to use a sword. We use the sword in a war against injustice. But just being a soldier is not enough. We should have some reason to be a soldier. And courage, patriotism and fighting spirit. Otherwise, it will become just work for pay.

Rediscover your "why." It's not just about code; it's about making a difference, solving problems, and yes, getting paid for the skill you've mastered.

Coding for longer hours beyond duty hours need not mean extra effort or love for coding. It could be helplessness or compulsion. It could also be inefficiency of the environment or/and the developer. We should aim for smart work and not slogging. Work-life balance is important.

Probably it may be a good idea to consult some expert career counselor.

Above all, it is not the end of the world if we do not like coding or do it well. There are many right people in the wrong places. Maybe you can excel at something else. Worry more about the time you are going to invest continuing with coding than the time invested so far in it. Make good use of the remaining time.

All the best!

Maybe a good approach. If you can - take some time off, a holiday of some sort, travel a bit if possible. Detach yourself from tech completely.

Once you are well rested, sit down and make a list of what you love about programming - even if this is not current but at some point where you enjoyed some aspects. Write it down.

Now allocate some time whenever you can, to do some of the stuff you wrote down outside of the bounds of work, just for fun. I write blog articles and work on side projects for fun, there's no major monetary reward I get out of these but I enjoy it.

If you are a 9-5 coder, that's perfectly fine and respectable, a job pays the bills. In this case - hobby coding as mentioned above will make it seem like a chore so this is maybe not a good route for you.

In the above case, write down your weaknesses - which seems to me like you struggling with problem-solving. Take it one day at a time, initially, this will be hard and you may want to give up but keep going, just practice in small increments and when you succeed celebrate that, and give yourself some sort of reward.

If you keep beating the nail, eventually it will go in. Same concept, just keep practicing the things you are not good at, and as you gain more experience - you will get better.

If all else fails, maybe it's time to have an honest review of where you are at. Then either look for a Job that fits you better, change your language or framework or just take a break completely and try another career path.

Ultimately, you going to be in the industry you choose for probably 10 - 20 years, even retirement - so find what you love and do that.

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?