saheb37

Yes, it's a feeling majority of us experience at some point or another. After writing code and making software for a few years, you feel it's not fun anymore.

You should experiment more and find out what tasks or activities you find fulfilling so you can look for roles that allow you to do them more. For instance, if you enjoy investigating issues or incidents, then there are roles that allow you to spend majority of your time doing that.

Looking back helps. Why did you get into programming in the first place? Perhaps you like working from scratch. So go back and do that. This is a good way to reevaluate whether you still like programming like you once did.

If you don't care about low level details and don't enjoy programming, that's fine too. You can explore management roles, where majority of time goes in managing people, processes, and/or products.

If you feel you still want to be on the tech side, there are plenty of roles that are worth exploring: platform engineer, data engineer, network engineer, compiler engineer, research engineer, database engineer, etc.

The field is vast; you can just keep expanding your breath. It's okay not to find a niche.

You can teach, or study more, then teach. Presuming you still like learning more about computer science.

You can write about tech, instead of writing code. Still be in tech industry, but write words instead of code. Communicate with humans, instead of computers.

You can go further away and still be in tech I suppose, get into math modelling roles or quant roles.

Also worth ruling out is burnout. If you are burned out, you probably won't find anything interesting. So take a break, and contemplate what sort of things interest you. Whatever piques your curiosity, just follow that, and see where that takes you.

How about INR (India)? Anytime soon?

It does resonate to some extent, but I still like software.

If you dislike the industry, you might still not like product/engineering-management roles.

It seems to me like myself, you need to find out what kind of work you like, what you'd explore for your own curiosity even if you are not paid.

Trying out OS/networks/compilers/data-science/research roles might be worth your while. But, if core CS is not your thing, it's possible you will find management roles (product/engineers) more satisfying.

I liked how Hunter S. Thompson put it in words when he was asked for advice.

You ask advice: ah, what a very human and very dangerous thing to do! For to give advice to a man who asks what to do with his life implies something very close to egomania. To presume to point a man to the right and ultimate goal— to point with a trembling finger in the RIGHT direction is something only a fool would take upon himself.

I am not a fool, but I respect your sincerity in asking my advice. I ask you though, in listening to what I say, to remember that all advice can only be a product of the man who gives it. What is truth to one may be disaster to another. I do not see life through your eyes, nor you through mine. If I were to attempt to give you specific advice, it would be too much like the blind leading the blind.

https://fs.blog/2014/05/hunter-s-thompson-to-hume-logan/

I have quite enjoyed a couple of books by David Eagleman: The Brain, and Sum.

I haven't got around watching the movie yet, is it any good? I will give it a try.

I will take the bullet and suggest Ayn Rand's Fountainhead.

If you are a teenager it will definitely make you think and likely leave an impact on you. It's not a typical novel, more like philosophical ideas presented in the form of a novel. Ideal characters placed in real life. You will also understand why the world is divided into Ayn Rand lovers and haters.

It questions how the world works, how it should work, how people live their lives, and how they should live their lives, etc, etc.

Warning you, it's not filled with plots twists.

You might enjoy Undoing Project by Michael Lewis as well, it's like the backstory of Thinking Fast and Slow.

All the fiction books that have left a lasting impact on me have been long...

A Little Life by Hanya Yanagihara (https://www.goodreads.com/book/show/22822858-a-little-life)

It is emotionally intense, beautifully written, and is a hypnotic read. Larger than life characters centered around one enigmatic protagonist, Jude. It's about pain, friendship, love, and the brutality of memory and experience.

Shantaram by Gregory David Roberts (https://www.goodreads.com/book/show/33600.Shantaram)

An Australian gangster escaping his home country and falling in love with India (Mumbai). Lots of philosophy. A moral tale. Plenty of drama. And a love story with deep, dark characters.

Fountainhead by Ayn Rand (https://www.goodreads.com/book/show/2122.The_Fountainhead)

A novel on idealism for the irrational, real world we live in. Centered around an ideal man, Roark, who struggles to survive despite being a brilliant architect; he doesn't give up on his principles and never conforms. Not a typical novel, disliked by many.

The first time I implemented the backtracking algorithm it felt really special. I was struggling to solve 8 queen problems for a couple of nights, banging my head around it. And then when it worked, I knew my love for programming was not going anywhere any time soon.

It was ugly, I had used 8 for loops, each running for 8 iterations, but, I still felt awesome when it worked. Before this, I had written only lab programs. Next, I applied the backtracking algorithm to solve Sudoku recursively, and that's how it all began. I entered the world of algorithms.

I know it's just one form of brute force algorithm, maybe doesn't even count as one, and is not that elegant, but, it will always remain my favorite.

It takes a long time to create something rare and valuable. Patience is priceless.

Going all the way for your dream (or something you believe in); it doesn't matter how many times you fail, and only you should be responsible to decide when to let it go when you think it's time to move on. Doing what you want, for as long as you want, is what life is all about.

Only one or maybe two things are really important at any point in your life, rest of them just seem important, but they are not.

Boredom is the biggest problem of our generation.

An Indian Bollywood movie comes to my mind, the hero recreates an entire day by planting false memories in the minds of people around him, he exploits the power of visual sense to do so, which sticks quickly to your mind.

https://en.wikipedia.org/wiki/Drishyam_(2015_film)

don't you get tired of NPEs and checking everything with possibility that it can be null? Scala solves it using Options.

There are lot more, but this is one which irritates me the most.

I agree its not a real life example :) It was never meant to be. And definitely there is some better approach to implement the same hierarchy.

Thanks, got your point, will keep it more simple and generic next time :)

I didn't intend to screw up the actual point, maybe I did but I think the actual point was still understandable, isn't it? If not please let me know the actual point where the article lost it in your case.

traits in Scala doesn't always have to be in a "is a" relationship. If it makes you understand then think of them as adding behavior/mixins. And about why the syntax confused you, the first "with" trait has to be extended, if it could replace extends with "with" in case of traits then maybe you would have liked it better.

Maybe to make it more interesting, it turned out to complex as you are saying. But idea was not to use A, B, C etc. Will try to come up with something different next time.