Opening an AI panel in your editor feels like cheating until the first bad multi-file rewrite lands in a pull request you cannot explain. IDE assistance is a power tool. From zero, you need the right account, an approved extension, a tiny task, and a habit of reading every diff.
This is Part 1 of the Gemini coding surfaces tutorial (GM22). It pairs with the product map (Code Assist, Android Studio, Antigravity notes) and assumes you already know Gemini is not one single app. Labels and eligibility change; re-check live docs the week you onboard a team.
How IDE assist differs from chat
- How IDE assist differs from chat and from terminal agents
- A from-zero setup path that respects work vs personal accounts
- First tasks that build skill without wrecking the repo
- What “good” looks like in completions and chat-in-IDE
- Safety defaults: secrets, licenses, review
- How Android Studio fits for mobile teams
From zero path
- Confirm personal vs work Google account (company laptop policy wins).
- Install only the approved extension or built-in Studio Gemini feature.
- Open a toy repo or a throwaway branch of a real repo.
- Ask for a one-function change; read the diff; run tests.
- Write a three-line note on what helped and what you rejected.
Gemini coding ide from zero
| Use | Avoid |
|---|---|
| Complete boilerplate you understand | Accepting huge diffs unread |
| Explain unfamiliar code you own | Pasting production secrets into chat |
| Suggest tests you will run | Skipping review because it “looks right” |
| Rename with confirmation | Drive-by dependency adds you cannot justify |
First-week task menu
- Add a unit test for an existing pure function
- Explain a legacy function, then write the explanation in your notes (not only chat)
- Extract a small helper with identical behavior
- Improve an error message without changing control flow
# Human checklist after any AI edit
# 1) Read the full diff
# 2) Run the tests you trust
# 3) Search for new network/file side effects
# 4) Confirm no secrets in logs or source
# 5) Request review if auth, payments, or migrations touchedAndroid Studio note
Mobile teams should train in Studio, not only in generic VS Code demos. Gradle, manifests, and emulator context matter. Start with explain and small UI or test changes. Still own the merge.
Enterprise vs consumer reality
Many consumer IDE paths shifted in mid-2026 toward Antigravity-oriented tooling for Pro/Ultra and free individual tiers, while enterprise Standard/Enterprise Code Assist style licenses often remained on existing paths. If your extension suddenly refuses requests, diagnose edition and deprecation before you blame “the model got dumb.” Details live in GM25 and the product map.
Set up on an approved surface only
- Set up on an approved surface only.
- Complete one tiny task on a feature branch.
- Paste the diff summary into a PR description in your own words.
- List one suggestion you rejected and why.
Three overlapping AI extensions fighting keybindings
- Three overlapping AI extensions fighting keybindings
- Personal account on company code
- No tests run after generation
- Training juniors on autonomy before review culture exists
A squad banned multi-file AI edits until code
A squad banned multi-file AI edits until code owners could explain every accepted line. Throughput rose because review time fell. Another team installed every plugin after a conference and spent a sprint untangling conflicting formatters and secret leaks in chat history.
Ship one small, reviewed change this week using only the habits from this part. Coding AI skills stick when they produce merges you can defend, not when they produce impressive demos you cannot explain.
Ship one small, reviewed change this week using only the habits from this part. Coding AI skills stick when they produce merges you can defend, not when they produce impressive demos you cannot explain.
Ship one small, reviewed change this week using only the habits from this part. Coding AI skills stick when they produce merges you can defend, not when they produce impressive demos you cannot explain.
Ship one small, reviewed change this week using only the habits from this part. Coding AI skills stick when they produce merges you can defend, not when they produce impressive demos you cannot explain.
Ship one small, reviewed change this week using only the habits from this part. Coding AI skills stick when they produce merges you can defend, not when they produce impressive demos you cannot explain.
Ship one small, reviewed change this week using only the habits from this part. Coding AI skills stick when they produce merges you can defend, not when they produce impressive demos you cannot explain.
Ship one small, reviewed change this week using only the habits from this part. Coding AI skills stick when they produce merges you can defend, not when they produce impressive demos you cannot explain.
Ship one small, reviewed change this week using only the habits from this part. Coding AI skills stick when they produce merges you can defend, not when they produce impressive demos you cannot explain.
Ship one small, reviewed change this week using only the habits from this part. Coding AI skills stick when they produce merges you can defend, not when they produce impressive demos you cannot explain.
Ship one small, reviewed change this week using only the habits from this part. Coding AI skills stick when they produce merges you can defend, not when they produce impressive demos you cannot explain.
Ship one small, reviewed change this week using only the habits from this part. Coding AI skills stick when they produce merges you can defend, not when they produce impressive demos you cannot explain.
Ship one small, reviewed change this week using only the habits from this part. Coding AI skills stick when they produce merges you can defend, not when they produce impressive demos you cannot explain.
Ship one small, reviewed change this week using only the habits from this part. Coding AI skills stick when they produce merges you can defend, not when they produce impressive demos you cannot explain.
Ship one small, reviewed change this week using only the habits from this part. Coding AI skills stick when they produce merges you can defend, not when they produce impressive demos you cannot explain.
Ship one small, reviewed change this week using only the habits from this part. Coding AI skills stick when they produce merges you can defend, not when they produce impressive demos you cannot explain.
Ship one small, reviewed change this week using only the habits from this part. Coding AI skills stick when they produce merges you can defend, not when they produce impressive demos you cannot explain.
Ship one small, reviewed change this week using only the habits from this part. Coding AI skills stick when they produce merges you can defend, not when they produce impressive demos you cannot explain.
Ship one small, reviewed change this week using only the habits from this part. Coding AI skills stick when they produce merges you can defend, not when they produce impressive demos you cannot explain.
Ship one small, reviewed change this week using only the habits from this part. Coding AI skills stick when they produce merges you can defend, not when they produce impressive demos you cannot explain.
Ship one small, reviewed change this week using only the habits from this part. Coding AI skills stick when they produce merges you can defend, not when they produce impressive demos you cannot explain.
Ship one small, reviewed change this week using only the habits from this part. Coding AI skills stick when they produce merges you can defend, not when they produce impressive demos you cannot explain.
Ship one small, reviewed change this week using only the habits from this part. Coding AI skills stick when they produce merges you can defend, not when they produce impressive demos you cannot explain.
Ship one small, reviewed change this week using only the habits from this part. Coding AI skills stick when they produce merges you can defend, not when they produce impressive demos you cannot explain.
Ship one small, reviewed change this week using only the habits from this part. Coding AI skills stick when they produce merges you can defend, not when they produce impressive demos you cannot explain.
Ship one small, reviewed change this week using only the habits from this part. Coding AI skills stick when they produce merges you can defend, not when they produce impressive demos you cannot explain.
Ship one small, reviewed change this week using only the habits from this part. Coding AI skills stick when they produce merges you can defend, not when they produce impressive demos you cannot explain.
Ship one small, reviewed change this week using only the habits from this part. Coding AI skills stick when they produce merges you can defend, not when they produce impressive demos you cannot explain.
Ship one small, reviewed change this week using only the habits from this part. Coding AI skills stick when they produce merges you can defend, not when they produce impressive demos you cannot explain.
Ship one small, reviewed change this week using only the habits from this part. Coding AI skills stick when they produce merges you can defend, not when they produce impressive demos you cannot explain.
Ship one small, reviewed change this week using only the habits from this part. Coding AI skills stick when they produce merges you can defend, not when they produce impressive demos you cannot explain.
Ship one small, reviewed change this week using only the habits from this part. Coding AI skills stick when they produce merges you can defend, not when they produce impressive demos you cannot explain.
Account, approval, tiny task, read the diff
- Account, approval, tiny task, read the diff.
- IDE assist is not a license to skip review.
- Next: terminal agents and Antigravity mental model.
Sources
Keep going
Same lessons in your feed
Short diagrams, hooks, and weekly tutorials on Substack, Instagram, X, and Facebook.
Merch on Etsy
Open store →
Naive Bayes Mouse Pad, Data Science Mouse Pad, Analytics Mouse Pad, Bayesian Mouse Pad
View on Etsy →
Y Hat Mouse Pad, Data Science Mouse Pad, Analytics Mouse Pad, Y Pred Mouse Pad
View on Etsy →
SQL Order of Operations Coffee Mug – Data Science Gift
View on Etsy →
Imbalanced Classes Mouse Pad, Data Science Mouse Pad, Analytics Mouse Pad, Imbalanced Mouse Pad
View on Etsy →