- Delete unused or obsolete files when your changes make them irrelevant (refactors, feature removals, etc.), and revert files only when the change is yours or explicitly requested. If a git operation leaves you unsure about other agents' in-flight work, stop and coordinate instead of deleting.
- Before attempting to delete a file to resolve a local type/lint failure, stop and ask the user. Other agents are often editing adjacent files; deleting their work to silence an error is never acceptable without explicit approval.
- NEVER edit
.envor any environment variable files—only the user may change them. - Coordinate with other agents before removing their in-progress edits—don't revert or delete work you didn't author unless everyone agrees.
- Moving/renaming and restoring files is allowed.
- ABSOLUTELY NEVER run destructive git operations (e.g.,
git reset --hard,rm,git checkout/git restoreto an older commit) unless the user gives an explicit, written instruction in this conversation. Treat t
When analyzing large codebases or multiple files that might exceed context limits, use the Gemini CLI with its massive context window. Use gemini -p to leverage Google Gemini's large context capacity.
Use the @ syntax to include files and directories in your Gemini prompts. The paths should be relative to WHERE you run the gemini command:
| import SwiftUI | |
| /** | |
| ### Exercises for the viewer | |
| - Phase interrupt handling. | |
| - Use Swift concurrency. | |
| - Color scheme awareness. | |
| - Rework animations to be more spring-like à la what shipped in `0.90.0`. |
| # I'll be doing another one for Linux, but this one will give you | |
| # a pop up notification and sound alert (using the built-in sounds for macOS) | |
| # Requires https://github.com/caarlos0/timer to be installed | |
| # Mac setup for pomo | |
| alias work="timer 60m && terminal-notifier -message 'Pomodoro'\ | |
| -title 'Work Timer is up! Take a Break 😊'\ | |
| -appIcon '~/Pictures/pumpkin.png'\ | |
| -sound Crystal" |
| /* | |
| RUN THE SCRIPT BY YOURSELF: | |
| - Run `node paddle-revenue.js` on your server and let it run 24/7. | |
| - Access the API at http://your_server_ip:8175/ (JSON) | |
| HOSTED VERSION: | |
| If you don't want to run the script by your own, you can use the | |
| hosted version. The price is $5 per month per Paddle account. | |
| Here is how: |
If you want to test a contract that depends on other contract, but you don't own the latter contract (or you do but you want to test the first contract in isolation), you need to either stub or mock that dependency.
If you are not sure about the difference between a stub and a mock, check this StackOverflow question
If the contract you are testing receives its dependency in some way, you can write a stub contract and use that in your tests. It would be something like this:
contract ContractToTest {Follow this Guide with YOUR OWN RISK!
REQUIRED: NX-Atmosphere 0.18.x
As Atmosphere 0.18.x Releases, there is dns.mitm module implementation to extend Nintendo Switch hosts file, but first we need to activate dns.mitm module to be started by configuring system_settings.ini file in atmosphere/config. Here's the snippet section of system_settings.ini file:
...
[atmosphere]
...
...Translated from https://blog.isquaredsoftware.com/2020/05/blogged-answers-a-mostly-complete-guide-to-react-rendering-behavior/, author: Mark Erikson (from Redux team)
Bài viết cung cấp chi tiết về cách mà React render hoạt động, và việc sử dụng Context và Redux ảnh hưởng thế nào tới quá trình render của React.
Rendering is the process of React asking your components to describe what they want their section of the UI to look like, now, based on the current combination of props and state.
General iOS, CS questions and interview prep resources.
-
iOS Interview Questions for Senior Developers (useful even if you're not senior yet)