the resale market for disk has been on a downtrend for years, you can sign into someone's else psn account too and share games, you are a washed up gamer, its okay I am washed up too.
it just a higher level of abstraction but not high enough that it replaces developers, I don't think the LLMs are even capable of reaching that level. Saying the creative process is gone is laughable. A lot of people make these claims and only have an internal tool that no one uses to show for it.
I built a "simple" storage application recently, uploading large files from a phone is not trivial, you can't just command Claude to do it without giving it good context.
This truly shows how king making in venture capital is done, kids have the MIT pedigree but sometimes this is not enough for certain demographics, give them a ton of money to explore ideas and pivot, product is a vscode fork that sells subsidized AI, only possible with venture capital. Providing inference at unsustainable rate deemed as "product market fit". Product loses money until they exit.
VCs that say "I always knew the team was special", give me a break.
I can use Gemini 3 Flash with the harness I built for around 8 years and still not exceed the cost of a Mac Studio with 128GB, the price for privacy is very high. Agentic flows that get stuck can be worked around but I prefer developer velocity.
For corporate use, if the corporation would break the law sending anything to the open internet or to the US, then you can't use any model that's not hosted in house. And there are many such cases.
Sure, but Gemini subscription gives you just that - Gemini subscription, but new computer allows you to do other stuff with it as well. When you're upgrading anyway for other reasons then it's not fair to compare full Studio price to just one subscription.
I use Gemini 3 Flash, I've seen the Claude Code setups, bullish on Anthropic people are driving up tokens but I am able to produce outcomes with a fraction of the money.
Do you mind sharing your workflow? What do you mean by fraction of the money, in my case personally, I'm yet to reach a session limit on the subscription plan. I'm not "tokenmaxxing" as they say, so hard to see a scenario in which the plan is expensive for the value I get.
If you don't hit a limit running Opus, it means you are very much in the loop.
For example you probably don't have days where you ask Opus to review your whole code base and look for code duplication/technical debt/robustness issues, and then to fix some of the found issues, and do this 3-5 times until no big issues are found anymore.
What’s your prompt for this, the way you described it made it seem like there’s a generalizable way I can go about this. I just rely on a testing pipeline instead so can’t think of why I would need to proactively find holes where tests haven’t already done that for me.
I use similar workflow. Here is my refactoring and code quality prompt that I regularly run:
Perform a thorough analysis of the <project_name> project (the code and the documentation).
- Explore the project, go over all important files one by one and look for any mistakes or possible bugs.
- Look for refactoring opportunities and ways to improve code quality and organization.
- Identify any potential cruft/bloat, to ensure our code is clean and logically laid out. Keep in mind that efficient and good quality code needs to avoid over-engineered constructs and needless complexity. Avoid complicated logic where simple solutions would be more elegant.
- Pay attention to comments: There should be enough of them to document the intent and provide high-level overview of the code logic, but not too much; avoid/remove excessive comments that simply restate the code logic or do not provide any useful information.
- Every important function should have a top-level docstring comment that clearly explains its purpose, high-level logic overview, arguments, and return values.
- Analyze the names of constants/variables/functions/classes and other code elements: could some of them be renamed to make their purpose more clear?
- Analyze the documentation, uncover any potential inaccuracies/omissions and ensure the docs reflect the code.
- Brainstorm ideas for improvements of the code and docs.
After you finish the analysis, save an analysis report into "<project_name>_analysis_report.md" in the project root folder.
tests will not find inconsistent naming, duplicate functions, scenarios you have not thought about testing
I use quite plain prompts, nothing fancy:
> go over the tests and do a code review, focusing on how well they test inventory management, planner and controller. maybe some tests need to be deleted, maybe other tests need to be added. the end goal should be good coverage of the core features.
> do a code review, focusing on robustness/correctness issues. validate that the code correctly implements specification.md. focus on the async client.
> there was a big refactor. please do a code review, focusing on eliminating tech debt. look for unused, obsolete or duplicate code that can be removed, look for mismatched interfaces, inconsistent function/argument/variable names. do not output what is correct, just the issues you found. for each issue output instructions for a coding agent on how to fix it. do not nitpick.
I spend around $20 a month through API fees using my own harness, https://slidebits.com/isogen. Nothing too special, I prompt it produces file changes using grep and vector search and I can individually accept which files.
For comparison someone showed me an internal company tool he was working on. He had Claude agents dangerously skipping permissions and firing up github branches through a vm sandbox just to make a single feature change. One agent to code and the other to review.
well 2026 is easily the most software I shipped so AI is definitely making the process faster. Sad if you with agree with the post, I'm outlier though AI has enabled me to build several subscription apps that was able to make money, not a lot but it will compound trust me.
I was able to release two new iOS apps including a game, and a cross desktop application just this year. I refuse to go back to writing code by hand. If it doesn't help your productivity that's okay, ignoring how productive it has made developers like myself is a choice.
AI was also able to help me create my first subscription payment workflow.
It is like farming without Roundup, less crops, more energy, less toxic chemical risks.
I don't think it surprisingly easy at all unless you are running multiple background tasks overnight, I think Gemini will eventually be the default agentic coding agent in the future when it comes to price and efficiency because its backed by sound money.
I don't use the Claude Code harness, grep instead of using a combination of vector search is super expensive and not sure how their read file implementation is. I built my own harness for example that restrict reads and writes in a token efficient manner. Building your own harness will always be the cheapest option in the long run.
I am an early Gemini daily driver type engineer, feels like Node, Firefox, React and Tailwind all over again, Claude Sonnet is 10x more expensive, quick thought experiment do you think 10 Gemini prompts is needed to match the quality of one Claude Code prompt? The harness around Gemini is an issue but I built my own (in Rust)
Not a trivial thing to vibe code without any domain expertise but this project took me under 2 weeks with a AI coding agent harness I built myself. I use Gemini 3 Flash as my main driver as well.
