I use https://github.com/rimutaka/lambda-debug-proxy to run Lambdas locally while still being part of the AWS pipeline. It eliminates the need to emulate the input/output. That tool is for Rust only, but there is no reason why it can't be ported to other languages.
This is like a drunk ex bursting into your apartment, smashing furniture and demanding that you stop seeing that new boyfriend. Not a winning strategy by any means.
The articles states that it takes approximately 1000 requests to optimize / warm up. I suspect that they had concurrency set at the default 999, so the first 999 requests would spin up new instances.
Does that mean their 15,000 requests were actually 15 requests spread over 1000 instances?
I would love to see their pitch deck with the TAM and that sweet x10000 ROI with their 10% fee! :)
Although they may add value to OSS in the short term by bringing in the $$$ we wouldn't otherwise get, their ultimate purpose as a business is to maximize the return to the shareholders, who are not you or me.
What we really need is more competition in this space to drive the fees down.
Andrew, it would be interesting to hear a bit about the founding story. One question I'd like to ask is how did you acquire the customers in the early days? What was the plan for that and what actually worked?
> NZ manuka honey is now also riven by violent gang crime cashing in on the huge profits. Hive stealing is a thing.
I'd like to see a proof of that. The industry is very consolidated with a few dominant players and a lot of small beekeepers who happened to have manuka on their private land. It went through a boom, prices crashed and most unsavory operators moved on. There may be some opportunistic hive stealing, but that always existed even before manuka was the thing.
"This hunger crisis, experts say, is global and caused by a multitude of factors [...]: the sudden loss in income for countless millions who were already living hand-to-mouth; the collapse in oil prices;"
It's a painful "mistake". Running a marathon is painful. Your legs run out of glycogen after about 30km and all you can think of is "I want to stop".
I'm surprised her mind was sharp enough to pick up the mistake.
Time: 3h 46m, pace: 5:21. That's fast for what is more like a training run. She could probably do solid 5:00 pace in a real competition.
The concept of tracking changes, branches, history & blame are pretty universal across different domains and should apply well.
The smallest unit of change in Git is a line (correct me on that), which doesn't work well with something as simple as a text document. E.g. collaboratively working on a ReadMe file on GitHub is quite cumbersome compared to Google Docs or MS Word.
Git is no more than a versioned file repo for CAD or vector files.
The last 3 paragraphs talk about explore/exploit ratio in bee colonies - most bees "exploit" what others found, small number of bees "explore" new grounds.
We do exactly the same. We exploit in the times of plenty and explore when the going get tough. The same evolutionary forces act on us as a society as on the bees, so it is unfair to say that bees know better than us how to get that ratio right.
Totally. I outsource a lot of my reading choice to others. Would love to follow someone with a similar reading taste. There must be a product for that.
It looks like a load of rubbish. Half the links loop back to that same post. No corroboration, no proof, quoting a source that contradicts the claims made in the post.