this post was submitted on 23 Oct 2023
10 points (81.2% liked)
Ask Experienced Devs
1248 readers
1 users here now
Icon base by Delapouite under CC BY 3.0 with modifications to add a gradient
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
IDEs are tools and you should use the tool that works best for you.
IDEs have tons of tools to teach, debug, refactor, generate code, etc. I've worked in projects where any one of those tools is valuable. When I was learning, I found IDEs to be great aids that helped me avoid common pitfall.
IDEs also do have overhead. I've worked on projects where that overhead is so high the IDE isn't a viable tool.
The first thing you should learn as a dev is to stop worrying about what buzz words people apply to different technologies and closely examine the pros and cons of a technology as it relates to your problem set. Create solutions to problems, not solutions in search of a problem. If you can do that, you'll be off to a great start.