3 ms·
There was this one time, I was interviewing for a devops position. They didn't have anyone like that despite growing to a fairly large organization, and ultima
by hosh 4y ago
There was this one time, I was interviewing for a devops position. They didn't have anyone like that despite growing to a fairly large organization, and ultimately, balked on my asking salary. The organization's notion of devops is Heroku, and their notion of scaling is sliding that bar to add more servers.
It can work, though it gets expensive fast.
- deleted 4y ago[deleted]
- pelagicAustral 4y agoWell yes, and I feel like if you're part of a small team, you do want to have much more control over the deployment strategy and implementation, you do want to have ironed-out documentation and perhaps you even want every member of the core team to be able to act in a heartbeat to re/deploy when needed. On the other hand, of you do have the resources, then it is likely that you will have money to pay for the engineers and have an operating devops team. So, yeah, while there is probably some place in the middle of these cases where this abstraction can work I think for the vast majority of software implementations this is merely a solution looking for a problem, and of course, as long as a collective we refuse to address the extreme added complexity brought into the field by the Javascript ecosystem we are never going to eventually find true solutions for any engineering problem.