Gemini 2.5 Pro vs. Claude 3.7 Sonnet: Coding Comparison

(composio.dev)

483 points mraniki | 1 comments | 31 Mar 25 12:09 UTC | HN request time: 0.212s | source

Show context

raffkede ◴[31 Mar 25 17:30 UTC] No.43537515[source]▶

I had huge success letting Gemini 2.5 oneshot whole codebases in a single text file format and then split it up with a script. It's putting in work for like 5 minutes and spits out a working codebase, I also asked it to show of a little bit and it almost one shotted a java cloud service to generate pdf invoices from API calls, (made some minor mistakes but after feeding them back it fixed them)

I basically use two scripts one to flatten the whole codebase into one text file and one to split it, give it a shot it's amazing...

replies(2): >>43537589 #>>43539405 #

archeantus ◴[31 Mar 25 17:37 UTC] No.43537589[source]▶

>>43537515 #

Can you please expound on this? You’re using this approach to turn an existing codebase into a single file and then asking Gemini to make changes/enhancements? Does it also handle breaking the files back out? Would love more info!

replies(2): >>43537797 #>>43537938 #

1. ZeroTalent ◴[31 Mar 25 18:11 UTC] No.43537938[source]▶

>>43537589 #

There is a better way that I'm using:

1. Cursor Pro with Sonnet to implement things the Cursor way.

2. Install the Gemini Code extension in Cursor.

3. Install the Gemini Coder Connector Chrome extension: https://chromewebstore.google.com/detail/gemini-coder-connec...

4. Get the free aistudio.google.com Gemini API and connect the extensions.

5. Feed your codebase or select files via the Cursor extension and get the implementation from aistudio.google.com.

I prefer having Sonnet implement it via Cursor rather than Gemini because it can automatically go through all the linting/testing loops without my extra input, run the server, and check if there are no errors.

↑