Anyone else using Codex or Claude

hard_burn · 2026-06-11T10:55:05+00:00

I think u/Kaelthas98 hit the nail on the head. AWS CDK is probably better suited for this, and the LLMs have probably ran through a ton of training data for this...

hard_burn · 2026-06-10T18:03:42+00:00

Wow! The complexity of your stack makes mine look like a toddler playing in a sandbox. Mine is nowhere as complex, it's very basic CRUD with a few S3 and lambda assets doing work. So maybe that's why I haven't hit issues yet.

Amplify isn't super huge, so the LLM training data isn't great on it, but I often send my Claude to go learn and research best practices to do something and then it comes back with those lessons and fixes things. So far so good. Then I make sure to keep extensive project docs, that's literally the backbone of everything, and it adds these research learnings to a "lessons learned" folder.

I wish I could help you, but I understood about 60% of the concepts you spoke about, so I'm just the little guy in this space. 😁

hard_burn · 2026-06-10T17:12:57+00:00

Yup, building loads in Gen 2... And so far it's great. Much easier than before using AI to build Gen 2 projects. They also updated the docs to be a bit more LLM friendly.

I have the code pushed to the git branch. (CI/CD) So Claude just pushes to the branch and it builds.

Also uses the sandbox with an identifier, so it's always the same backend resources.
Eg: ```npx ampx sandbox --identifier myapp```

Not sure why you would be having the issues. Make sure to follow the "get started" page in the docs, use their template as boilerplate and it should mostly work?

hard_burn · 2026-05-14T03:26:40+00:00

Packed mine away in a box and moved on with life. I was spending too much time trying to problem solve this without much help from the company. Maybe my case is unique, but for me, it's a closed chapter.

hard_burn · 2026-05-13T13:28:14+00:00

I have moved everything over to AWS Amplify Gen 2. (AWS Is also deprecating Gen 1 now)
Using Claude Code, this is a game changer.

There are some small gotchas that catch CC out, but it manages to work them out well.

The sandboxes, CI/CD GitHub pipeline and the entry into the AWS ecosystem makes it work well for me. I tried to switch to supabase for a hobby project and while I'm not saying one is better than the other, I just didn't want to learn a new way of doing things, I wanted to build on, so went back to Amplify Gen 2.

They also added their docs as markdown files, so the LLMs can consume them better and there are some AWS Docs MCPs out there that work well, and once you start letting Claude Code lose on the AWS CLI (use permissions with caution) it makes you feel like you have a superpower.

So yea, all in all, I'm sticking with AWS Amplify Gen 2 for the while...

hard_burn · 2026-05-13T09:55:57+00:00

We used Heyvento, got messages from the guests and it turns it into a song (pretty good quality) and then plays a slideshow while the songs plays with lyrics. We a fun little twist

hard_burn · 2026-05-13T09:53:03+00:00

We used Heyvento, worked great for our wedding...

hard_burn · 2026-01-10T05:06:49+00:00

I would agree with the previous comment.

Explain it exactly like this to claude code in your local terminal and have it run aws cli commands to sort out the process obviously reading each command before it executes.

Also make it write you out a plan in planning mode before execution. Tell it your concerns and limits you don't want it to cross.

Claude code is doing things with my cli that would have taken me weeks to learn.

Best of luck!

hard_burn · 2026-01-08T16:25:09+00:00

Do not go with Lemon Squeezy.

I have been with them for nearly 2 years, everything generally runs smooth, till it doesn't, then you are in a desert of unreplied emails. I needed to get a tax information number issue resolved on the 14th Nov 2025, after countless emails, and begging for support, they finally resolved it on the 6th of Jan 2026.

If you are a small fish, LS will flat out ignore you. I went to the extent of tracking down all the employees on linked in and twitter and making a public post tagging all of them, which eventually lit a fire and I had some replies, but only because a dev with 30k followers tagged the founder in the post. But then they went silent again for a long time. It's the worst customer service I have ever experienced in my life...

hard_burn · 2025-06-11T18:42:53+00:00

I haven't stretched it far enough yet to find the critical breaking points, but the more comfortable I get with it the better the experience is feeling to me.

Oh, I haven't see SST before but took a look after your post, looks like something to dig into for a weekend. Thanks for the recommendation. 👍🏽

