Who knows what it is? - wrong answers only
#BuyYourselfSomethingPretty
Who knows what it is? - wrong answers only
#BuyYourselfSomethingPretty
You need the skills to back it up.
AWS often sells the dream of "get certified and you'll be ready to be a solution architect"
People then rote learn the answers and slap it on their CV.
But this fails at interview 👇 🧵
You need the skills to back it up.
AWS often sells the dream of "get certified and you'll be ready to be a solution architect"
People then rote learn the answers and slap it on their CV.
But this fails at interview 👇 🧵
I saw a post suggesting you should never use a reduce function - it's too complicated to understand
- if your engineers can't understand a reduce function, why did you hire them?
- if you want to make your code more readable, use name functions.
I saw a post suggesting you should never use a reduce function - it's too complicated to understand
- if your engineers can't understand a reduce function, why did you hire them?
- if you want to make your code more readable, use name functions.
But there is one thing that most people forget
Developers are EXPENSIVE $$$
Lets say you pay a developer $50/hr
You have a single Lambda that costs $100/month
But there is one thing that most people forget
Developers are EXPENSIVE $$$
Lets say you pay a developer $50/hr
You have a single Lambda that costs $100/month
5 top causes and how to fix them
1. Memory Mismatches = Money Down the Drain
- Over-provisioning RAM? You're burning cash
- Under-provisioning? Less CPU power = slow execution = higher costs
- Fix: Monitor + right-size your Lambdas
5 top causes and how to fix them
1. Memory Mismatches = Money Down the Drain
- Over-provisioning RAM? You're burning cash
- Under-provisioning? Less CPU power = slow execution = higher costs
- Fix: Monitor + right-size your Lambdas
The new job has been intense.
What I'm going to be talking about over the next few months:
- Amazon Connect
- Bedrock / Amazon Q
- startup culture, how we're building our team, the wins and losses.
And of course how Serverless fits into all of this!
The new job has been intense.
What I'm going to be talking about over the next few months:
- Amazon Connect
- Bedrock / Amazon Q
- startup culture, how we're building our team, the wins and losses.
And of course how Serverless fits into all of this!
Lot of ups and downs but here's the key things.
Lot of ups and downs but here's the key things.
Great talks, interesting discussions and some new friends made
#serverless #serverlessdays #rome
Great talks, interesting discussions and some new friends made
#serverless #serverlessdays #rome
Content is one of those areas.
My YouTube channel has had over 4000 unique users watch a video in the last 28 days.
Yet AWS prefer to pump money into meetups and user groups.
Those things are great and super valuable, but they get 30-50 people max per month.
Content is one of those areas.
My YouTube channel has had over 4000 unique users watch a video in the last 28 days.
Yet AWS prefer to pump money into meetups and user groups.
Those things are great and super valuable, but they get 30-50 people max per month.
I'm looking for suggestions for conferences to apply to and talk about AWS and serverless.
Let me know which conferences you are going to in 2025
#aws #serverless
I'm looking for suggestions for conferences to apply to and talk about AWS and serverless.
Let me know which conferences you are going to in 2025
#aws #serverless
Looking forward to catching up Yan Cui
If you're at #reinvent24 and want to catch up, book a chat with me on re:meet
#aws #serverless
Looking forward to catching up Yan Cui
If you're at #reinvent24 and want to catch up, book a chat with me on re:meet
#aws #serverless
- testing different secrets
- adding millions of logs
Then you realise it decrypted perfectly and my own code errored the line after that
#code
- testing different secrets
- adding millions of logs
Then you realise it decrypted perfectly and my own code errored the line after that
#code
You can check out the full listing and register to attend on our site - believeinserverless.com/reinvent
You can check out the full listing and register to attend on our site - believeinserverless.com/reinvent
Believe in Serverless has community talks with some amazing speakers.
Tycko Franklin, @readysetcloud.io, Dave Hall, @focusotter.bsky.social , Khawaja Shams, Greg Olmstead, @ryancormack.bsky.social , @brianleroux.bsky.social and @andmoredev.bsky.social
Believe in Serverless has community talks with some amazing speakers.
Tycko Franklin, @readysetcloud.io, Dave Hall, @focusotter.bsky.social , Khawaja Shams, Greg Olmstead, @ryancormack.bsky.social , @brianleroux.bsky.social and @andmoredev.bsky.social
It's not that hard but would be so much better
It's not that hard but would be so much better
Even the ones you think are smart.
This is what I would tell them:
Even the ones you think are smart.
This is what I would tell them:
Chat & Custom url handles
Chat & Custom url handles
My god is that phone heavy.
Going from my 3a (147g) to this (188g) is craxy.
and it's only 1mm taller and 2mm wider!
Anyone else got it and found it heavy?
My god is that phone heavy.
Going from my 3a (147g) to this (188g) is craxy.
and it's only 1mm taller and 2mm wider!
Anyone else got it and found it heavy?
It took less than a day to build and I think it'll be super useful
It's built using Momento topics but I've not seen anyone else add persistent storage to live chat with it so far.
Video will be coming soon on how I built this whole app!
#aws #serverless #remeet
It took less than a day to build and I think it'll be super useful
It's built using Momento topics but I've not seen anyone else add persistent storage to live chat with it so far.
Video will be coming soon on how I built this whole app!
#aws #serverless #remeet
At lunch I said I would try and build a live chat by the end of the day.
It turns out that 4.5 hours wasn't enough time.
I got the UI and the APIs built, but couldn't get the Momento topics done in time.
At lunch I said I would try and build a live chat by the end of the day.
It turns out that 4.5 hours wasn't enough time.
I got the UI and the APIs built, but couldn't get the Momento topics done in time.
const url = `https:// calendar.google.com/ calendar/render?action=TEMPLATE &dates=202412${date}T${time}00Z%2F202412${date}T${endTime}00Z &details=${description}&location=${venue}&text=${title}`;
Then open the url in a new tab.
const url = `https:// calendar.google.com/ calendar/render?action=TEMPLATE &dates=202412${date}T${time}00Z%2F202412${date}T${endTime}00Z &details=${description}&location=${venue}&text=${title}`;
Then open the url in a new tab.