Forwarded from Big Habesha Tech
α₯αα΄α΅ α¨αααΆαα½αα α¨α£α΅αͺ ααα³ ααα
α₯αα½ααα?
αααΆα α αα΅ααα α΅ αα α¨αααΆαα½α α£α΅αͺ α²αα¨α΅ α¨αα α¨α α₯α α αα αα α«ααα α¨α£α΅αͺ ααα³/αα α αΌα αα΅α¨α α α΅ααα ααα’
αα ααα ααα΅α¨α α ααααͺα« windows+R α°ααα α¨ααα£αα textbox αα cmd α₯αα α₯αα αααα’ α ααα ααα¦
α₯αα α ααα enter α₯ααα«ααα’ α¨αα«α α₯αα°αα α ααα΅/α°αα«α«α’/ α αα ααα£αααα’ battery life report saved to file path C:\Users\yourname\battery-report.html .
α αα¨α¨α»α start α₯αα α αα α¨αα α¨αααα path α₯α» copy α α΅ααα paste α₯αα°ααααα’ ααα³αα¦
α αα α΅α αααΆαα½α α¨α°αα«α© αα¨ααα½α α₯αααααα’ α΅αα½ αα α₯αα³α°α¨αα DESIGN CAPACITY α₯α FULL CHARGE CAPACITY α¨αα ααα«αα½ α¨αααα α²αα DESIGN CAPACITY α¨ααα α α αα₯ α«αα α£α΅αͺα α²αα¨α΅ α«αα α α α α mWh α²αα α¨FULL CHARGE CAPACITY α α αα₯ α«αα α°αα α αα αα α«αα α¨α£α΅αͺα α¨αα«α α α α α mWh ααα’
Β©bighabesha_softwares
αααΆα α αα΅ααα α΅ αα α¨αααΆαα½α α£α΅αͺ α²αα¨α΅ α¨αα α¨α α₯α α αα αα α«ααα α¨α£α΅αͺ ααα³/αα α αΌα αα΅α¨α α α΅ααα ααα’
αα ααα ααα΅α¨α α ααααͺα« windows+R α°ααα α¨ααα£αα textbox αα cmd α₯αα α₯αα αααα’ α ααα ααα¦
powercfg /batteryreport
α₯αα α ααα enter α₯ααα«ααα’ α¨αα«α α₯αα°αα α ααα΅/α°αα«α«α’/ α αα ααα£αααα’ battery life report saved to file path C:\Users\yourname\battery-report.html .
α αα¨α¨α»α start α₯αα α αα α¨αα α¨αααα path α₯α» copy α α΅ααα paste α₯αα°ααααα’ ααα³αα¦
start C:\Users\yourname\battery-report.html
α αα α΅α αααΆαα½α α¨α°αα«α© αα¨ααα½α α₯αααααα’ α΅αα½ αα α₯αα³α°α¨αα DESIGN CAPACITY α₯α FULL CHARGE CAPACITY α¨αα ααα«αα½ α¨αααα α²αα DESIGN CAPACITY α¨ααα α α αα₯ α«αα α£α΅αͺα α²αα¨α΅ α«αα α α α α mWh α²αα α¨FULL CHARGE CAPACITY α α αα₯ α«αα α°αα α αα αα α«αα α¨α£α΅αͺα α¨αα«α α α α α mWh ααα’
Β©bighabesha_softwares
lay-tech
Photo
ππFor real time communication like telegram, Facebook... We can use socket io. This week I have built flutter mobile app for wisdom academy
π4
π§ 1. What Is Cursor AI?
Cursor is an AI-powered code editor built on top of VS Code, but enhanced with:
Deep AI code completion
Inline chat (like ChatGPT inside your editor)
Codebase-aware reasoning
Refactoring and explanation tools
Auto test, documentation, and debugging assistance
It integrates directly with OpenAI models (like GPT-4 or Claude) to understand your entire project context, not just a single file.
βοΈ 2. What You Should Understand Before Using It
Before diving in, you should know these foundational ideas:
𧩠a) Context Awareness
Cursor doesnβt just look at your current file β it can analyze:
Linked imports
Related files
Entire function calls
Even docs and configuration files
π This means you must organize your project clearly β file naming, structure, and comments matter.
Good project hygiene = better AI output.
𧩠b) Prompting Matters
Cursorβs inline chat and /ask command depend on your prompt quality:
Be specific: βRefactor this React component to use useMemoβ is better than βmake it better.β
Include context: βThis function is called in userController.js, update both.β
Limit scope: βFix this function onlyβ helps Cursor avoid unnecessary edits.
𧩠c) Model Selection
Cursor lets you choose between models:
GPT-4 / GPT-4-turbo β best accuracy, context understanding.
Claude 3.5 / Sonnet β excellent for long documents.
Small models (GPT-3.5, etc.) β faster but less accurate.
π For serious code work, always use GPT-4-turbo or Claude Sonnet if available.
𧩠d) Privacy & Security
By default, Cursor may send parts of your code to the model provider (OpenAI or Anthropic) for analysis.
So before using it:
Avoid pasting confidential keys, credentials, or private data.
Configure .env to ignore sensitive files from being read by AI (cursor.ignore works similar to .gitignore).
π 3. Main Features You Should Learn to Use
Here are Cursorβs most useful features and when to use them:
π§ Inline Chat (β + K or Ctrl + K)
Highlight a code section and type a command like:
βExplain this function.β
βRefactor this to use async/await.β
βAdd error handling and logging.β
Cursor will rewrite the code directly inline β you can accept or reject changes.
4. Best Practices When Using Cursor
β Keep commits small β donβt let AI refactor your entire project at once.
β Always review changes before committing.
β Structure code clearly (good naming = better AI understanding).
β Write comments to help Cursor understand function intent.
β Use version control β never apply big changes without Git.
β Use .cursorignore to exclude sensitive files or large data.
Cursor is an AI-powered code editor built on top of VS Code, but enhanced with:
Deep AI code completion
Inline chat (like ChatGPT inside your editor)
Codebase-aware reasoning
Refactoring and explanation tools
Auto test, documentation, and debugging assistance
It integrates directly with OpenAI models (like GPT-4 or Claude) to understand your entire project context, not just a single file.
βοΈ 2. What You Should Understand Before Using It
Before diving in, you should know these foundational ideas:
𧩠a) Context Awareness
Cursor doesnβt just look at your current file β it can analyze:
Linked imports
Related files
Entire function calls
Even docs and configuration files
π This means you must organize your project clearly β file naming, structure, and comments matter.
Good project hygiene = better AI output.
𧩠b) Prompting Matters
Cursorβs inline chat and /ask command depend on your prompt quality:
Be specific: βRefactor this React component to use useMemoβ is better than βmake it better.β
Include context: βThis function is called in userController.js, update both.β
Limit scope: βFix this function onlyβ helps Cursor avoid unnecessary edits.
𧩠c) Model Selection
Cursor lets you choose between models:
GPT-4 / GPT-4-turbo β best accuracy, context understanding.
Claude 3.5 / Sonnet β excellent for long documents.
Small models (GPT-3.5, etc.) β faster but less accurate.
π For serious code work, always use GPT-4-turbo or Claude Sonnet if available.
𧩠d) Privacy & Security
By default, Cursor may send parts of your code to the model provider (OpenAI or Anthropic) for analysis.
So before using it:
Avoid pasting confidential keys, credentials, or private data.
Configure .env to ignore sensitive files from being read by AI (cursor.ignore works similar to .gitignore).
π 3. Main Features You Should Learn to Use
Here are Cursorβs most useful features and when to use them:
π§ Inline Chat (β + K or Ctrl + K)
Highlight a code section and type a command like:
βExplain this function.β
βRefactor this to use async/await.β
βAdd error handling and logging.β
Cursor will rewrite the code directly inline β you can accept or reject changes.
4. Best Practices When Using Cursor
β Keep commits small β donβt let AI refactor your entire project at once.
β Always review changes before committing.
β Structure code clearly (good naming = better AI understanding).
β Write comments to help Cursor understand function intent.
β Use version control β never apply big changes without Git.
β Use .cursorignore to exclude sensitive files or large data.
π3β€1
αα¨α¨α»αα α³α³α α΅α«α ααα΅α«α΅ ααα¨α ααα ααα¨α α₯ ααα¨α αα
π4
πThe Code is Write-Once, Read-Many: Your past actions are immutableβyou can't change the execution. But you can change the compiler. Stop compiling old memories with negativity. Recompile them with growth, resilience, and wisdom.
π3
π§ How to Understand Logic Easily (Real Truth)
1. Think Like a Human, Not a Programmer
Before writing code, ask:
π βHow would I solve this in real life?β
Logic always comes before syntax.
2. One Problem = One Small Step
Donβt try to solve everything at once.
Break it into:
β’ What is given?
β’ What is needed?
β’ What changes step by step?
Small thinking β Big clarity.
3. Mistakes Mean Youβre Learning
If your code fails:
β Your brain is growing
β Your logic is improving
β Youβre on the right path
No errors = no learning.
πΉ 4. Compare Yourself Only With Yesterday
Every developer once:
β’ Didnβt understand loops
β’ Didnβt understand logic
β’ Googled basic questions
Consistency beats talent.
π― Golden Rule of Programming
βUnderstand the problem first. Code comes later.β
1. Think Like a Human, Not a Programmer
Before writing code, ask:
π βHow would I solve this in real life?β
Logic always comes before syntax.
2. One Problem = One Small Step
Donβt try to solve everything at once.
Break it into:
β’ What is given?
β’ What is needed?
β’ What changes step by step?
Small thinking β Big clarity.
3. Mistakes Mean Youβre Learning
If your code fails:
β Your brain is growing
β Your logic is improving
β Youβre on the right path
No errors = no learning.
πΉ 4. Compare Yourself Only With Yesterday
Every developer once:
β’ Didnβt understand loops
β’ Didnβt understand logic
β’ Googled basic questions
Consistency beats talent.
π― Golden Rule of Programming
βUnderstand the problem first. Code comes later.β
π3