Used Natively in three mock interviews this week. It listens and suggests what to say.
5,000 views
Your month of Ultra
From Natively · now
Your key is inside. It works for 30 days.
A query that was fast last month now takes four seconds. Where do you start?
I'd start with the query plan. Run EXPLAIN on it and see whether it has fallen back to a full table scan, because usually the table has grown past the point where a missing index stopped being free. Then I'd check how much it reads against how much it returns. If the page shows twenty rows and the query reads a hundred thousand, the fix is the query, not the hardware. I'd only look at caching once the query itself is right.
How I prep for technical interviews now
Practised my behavioral answers with it all weekend. Honest review below.
5,000 viewsUsed Natively in three mock interviews this week. It listens and suggests what to say.
5,000 viewsYour month of Ultra
From Natively · now
Your key is inside. It works for 30 days.
A query that was fast last month now takes four seconds. Where do you start?
I'd start with the query plan. Run EXPLAIN on it and see whether it has fallen back to a full table scan, because usually the table has grown past the point where a missing index stopped being free. Then I'd check how much it reads against how much it returns. If the page shows twenty rows and the query reads a hundred thousand, the fix is the query, not the hardware. I'd only look at caching once the query itself is right.
How I prep for technical interviews now
Practised my behavioral answers with it all weekend. Honest review below.
5,000 viewsA query that was fast last month now takes four seconds. Where do you start?
I'd start with the query plan. Run EXPLAIN on it and see whether it has fallen back to a full table scan, because usually the table has grown past the point where a missing index stopped being free. Then I'd check how much it reads against how much it returns. If the page shows twenty rows and the query reads a hundred thousand, the fix is the query, not the hardware. I'd only look at caching once the query itself is right.
Natively answered this live in my mock interview
The overlay only I can see. My notes were ready when the call ended.
5,000 viewsA query that was fast last month now takes four seconds. Where do you start?
I'd start with the query plan. Run EXPLAIN on it and see whether it has fallen back to a full table scan, because usually the table has grown past the point where a missing index stopped being free. Then I'd check how much it reads against how much it returns. If the page shows twenty rows and the query reads a hundred thousand, the fix is the query, not the hardware. I'd only look at caching once the query itself is right.
Natively answered this live in my mock interview
The overlay only I can see. My notes were ready when the call ended.
5,000 viewsFree on your own keys. Here it is answering a system design question live:
viewsA query that was fast last month now takes four seconds. Where do you start?
I'd start with the query plan. Run EXPLAIN on it and see whether it has fallen back to a full table scan, because usually the table has grown past the point where a missing index stopped being free. Then I'd check how much it reads against how much it returns. If the page shows twenty rows and the query reads a hundred thousand, the fix is the query, not the hardware. I'd only look at caching once the query itself is right.
How I prep for technical interviews now
Your month of Ultra
From Natively · now
Your key is inside. It works for 30 days.
Free on your own keys. Here it is answering a system design question live:
viewsA query that was fast last month now takes four seconds. Where do you start?
I'd start with the query plan. Run EXPLAIN on it and see whether it has fallen back to a full table scan, because usually the table has grown past the point where a missing index stopped being free. Then I'd check how much it reads against how much it returns. If the page shows twenty rows and the query reads a hundred thousand, the fix is the query, not the hardware. I'd only look at caching once the query itself is right.
How I prep for technical interviews now
Your month of Ultra
From Natively · now
Your key is inside. It works for 30 days.
Tried it on a sales call. The notes were ready before I closed the tab.
5,000 viewsA query that was fast last month now takes four seconds. Where do you start?
I'd start with the query plan. Run EXPLAIN on it and see whether it has fallen back to a full table scan, because usually the table has grown past the point where a missing index stopped being free. Then I'd check how much it reads against how much it returns. If the page shows twenty rows and the query reads a hundred thousand, the fix is the query, not the hardware. I'd only look at caching once the query itself is right.
Natively answered this live in my mock interview
My setup for technical interviews this year, and why Natively is in it.
viewsTried it on a sales call. The notes were ready before I closed the tab.
5,000 viewsA query that was fast last month now takes four seconds. Where do you start?
I'd start with the query plan. Run EXPLAIN on it and see whether it has fallen back to a full table scan, because usually the table has grown past the point where a missing index stopped being free. Then I'd check how much it reads against how much it returns. If the page shows twenty rows and the query reads a hundred thousand, the fix is the query, not the hardware. I'd only look at caching once the query itself is right.
Natively answered this live in my mock interview
My setup for technical interviews this year, and why Natively is in it.
viewsA query that was fast last month now takes four seconds. Where do you start?
I'd start with the query plan. Run EXPLAIN on it and see whether it has fallen back to a full table scan, because usually the table has grown past the point where a missing index stopped being free. Then I'd check how much it reads against how much it returns. If the page shows twenty rows and the query reads a hundred thousand, the fix is the query, not the hardware. I'd only look at caching once the query itself is right.
Natively answered this live in my mock interview
Used Natively in three mock interviews this week. It listens and suggests what to say.
5,000 viewsYour month of Ultra
From Natively · now
Your key is inside. It works for 30 days.
A query that was fast last month now takes four seconds. Where do you start?
I'd start with the query plan. Run EXPLAIN on it and see whether it has fallen back to a full table scan, because usually the table has grown past the point where a missing index stopped being free. Then I'd check how much it reads against how much it returns. If the page shows twenty rows and the query reads a hundred thousand, the fix is the query, not the hardware. I'd only look at caching once the query itself is right.
Natively answered this live in my mock interview
Used Natively in three mock interviews this week. It listens and suggests what to say.
5,000 viewsYour month of Ultra
From Natively · now
Your key is inside. It works for 30 days.
Free on your own keys. Here it is answering a system design question live:
viewsA query that was fast last month now takes four seconds. Where do you start?
I'd start with the query plan. Run EXPLAIN on it and see whether it has fallen back to a full table scan, because usually the table has grown past the point where a missing index stopped being free. Then I'd check how much it reads against how much it returns. If the page shows twenty rows and the query reads a hundred thousand, the fix is the query, not the hardware. I'd only look at caching once the query itself is right.
How I prep for technical interviews now
Free on your own keys. Here it is answering a system design question live:
viewsA query that was fast last month now takes four seconds. Where do you start?
I'd start with the query plan. Run EXPLAIN on it and see whether it has fallen back to a full table scan, because usually the table has grown past the point where a missing index stopped being free. Then I'd check how much it reads against how much it returns. If the page shows twenty rows and the query reads a hundred thousand, the fix is the query, not the hardware. I'd only look at caching once the query itself is right.
How I prep for technical interviews now
Post about Natively,
get a month of Ultra
Share Natively anywhere public, in your own words: a thread, a review, a video. When it reaches 5,000 views, our biggest plan is yours for a month, free.
One post, one month
No follower count and no niche. If one public post about Natively reaches the bar, you get Ultra.
Post
Natively answered this live in my mock interview. Here's how:
A query that was fast last month now takes four seconds. Where do you start?
I'd start with the query plan. Run EXPLAIN on it and see whether it has fallen back to a full table scan, because usually the table has grown past the point where a missing index stopped being free. Then I'd check how much it reads against how much it returns. If the page shows twenty rows and the query reads a hundred thousand, the fix is the query, not the hardware. I'd only look at caching once the query itself is right.
Reach 5,000
Views
0
Get Ultra
Your month of Ultra
From Natively
Paste it in Settings, Plans & Billing
Ultra · 30 daysPast 5,000?
Send every link at once.
Put all your posts in one go, up to 10. You can send once a day, so a second batch waits until tomorrow.
- Read by a person, not a bot
- An answer by email within a few days
- Nothing to pay, ever
The rules
Hover a rule, or tap it, to read it in full.
Every claim is read by a person.
A month of Ultra,
on us
Ultra is our biggest plan, for continuous recording and the heaviest daily use. We run everything, so there is nothing to set up and no keys of your own. See every plan.
Ultra
HEAVY USERSFor continuous recording and the heaviest daily usage.
$0$35for 30 days
Then it simply stops. Nothing is charged.
Send your links- Maximum AI usage, all day
- Continuous recording & transcription
- Maximum web searches
For one public post that reaches 5,000 views. One free month per person.
