“Packaging your Lambda functions as container images enables you to use familiar tooling and take advantage of larger deployment limits.” (via @Pocket) #longreads https://aws.amazon.com/blogs/compute/optimizing-lambda-functions-packaged-as-container-images/
“The core underlying issue is that value for software projects is tricky to measure, but tracking effort is easy.” (via @Pocket) https://pocket.co/xhR8jZ
🦀 🎉
“One reason that I am excited to be joining the team at Amazon is that our scope is very simple: help make Rust the best it can be.” (via @Pocket) https://smallcultfollowing.com/babysteps/blog/2020/12/30/the-more-things-change/
“Looking at the progression of code above, evolving from the first tabular version to the final JSON version, at what point in the transformation did the table stop being code and start becoming configuration?” (via @Pocket) #longreads https://pocket.co/xhR8R3
“Configuration is no less a detail than any other aspect of a software system. Its common second-class citizenship, however, causes it to be accorded less respect and visibility, leading to a high incidence of latent configuration errors.”
“Sorry, I don’t know how to explain it better than that. What I can do instead is talk about some systems design problems and archetypes that repeat, over and over, across multiple fields.”
Systems design explains the world: volume 1(via @Pocket) https://apenwarr.ca/log/20201227
“Why was this meeting so valuable? Well, there were a few reasons.”(via @Pocket) https://leaddev.com/culture-engagement-motivation/gaining-insight-and-preventing-misalignment-without-micromanaging
“Customers do not care or know what happens behind the scenes. They care about your value proposition which is inside your business logic.” (via @Pocket) https://medium.com/galvanize/aws-as-a-framework-9abd2b1f6dc1
“These hidden gems of writing the idea in a structured way and asking people for comments afterward prevents many endless debates.” (via @Pocket) https://candost.blog/how-to-stop-endless-discussions
“I interviewed 17 crossovers on common software misconceptions, how the two worlds relate to each other, whether we can truthfully call what we do engineering, and what the different fields can teach and learn from each other.” (via @Pocket) #longreads https://pocket.co/xhR7ZA
“When we look into these scenarios, a primary reason for the problems is that the engineering organization has neglected to provide developers with an effective working environment.” (via @Pocket) #longreads https://pocket.co/xhR7Sz
“I’d summarize it like this: trad engineers are better at the overall strategic process of making a product, while software engineers are better at the day-to-day process.”
What engineering can teach (and learn from) us • Hillel Wayne https://www.hillelwayne.com/post/crossover-project/what-we-can-learn/
What are your thoughts on generally biased-short estimates being a symptom of partial understanding/specification rather than an intrinsic problem with estimating?
“Strategy is not in the business of razzle-dazzle, it’s in the business of getting to the core of the issues so that the solution becomes simple and obvious.”
Make Boring Plans. https://skamille.medium.com/make-boring-plans-9438ce5cb053
TIL: `The term soft skills was created by the U.S. Army in the late 1960’s. It refers to any skill that does not employ the use of machinery…In 1972, a US Army training manual began the formal usage of the term “soft skills”.`
Skipped ahead only to learn of the 25x programmer and also hiring for “passion” to backfill when senior programmers blow off customer proof-of-concept feature requests.
Teammate 1: “We need to reduce the GC frequency to maintain performance..”
Manager: “Let’s ask the person who liked Grant Green. They’ll drop the funk.”
