Olden_Dev

Back in the 1980s: I put my first BASIC command in my TRS80 Model 4P (still have it and it works). I was hooked. Now my company delivers business solutions. Fun

[Olden_Dev @OldenDev]

Update on the project comparison (created a "timekeeping" app attempted in a simultaneous one-shot session with Claude Code Opus4.6 and GPT5.4): I hope this is helpful. I think immediately a clear winner emerged. Give feedback and let me know if I left something out. I gave the exact instructions with identical plans (created by Grok for fairness) to both models. Here's what happened:
-Both finished the first pass in about the same time, within a few minutes about 40 min total. GPT produced in stages so a little more time 20 min was required notes below.
-GPT produced a "initial MVP" purely for viewing and did this several times. Rather than delivering every step at once, GPT allowed confirmation at several steps. I like this approach. Catch errors in stages. Took extra time, but it was welcomed.
-The first pass was more complete from Claude, but not everything worked refactoring required on most of the windows, especially errors involving CRUD operations. I had to request refactoring several times, still trying to resolve CRUD issues. Not resolved.
-I actually liked the frontend GPT5.4 generated, it's actually very pleasing to use.
-Claude had several parts that did not include add, edit or delete options. I could not add team or clients. After the "Add" buttons were included, they did not work.
-Tried to enter a new client in Claude, it would not add. It froze, then the record did not add, same for projects.
-GPT5.4 is building everything in steps and requests checks as we go along, I kind of like this feature. So far everything is working but the next phase is the CRUD, where problems are usually found. Essentially no errors.

Summary with winners (sorry not in a table):
Frontend design: GPT
Fully functioning: GPT (after stepping through phased output), everything worked no issues
CRUD: GPT, Claude is still not ready, taking several passes and still does not work. I'm not going to keep trying.
Fields included: GPT was much more thorough with all the fields as specified in the design plan. Claude took the minimal approach, left fields out.
Followed the design: GPT, I'm still checking this, but appears every design element was followed. Claude omitted many items.
Code review: Tie - this was done at a high level but the code seemed cogent without strange patterns, linting was self checked by both, and no problems were found (not the best analysis, but fine for purposes here).
Token use: Claude 45k, GPT recorded zero tokens, this has to be configured up front and I didn't do this. Apologies on this, as mentioned I have the max subscriptions on everything so I usually don't pay attention to the costs, unless I hit a wall, which we rarely do.

Winner analysis
Here's my assessment. GPT5.4 clearly won this one. It followed the design, gave steps for checking and after adding CRUD operations everything worked without error. Plus the frontend design is so pleasing and easy to work with in GPT. I would actually enjoy working in the GPT app and I might end up using this internally. Not sure about making it a product offering though. I'm a huge general Claude fan, I use it for many things, but Claude Code (CLI) needs work. I think Opus 4.6 is smart enough, but for some reason it does not produce rock-solid out of the gate. This has happened with several projects.

Screen shots:
Claude's first pass (the plain looking one), and GPT's first pass (the fancier looking window); followed by GPTs project entry window followed by Claude project entry window. I'm not sure how the images will show, but GPTs windows have much more verbiage and has the very light tan background. Claude images are black and white.

[Olden_Dev @OldenDev]

I'm testing Grok Build with a new project. I'm not a huge fan of CLI, but it's powerful and in this case Grok is doing a great job so far. Super fast at this point. I'll report more as progress is made.

[Olden_Dev @OldenDev]

@SenWarren Elon is inspiring. Us producers in society want to be able to achieve a small portion of what he has done. A wealth tax is a terrible idea. Please don't do this.

[Olden_Dev @OldenDev]

So a very large customer says "hey we cannot find this functionality out there, can you build it???". Of course I said "yes". How could I say "no" to my new project addiction. But this one already has a need!

[Olden_Dev @OldenDev]

@icanvardar Agreed. All hype.

[Olden_Dev @OldenDev]

@ApexSeeker_ When you start doubting things. That's when you start adulthood.

[Olden_Dev @OldenDev]

@vxunderground Hype hype hype.

[Olden_Dev @OldenDev]

@tuuu28283 Yes! Delicious!

[Olden_Dev @OldenDev]

Building a nice specialty software for scheduling/timekeeping for first responders using GPT5.5 (med). The model has performed perfectly.

I've asked the team to try to estimate the time savings and they estimate about 75% to 80% time savings for coding, maybe 25% unit testing time savings. No real savings in code review and UI design. The last two parts cannot be omitted.

[Olden_Dev @OldenDev]

@ewarren Really government needs to stay out of it. The market will keep things real. Closing loopholes only makes the businesses create workarounds. They don't really work.

[Olden_Dev @OldenDev]

@DaveShapi We have not experienced that, yet. 5.6 will be amazing I bet, and with maybe just a little hype and fanfare (like this will be the most dangerous thing ever released in the history of the world , kind of hype).

[Olden_Dev @OldenDev]

@Prathkum I agree. I rarely get hallucinations any more. It used to happen quite regularly.

[Olden_Dev @OldenDev]

@PaulGugAI Yes I agree! Sometimes I use "High" but I don't really see much difference.

[Olden_Dev @OldenDev]

Already up and Codex (GPT5.5 medium) is running through "slices" 99% of the time without error. This is great. It still needs SWE interaction and testing/code checks, but I think over all it saves about 60% in coding time. That's significant in terms of delivery time, NOT employee replacement time.

[Olden_Dev @OldenDev]

@JustinThomasAI @sweatystartup This is a great assessment of the situation!

[Olden_Dev @OldenDev]

@RohdeAli Probably working harder but way more productive.

[Olden_Dev @OldenDev]

Had a customer tell me they decided to create their entire accounting system and warehousing system using AI. I told them best of luck, it's not as easy as it might seem especially with very complex requirements. We will see if they can pull it off. We will be here to catch them if they fall. 😂 But we will be observing.

[Olden_Dev @OldenDev]

@NellyKordangcv Thank you! I appreciate it!

[Olden_Dev @OldenDev]

One of the things I require of my SWEs, is to apply all migrations manually. This way, they can review them before running, understand them, and make revisions where necessary. This comes in very handy when you are applying migrations to a few hundred production database. Whew.

[Olden_Dev @OldenDev]

@Eman_8282 Don't really want it but I have heard it's a great source of iron.

[Olden_Dev @OldenDev]

Codex (GPT5.5) seems to be improving with its UI skill. I'm actually impressed by some of the screen layouts provided. previously, the model would ignore our "screen layout rules" and use its own structure. It now follows every rule and consistently produces UI as planned. Seems the improvements are being updated and improved without a lot of hype and fanfare. That's good.