Ian

Front-end developer 💻 | Scuba diver 🤿 | Music lover 🎶

[freeCodeCamp.org @freeCodeCamp]

As a developer, you should know core system design concepts.

This helps show potential employers that you can turn design requirements into production-ready code.

This course covers app architecture, API design, caching, networking, databases, and more.

https://t.co/j6TmwXZox7

[Ryo Lu @ryolu_]

Using Cursor well = fast, clean code.

Using it wrong = AI spaghetti you’ll be cleaning up all week.

Here’s how to actually use it right:

1. Set 5-10 clear project rules upfront so Cursor knows your structure and constraints. Try /generate rules for existing codebases.

2. Be specific in prompts. Spell out tech stack, behavior, and constraints like a mini spec.

3. Work file by file; generate, test, and review in small, focused chunks.

4. Write tests first, lock them, and generate code until all tests pass.

5. Always review AI output and hard‑fix anything that breaks, then tell Cursor to use them as examples.

6. Use @ file, @ folders, @ git to scope Cursor’s attention to the right parts of your codebase.

7. Keep design docs and checklists in .cursor/ so the agent has full context on what to do next.

8. If code is wrong, just write it yourself. Cursor learns faster from edits than explanations.

9. Use chat history to iterate on old prompts without starting over.

10. Choose models intentionally. Gemini for precision, Claude for breadth.

11. In new or unfamiliar stacks, paste in link to documentation. Make Cursor explain all errors and fixes line by line.

12.Let big projects index overnight and limit context scope to keep performance snappy.

Structure and control wins (for now)

Treat Cursor agent like a powerful junior — it can go far, fast, if you show it the way.

[Velvet | Social Trading Terminal @Velvet_Capital]

Velvet x Binance Wallet Airdrop Campaign

Rewards: 8,000,000 $VELVET to 30,000 Winners

Come experience the future of DeFAI Trading and Portfolio Management with Velvet Capital and get rewarded!

[Ian @enhsu79]

Leetcode daily, 520. Detect Capital

#LeetCode #typescript

[Ian @enhsu79]

Leetcode daily, 290. Word Pattern

#LeetCode #typescript

[Frantz Kati @bahdcoder]

It's finally here !!

The Software Engineer Growth Tracker

A powerful notion template to track your growth and level up your career in 2023.

I'm sharing this free for a limited time only.

Reply "growth" below, and I'll dm you the download link (Must be following to receive)

[Ian @enhsu79]

Leetcode daily, 55. Jump Game

#leetcode #typescript

[Ian @enhsu79]

Leetcode daily, 309. Best Time to Buy and Sell Stock with Cooldown

#leetcode #TypeScript

[Ian @enhsu79]

Day100
Leetcode daily, 834. Sum of Distances in Tree

#100DaysOfCode #leetcode #TypeScript

[Ian @enhsu79]

Day99
Leetcode daily, 886. Possible Bipartition

#100DaysOfCode #leetcode #TypeScript

[Ian @enhsu79]

Day98
Leetcode daily, 841. Keys and Rooms

#100DaysOfCode #leetcode #TypeScript

[Ian @enhsu79]

@ChesaroMaldini Nice, the same concept

[Ian @enhsu79]

Day97
Leetcode daily, 1971. Find if Path Exists in Graph

#100DaysOfCode #leetcode #TypeScript

[Ian @enhsu79]

@shankhungryman I just opened it👍

[Ian @enhsu79]

Day95
Leetcode daily, 150. Evaluate Reverse Polish Notation

#100DaysOfCode #leetcode

[Ian @enhsu79]

@ChesaroMaldini Clever solution!
But js don't have build-in stack peek
So I just follow my intuition to solve this problem LOL

[Ian @enhsu79]

Day96
Leetcode daily, 739. Daily Temperatures

#100DaysOfCode #leetcode #TypeScript

[Ian @enhsu79]

@shankhungryman It's TypeScript

[Ian @enhsu79]

Day94
Leetcode daily, 232. Implement Queue using Stacks

#100DaysOfCode #leetcode

[Ian @enhsu79]

Day93
Leetcode daily, 1143. Longest Common Subsequence

#100DaysOfCode #leetcode