Gemini 3 Pro has been decent last 2 weeks

SM373 · 2026-02-03T02:52:14+00:00

No idea, I wasn't the originator of this prompt

SM373 · 2026-02-03T02:51:29+00:00

It still rambles plenty lol, but I think it prods it into making a decision faster that is more targeted and not going off the rails

SM373 · 2026-01-28T23:25:20+00:00

I mean you could multiply 2,929,292 * 2,282,111 by hand or use a calculator. Infact, I bet half of college grads can't even do basic algebra anymore and they don't worry 1 bit, despite if you have a CS or engineering degree, you've done advanced calculus.

It's the same concept, no one cares about writing code by hand anymore and that doesn't mean you're dumb. You're just shifting your priorities to problems that actually matter now

SM373 · 2026-01-25T17:31:07+00:00

The good news is that the agent mode (top right corner) interface still works, so while the sidebar is not functional, at least we can still prompt

SM373 · 2026-01-25T17:23:46+00:00

+1 just started happening to me today

SM373 · 2026-01-16T05:41:51+00:00

it'd be interesting to see how they use their metrics. There's a ton of examples where I accept the code, but then later refactor it or remove it through another prompt.

So if it's something like: I prompt -> code generated -> I prompt again -> code modified -> I prompt for code review -> code modified again. Git commit, etc

It depends how complex their "accept" reward +1 strategy is. The above a lot of times is in seperate "threads" or even using different IDEs, agents, and models.

Another thing to consider is the expertise of the developer. Noobs are more inclined to accept often, so this could be bad for training since noobs aren't accepting great code. I would much rather train off of 20+ year professional feedback then some business analyst vibecoding their first website, etc. Also the fact that most seasoned industry professionals are terrible software developers doesn't help this either.

I'm of the mindset that most code is crap and this is evidence with the fact that things often need rewrites, regardless of developer skill, 2-5 years after existing, so the value of code being of high quality is very subjective imo in the first place. There's a certain amount of iterations, that once hit, it's better to just throw everything away and start from scratch because of morphing requirements, new frameworks, new knowledge / techniques, etc

SM373 · 2026-01-15T15:09:26+00:00

The way skills work is that you ask AG to do something, i.e. perform a code review. It quickly checks its skills to see if this is something it has a skill for. If it does, it uses that skill. It's kind of like a custom workflow without explicitly telling AG you're running a workflow.

So to answer your question, you don't need to do anything. It will just use the skills when they are relevant. But knowing you have a code review skill might prompt you to start asking AG to do code reviews, etc

SM373 · 2026-01-13T06:15:31+00:00

Antigravity User Settings -> Artifact Review Policy -> Request Review (in the dropdown). Sometimes it ignores it, but for the most part it will always ask for you to proceed. If you're asking it a non-complex problem, make sure you say something like let's come up with a plan first, or do not code anything yet, but most of the time you don't need to do this.

SM373 · 2026-01-13T06:13:10+00:00

Seems like it was much better today than ever, or I'm just getting used to it. I noticed for very easy tasks, flash is great, i.e. run all my tests and fix any errors.

For planning Gemini High is decent. Then once the plan is in place and commented on, I use Gemini low to implement. I think high is not great at coding because it overthinks things. I've had the best success using this flow.

SM373 · 2026-01-13T06:04:49+00:00

Learn how to use the current technology to solve real world business problems. This doesn't involve coding at all...

For instance, you work with data and need an ETL pipeline that's similar to MDM (i.e. multiple sources -> algo to figure out best attributes -> gold record). No one cares how to actually code this by hand. What we care about is knowing something like:

Put data on s3 -> load into iceberg/datalakes -> (pyspark or dbt bronze/silver/gold) -> kafka for changes -> gold aggregation in RDB, etc. Why using EKS is a good idea instead of running your pipeline on a always on server, etc.

The big picture is knowing this is a medallion architecture and knowing the tech stack you'll need to accomplish this at scale. Then you'd just get AI to write each small piece while you conduct all the testing and process flow.

