DEV Community

Cover image for Hack, Reflect, Look Forward: Building My Portfolio with Google Gemini + Antigravity
Rohan Mirjankar
Rohan Mirjankar

Posted on

Hack, Reflect, Look Forward: Building My Portfolio with Google Gemini + Antigravity

Built with Google Gemini: Writing Challenge

This is a submission for the Built with Google Gemini: Writing Challenge

What I Built with Google Gemini

Instead of building yet another template-based portfolio, I decided to experiment.

I built my personal Portfolio using Google’s Antigravity along with Google Gemini as my thinking partner, debugger, and architecture assistant.

The Problem:

Most student portfolios:

  • Look the same
  • Focus more on design than depth
  • Don’t clearly communicate thinking

I wanted mine to:

  • Show my technical journey (not just projects)
  • Feel modern and interactive
  • Reflect how I think as a developer
  • Be AI-assisted

The Role of Google Gemini

Gemini helped me break the portfolio into meaningful sections instead of randomly stacking components. It felt like having a design-thinking partner on demand. It helped me reason through problems instead of just pasting solutions.
Gemini helped me in three major ways:

1. Architecture Clarity

Before writing code, I asked Gemini to help structure:

  • Hero section narrative
  • Projects showcase logic
  • Skills grouping strategy
  • GitHub integration ideas

2. UI + Microcopy Iteration

I used Gemini to:

  • Refine section headings
  • Improve project descriptions
  • Make my copy sharper and less generic
  • Generate alternative layout ideas

3. Debugging + Refinement

While working with Antigravity, I hit issues around:

  • Component structuring
  • Responsive tweaks
  • State management patterns

Demo

View demo

portfolio

You can explore:

  • My skills and projects
  • GitHub integration
  • Clean responsive UI

What I Learned

1. AI Is a Thinking Tool, Not a Replacement 🚀

  • I realized the quality of output depended on the quality of my thinking.
  • When I asked half-baked questions, I got half-baked answers.
  • When I explained the problem properly — what I tried, what failed, what constraints I had — the responses became much sharper.

2. Prompting Is a Technical Skill ✨

Prompting turned out to be a skill of its own.

  • I learned to break big problems into smaller, focused questions.
  • I requested explanations, not just code, so I could actually understand what was happening.
  • This improved how I solve problems even without AI.

Gemini helped me move faster — but deciding when something was “good enough” was still my responsibility.

Google Gemini Feedback

What Worked Well:

  • Clear explanations when I asked conceptual questions
  • Fast iteration cycles
  • Helped me refine ideas instead of just outputting code
  • Great for restructuring messy thoughts

Where I Hit Friction:

  • Sometimes responses were too high-level
  • Occasionally I had to rephrase prompts for clarity
  • Needed to cross-check certain implementation details

That friction improved my clarity. It forced better thinking.

Let’s keep learning and building 🚀

Top comments (0)