3 ms·
You are on such a high horse, it pains me to even respond to you. You can call it devops, a mess, whatever you want... but nothing about serverless frameworks
by cheeze 6y ago
You are on such a high horse, it pains me to even respond to you.
You can call it devops, a mess, whatever you want... but nothing about serverless frameworks is creating that mess. A service is a service, whether it's running Lambda, Spring Boot, or whatever the hottest new framework is... Nothing prevents you from documenting a service. Nothing prevents you from creating basic alarms (it's literally easier for me to create these alarms because of CDK than it is to alarm on the standard service framework I use).
We get it, you don't like serverless. But you're going to rag on OP and question their competence, and then drop some "you pick the label you want to wear"? Come on dude, seriously?
You're strawmanning too here... Can you show me where OP said they are using one tool for all of their tasks? they literally said "for one-off, little processes."
I cant imagine what it's like to be this arrogant.
- wokwokwok 6y agoIf you read my comment, you’ll realise that I’m not saying serveless is bad. I’m saying; if that’s your only tool, you’re not doing your job. “Velocity” is not an excuse for not doing your job to a professional degree. Its a strawman people use to justify doing substandard work (or, often, pressuring engineers who know better, into doing substandard work).