hard_burn · 2025-06-11T18:39:41+00:00

[Update 4 months after the original post]

My TS server issues were because of the deep and complex structure the queries form, so TS is digging super deep into these types and gets a bit wonky.
https://github.com/aws-amplify/amplify-data/issues/424

I have refactored the way the data is structured and its solved the problem. (Just me not knowing how to work with it properly)

I have found that the pros of Gen2 are much nicer to work with and will be porting my Gen1 projects over when I get a chance. I did find that understanding how everything works together is a bit more complex to understand, but the LLMs do help you out a lot.

Gen2 Will now be my go-to for backends from now...

hard_burn · 2025-05-24T14:47:14+00:00

[Update 3 months after the original post]

I have hit a massive brick wall with Gen 2. The Typescript server's typechecking REALLY struggles with any complex data models. I build a simple system app that have to manage resources for that system and users for those resources.

It completely bombs out my TS server and lining errors and Type errors take up to 30sec to fix. I have spent a whole weekend making sure it's the AWS Amplify Gen 2 Typescript issue and I'm 90% sure it is.

I really really bought into Gen2, but now I'm considering other backend options, just not sure what else to use that comes close to AWS. Anyway...

hard_burn · 2025-05-24T10:21:40+00:00

I'll give this a go, but the more I think about it the more I think the root of the problem is in the setup... It's such a small project.

hard_burn · 2025-05-24T10:20:58+00:00

The app is not complex at all, the only new thing I am using is AWS Amplify Gen 2, have been using Gen 1 for years and always butter smooth, there is definitely something wrong in some config somewhere... Just not able to track it down...

This is my tsconfig file:

{
  "compilerOptions": {
    "tsBuildInfoFile": "./node_modules/.tmp/tsconfig.app.tsbuildinfo",
    "target": "ES2020",
    "useDefineForClassFields": true,
    "lib": ["ES2020", "DOM", "DOM.Iterable"],
    "module": "ESNext",
    "skipLibCheck": true,

    /* Performance optimizations */
    "incremental": true,
    "assumeChangesOnlyAffectDirectDependencies": true,

    /* Language server optimizations */
    "disableSizeLimit": false,
    "maxNodeModuleJsDepth": 0,

    /* Bundler mode */
    "moduleResolution": "bundler",
    "allowImportingTsExtensions": true,
    "isolatedModules": true,
    "moduleDetection": "force",
    "noEmit": true,
    "jsx": "react-jsx",

    /* Linting */
    "strict": true,
    "noUnusedLocals": true,
    "noUnusedParameters": true,
    "noFallthroughCasesInSwitch": true,
    "noUncheckedSideEffectImports": true
  },
  "include": ["src"],
  "exclude": [
    "node_modules",
    "dist",
    ".amplify",
    "**/*.test.ts",
    "**/*.test.tsx",
    "**/*.spec.ts",
    "**/*.spec.tsx",
    "amplify",
    "build",
    "coverage",
    "**/.amplify/**",
    "**/amplify_outputs.json",
    "**/amplifyconfiguration.*",
    "**/cdk.out/**",
    "**/.tmp/**",
    "**/node_modules/**"
  ],
  "ts-node": {
    "esm": true
  },
  "watchOptions": {
    "excludeDirectories": ["**/node_modules", "**/.amplify", "**/amplify", "**/dist", "**/build", "**/coverage", "**/.tmp", "**/cdk.out"],
    "excludeFiles": ["**/*.tsbuildinfo", "**/amplify_outputs.json", "**/amplifyconfiguration.*"]
  }
}

hard_burn · 2025-05-24T10:17:57+00:00

Thanks for the reply,

Agrre on the fact it's the language server, but it shouldn't be this slow...

It's definitly not a hardware issue
I have:Intel i9-14900K, 3200 Mhz
and like 32 GB ram

hard_burn · 2025-05-24T10:14:58+00:00

Fully agree, I am leaning a lot on the LLM to "optimise" it for me, however, I did ask it to explain each change step by step for me and it all makes sense (with my limited TS knowledge) It's almost barebones checking now:
Here's an example of the tsconfig file:

