via reddit

Comments

Planning work

I'm sure many of you saw this gif in various places recently. There's lots of similarities that are obvious from a software engineering perspective. To me it shows how difficult a re-write really is.

Estimating

“Most people overestimate what they can achieve in a year and underestimate what they can achieve in ten years.”

The same is true for what I can achieve in an afternoon and what I can achieve in a week.

Links

The data in this article was a bit surprising to me. Function instance size doesn't matter and it seems nearly impossible to write a fast starting function if you need a common library like boto3. If your function is >15 MB you're better off packaging it as a container.

Cold Starts in AWS Lambda | Mikhail Shilkov

Selection of languages, instance sizes, dependencies, VPC, and more

This was a thorough write-up of how to reverse engineer a Dockerfile using only the container image. It has been a long time since I've had to do this, and is very helpful to understand how container images work.

I read this book last month and really enjoyed it. I was going to link to the TED talk from the author, but it doesn't do the book justice. My summary is you'll have more good ideas with more diversity in people you hang out with and you should let hunches germinate over long periods of time. Lots of examples in the book for why your companies shouldn't keep R&D research a secret and why working in an office is probably beneficial for innovation.

This is an affiliate link.