Umm actually that was what I tried to do when I started my career but soon I realized I am reinventing the wheel and wasting some of my time doing something that I can just implement by directly importing some library and make a innovative product or tool without reinventing the wheel.
Yes there is still some problems and things that I don't like but since things are open source I can just edit it according to my needs or if I have an better approach I try raising a pull request to that tool or package and help the community because that's one of the things that open-source promotes better tools and products by collaboration.
I am kind of over it now and I use django (which is quite opinionated and follows a battries included approach) and python and my main motive is using tools to build solutions without reinventing the wheel.
I think you should try using them and if possible try contributing so that you can feel the same amount of security with other people's tool as you feel with your own.
Well, it isn't just about that. I don't mean just simple libraries, or anything.
I mean things on the scale of tools like Maven/Gradle. and various programs of a similar caliber.
Unless that could be treated the same in this scenario.
Technically they make the work of a developer simpler and help them in doing so without reinventing the wheel so I would treat them similarly and if you understand the internals or the processes then just try contributing to the parts that you feel isn't good or problematic or atleast raise a issue on the repo so that someone might notice it and try fixing it or you might get clarity on why something is like that and what they considered while doing that or if you can fix it try to raise a pull request after all you are free to ask or contribute.
I have also got replies on repos which explained why something was done in some way and not the other way and most of them reply with atleast some kind of explanation or link to resources. If you don't understand still then you can try asking here and most probably someone would explain you that.
BTW if I am not satisfied with a tool I try looking for alternatives that might have the things or features that I need.
What about IDEs? There's not really any alternatives for that, and to me, they seem too complex.
Yes, people tell me to learn, and I want to, but things like IntelliJ, which I tried just overwhelm me. And they feel overbloated, with no menu organization that makes them beginner friendly, nor do they explain their features.
Is it okay to be upset with an IDE for this reason, or am I making a fuss over a learning curve? Because I honestly don't know what approach I should take to being scared of tools, and programs, etc.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Umm actually that was what I tried to do when I started my career but soon I realized I am reinventing the wheel and wasting some of my time doing something that I can just implement by directly importing some library and make a innovative product or tool without reinventing the wheel.
Yes there is still some problems and things that I don't like but since things are open source I can just edit it according to my needs or if I have an better approach I try raising a pull request to that tool or package and help the community because that's one of the things that open-source promotes better tools and products by collaboration.
I am kind of over it now and I use django (which is quite opinionated and follows a battries included approach) and python and my main motive is using tools to build solutions without reinventing the wheel.
I think you should try using them and if possible try contributing so that you can feel the same amount of security with other people's tool as you feel with your own.
Well, it isn't just about that. I don't mean just simple libraries, or anything.
I mean things on the scale of tools like Maven/Gradle. and various programs of a similar caliber.
Unless that could be treated the same in this scenario.
Technically they make the work of a developer simpler and help them in doing so without reinventing the wheel so I would treat them similarly and if you understand the internals or the processes then just try contributing to the parts that you feel isn't good or problematic or atleast raise a issue on the repo so that someone might notice it and try fixing it or you might get clarity on why something is like that and what they considered while doing that or if you can fix it try to raise a pull request after all you are free to ask or contribute.
I have also got replies on repos which explained why something was done in some way and not the other way and most of them reply with atleast some kind of explanation or link to resources. If you don't understand still then you can try asking here and most probably someone would explain you that.
BTW if I am not satisfied with a tool I try looking for alternatives that might have the things or features that I need.
What about IDEs? There's not really any alternatives for that, and to me, they seem too complex.
Yes, people tell me to learn, and I want to, but things like IntelliJ, which I tried just overwhelm me. And they feel overbloated, with no menu organization that makes them beginner friendly, nor do they explain their features.
Is it okay to be upset with an IDE for this reason, or am I making a fuss over a learning curve? Because I honestly don't know what approach I should take to being scared of tools, and programs, etc.