I'm working on this loan interest calculator, but I'm a little bit stuck because there's multiple ways of coding this, I just feel very sensitive about doing this because struggling to even write "easy" code is a real bad put off.

The question is, once you get used to solving problems, will it always be less stressy? Or is this just a hurdle when your first starting out? I find when your working on small problems and it takes hours to do, this is very stressful, even more so when you know this is supposed to be easy stuff. Is web development a often like this? It seems like something not stressful, but in real life, I imagine it's full of stress. Like fixing a pc, half the time you just want to throw it out the window.

I enjoy the challenge but don't like the stress.

Edited November 23, 20187 yr by NullDrone

6 hours ago, NullDrone said:

I'm working on this loan interest calculator, but I'm a little bit stuck because there's multiple ways of coding this, I just feel very sensitive about doing this because struggling to even write "easy" code is a real bad put off.

The question is, once you get used to solving problems, will it always be less stressy? Or is this just a hurdle when your first starting out? I find when your working on small problems and it takes hours to do, this is very stressful, even more so when you know this is supposed to be easy stuff. Is web development a often like this? It seems like something not stressful, but in real life, I imagine it's full of stress. Like fixing a pc, half the time you just want to throw it out the window.

I enjoy the challenge but don't like the stress.

Web development will always have difficult problems to solve, unless you get to a level and just give up on moving forwards.  If you learn enough to become a junior you can just stay at that level, but you'll never earn much and the projects will get boring.  If you push yourself to continually progress then you're always going to feel somewhat out of your depth.  That's how I felt with every new role I've taken on - the development tasks have got progressively harder.  I'm sure if I somehow went to Google as a principal engineer I'd be well out of my depth.

I think the trick is to make small incremental steps.  What you find hard now will be bread and butter in a year's time.  If you take too big a leap you will struggle and not enjoy things.  Also don't be afraid to ask others.  If I'm faced with a problem that I'm struggling to solve in work that I can't find any answers too I will ask others, a key skill of a developer is ability to collaborate with others, when faced with a particularly difficult story a group of us might mob on a problem.  We might even spike out some ideas just to flesh out what we might do.

You have to be at peace with the fact you will face many problems that you don't immediately know how to solve so you have to use the various tools at your disposal to figure them out.  Also there's nothing wrong with being faced with a problem that is well out of your area of expertise and passing it onto somebody else who works in that area, this is especially common with teams of specialists, no one person is expected to know everything.

On ‎11‎/‎23‎/‎2018 at 7:16 AM, rbrtsmith said:

Web development will always have difficult problems to solve, unless you get to a level and just give up on moving forwards.  If you learn enough to become a junior you can just stay at that level, but you'll never earn much and the projects will get boring.  If you push yourself to continually progress then you're always going to feel somewhat out of your depth.  That's how I felt with every new role I've taken on - the development tasks have got progressively harder.  I'm sure if I somehow went to Google as a principal engineer I'd be well out of my depth.

I think the trick is to make small incremental steps.  What you find hard now will be bread and butter in a year's time.  If you take too big a leap you will struggle and not enjoy things.  Also don't be afraid to ask others.  If I'm faced with a problem that I'm struggling to solve in work that I can't find any answers too I will ask others, a key skill of a developer is ability to collaborate with others, when faced with a particularly difficult story a group of us might mob on a problem.  We might even spike out some ideas just to flesh out what we might do.

You have to be at peace with the fact you will face many problems that you don't immediately know how to solve so you have to use the various tools at your disposal to figure them out.  Also there's nothing wrong with being faced with a problem that is well out of your area of expertise and passing it onto somebody else who works in that area, this is especially common with teams of specialists, no one person is expected to know everything.

Do you find web development a lot of the time knocks your confidence and makes you think you can't do it?

I find the problem i'm having is just simply a lack of confidence, because I'm given a problem, I don't know how to go about solving it, when I make an attempt I feel there must be some standard way of doing it and it really knocks my confidence if I were to search google to solve the problem for me.

I like a challenge, but hate being in a situation of not being able to do it at all, it knocks your confidence, but I take it once you get into this, you eventually learn to accept that eventually you'll find a solution on your own eventually and not to spend too much time on something you just can't do.

I am actually very good at problem solving, but half the time your given a problem that you just have no clue on how to solve and this knocks your confidence. Fear of failure is usually the main problem. For my coursework I didn't have a clue how to solve it, but told myself eventually you find a solution, you just have to give the question/problem a little patience, many times you give up straight away when it's overwhelming.

Then again, I also find that at college the other students had solved problems where I didn't even know where to start or look, half the time your presented with a problem and have no clue, yet the other students have done very well, I think how the hell did they even solve that. I find that when you go for a job usually they give you something where you don't even know where to start. For brute forcing, you have to know what options are available.

Edited November 25, 20187 yr by NullDrone

9 hours ago, NullDrone said:

Do you find web development a lot of the time knocks your confidence and makes you think you can't do it?

No because I am at peace with the fact I will never know the answer to everything.  As I've said before a big part of being a developer is collaborating with others to solve a problem - ask for help!  Yes you should have a good level of knowledge but for many problems you will have to research solutions or ask others.

Often especially at places like Sky you are faced with big features that might take weeks to complete, you have no idea how to build the whole thing so you break it down into smaller chunks and solve them one by one learning as you go.

I think (and I mean this with the greatest respect) that you have confidence issues and learning to code better won't solve those, because the better a developer gets the more they realise actually how little they know.

12 hours ago, NullDrone said:

Do you find web development a lot of the time knocks your confidence and makes you think you can't do it?

I find the problem i'm having is just simply a lack of confidence, because I'm given a problem, I don't know how to go about solving it, when I make an attempt I feel there must be some standard way of doing it and it really knocks my confidence if I were to search google to solve the problem for me.

I like a challenge, but hate being in a situation of not being able to do it at all, it knocks your confidence, but I take it once you get into this, you eventually learn to accept that eventually you'll find a solution on your own eventually and not to spend too much time on something you just can't do.

I am actually very good at problem solving, but half the time your given a problem that you just have no clue on how to solve and this knocks your confidence. Fear of failure is usually the main problem. For my coursework I didn't have a clue how to solve it, but told myself eventually you find a solution, you just have to give the question/problem a little patience, many times you give up straight away when it's overwhelming.

Then again, I also find that at college the other students had solved problems where I didn't even know where to start or look, half the time your presented with a problem and have no clue, yet the other students have done very well, I think how the hell did they even solve that. I find that when you go for a job usually they give you something where you don't even know where to start. For brute forcing, you have to know what options are available.

No one woke up one day and suddenly became a surgeon. Perseverance is a key still in basically every job, if you don't know something, you should be compelled to find a route that will get you to understanding it better, otherwise you might not be as passionate about it as you think.

Edited November 26, 20187 yr by Jack