I haven't had a long career yet. On the contrary I took a long gap early in my career (quit my job after one year of working at my first company) with no foreseeable plans to return to software development.

Meanwhile while I battle my inner fears of lack of confidence and worth and financial uncertainty, I'm finding it extremely and excruciatingly difficult to find a selfless mentor to guide me to make my first production ready app, not because it's hard, but because I do not know how to ask for help this big.

Even more meanwhile (I'm nesting meanwhiles now 😅), taking advice from JLongster I've started to not attempt to not feel inadequate and spend more time researching before I jump onto making something. The irony of this approach is, as I research I find the lack growing instead of the original expectation that it'd reduce. But hopefully I'll keep on it.

The biggest change in how I develop software in my short career yet has been to survive. I remember the day when we were in the middle of our 6 months training, because we were hired freshers from other backgrounds than computer science or IT. I couldn't keep up with the pace and decided to pack up and leave the first flight that weekend. I did pack my bags but stayed back wondering that giving up is easy for a reason — living up with the consequences of giving up equalises the easiness that came with it, perhaps the other option might be worth it, no matter how much time it'll take.

When i first started developing, i just used to not think much about anything i have had to deal with in future regarding the project and just go with anything i have had thought of for little...

Now as the years been passed, i have been doing proper research about every possible functionality and stack to be used in project, and choose the right one possible, so i don't have to face much issues when managing the project and making changes into it. As we all know , first draft of project is never an end of project , there are going to be huge changes in everything possible that client can make us do. i would keep in mind about stack and way of developing the project and keep in mind about the performance, security, type of users will be using the software so everything created is basically user friendly for that kind of group (not too complex and confusing for them) ...

Even if it takes week to two to me to decide the final stack for the project , i would not mind at all to proper research and take the project from a piece of paper into something functional as i would have decided the possible right stack for it and made the plans for the process and i'm good to go.

But another thing i have noticed is too much of research and being double minded about multiple things , can lead to confusion for our self and make huge mistakes.