Le Dien Phuc phucledien

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 .env or 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 restore to an older commit) unless the user gives an explicit, written instruction in this conversation. Treat t

Follow this Guide with YOUR OWN RISK!

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]
...
...

libdispatch efficiency tips

The libdispatch is one of the most misused API due to the way it was presented to us when it was introduced and for many years after that, and due to the confusing documentation and API. This page is a compilation of important things to know if you're going to use this library. Many references are available at the end of this document pointing to comments from Apple's very own libdispatch maintainer (Pierre Habouzit).

My take-aways are:

You should create very few, long-lived, well-defined queues. These queues should be seen as execution contexts in your program (gui, background work, ...) that benefit from executing in parallel. An important thing to note is that if these queues are all active at once, you will get as many threads running. In most apps, you probably do not need to create more than 3 or 4 queues.
Go serial first, and as you find performance bottle necks, measure why, and if concurrency helps, apply with care, always validating under system pressure. Reuse

	# 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"

	pipelines:
	branches:
	develop:
	- step:
	name: Update
	script:
	- apt-get update
	- apt-get -y install jq zip
	- FILE_NAME=crx.zip
	- zip -r $FILE_NAME ./app

	/*
	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:

	# A Best in Class Checklist
	A boiled down checklist adapted from this [post](https://www.swiftjectivec.com/a-best-in-class-app/), created by @jordanmorgan10.

	> To use this, create a Github Issue in your own repo, and simply copy and paste this text.

	## iOS Core Technology
	_Things any iOS app can benefit from_

	- [ ] iCloud Sync
	- [ ] [Core Spotlight integration](https://github.com/DreamingInBinary/Spend-Stack/issues/120)

	import Foundation

	struct Promise<T> {
	typealias ResultType = Result<T, Error>
	typealias ResultObserver = (ResultType) -> Void
	typealias CreatorFunction = (@escaping ResultObserver) -> Void
	private let creatorFunction: CreatorFunction

	init(creatorFunction: @escaping CreatorFunction) {
	self.creatorFunction = creatorFunction

Le Dien Phuc phucledien

Table of Contents

set -e, -u, -x, -o pipefail

libdispatch efficiency tips

	// #!Swift-1.1
	import Foundation


	// MARK: - (1) classes

	// Solution 1:
	// - Use classes instead of struct
	// Issue: Violate the concept of moving model to the value layer
	// http://realm.io/news/andy-matuschak-controlling-complexity/