The US government explicitly recommends 6 memory safe languages:
C# - created by Microsoft
Go - created by Google
Java - created by Sun, bought by Oracle
Rust - create bor Mozilla
Swift - created by Apple
And ...
Python - create by one fucking genius on his own in his Christmas holidays - @gvanrossum.
Python is an extraordinary demonstration of the impact one person (and the group they build) can have on the world.
https://t.co/gCgXC4WV5r
At last, I can break out the news that...
Powertools for AWS Lambda is now an official AWS team!!!!!!!
This secures:
🤩 Long-term project sustainability
🤩 Feature parity across languages
🔥 New home https://t.co/Npa6AJmg9l
🚀 Plan beyond Lambda
1/
#aws#serverless
I’m #hiring !
Check out this job at Evernorth Health Services: Senior Software Engineer (Backend) - Evernorth Health Services - Remote https://t.co/W1XZ8Ia65t
I’m #hiring
Check out this job at Evernorth Health Services: Senior Software Engineer (Full Stack) - Evernorth Health Services - Remote https://t.co/kjCMD2GYzd
@AllenHeltonDev @IsenbergRan @edjgeek@awscloud@AllenHeltonDev @IsenbergRan - great episode!
@IsenbergRan - we’re starting such a team in my org. The decision template which you had mentioned to convince stakeholders is really cool, can you share a sample template that you had used?
Big @pydantic Announcement 🚀
I've just closed a seed round led by @sequoia with @PartechPartners.
Here's the @TechCrunch article!
More info on https://t.co/t3bWAaNGLk
https://t.co/jU7f7fwegy
One of the greatest things to hear from customers is how they’re using AWS Lambda Powertools to accelerate app modernisation, and to more easily go from Prototype to Prod for net-new workloads.
Had a heart-warming conversation with a customer today ;-)
Something that frustrates me is how hard it is to find people who can (1) own a problem domain, (2) execute it, document it, (3) keep people informed about their progress, (4) next steps, and (5) potential partnerships to scale the effort.
Promo-driven work is everywhere
@DRo_604@DRo_604 sorry if I wasn't clear. I'm talking about 'resource policy' here. API gw today in Account-A can invoke Lambda in Account-B just by adding 'lambda:InvokeFunction' for the api gw route in Account-A. If we want to replace lambda with sycn sfn in Account-B, ain't possible
@DRo_604 While I want to make use of the native integrations in step functions with low/no-code solutions. This bottleneck of cross-account invocation for step-functions presents a big challenge to enterprises. So I would like to humbly say 'improve adoption then improve feature sets'
@DRo_604 We need resource invoke policies like how you have for lambdas. Especially if you would like to improve adoption of synchronous step-functions. Many Enterprises including mine, have journey (api-gateway) and application as separate aws accounts.
@heitor_lessa@heitor_lessa that’s great news. I’ve been internally advocating for Powertools in my team as well rather than building something ourselves. How could we get in touch with you for an interview?
After watching 289 talks, I can now confidently share my re:Invent 2022 recap 🕵️♂️
Verdict: I am whelmed. Not underwhelmed or overwhelmed, just whelmed.
Since there were a bunch of other "unboxing" recaps already, here's a thread with an ✨actionable✨ recap.