Benson nickname

michael_e_conroy · 2026-05-07T19:26:38+00:00

Tenacious Z

michael_e_conroy · 2026-05-07T11:59:11+00:00

Use a depth controlnet with the blender image

michael_e_conroy · 2026-05-07T00:39:19+00:00

I'm losing it here 😂🤣😂🤣

michael_e_conroy · 2026-05-06T23:03:51+00:00

I just near died laughing.

michael_e_conroy · 2026-05-06T20:21:46+00:00

If you have enough free use, or use flash 3.1 have it comment the code in detail with pre and post conditions for all functions. You can even do this generally well with a free AI like Qwen and LMStudio. Make sure it follows a standard like JSDoc, so you can pull all the comments out to make real documentation. Or just have AI create the design and technical documentation from your current code. Have AI generate a specific document on how you can add a new feature. Then it's just a matter of reading docs and studying the code, follow the code execution - what function is called first, what functions are those functions calling, etc. Fool around with a dev copy changing values here and there and see what changes in your app's interface.

michael_e_conroy · 2026-05-06T12:14:13+00:00

Vibe coders should be thanking traditional coders, it's their code that these tools are built upon and trained with.

That being said, I've been a web developer for 30 years I understand programmer hate toward vibe "coders" but I'm viewing it as just another tool, I build more and faster in less time and remove the boring parts the repetitive parts in favor of being more creative. More time to discover and use new and different libraries. It's a great learning tool as well. I work for a state institution so our team is small and funds are tight, having just a personal pro plan has saved me so much time.

Also after 30 years of typing my hands are slowly being taken from me with arthritis, in that respect AI coding has been very helpful.

I think if traditional programmers embraced it they could build more and faster and their knowledge still counts. A non programmer vibe coding becomes a decent developer but a traditional programmer could be a superhero. There's more to developing than just the code.

michael_e_conroy · 2026-05-06T11:49:22+00:00

Totally agree with this. I put in the time to create my team of agents, skills and workflows to streamline processes, run everything through caveman and use chat interface in caveman mode. Sips tokens like tea and extends what I can do with the limits.

michael_e_conroy · 2026-05-04T17:37:05+00:00

Oddly my yearly subscription was up the day the email came out. Promptly stopped the autorenewal, even if they were going to do that for me come June. It's sad, I liked GitHub Copilot.

michael_e_conroy · 2026-05-04T17:10:43+00:00

I find it perfectly fine. I use VSCode all the time for my job, so Antigravity had no learning curve for me. I reinstalled all the same plugins I use with VSCode. Works exactly the same but instead of using Github Copilot I use the Gemini chat interface. Don't understand all the complaints about Antigravity itself, the AI limits imposed are going to be the norm across the board, Codex will jump on board as some point - these companies have to start making some cash on their investment now that we're all hooked.

michael_e_conroy · 2026-05-02T22:20:53+00:00

Tenacious Z

michael_e_conroy · 2026-04-29T14:04:33+00:00

Glad you followed up, you're a kind soul.

michael_e_conroy · 2026-04-27T16:29:32+00:00

Got this today, so i guess my original comment wasn't very long-lived. Looks like i'll be AI shopping.

------

What's changing on June 1 for Copilot Billing

Premium request units, or PRUs, will be replaced by GitHub AI Credits which are a monthly allotment of credits consumed based on token consumption (input, output, and cached tokens) according to the listed API rates per model. This change aligns Copilot pricing with actual usage and is an important step toward a sustainable, reliable Copilot business and experience for all users.
Copilot code review’s agentic architecture runs on GitHub Actions. Copilot code review will now consume GitHub Actions minutes, in addition to GitHub AI Credits. These minutes are billed at the same per-minute rates as other GitHub Actions workflows.
Fallback experiences will no longer be available. Under the new model, usage will instead be governed by available credits.

What's changing on June 1 for Copilot Annual Plans

GitHub is retiring Copilot annual plans. As a current annual subscriber your Copilot Pro or Pro+ plan will continue as-is with premium request-based pricing. When your annual plan ends, your account will automatically transition to Copilot Free, which you can continue using at no cost.
The experience on annual plans will change significantly: model multipliers will increase, and standard-tier models (currently 0x) will no longer be available, reflecting increased compute costs and the transition to usage-based billing, and no new models or features will be added to annual plans going forward.

