I’m trying to wrap my head around with the latest “hot thingy”, serverless… While most of my experience has been in the AWS lambda space, I assume it’s not much different in the rest of the ecosystem.
I agree that if you read any of the Hello world tutorials out there, it looks simple. Write 20 lines of code, run this command line, and voila, you have an API. Whoa … Not so fast, buddy. Here’s an (incomplete) list of things you will need to know in order to use it in production: Terraform or CloudFormation, API Gateway…
I’ve been thinking about this for a while.
Maybe we are doing something wrong.
Take the standard log prologue:
02/22/2020 14:05:00 Application started
02/22/2020 14:05:01 Verifying dependencies
02/22/2020 14:05:02 Database and upstreams OK
02/22/2020 14:05:03 Got request from IP:184.108.40.206
02/22/2020 14:05:03 Calling upstream blah, request ID 1
02/22/2020 14:05:04 Got success response for request ID 1
02/22/2020 14:05:05 Responding to caller 220.127.116.11 request ID 1
Now add on top of this structured logging with enriched information.
A few points.
How much of that data is really necessary ?
How often do you read it all ?
Have you ever measured the ratio…
TL;DR Maybe we’re doing something wrong
First of all, let me break the bad news: you are discriminating.
As long as your recruiting ad contains any other words than “I’m looking into hiring a human being”, you are discriminating. Change my mind.
There’s a lot of emulation out there about stopping discrimination in the hiring process, about being an equal-opportunity employer. Which is good. Absolutely great. Nobody should be judged on criteria like skin colour, gender, ethnicity, etc. Everybody deserves a chance. What I find puzzling in this is the fact that most of the “features” used in fight against…
I write code