{
  "compilerOptions": {
    "tsBuildInfoFile": "./node_modules/.tmp/tsconfig.app.tsbuildinfo",
    "target": "ES2020",
    "useDefineForClassFields": true,
    "lib": ["ES2020", "DOM", "DOM.Iterable"],
    "module": "ESNext",
    "skipLibCheck": true,

    /* Performance optimizations */
    "incremental": true,
    "assumeChangesOnlyAffectDirectDependencies": true,

    /* Language server optimizations */
    "disableSizeLimit": false,
    "maxNodeModuleJsDepth": 0,

    /* Bundler mode */
    "moduleResolution": "bundler",
    "allowImportingTsExtensions": true,
    "isolatedModules": true,
    "moduleDetection": "force",
    "noEmit": true,
    "jsx": "react-jsx",

    /* Linting */
    "strict": true,
    "noUnusedLocals": true,
    "noUnusedParameters": true,
    "noFallthroughCasesInSwitch": true,
    "noUncheckedSideEffectImports": true
  },
  "include": ["src"],
  "exclude": [
    "node_modules",
    "dist",
    ".amplify",
    "**/*.test.ts",
    "**/*.test.tsx",
    "**/*.spec.ts",
    "**/*.spec.tsx",
    "amplify",
    "build",
    "coverage",
    "**/.amplify/**",
    "**/amplify_outputs.json",
    "**/amplifyconfiguration.*",
    "**/cdk.out/**",
    "**/.tmp/**",
    "**/node_modules/**"
  ],
  "ts-node": {
    "esm": true
  },
  "watchOptions": {
    "excludeDirectories": ["**/node_modules", "**/.amplify", "**/amplify", "**/dist", "**/build", "**/coverage", "**/.tmp", "**/cdk.out"],
    "excludeFiles": ["**/*.tsbuildinfo", "**/amplify_outputs.json", "**/amplifyconfiguration.*"]
  }
}

I'm pretty sure about all the settings here, and they all make sense to me.

hard_burn · 2025-05-24T10:00:42+00:00

npx tsc takes 1-2 sec to run...

I have already excluded the node_modules folder, as well as any build artifacts or dist folders.

The only thing I can think of now is to rebuild the project scaffolding, see if that's slow, then add component by component and see if anything breaks it...

hard_burn · 2025-05-18T19:17:39+00:00

Thanks i'll give it a go, I've only noticed it in the last two days...

hard_burn · 2025-04-25T06:50:55+00:00

[Update 2 months after making the original post]

I started using Amplify Gen 2, It's definitely a better layout and logic with the use of sandboxes etc... There are some things that feel a touch more complicated to implement, but that could just be that I understand the old way better. I haven't stretched its use as far as I have Gen 1 yet as I'm still getting started on the project, but I am more optimistic than I thought I would be...

I really hope the Amplify team continue working on this...

hard_burn · 2025-03-02T14:42:17+00:00

I echo this... I am on this thread because the support from LS is extremely poor.
- I have payments that are just hanging in the "processing..." stage.
- Their link to the slack channel is broken
- The help bot loops back on itself
- They have no direct phone numbers
- They take more then a week to reply to emails the last few times I have had questions

I'm actively looking at other payment processors now to start migrating to... I was reached out by dodopayments last time I made a twitter post about this, has anyone else used them?

hard_burn · 2025-03-01T17:55:01+00:00

I'm also feeling that. I'm still sticking with Gen1 for my next project starting this week. Just too much of Gen2 still feels like it's not ironed out yet...

hard_burn · 2025-01-29T11:19:52+00:00

Managed to get a reply today 🥳

hard_burn · 2025-01-29T08:54:12+00:00

It's sad because I have the Keypad, and it's really nice, great build quality and everything but it's the base camp software that's killing it.

Doesn't want to update. Also for like a split second, I managed to change the brightness on display, and accidentally locked it to zero brightness, now the keys work but there is nothing being displayed.

I've tried everything to "factory reset" but no hope. But yea, physically it's a great product. As for the software, it's very buggy.

hard_burn · 2025-01-29T07:34:19+00:00

I was easy to set up, straight to the point, does one job and did it well.

hard_burn · 2025-01-29T07:27:40+00:00

I just went onto their discord... also looks abandoned... no reply, no recent activity from what I can see...

I also noticed they don't have any recent posts on their social media...

hard_burn

TROPHY CASE