why is it so hard to use Google's APIs @OfficialLoganK ?
steps:
1⃣ "Get API key" in the docs page → redirects to a different page
2⃣ "Create API key" → asks me to select a project
3⃣ "Select a project" → asks me to create a project
4⃣ Project created → asks me to name the key
5⃣ Name the key → asks me to connect billing account
6⃣ Click on "free tier" → redirects to a different page
7⃣ "Link billing account" → prompts me to fill the form to increase the quota
I saw 4 pages, 7(!) modals and I still can't use the API key.
Then somewhere along the way I also see a prompt to use VertexAI which quadruples the confusion. it's just stupid.
Logan Kilpatrick @OfficialLoganK 3h
I am sorry for the pain on this, we are doing a bunch to address this:
1. We are moving the docs into AI Studio, so you won't need to jump from the docs into AI Studio, it will all be integrated, ETA is Q1 to be fully complete with this.
2. Right now, we auto create projects and keys for new users so they don't need to click anything, it just works. I think the edge case is that it only happens during the account creation flow right now. I pinged the team to make sure we add this for existing users so they will be able to just have a project and key created by default, ETA 2nd week of Jan.
3. Will be fixed by the above, we will also auto select a project going forward, ETA 1st week of Jan.
4. We will auto populate a name for you when you create a new key, ETA 2nd week of Jan.
5 & 6. We are bringing the billing setup process directly into AI Studio, this will make it so we don't have to redirect to the cloud console for you to setup a billing account, ETA for initial rollout is Jan 20th.
7. I will debug this part further, agreed it is super confusing. The issue here is that we limit the number of projects you can add to a single billing account (since this is one of the ways that people commit mass scale abuse / fraud on our platform), let me poke around to see what we can do to make this more simple.
Thank you for the feedback and sorry for the hassle on this. Always more to do!
The current latest Minio release that is working for us for local development is now almost a year old and soon enough we will have to upgrade. Curious what others have replaced it with that is as easy to set up and has a management UI.
I think that's part of the pitch here... swapping out Minio for Garage. Both scale a lot more than for just local development, but local dev certainly seems like a good use-case here.
Graphite isn’t really about code review IMO, it’s actually incredibly useful even if you just use the GitHub PR UI for the actual review. Graphite, its original product anyway, is about managing stacks of dependent pull requests in a sane way.
As someone who uses Cursor, i don't understand why anyone would use CLI AI coding tools as opposed to tools integrated in the IDE. There's so much more flexibility and integration, I feel like I would be much less productive otherwise. And I say this as someone who is fluent in vim in the shell.
Now, would I prefer to use vs code with an extension instead? Yes, in the perfect world. But Cursor makes a better, more cohesive overall product through their vertical integration, and I just did the jump (it's easy to migrate) and can't go back.
I agree. I did most of my work in vim/cli (still often do), but the tight agent integrations in the IDEs are hard to beat. I'm able to see more in cursor (entire diffs), and it shows me all of the terminal output, whereas Claude Code hides things from you by default, by only showing you a few pieces and summaries of what it did. I do prefer to use CC for cli usage though (e.g. using aws cli, Kubernetes, etc). The tab-autocomplete is also excellent.
I also like how cursor is model-agnostic. I prefer codex for first drafts (it's more precise and produces less code), for Claude when less precision or planning is required, and other, faster models when possible.
Also, one of cursor's best features is rollback. I know people have some funky ways to do it in CC with git work trees etc, but it's built into cursor.
Mobile developer here. I historically am an emacs user so am used to living in a terminal shell. My current setup is a split pane terminal with one half running claude and the other running emacs for light editing and magit. I run one per task, managed by git worktrees, so I have a bunch of these terminals going simultaneously at any given time, with a bunch of fish/tmuxinator automation including custom claude commands. I pop over to Xcode if I need to dig further into something.
I’ve tried picking up VSCode several times over the last 6-7 years but it never sticks for me, probably just preference for the tools I’m already used to.
Xcode’s AI integration has not gone well so far. I like being able to choose the best tool for that, rather than a lower common denominator IDE+LLM combination.
Now that I can do a lot with 3-6 AI agents running usefully 2-5min at a time to crank through my plans, the IDE is mostly just taking valuable space
For backend/application code, I find it's instead about focusing on the planning experience, managing multiple agents, and reviewing generated artifacts+PRs. File browsers, source viewers, REPLs, etc don't matter here (verbose, too zoomed-in, not reflecting agent activity, etc), or at best, I'll look at occasionally while the agents do their thing.
It is very easy to open multiple terminals, have them side by side, do different things. It is more natural to invoke agents and let them do their things.
The Claude Code integration with IntelliJ (or any Jetbrains IDE for that matter) is the perfect combination. That is the perfect world to me. An entire company maintaining a fork of VS Code just doesn't compute to me, but its how you sell it to shareholders.
Edit: it looks like you've been breaking the site guidelines quite a bit, unfortunately. Could you please not do that? We end up banning accounts that keep doing it and I don't want to ban you.
I have a pretty firm grip on life and touch plenty of grass both literally and figuratively.
However, when something I care about crashes and burns once in a blue moon, I make sure to put the fire out, at least to make it survive till regular hours. Things I care about can be both business and personal, and nobody bugs me for them.
Maybe we shouldn't make any assumptions about people we don't personally know, while we are at it.
> However, when something I care about crashes and burns once in a blue moon, I make sure to put the fire out, at least to make it survive till regular hours.
You are free what you choose to do with your personal life.
Meanwhile, it is pretty obvious that it's pointless to demand or expect personal sacrifice to maintain unrealistic levels of high-availability in services that are far from critical. I mean, do you honestly believe that these messages you and I are writing are so important to get out that someone must sacrifice their personal time to ensure it is served to the world in this very instant instead of, say, 3 or 6 or 13 hours? Absurd.
It looks like I failed to convey what I've tried to say in the first comment. Let me reiterate one more time.
- I believe dang sees HN as his baby, so *voluntarily* monitors it as a critical infrastructure *for him*.
- I personally like this kind of commitment from people who like their job, however *I don't expect or demand it in any way*.
- I also hope that attention doesn't affect his life. *Especially negatively and/or in a crippling way*.
I don't care whether this site is down for 6 seconds or 6 hours. I just wanted to commend him for liking what he's doing this much. I demand nothing from any service provider I use. Let it be a small, one person operation or dang or Amazon/Google.
I also keep servers up in my daily job, and some are more important than others, but none of them requires me to wake up 5AM to solve a problem (by design). So I don't demand anything from others something which I won't do.
As long as nobody is dying, nobody should stop, drop, and work on something else regardless of time, date and location.
I recently ran into an issue with the Cloudflare API feature that if you want to roll back requires contacting the support team because there's no way to roll it back with the API or GUI. Even when the exact issue was pointed out, it took multiple days to change the setting and to my knowledge there's still no API fix available.
