Vibe coding vibes be like 😭

you are welcome. and it took me 3 reversions to last commit to get just a simple restructuring done.

codes from original place. it could be a disaster. well. as long as we understand how stupid it is now. there are ways to tackle. 1- specifically ask it NOT to change anything. 2- ask it to move one page at a time. test it and commit the codes before move to the next. 4/

when asked to restructure the project, e.g., have folders of /pages, /components, etc. cursor started to make a lot of mistakes. Most destructing ones? 1 - modify the codes at the same time of moving 2- move half way and forget about it. 3- done moving but forgot to delete 3/

until it is unable to be maintained or read as it is full of duplicated codes, messy functions and random patches. this is pretty junior behavior - wondering where it picked that up.. hmmm 2/

#AvoidGettingMadAtCursorTips Cursor is terribly bad at structuring a project properly when starting from scratch instead of a project boilerplate. It keeps all the codes in the single file, e.g., app.tsx in case of react. 1/

In the past two months, we've been working with a high-profile, large-scale Vite project to test and optimize Rolldown-Vite for production. After getting the massive project to successfully build on Rolldown-Vite, we've landed improvements in @rolldown_rs that have gotten the

Me teaching @cursor_ai 🤡

I am a paid user - I used Agent & Auto mode. I’m guessing Cursor’s performance takes a dive when the quota is nearly used up? That said, it really feels like Cursor needs to address the “long conversation” issue — it should be able to handle larger, more complex projects. done.

made them: : sortField and sortDirection.. bravo I know I prolly shouldn't have called it "the artificial illiterate," but I didn't expect it to misbehave like this. Is it just me, or has Cursor been showing some deteriorating behavior after the recent updates? 7/x

- when the sort button is triggered, within 10 minutes, I got the sort working; Meantime, I also found several mistakes made by cursor. For example, the api parameters to fetch chats are supposed to be: sortBy, and sortOrder, but Cursor made them: 6/x

Back and forth a few times, I realized that it wouldn't and couldn't solve my sort problem. I had to roll up my sleeves and do it myself. After I cleaned lots of ineffective codes and simply did a fetchChats with the toggled sort direction (asc or desc) - when 5/x

But when I ask it to compose a commit message for me based on the shitty changes, it doesn't think the conversation was too long and it is working. 4/x

it says: this conversation is too long. I suggest you to start a new chat. 🤡 3/x

Apparently Cursor thinks the best way to sort Create Time is to compare string value instead of timestamp value, after I told it - whats the intelligent part of your code? it starts to evade the difficult question, like any other man that breaks hearts. lol 2/x

I battled with the sort features for the past 2 days. yes, battled. but not with the coding, but with Cursor. @cursor_ai thank you for upsetting me so much so that I was almost struck by depression. 1/x

experiencing issues with Github anyone❓

The Soviet Union—and its successor, the Russian Federation—has been among the bloodiest sovereign powers in modern history. Its legacy is marked not only by wars of aggression against neighboring countries such as Poland (e.g., the Soviet invasion of Poland in 1939), China (e.g.,

Cursor couldn't do it right without me abusing it it made me an evil person, it changed me forever🥲

https://t.co/2AXiugK6Q5