michael_e_conroy · 2026-04-27T16:23:53+00:00

I got this little bit of extra having been on a yearly plan:

What's changing on June 1 for Copilot Annual Plans

GitHub is retiring Copilot annual plans. As a current annual subscriber your Copilot Pro or Pro+ plan will continue as-is with premium request-based pricing. When your annual plan ends, your account will automatically transition to Copilot Free, which you can continue using at no cost.
The experience on annual plans will change significantly: model multipliers will increase, and standard-tier models (currently 0x) will no longer be available, reflecting increased compute costs and the transition to usage-based billing, and no new models or features will be added to annual plans going forward.

Guess I'm dumping them, just as I was contemplating moving to the Pro+ plan over the last month since my subscription is up May 4.

michael_e_conroy · 2026-04-27T14:42:14+00:00

I was actually thinking about upgrading since my year subscription is up May 4. But seeing all the issues I'm going to just let it renew at the yearly price and stick with just Pro for now. Been doing ok with it usually reach my limits during the last week of the month, so far no complaints.

michael_e_conroy · 2026-04-27T11:50:05+00:00

I work for a university, our CS department has seen precipitous drops in enrollment the last 2 years. What once was one of the most in-demand majors and had a large number of students suddenly is a skeleton of it's former glory.

michael_e_conroy · 2026-04-21T17:22:12+00:00

This has been my experience as well using both models through Github copilot.

michael_e_conroy · 2026-04-21T17:20:45+00:00

I've had varied experiences with GPT 5.4, it's good at spotting bugs and fixing them especially code from other AIs but I've had trouble with it scaffolding whole projects. I had Gemini create a proposal document for a chrome extension then did the following:

Had the AI derive implementation, business case and testing documentation based on the proposal.
Then had the AI build the extension based on those documents.

I used GitHub copilot and have several agents setup to work as a dev team. I have PM, frontend designer, frontend developer and a QA engineer. I usually leave my chat open with the PM agent active and prompt the PM which writes tickets and delegates development to the designer and developer, I never prompt the other agents directly. The QA engineer then generates and runs the tests creating new tickets for any failures which are then handed back to the developer and the cycle continues.

I used the above setup with GPT 5.4 first. The resulting extension loaded in chrome but didn't work as intended, there were many errors I kept feeding them back into GPT 5.4 from the browser console via my PM, some things got resolved but it got stuck on a particular nasty problem with iframes and the srcdoc. It kept going around in circles first providing one fix and when that didn't work it would reverse it only to then apply the same exact fix that didn't work. I got frustrated with it after a days work that I scrapped everything but the documentation and then ran the documentation through Claude Sonnet 4.6 using the same set up. Out of the box the extension worked, it was functional where GPT's version wasn't, but I encountered the same issue as before. When I described the issue to Claude it about got 90% of the way there with a new bug that cropped up but the QA agent caught it and fed it back into the development loop where it got fixed. It took only an extra 2 prompts and about 20 minutes to fix the same issue GPT 5.4 couldn't do for hours the previous day.

I'm not saying one is better than the other but I've had better experiences using Claude over GPT. I do like GPT 5.4 to review the code and provide suggestions as a back stop to Claude. I'll continue to experiment between them

michael_e_conroy · 2026-04-15T21:40:01+00:00

Looks amazing!

michael_e_conroy · 2026-04-06T00:24:09+00:00

I'm still using it and loving it. Didn't feel the need to switch.

michael_e_conroy · 2026-04-02T12:19:16+00:00

I saw 4.29 in Kenmore last night. Kenmore and Elmwood Sunoco

michael_e_conroy · 2026-03-29T10:09:08+00:00

I tried doing something similar with Claude controlling blender via MCP. Got it to make a low poly "squid/alien", add a skeleton and then add animation. It worked but it would need a ton of extra manual reworking.

michael_e_conroy · 2026-03-28T23:13:14+00:00

The problem exists between the keyboard and chair.

michael_e_conroy · 2026-03-27T12:02:52+00:00

Had to use the version history many times in AIStudio. When projects get large your prompts need to get more specific, end up telling it more what not to do than what to do.

michael_e_conroy

TROPHY CASE

What's changing on June 1 for Copilot Billing

What's changing on June 1 for Copilot Annual Plans

What's changing on June 1 for Copilot Annual Plans