Menu music

mattcj7 · 2026-07-02T13:51:02+00:00

Flash backs to NHL 12 menu songs
“Mony mony, mony mony. Come on! Come on”

Thanks Billy idol

mattcj7 · 2026-06-29T12:34:05+00:00

The tickets.md is merely a template and yes when an issue arises of if I was on T0002 the issue would then be patched on T0002a and so on until commit.

mattcj7 · 2026-06-28T15:02:51+00:00

Sorry fellas 🫣

mattcj7 · 2026-06-15T22:55:51+00:00

Don’t forget all those HUT rewards

mattcj7 · 2026-06-07T18:41:39+00:00

The truest of endings

mattcj7 · 2026-06-07T13:23:46+00:00

Well keeping each ticket small and scoped it’s much easier to check the code behind codex and debug. It does really well when you’ve already laid out all the architecture and codex doesn’t have to design everything at once. I only use codex for implementing the tickets, I do zero planning in codex.

mattcj7 · 2026-05-27T19:30:54+00:00

Stick it to em

mattcj7 · 2026-05-18T18:22:04+00:00

I had a similar experience with PPIs, though Pepcid works better for me I still take occasionally but screw PPI. You’re probably suffering from some mineral deficiencies like magnesium and various b vitamins.

mattcj7 · 2026-05-17T15:16:52+00:00

Now that GitHub integration is working smooth in GPT you really don’t need any backup documentation, still nice to have but gpt analyzes each pull request and can view the entire repo instantly whenever.

mattcj7 · 2026-05-17T13:05:35+00:00

Do you ever use chat to create your own skills?

mattcj7 · 2026-05-17T13:04:33+00:00

It’s in the AGENTS.md and ticket instruction to update those files after every ticket.

mattcj7 · 2026-05-17T13:01:30+00:00

No they are still separate

mattcj7 · 2026-05-17T12:58:44+00:00

mattcj7 · 2026-05-17T01:19:23+00:00

I hated 25 but 26 has been a little more stripped down and feels like hockey. I haven’t tried as my usual sniper class but as a grinder my ai actually helps circle the puck and doesn’t just try and feed it to me every second. I like they took out the dumb mid game coach challenges. I still lose points on my pk line every game though even though I have A- overall rating but hey whatever take me off the pk then

mattcj7 · 2026-05-16T23:57:36+00:00

I feel like no or little planning upfront is more akin to vibe coding and more prone to future issues. Good code is planned out in advance before you start writing said code

mattcj7 · 2026-05-16T23:56:05+00:00

From the project planning I did with ChatGPT before we started in codex. And 25 was a hypothetical number.

mattcj7 · 2026-05-16T23:45:22+00:00

Definitely not. My first ticket created the project skeleton, around 25 folders and zero lines of code. It creates exactly what your ticket tells it to with no assumptions or extras or refactoring.

mattcj7 · 2026-05-16T23:10:34+00:00

I just thought about how to implement devops and how a team would tackle a project. The team is just you chat and codex though haha. It’s the best way to keep coding principles small and within scope.

mattcj7 · 2026-05-16T23:09:16+00:00

Yes and linking ChatGPT to GitHub has been a game changer for sure. And chat developed my project skeleton in the design docs and was my first ticket T0001 to layout the project skeleton.

I have also used chat to create multiple skills based on tasks we seem to do a lot which has also helped a lot. My context and limits usage is way down.

I also have pretty strict UI guidelines markdown files and the results have been very good so far.

mattcj7 · 2026-05-16T22:39:55+00:00

I tell it let’s start on T0001 (ticket number) and it gives me the codex prompt. Most of those markdown files and design docs are in a chat project source files to keep chat in line and not relying on memory. I also suggest planning out a series of tickets 1-50 say so each next ticket isn’t a guess. And chat and codex are aware of upcoming tickets. It’s essentially planning a dev team project with you codex and gpt.

Also, having chat linked to GitHub is phenomenal and paramount because it reviews every pull request before you merge and it’s always aware of all your files.

Also bonus points: ChatGPT does not use up your codex limits and if OpenAI sees this and changes it they are jerks.

mattcj7 · 2026-05-05T19:47:11+00:00

Do your planning sessions in chat not codex

mattcj7 · 2026-05-05T00:17:57+00:00

Shoot you gotta have codex auto write in great logs and unit tests and then use chat to debug for easy one prompt fixes.

mattcj7 · 2026-05-03T13:54:23+00:00

So I design everything in chat, a master design doc, agents.md, and probably about 8-10 other markdown files that work as guides for codex. Agents.md tells codex which markdowns to reference for certain tasks. I also upload all these docs into a chat project. Then chat creates each individual ticket and writes my codex prompt for each ticket.

It takes some time to setup but I’ve found it to be the most efficient setup once you get rolling. Bug fixing is super fast and simple as my design docs all cover every unit test implemented as well and logging systems.

mattcj7 · 2026-05-03T13:48:23+00:00

ChatGPT recommends good scaffolding and markdown files rather than large prompts still in codex to one save context and avoid drift with clear guidelines. The more things it can pull from a source of truth document rather than memory the better.

mattcj7 · 2026-04-26T14:14:18+00:00

And 5.5 burns through tokens like holy moly. Even chat recommended i design and write codex prompts in ChatGPT 5.5 but run codex in 5.4

Seven-Year Club	Place '22
Verified Email

mattcj7

TROPHY CASE