In my mind, it's not so much the knowledge or tools that separates the two groups as it is the process. Do you have a thorough assessment/validation system? Do you consciously know what the risks and possible failure modes in your systems are? What are the fallback systems, and have you formally thought of what should and will happen when those fail? Is your code reviewed by someone other than its author? Is your code maintainable and understandable for others? What records from construction and production are you keeping and why?
You can do engineering in basic VBScript and you can do hacks in horrible but algorithmically amazing C++.
A lot of this effort doesn't make sense in a casual web environment. If you're building an app with ads aiming to flip in a couple of years - or even to run it as lifestyle - you might not be very troubled when one of your features has a glitch and you don't necessarily have to have planned for HE.net going down or looked for Django exploits. There isn't anything necessarily wrong with that, it's just not engineering.
Now you know the pain of legit engineers who share their title with Java cargo-culters and Rails bros.