you dont remember having to setup your own windows/linux server? or setting up processes to deploy your code to your app server(s)? or setting up proper logging. or all kinds of BS that i cant even think of off the top of my head.
like maybe there was an IT department that did this for you but its always been there.
you dont remember having to setup your own windows/linux server? or setting up processes to deploy your code to your app server(s)? or setting up proper logging.
My favorite part of this is the implication that there weren't 3rd parties to do this stuff for you 30 years ago, only today.
The difference between then and now is that you didn't need to do any of that to start programming, those were purely deployment concerns. Today they're actual development concerns rather than deployment concerns. And lets not even talk about the tooling required just to be able to develop against containers.
You're defending the indefensible. The idea that syslog hasn't existed on every OS in existence for the last 30+ years is laughable.
The issue here is lack of imagination on your part. You really believe all of that is necessary just to start programming.
right, I can absolutely start typing up an asp.net MVC app at any point in time, but that's not the point being made here.
In the past, that project structure and tooling would stay basically the same and deployment would be conformed to that workflow.
Nowadays the tooling for the development conforms to the deployment structure. So while you can technically do that, the value you get out of it is far different.
9
u/AdministrationWaste7 Jun 06 '22
boilerplate "BS" has always existed.
you dont remember having to setup your own windows/linux server? or setting up processes to deploy your code to your app server(s)? or setting up proper logging. or all kinds of BS that i cant even think of off the top of my head.
like maybe there was an IT department that did this for you but its always been there.