Skip to main content
7 answers
Asked Viewed 421 times Translate

As someone who is a software developer, what is the most challenging part of the job?

Troubleshooting, making sure your input gives you and the user the output that is desire. Important, people are important, think of yourself as they. Erik Solá
+25 Karma if successful
From: You
To: Friend
Subject: Career question for you

7
Pros
7
0

7 answers


Updated Translate

Dinesh’s Answer

There couple of challenges of software developer, but it's easy to mitigates. The technical challenges are not really problems, they are just challenges and most often fun to deal with. The satisfaction gained by solving a critical problem is immense and long lasting. Here is the details:

Technical challenges are what you normally associate with the core coding aspect of software development. It's learning the languages, the frameworks, the systems and the algorithms. It's dealing with writing quality, maintainable code that can scale to multiple systems that can serve millions of users. It's finding and fixing logical errors, debugging some esoteric minute bug in the code.


Operational challenges are less unique to software development and thus less mentioned but equally if not more difficult to handle. Dealing with management, career advancement and recognition, collaboration with other engineers as well as designers and product managers, and continuous education of both technical and business parts of an organization are all issues that software developers face. As a matter of fact, the emphasis on the pure technical challenges above downplay these operational challenges.

Also, there are some other challenges such as:

  • The requirements are not clearly defined.
  • The requirements are defined by people who don’t understand software.
  • The requirements are clearly defined, but then changed in the middle of development.
  • The requirements are not defined at all.
  • The requirements are defined, but not communicated properly.
  • You’re being forced by management to work on more projects than you have time for.
  • You’re being forced by management to use a certain set of tools even if you know they’re not the right ones for the job.

Hope this will help to your query.

0
Updated Translate

Jerel’s Answer

I'd have a hard time picking a "most" challenging, but here are a few things that I myself find challenging in the job.

It's easy to get lost in the sea of new technologies, frameworks, languages, patterns, etc. This is especially relevant for frontend engineers that do work primarily in the browser. As a developer for 10 years, I've seen and used so many JavaScript frameworks, state management libraries, and programming patterns come and go. Not only is it difficult to keep up with it all, but I find it also difficult to find some restraint. Innovation is exciting and it can be tough to stick with something that may start to feel "old" after a while. That doesn't mean that you can't use the new stuff, but it can be difficult to fight the urge to always be bringing in new stuff.

Finding the "right" solution can be pretty difficult. I can't tell you how many times my team and I have built something that we were excited about and just KNEW the customer would love it, only to get feedback that what we built was confusing or unintuitive. What may work today also may not be sufficient tomorrow. As customer needs grow and evolve, so does the product that you need to build. Sometimes a simple change to the text of a button can be responsible for an explosion of interaction from your customers. This can also take huge chunks of time. While the customer only sees the updated text, there can be many hours that go into deliberation, setting up ways to measure success, etc.

Hope this helps!

0
Updated Translate

Lev’s Answer

You're never done learning. New systems, frameworks, languages, architectures...

0
Updated Translate

Leon’s Answer

One of the most challenging aspects is probably finding an approach to your problem that both works and is efficient. This usually involves coming up with diagrams or planning designs to tackle your problem. For example, if your team is trying to move their services from one cloud service to another, there are a lot of choices to make when it comes to where to move, what infrastructure management tools to utilize, etc. And as others have mentioned, you must constantly learn new technologies, but it's great for your own development :)
0
Updated Translate

Michele’s Answer

Even with 30+ years experience as a developer (oh, dear, am I really that old?! :) -- I still find the most challenging, but also the most rewarding, is staying current on the latest technologies and methods for creating the best solution possible. The goal of always wanting to implement the best solution, is itself, a never-ending challenge, so I would recommend always starting with the simplest approach, get that working with tests to validate correctness, and then start tinkering (refactoring) to make it faster, more elegant, using more of the latest proven methods, as available.

Michele recommends the following next steps:

Start simple.
Don't over-design.
Write tests to give you the confidence that your solution remains correct as you make changes/break things.
0
Updated Translate

Geri’s Answer

One of the biggest challenges is the continuous learning which you have to do to keep your skillset relevant. You are pretty much signing up for a lifetime of learning since there are new frameworks and languages coming out all the time.
0
Updated Translate

Jennifer’s Answer

The biggest challenge can be remembering that delivering VALUE to the END-USER is the GOAL.

Sometimes, programmers can get stuck in the weeds, working on particular solutions, and lose sight of the original intent of the project initiative. The role of Business Analyst is crucial, as a liaison and translator between the developers and the business unit end-users.

0