graeme nelson

Co-founder @ IPGN Solutions, on web dev journey

[graeme nelson @graeme_nelson]

@rauchg HAMI Voice https://t.co/e7170mUxOo (app at https://t.co/4MBGdblBHW)- mostly xai for chat and tool calls, xai voice-first form builder from images or docs, Soniox STT, AWS polly TTS for chat, mistral transcriptions.

[graeme nelson @graeme_nelson]

@thdxr Learning Tai Chi & dusting down the old guitar

[graeme nelson @graeme_nelson]

@matthew_meadows @michelleefang That’s cool

[graeme nelson @graeme_nelson]

I’ve been doing similar, ‘vibe spec’ a task or an ‘epic’ size project, Claude creates issues then work the issues in other sessions. Seems to work best when I break down to tasks small enough to handle in single sessions. I also tried a coordination repo for features with its own issues, generating session-sized tasks as issues in the app repo. Not sure that was ideal. Perhaps sub-issues is a better way to orchestrate larger tasks into session-sized tasks. I think md files are fine for patterns and specs that we’re happy to maintain. With issues it just needs to be accurate at the time of working the issues.

[graeme nelson @graeme_nelson]

@shadcn Grease! (Well, I was about 14), probably Wizard of Oz and Great Escape repeated most

[graeme nelson @graeme_nelson]

@rob_mcrobberson This is the space we’re tackling. I think we’re a bit away from ai powered systems replacing traditional ERP and ERP users within long-established businesses but I expect new & smaller businesses to embrace more readily

[graeme nelson @graeme_nelson]

@TRobinsonNewEra Sounds familiar https://t.co/xZsRFUKvTc

[graeme nelson @graeme_nelson]

Zod type check performance as mentioned in the migration guide and zod/v3 conflicts. Upgrading to zod v4 concurrently helped. Codemod caught most work. Had to rework a mistral OCR prompt that somewhat duplicated the required response structure. Slight issue with message id. In v4 I accessed the same id backend and client and used this to reference and update like / dislike feedback on individual messages that had been saved on server. I figure can adapt to use message index, though.

[graeme nelson @graeme_nelson]

@pilcrowonpaper Straight sql

[graeme nelson @graeme_nelson]

@thdxr Maybe there’s hope for me yet!

[graeme nelson @graeme_nelson]

@housecor Issues I had typically related to a serverless function terminating immediately on sending an ‘initial’ response while the dev version continued and completed the task. Yes, a skills issue on my part, but didn’t show up in dev. Preview deploy would be much like my staging

[graeme nelson @graeme_nelson]

@svpino Mistral works well for me

[graeme nelson @graeme_nelson]

Just sharing that our virgin broadband is down in Helensburgh G84 since lunchtime . Service tech visiting tomorrow scheduled. Virgin status shown no local issues. @Grok notes a high volume of outage reports nearby. At least we’ll get hoovering done!

[graeme nelson @graeme_nelson]

@letstri My first impressions of shadcn/ui was here’s one way to compose a good toolkit of components using consistent styling and built on decent headless components. A learning resource as much as copy/paste/build resource. No surprise AI loves it!

[graeme nelson @graeme_nelson]

@shadcn It must be Friday!

[graeme nelson @graeme_nelson]

@Shpigford Queue & worker on a vps - low volume / non-critical ai jobs . Had issues keeping a task running on vercel serverless unless awaited, so fire & poll didn’t work for me. Maybe skills issue. Figured it was serverless issue. Cron would have worked - if you can wait for cron intervals

[graeme nelson @graeme_nelson]

Started building End to End business platform for 18 months ago. It's a CRUD web app. Was / am new to web dev. I chose Next.js / Postgres app on Vercel & Neon, mostly because I didn't know any better. With hindsight I'd probably make the same choice. What am I missing out on?

[graeme nelson @graeme_nelson]

@dhh Thanks, was needing that reminder!

[graeme nelson @graeme_nelson]

@thdxr I’m well impressed with the synch engine approach and implementation but for a newbie like me it looks quite a challenge to follow, so sticking with ‘conventional’ nextjs crud approach for now on my dashboard. Once I’m 10x I may revisit!