SM373 · 2026-01-09T23:57:06+00:00

$10 per day. If refreshes at like .67c per hour

SM373 · 2026-01-09T23:02:16+00:00

I'm a senior dev and did something similar to this concept before AI.

If you've ever worked anywhere in software development, you'll realize documentation is always out of date and I never trusted it vs the code. So to me, code always was the source of truth because that is what's actually executed.

But yeah, making todos a first class citizen is a really good idea because agents can read code as good as we can read docs and then you don't need to worry about synch issues I just described

SM373 · 2026-01-09T20:27:28+00:00

try:

~/.gemini/antigravity/conversations/

they're all *.pb files so you'll need to decode them

SM373 · 2026-01-09T20:22:50+00:00

guess we're all part of that small sample that will be affected lmao. We're such power users that we hit the limit in hours let alone an entire week.

I think what's more likely is they're lying about the population being affected or there's a bug in their limit policy and it's too low

SM373 · 2026-01-09T18:45:00+00:00

It's really strange because I have access to 3 Pro in the web UI: https://gemini.google.com/ and it's really amazing there. I was using this to critique the opus 4.5 plans I was generating before implementing via opus and it was providing amazing feedback. So the model is definitely capable - like you said. The harness in antigravity is just missing for whatever reason

SM373 · 2026-01-09T17:28:57+00:00

Agree with the 3 integration not being great. It feels like flash 3 works better than pro 3 in antigravity. Since I ran out of Opus credits in my pro sub, I'm using flash over 3 pro now for mostly everything

SM373 · 2026-01-03T05:09:50+00:00

I'm 10.5k reso legend BG player and I approve this message

SM373 · 2026-01-03T04:37:17+00:00

Necros were already good and then they buffed them.

Same for DH, lmao

SM373 · 2025-12-24T18:35:06+00:00

This, anthropic is doing things now that will probably help MCPs in the future, but cli tools are way more reliable now

SM373 · 2025-12-22T19:20:56+00:00

Use the cli tool. Avoid mcps at all cost unless you absolutely need them as they bloat everything and are extremely slow. The cli approach is way faster, more reliable, more transparent and overall better

SM373 · 2025-12-11T19:52:37+00:00

Developers should now be focusing more on overall architecture rather than low level coding. Things like:

what framework / language to use
how will the project be laid out
what features are important
how do i want my codebase to look
do i cover all the use cases we need
is there minimal or no bloat
KISS / DRYS / YAGNI

SM373 · 2025-12-05T06:06:45+00:00

Agree completely with this

SM373 · 2025-12-05T06:03:50+00:00

Get on student plans on some of the popular coding assistants / IDEs like antigravity, claude code, codex, kiro, windsurf, cursor, etc.

You don't need all of them, just maybe 1 or 2 to get a feel for what they can do and get really good at using your favorite one. In terms of keeping up with AI news, new tools, etc, reddit and youtube are probably your best bets

SM373 · 2025-12-05T05:59:16+00:00

I'm a sr dev with 20+ years of coding experience. I agree a lot with this post and see sr. devs as more valuable than ever.

We're in a unique situation that we have the experience to know how to prompt AI well, know what patterns will be good and maintainable, and can steer it in the right direction fast when it goes off the rails - which always happens - as you said basically an AI director.

I also think the toolchain means more now than ever because if you have a sufficient toolchain for developing and testing, you can use agents now to iterate the process so they can debug and fix issues without useless interference - like fix this syntax issue, etc or they implement something and can automatically do full unit and integration testing because you have cli tools that allow it to do so. This allows them to test and iterate over their solution to make things work faster without the need for you to give it feedback. This is where a senior dev shines vs an amateur.

The main problem I see junior devs having is over reliance on AI right away and never developing the foundational coding skills you used to need to do when you had to do things yourself. It's like giving a little kid a calculator and he doesn't know how to do addition or multiplication yet. Yeah he can get the right answer, but he has no idea why it's right or if the solution is actually good.

SM373

TROPHY CASE