4 ms·

This assumes that survival is guaranteed if you do it the right way. Long term thinking can work in firms that are larger. For smaller firms with limited resour

by nafey 6y ago

This assumes that survival is guaranteed if you do it the right way. Long term thinking can work in firms that are larger. For smaller firms with limited resources, motivation and technical expertise getting velocity is crucial. This is one of the reasons startups run into issues when they have to scale. I think it has to be a well thought out balance of speed and quality that is required in such environments.

wokwokwok 6y ago
That's such a straw man, it pains me to even respond to it. Doing it 'quick and dirty right now with the tools I happen to know' instead of 'doing some research, then doing it in a way that is maintainable using standard tools and taking a bit longer' isn't 'endangering the survival of the company', it's professional level practice. Failing to do so is, a) negligent, and b) incompetent. I'm certainly not suggesting the OP isn't competent; they seem on the ball, and maybe serverless is the best choice for them because (insert reasons here)...but I think its fair to say, if you're using your one tool (ie. serverless) for all your tasks, you probably haven't done your due diligence. Specifically in this case, using a standard ETL tool to do ETL type tasks... would probably be suitable. Anyhow; no. Long term thinking isn't what this is about; it's about behaving like a professional when you do a professional job. You pick the label you want to wear as an engineer, because, your practices define you.
- 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 ago
    If 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).

by nafey 6y ago

wokwokwok 6y ago

That's such a straw man, it pains me to even respond to it. Doing it 'quick and dirty right now with the tools I happen to know' instead of 'doing some research, then doing it in a way that is maintainable using standard tools and taking a bit longer' isn't 'endangering the survival of the company', it's professional level practice. Failing to do so is, a) negligent, and b) incompetent. I'm certainly not suggesting the OP isn't competent; they seem on the ball, and maybe serverless is the best choice for them because (insert reasons here)...but I think its fair to say, if you're using your one tool (ie. serverless) for all your tasks, you probably haven't done your due diligence. Specifically in this case, using a standard ETL tool to do ETL type tasks... would probably be suitable. Anyhow; no. Long term thinking isn't what this is about; it's about behaving like a professional when you do a professional job. You pick the label you want to wear as an engineer, because, your practices define you.

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 ago
  If 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).