Ashbt
Joined 12 years ago
Karma
24
Submissions
7
Member since
Oct 17
Recent submissions
Comment · 6 months ago
Meta skills:
https://share.google/aimode/Fhd3GapqYWJ5vBBXo
Comment · 1 year ago
Amazing
Two things I would add:
1. Use git and commit changes (very) frequently.
Often the AI makes a recommendation that looks good, but has consequences 4 or 5 changes later that you'll need to reckon with. You'll see this especially with web vs. mobile UI behaviours. Cursor isn't so good at reverting changes yet, and GIT has saved me a LOT of headache.
2. Collaborate with o1 to create a PRD and put it in the same folder as your specs.
This increases the likelihood Cursor's recommended changes comply with your intent, style and color guidelines and overall project direction.
Comment · 2 years ago
I've done a similar thing using calendar events in the future.
It's easy.
Just open up your calendar app to a date like 5 years from now and type away.
This derisks the possibility that the "future you service" goes under, taking your cherished letters with it.
Comment · 2 years ago
Comment · 4 years ago
Made a bunch a while ago using Jukebox and cleaned it up a bit using some izotope plugins:
https://m.soundcloud.com/R05c0
It's really just a matter of time before they figure out how to make the music a bit more "cohesive."
Right now it's kinda like a stream of consciousness, vs. being verse, chorus, verse, chorus.
My prediction: in under 5 years, most of us will have a favorite AI band.
Comment · 9 years ago
I like it! Would probably call it 'Customer Success as a Service' (CSaaS) myself
Comment · 12 years ago
I don't know if docker would be the right service for my use case, but considering the user experience on this thread I thought I'd ask...
I'm looking to deploy a python based analytics service which runs for about 12 hours per job, uploads the results to a separate server then shuts down. At any given time there could be up to 100 jobs running concurrently.
Is this 'dockable' ?