3 ms·

Serverless? There are always servers. APIs don't exist in a vacuum or scale magically. If you don't understand how to build what's underneath, then you don't u

Serverless? There are always servers. APIs don't exist in a vacuum or scale magically. If you don't understand how to build what's underneath, then you don't understand what's involved and are at the mercy of vendors or someone else.

manquer 5y ago
By that logic I as AP dev should know systems programming and OS. A systems programmer should know kernel development ? A kernel developer should know assembly and microprocessor architecture? Everybody has at best little or shaky knowledge of underlying abstraction. Yes it helps to know more, but is not really practical to expect that knowledge as the minimum required.
- dilyevsky 5y ago
  Yes you should have at least some knowledge of architectural principles and design of an api layer you directly depend on. How is that not just common sense?
- jackcviers3 5y ago
  Yes. You should know one layer of abstraction below the one you are using. Always. Because everything leaks, and eventually you have to fix it.
deleted 5y ago
[deleted]
derefr 5y ago
I have built what was underneath — and then threw it away, because the managed-services vendor built it better, and the OpEx of paying them to manage it was less than the OpEx of paying myself to maintain it.
- o-__-o 5y ago
  This has been the story repeated over the past 30 years
  - airhead969 5y ago
    Not thirty years. 10-15. IT was a big industry that everyone did up until about 2010.
    - o-__-o 5y ago
      I’ve been involved in IT for over 25 years, I’ve seen a lot :)
- airhead969 5y ago
  It absolutely depends on scale. Smaller teams of better staff can sustain cloud infrastructure, especially if grabbing as many internal needs as possible so as to gather critical mass to make it pay for itself.
borplk 5y ago
Every time someone mentions serverless some smartass feels obligated to mention that "there are servers". Yes we know. It's a specific technical term to refer to category of serverless products like AWS Lambda.

manquer 5y ago

By that logic I as AP dev should know systems programming and OS. A systems programmer should know kernel development ? A kernel developer should know assembly and microprocessor architecture? Everybody has at best little or shaky knowledge of underlying abstraction. Yes it helps to know more, but is not really practical to expect that knowledge as the minimum required.

dilyevsky 5y ago
Yes you should have at least some knowledge of architectural principles and design of an api layer you directly depend on. How is that not just common sense?
jackcviers3 5y ago
Yes. You should know one layer of abstraction below the one you are using. Always. Because everything leaks, and eventually you have to fix it.

deleted 5y ago

[deleted]

derefr 5y ago

I have built what was underneath — and then threw it away, because the managed-services vendor built it better, and the OpEx of paying them to manage it was less than the OpEx of paying myself to maintain it.

o-__-o 5y ago
This has been the story repeated over the past 30 years
- airhead969 5y ago
  Not thirty years. 10-15. IT was a big industry that everyone did up until about 2010.
  - o-__-o 5y ago
    I’ve been involved in IT for over 25 years, I’ve seen a lot :)
airhead969 5y ago
It absolutely depends on scale. Smaller teams of better staff can sustain cloud infrastructure, especially if grabbing as many internal needs as possible so as to gather critical mass to make it pay for itself.

borplk 5y ago

Every time someone mentions serverless some smartass feels obligated to mention that "there are servers". Yes we know. It's a specific technical term to refer to category of serverless products like AWS Lambda.