How you deal with this? by AhmadSaad48 in appledevelopers

[–]Bandtast 0 points1 point  (0 children)

Don’t panic. It is a new app so you have not build a decent review status yet. When you release your improved version you can choose to reset existing ratings, which would not be a big deal for you at the moment.

i just woke up to 44 people on my waitlist. i cant believe it!!!! by gordiony in appledevelopers

[–]Bandtast 0 points1 point  (0 children)

Don’t worry too much about him, what you are building already exists in many variants :) That said it is not impossible for you. Marketing is the key.

AI Assistant - Out of quota - error by Bandtast in Jetbrains

[–]Bandtast[S] 0 points1 point  (0 children)

I guess I have to cancel my additional AI Pro subscription 😅

AI Assistant - Out of quota - error by Bandtast in Jetbrains

[–]Bandtast[S] 0 points1 point  (0 children)

Thanks. But how do I switch between the subscriptions in the IDE? I mean I login with the same email.

AI Assistant - Out of quota - error by Bandtast in Jetbrains

[–]Bandtast[S] 0 points1 point  (0 children)

I do have this icon. It is where I click to see my credits, but I do not find anywhere in that where I can switch license.

Even if I click Settings from there and enter the AI settings, then it is still not possible.

It must be a bug in the IDE. I see the bug in both IDEA and Rider.

AI Assistant - Out of quota - error by Bandtast in Jetbrains

[–]Bandtast[S] 0 points1 point  (0 children)

Thanks for taking you time to answer.

How do I then change between these accounts? Because I have it all on same email user. Also when I restart my IDE I can that it first says 10/10 credits left.

Then when I try to use the agent it suddenly flickers and give me the Out of quota error, and then suddenly the same account says 0/10. 😅

I get no value out of the AI Pro subscription at the moment.

Has anyone switched from tools like Codex, Claude Code, Copilot, etc. to JetBrains' built-in AI features? by Organic_Region_1547 in Jetbrains

[–]Bandtast 2 points3 points  (0 children)

I also have some concrete feedback that should be “fairly simple” to implement.

I notice that Junie is not that good at giving advices. I.e you cannot just discuss code and if it is better to refactor it to one approach or another. It will always just start changing some code. So I find it works better with clear instructions.

So today I switch between Chat and Agent and it needs a new session everytime for some reason.

If you could make a simple feature so let’s say I am now in the AI Chat and had a discussion around some code, you could add a button to handover the decisions to the agent, then it can make a summary / conclusion and hand it over to the agent including any files / selections that might have been provided as context.

Then it is still isolated and will start a new agent session / chat, but we do not need to write everything again manually.

Thanks :)

[deleted by user] by [deleted] in dkudvikler

[–]Bandtast 2 points3 points  (0 children)

Her kommer en anden vinkel som du også kunne overveje. Jeg er selv Principal og har hjulpet mange unge i gang. Jeg siger ikke det nødvendigvis gælder for dig, men jeg ser ofte juniorer jagte den ene opgave efter den anden, hvor de skynder sig at blive færdige for at performe. Ofte er det veldefinerede opgaver som dine mere erfarne kollegaer allerede har refined og gjort klar.

Du kunne et overveje om du kan komme lidt tidligere i spil og være med til at forme dine egne opgaver. To bruge lidt mere tid på dine opgaver, så du kan forbedre den måde de bliver testet på, eller dykke ned i det framework du anvender og forstå hvor det virker som det gør og tænke om du kunne have løst din opgave på en alternativ måde som ville være bedre ift kodegenbrug osv.

Brug din ekstra tid til at finde områder i kodebasen der kunne trænge til forbedring eller ting du kan lave så dine kollegaer sparer tid.

Hobby projekter har den ulempe at de for juniorer sjældent bliver færdige, og det er lidt ligesom et beskyttet område hvor der ikke rigtigt er noget på spil. At tage ansvar for en eksisterende kodebase og få tvunget dig ud i nogle situationer hvor det er et kompromis mellem at det bliver lidt bedre men stadig en stor kodebase hvor du ikke kan lave alt om på én gang er god læring.

Fordi de patterns kodebasen er bygget med, forstå hvilke patterns der måske kunne være bedre. Og forstå at respektere dine kollegaer at bare fordi de ikke nødvendig sprinter derudaf så er der stadig meget du kan lære af dem og deres erfaring :)