How am I interested in coding

What to do if coding feels boring, like everything is just the same anymore? [closed]


I started programming on a Commodore 64 when I was 6 years old. Now I am 28 years old and have to take 4 courses from a first degree in computer science.

After all these years, I am getting bored of writing code. I have taken a course in computer science in theoretical computer languages ​​and 10 years of C system coding in network security and I don't get any suggestion when I write code.

I can write code in C, C ++, Python, or any language, but I can't get upset about what I'm doing. I can't feel a challenge. I wrote multithreaded code, HTTPS MITM proxy, and a WSGI application with no special algorithms required.

I feel like all of these new things are all the same, with simpler (or more) abstractions or automations, but it all sounds the same to me. Again and again. The computable language is all computable, so the coding is just a replication of a similar pattern in this subset of a sub-function.

In my day-to-day work, I get bored of looking for bugs, running code benchmarks, or fixing the problem with the X, Y, Z library.

I am a very curious person. I am always stimulated by something. But I can't even when looking at great code. I'm more comfortable with the way things work.

Is it time to move my career forward? Or to get challenging things in computer science? Maybe a degree in CS?

I started reading my first book on project management, Peopleware, and I'm more interested in the life cycle of software development. What do you suggest to do?

Maybe you tried getting into Google, Microsoft, or Apple like some of my friends have. Or maybe a career in leadership positions. I also tried to find a good book on communication rules and "human personality" to prepare for the opportunity to get into management.

Any suggestions?

