Thanks so much for this post. This will certainly help me not going bald before my time.
I just wish I would have read it before spending 30+ hours trying to integrate trigger.dev into a saas i’m building.
I did start to realise I was getting better results when starting a new composer.
I’m not a coder and have been learning as I go along, so I’m very reliant on AI. This will surely help a lot. Thanks again.
Hahah you’re most welcome, as are your follicles. 
If you’re not already an experienced coder, you can certainly learn a fair bit about a particular technology using an AI assistant. But the caveat I’d add is you kinda have to force yourself to get in there with the code. Be bold and confident. Make mistakes and then blame the AI for them 
One of the worst things you can do is to assume that the AI is better than you’re capable of becoming. Your ability to see the bigger picture, and your vision for how it should operate, is still beyond even the best models. As a human being (which I boldly assume you are), your attention and focus is able to pick up on logical flaws that the AI will miss. Don’t be afraid to challenge it.
Get in deep with the code all the way along, too. If you don’t, you’ll reach a point of diminishing returns, where the AI can’t figure out what’s wrong, and you don’t understand well enough what it’s built for you to be capable of the manual debugging. At that point diving in yourself is a huge task and you’ll wish you knew your own codebase better (been there…)
Oh also also, another tip (which I’ll add to the doc) in case you’re not already – when things are being weird, make the AI insert copious amounts of debug logging, and then paste those logs back at it in bulk. Something they really do excel at is in reading far more lines of logs than we can be bothered to, and in seeing where the output is mismatched with their assumptions.
Best of luck with your coding journey @ianjh, you’ll be an expert in no time. And, y’know… with hair.
Can’t fucking thank you enough for making this - excited to go through the rest of the comments too when I get the chance. Just got started a week ago and have been going hard with it. Had figured out half this stuff through trial and error but I also had no clue if what I was doing was correct. The other half (such as using the composer) is news to me and I’m psyched to try it out!! Quick question, sure someone already mentioned this but what are your thoughts on using the one option shadow workspace is - seems like people have a positive opinion towards it, no?
But ya, thanks again, can’t thank you enough!! Absolutely insane what I’ve been able to do with this all with no coding knowledge, just know computers from my PC gaming days, but that’s just the basics. Adderall, Cursor & Mushrooms is all you need baby!!! You know what I’m talking bout!! Ya you do! 
You are most welcome!! Hahah sounds like you’re having a lot of fun with it 
It’s pretty amazing what you can achieve with some AI assistance, and you can gain a ton of experience very quickly.
Honestly I don’t have a good answer for you on the shadow workspace yet. I only tried enabling it myself a few days ago (mostly because I couldn’t find the setting in the usual place and assumed it wasn’t available for macOS yet!). I haven’t really noticed a significant difference so far, but I also haven’t given it a fair test either. If you have the spare RAM for it, I don’t see any reason not to give it a go. Hopefully I’ll be able to form a more useful opinion over the next couple of weeks!
Good luck with your coding journey! 