|
|
|
|
|
by borland
1475 days ago
|
|
This is a terrible idea. Understanding what's "underneath you" in the stack is a critical ability when things get complicated. In my experience, running the stack on your local machine as a developer gives you a huge boost in understanding the stack, being able to profile, inspect, and reconfigure it as needed. Sure, it's quick, convenient and easy if your dev stack is also the cloud stack, because you save time not trying to figure out why localhost mismatches the cloud. BUT, when things get messy, having that understanding of HOW EXACTLY your localhost mismatches the cloud gives you a great depth of knowledge, which you can then use for great benefit in the cloud. Also: remote debug tooling is crap. |
|