A Senior Developer working mostly with PHP and JavaScript, with a bit of Python thrown in for good measure, all on Linux. My tooling is simple, it's GitLab and JetBrains where possible.
I don't think it's that developers are being lazy or unskilled. I think it's more that companies want/need things to market as fast as possible. Time is money, and all that. Spending time building everything from scratch will slow that down, and there's only so much a client will pay for.
That said, if I had the choice, there's a lot of frameworks and libraries I would avoid. Not because they are bad, but because it's another level of technical debt to me managed.
The other side of this, developers use those libraries and frameworks because that's where the jobs are. Why would you avoid all of the tools which are there to help make things quicker, when there are more jobs for people who can use those tools than without?
It's like asking if a carpenter is less skilled because they use a router to inlay designs rather than hammer and chisel. Both get the job done. One just makes it faster and easier.
Which is the points I make in my article. I don't state that by using libraries / frameworks you're unskilled. I was merely saying that by using them and not learning how to do it without them CAN make you unskilled and get left behind when applying for jobs.
Some use frameworks out of reliance, or without thinking about other ways of doing it. So it was more about thinking why you're using a library or framework blindly.
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.
I don't think it's that developers are being lazy or unskilled. I think it's more that companies want/need things to market as fast as possible. Time is money, and all that. Spending time building everything from scratch will slow that down, and there's only so much a client will pay for.
That said, if I had the choice, there's a lot of frameworks and libraries I would avoid. Not because they are bad, but because it's another level of technical debt to me managed.
The other side of this, developers use those libraries and frameworks because that's where the jobs are. Why would you avoid all of the tools which are there to help make things quicker, when there are more jobs for people who can use those tools than without?
It's like asking if a carpenter is less skilled because they use a router to inlay designs rather than hammer and chisel. Both get the job done. One just makes it faster and easier.
Which is the points I make in my article. I don't state that by using libraries / frameworks you're unskilled. I was merely saying that by using them and not learning how to do it without them CAN make you unskilled and get left behind when applying for jobs.
Some use frameworks out of reliance, or without thinking about other ways of doing it. So it was more about thinking why you're using a library or framework blindly.