Good for you - this is the way it should (and for most sane people, does) work. You ignore the tools until you understand what they're automating. One day, you'

Good for you - this is the way it should (and for most sane people, does) work. You ignore the tools until you understand what they're automating. One day, you'll get bored of writing boilerplate and trying to design the best UI by compile/run/repeat, and you'll go back to the tools for their appropriate uses. It's always a benefit to understand exactly what's going on under the hood but I've seen some people take it too far, making this initial "I'm going to understand it properly" benefit into a curmudgeonly handicap^1. "I'm hardcore, I write all my UIs by hand! Those new fangled IDEs with their magic autocomplete - I keep my documentation on 430 sheets of fanfold printout! When I was young, we wrote all our code by hand using ed in Sanskrit, printed it out and hand soldered into hardware using tools we made by smelting our own iron!". They're often right, to a degree - they can still write reasonable programs, and they'll likely have fewer defects than a person who just blindly uses tools. However, they often can't work in teams or adapt rapidly to new developments, and development change times are orders of magnitude above those who both understand the tools and when to use them. 1 - I'm not accusing the author of this problem, but the general tone does set a few alarm bells ringing...