PS: I have a lot of interest i am not depressed :) I love mountain, trekking, do photoshoots and I am a sport climber, I love swimming and sports in general, sometimes I run, actually I am I read a book about the history of my country (Italy) from AC to today and love traveling (this summer I traveled 4000km to see and climb loads of places in Spain, all in just 3 weeks, no vacation but a marathon I love theater and life in general.


Thanks to everyone who has pondered the answer, I have the opportunity to clear my path.

For a summary purpose, we can generalize the most frequently voted answer.

First of all, the people agree need to make our work a pillar of your life and not the only reason to stay in life (that's not my case). So if you are the only livelihood when you work, you will quickly get into a really depressed situation. Vienna is not waiting for you :)

After this memory, people suggest:

  • Increase the technical complexity I am currently working on to increase the challenge and become less bored.
  • Change the subject to a non-technical subject by trying to become a manager, or promote a supervisor in a non-technical subject related to your job.
  • Change the subject to a different technical challenge. Are you a systems programmer? Try not to get bored developing applications for people so that you will be more comfortable with your useful software when you look at people
  • Make progress in your computer science degree on your academic path

For my purpose, the right answer is to get ahead in computer science as I think programming is not the only way to learn computer science and I think that if I try other avenues in computer science, I can feel better that are different from those in software development.






Reply:


That had to happen.

If code is your primary interest, it will drive you crazy, frustrated, and depressed at times, someday forever.

Get interested in product development and enjoy seeing people use them. That's the ultimate goal in writing the code, isn't it? Code is just a tool for doing something bigger.







I answer your question with a question ...

Is it a programmer's job to program or to solve problems?

They say you are bored because writing code looks like you did before, like every piece of code has been done before.

But how did you come to the conclusion that this code is the code that should be written? Most problems can be solved in hundreds of ways, but there is only one best Path.

If you really don't find a challenge, curiosity, or interest in finding solutions or solving problems, then you really need to change something. Though I'm not sure that would be software development management. I wouldn't want to work for a software manager who feels this apathy about problem solving. It should probably just be a different industry with different issues.

If you enjoy solving problems but hate coding, you may not find enough problems to solve. Every time my work feels like a chore, I believe there is a problem to be solved. Why am I doing a lot of work? What solution can I find to separate the strenuous work from my job? That's the beauty of programming.




Sounds to me like you have one quantity Done with procedural programming and fed up with it - which I fully understand. The step-by-step determination is similar in each language of the proceedings.

Since it sounds like you have a lot of non-professional activities, I would suggest learning some of the concepts that are not what you now know and - yes - there are many, but to start with I would take Haskell recommend because it is

  • functional - you write functions that you put together to create larger functions that eventually lead to a program.
  • Lazy Evaluation - Instead of determining step by step, pulls the running time the required values ​​as required. This means that in your programs it often happens that you work with infinite lists.
  • Pattern Matching - Instead of having large if structures, you list patterns of what the parameters look like and the runtime will pick the appropriate pattern and run the appropriate code.

Here is a complete sort function:

(See http://www.haskell.org/haskellwiki/Introduction#Ease_of_understanding for an explanation.)

If any of this is new to you, I would encourage you to begin the adventure.

Good luck and have fun.



Computers are boring consumers. If you code machine-to-machine interactions all day long, the machine will react the same every time. Good to finish the project but get boring after a while. It really helps break the monotony with something not directly related to the machine.

I took inspiration from both photography and the user experience. Think about it, how is it that Apple makes people vomit so they can get out of Santa Clara next when other vendors get a lukewarm response? Do you seriously believe that Android would have gotten just as big a response if Apple hadn't resisted releasing the iPhone on Verizon for so long? I'll give you a big hint: it's not necessarily that these products are technically mature. Mania has a large psychological component.

Understanding product design and user experience is something many of us need to learn a lot about. What makes someone tick? How do you design something that is cool enough to leave the established solution? How do you create your own tech cult like Apple? These are all very interesting and stimulating questions. They flow into software development - but now you have a different focus.




Presumably you don't have enough technical challenges?

  • Try highly distributed systems. Can you easily code a system to collect logs from 1000 computers in a cluster with microsecond accuracy?
  • Try in real time. Pack all of your processes in one turn of an engine.
  • Try computer vision or image processing. Math skills, formula code skills, and optimization skills are practical.
  • Try AI. See how IBM's computer plays Jeopardy? There is likely a degree of algorithmic sophistication involved in this area.

Of course, be prepared to start earning less in an area where it is difficult, not boring, for you.


I found motivation when I switched to a field in which there are no "right" solutions. I write editorial tools and my work is as good as users find it useful. I meet a lot of non-tech people and together we try to find ways to improve the software they need to work with. I find the human interaction and the need to constantly change perspectives very pleasant and suddenly coding is no longer fun so boring.

I know this is not for everyone. Some have to do with the uncertainty that it is more difficult to have an objective measure of the quality of your work than others.

But it's an option to think about.


Yes, sometimes I feel like the reality is that you are writing the same type of code over and over again. But no, I'm not bored yet. Why this?

Because I basically enjoy discovering new ways of coding and new, succinct, elegant ways to express something in code. There are two ways of doing this: learning new programming languages ​​or learning new libraries or frameworks.

Learning a new programming language has gotten easier for me with every language I've tried. And after a while it stopped being very interesting. But then, about a year or two ago, I finally got into functional programming, which as a programming paradigm differs enough from OOP to be a new challenge. I think this has really enriched my programming skills and given me a new perspective from which to look at a programming problem. I'm now trying to discover different programming paradigms instead of just different programming languages. That's a bigger challenge.

Second, learning a new library, framework, or API: As you rightly said, new frameworks often don't solve new problems. You just solve it in other ways, e.g. B. by adding an additional level of abstraction. This may be possible because today's computers are more powerful than previous computers. or maybe because we as a whole are increasingly able to write software.

That last bit probably needs some explanation. I'll give an example: while I've been training my programming skills for the longest time, I've never given serious thought to how to maintain the code I wrote. Since I started programming for a job, my perspective has changed. Writing maintainable code is often very important in a corporate environment because every hour you spend coding is real money. A company will therefore try to keep the existing code whenever possible, and there is a chance that they may have to pass your code on to a successor.

I find that writing maintainable code is a big challenge. Often times this means that you are not writing particularly clever and highly optimized assembler code (remember The Story of Mel - A Real Programmer? ;-) Instead, you are more likely to use abstraction. The more precisely you can tailor your code to some business rules and problem domain, the better. This is where all of these new libraries come in. If you can write code in a way that is clean, clear, concise, and easy to understand, that's a good thing.

Sorry if this answer is a bit tedious. I've tried to show where my motivation for programming comes from ... and I would be interested to know if you have felt the same way at some point and if (and why) your motivation stopped at some point.





If you're tired of writing code, if it doesn't excite you, if it bores you, it might be time for a change. You could take on a leadership position, managing and directing other programmers with your years of experience. Or try moving sideways in the system architecture where you can design and plan systems and others would do most of the implementation.

Or, you can completely transform your career around something that has absolutely nothing to do with computers. Have you wondered what your dream job would be if someone could give it to you?


Start playing with microcontrollers. It's the most refreshing and exciting application of programming talent that I can think of.


It sounds like the starting points of our background are similar in that we both started programming on similar machines around the age of 6 and both of us stopped programming for various reasons. None of my degrees have anything to do with programming - I all have music degrees - although I have graduated from some computer science courses.

You are right, I believe, in finding that programmers often solve the same problems over and over, and that the "new" is all based on the "old". It is to your credit that you realize this fact; Too many developers and business people see new technologies as completely separate from old ones.

Solving such problems is of no interest to you. What would be interesting? Do you like solving problems in general? Perhaps life as a "business" software developer is not for you.

I know I have provided more questions than answers, but I hope that answering these questions provides some insight into a direction that you should be headed.


It sounds like you're stuck to me. You are in a situation you don't want to be in and you don't know how to get out of it. My advice is simple: do something different just to do something different. Even if it doesn't solve your problem, you will likely get stuck.

I can write code in C, C ++, Python, or any language, but I can't get upset about what I'm doing. I can't feel a challenge. I wrote multithreaded code, HTTPS MITM proxy, and a WSGI application with no special algorithms required.

Don't get this wrong (these are decent accomplishments), but this is hardly a comprehensive list of all of the challenging and exciting problems in programming. There are still many challenging problems to be solved. The hardest problems are working on a scale. You've written a WSGI application, but have you written one that can handle a billion page views per day? You wrote multithreaded code, but you wrote multicomputer code (with hundreds of computers)?

In short, if you want to try doing something that isn't technical, you should give it a try. But don't do this because you feel that you have solved all the problems that need to be solved as it has not.


We use cookies and other tracking technologies to improve your browsing experience on our website, to show you personalized content and targeted ads, to analyze our website traffic, and to understand where our visitors are coming from.

By continuing, you consent to our use of cookies and other tracking technologies and affirm you're at least 16 years old or have consent from a parent or guardian.

You can read details in our Cookie policy and Privacy policy.