4 ms·

Really, it's funny you say "operational details" in such a dismissive way. Is it possible you're projecting? Ops is vital to launching an app, but it also has

• dkarapetyan 11y ago
  Correct and that is the point. So whenever someone says full-stack they really mean frontend/backend application stuff assuming an infinitely scalable, redundant, fault-tolerant, datastore and compute fabric. The reality is otherwise and I don't see how you can call someone full-stack if they think they can completely ignore the realities of infrastructure. And I forgot security considerations.
• benjiweber 11y ago
  I think we can work much more effectively with ops a core part of the development process. If you spend weeks/months building an app and then launch it and find nobody wanted it then you've just wasted a lot of time and effort. If you spend weeks/months building an app and then discover you can't deploy it in the way you planned because of an operational detail, you're going to incur a lot of rework. How long is it going to take you to get your app into production? If you start right from getting your hello world webapp into a production operations environment, then iterate until you have something you can start testing with users you won't have any of these problems. You will however, have to start considering operations from the start. There's a lot less waste, it's lower risk, but you can't ignore operational concerns as someone else's problem.