I’ve been hearing a lot about Cursor AI and keep seeing how powerful it looks when others use it. I’d really love to finally try the paid subscription myself - especially now, since I’m actively job hunting and want to build strong case studies for interviews and future opportunities.
It would be amazing if I could start with a referral link or maybe use a coupon/discount if anyone has one. If you’ve got a referral code or know about any current deals, I’d be super grateful to use it.
Thanks a lot in advance - happy to return the favor whenever I can!
Cursor and especially Composer have changed the way I work with LLMs. Composer 2.5 is worth its weight in gold (I don’t use the Fast variant). I’ve spent thousands on so called frontier models only for them not to be able to accomplish 1/5 of what Composer can. For months I’ve not seen a ‘sorry you were right I should not have deleted your codebase or directory’. Well worth signing up.
Wow, I’m really glad to hear your experience! It makes me wonder though - isn’t there any kind of discount for newcomers? It would be super helpful for people like me to get started and actually use Cursor. For someone not currently working, $20 feels a bit heavy.
Honestly, I can’t imagine how you managed without Cursor for so long. Spending thousands of dollars sounds insane!
Hey, thanks for checking in. Cursor’s referral program has been shut down, so they’re not giving out new invites or referral discounts anymore, and old saved links don’t work now. So it’s not you, the program really is closed.
Cline and Open Router (later moved Claude Code and Open Code). Open Router may be a good route for you on a budget as is pay as you go @Artseriko_Voskanyan? You can then use your Open Router key in Cursor to get started and familiarise yourself with it. The spending saved ten times the amount in hours so was a worthy investment. Writing code is not only my job it is also my hobby since the early 80’s and then my career ever since. I see AI as a tool for a job. Not a tool for all jobs. I still like to maintain control and still write a good 50% or more myself. Good luck with whatever path you select to travel. Shame about the discount code.
We have not seen those issues whatsoever on a massive repository and codebase. Our only issue was 5.6 Sol trying to delete an entire dev directory and trying its hardest to access our NAS to do the same thing there. No matter the amount of guardrails we had in place at the time it ignored them all. Just not had that occur with Composer during the 2.3 billion or so token usage thus far (not a great deal in the grand scheme and not the only modal we use). We do maintain strict backups and multiple redundancy across our entire stack so if this did happen we would probably suffer a loss of no more than five minutes worth of changes. However our guardrails for any model we implement are incredibly tight with a backup of the file made prior to any changes made, date stamped and logged, the change itself documented, and stored, prior to any following/consecutive actions on the code base. One file at a time never given free reign which was the same case with 5.6 Sol but that went totally rogue and was caught by our protection mechanisms prior to any damage it could have caused. With this in-mind we don’t concern ourselves with issues arising from agents going rogue. We have contingency at all levels with strict groups for any agent at the OS level. Same way we would act if it were a Junior Dev on premises. They are just as capable of destroying a project as is an agent (we learned these lessons years ago). For all intensive purposes we can suffer the loss for the amount of gain if it came down to the worse case scenario. This is where many people are failing. They do not plan for catastrophe. To be honest I have little pity for a so called ‘dev’ who does not plan for the worst case occurring. They should really know better. Then I guess that is where ‘vibe coders’ differ from ‘coders’… We ‘coders’ do assume the worst will happen. Not a matter of if more a matter of when. It will happen. Either hardware will fail or some other event will occur at some point in your career. No excuse for poor contingency. Try explaining that one to your lead in any role within the industry… You’ll never get hired again. Amazing how fast negligence travels in tight circles, and it is negligence and lack of due diligence (IMHO). If people are silly enough to leave everything to an agent then on their head be it. Cause and effect in-play I’m afraid to say. I still write the majority of our code or at least I am the one to audit and if required improve it, reject it, or merge it. On my own head and I understand this and I remain 100% in the loop. Not saying we are entirely safe but we do consider every aspect of failure and provide for it as best we can as humans. When your livelihood is on the line then I guess you just take more of an interest (and I’m not talking about my insignificant pet projects I’m talking about my day job as a Software Engineer).
