I have multiple AI services in my recently purchased Jetbrains Junie subscription. Right now I'm using codex for my work. It feels like having a pro developer team of 10 API experts at your service and ready to answer any request on your code base or any complex question right away. I've already taken the back seat and let AI do must of the hard work as per my instructions andrequests.
It's absolutely amazing. I've been professionally doing webdev for 25 years now and never had this competent a colleague, mentor or even senior. I Review every change and submit on my behalf. I do sometimes catch surprisingly human slipups (a few collisions with super-strict property typings, plural and singular naming lapses, etc.) but the AI fixes those instantly when I point them out. AI in turn finds mine too and points them out and asks if it can fix them. The context window lasts the whole project and the suggestions AI makes for next steps and improvements are really good and even inspired. Seriously.
The best part is that I can discuss the more abstract aspects of the app. I swear I have never had this consistency of competences when discussing my work and projects with someone else. I do not need anybody else on my "team" anymore. Not for coding that is. True thing.
Here's an excerpt of my ongoing work discussion with AI ( this is real! ):
>>>>>>>
> Could you explain the reasoning behind implementing a Baseline service? Is this a good practice and if so, why?
> Short version: Yes, itâ(TM)s good practice here because you need the same Baseline metadata (file list + meta.name/type) in multiple places (Baseline routing + Mainview). A service is the cleanest way to share that data without duplicating fetch logic or tightly coupling components.
Why it makes sense:
â Single source of truth: one place to load and cache the list of Baselines.
â Decoupling: Mainview and Baseline donâ(TM)t need to know how to fetch or parse the index.
â Less duplication: avoids copy/paste HTTP logic in every component.
â Easier to evolve: if the index format changes, you update one place.
â Easier to test: you can stub the service.
Downsides:
â Slightly more code and indirection.
â If the data is only ever used in one component, a service would be unnecessary.
Given your setup (routing + entry generation), the service is a good fit. If you want, I can keep it simpler by moving the logic into Mainview and passing data down, but that couples the components more tightly.
If AI pans out only half of what we expect, the world will look very different in a few years time.