Skip to content

Instantly share code, notes, and snippets.

Avatar
🏠
Working from home

Furkan Üzümcü Furkanzmc

🏠
Working from home
View GitHub Profile
@adamawolf
adamawolf / Apple_mobile_device_types.txt
Last active Oct 21, 2021
List of Apple's mobile device codes types a.k.a. machine ids (e.g. `iPhone1,1`, `Watch1,1`, etc.) and their matching product names
View Apple_mobile_device_types.txt
i386 : iPhone Simulator
x86_64 : iPhone Simulator
arm64 : iPhone Simulator
iPhone1,1 : iPhone
iPhone1,2 : iPhone 3G
iPhone2,1 : iPhone 3GS
iPhone3,1 : iPhone 4
iPhone3,2 : iPhone 4 GSM Rev A
iPhone3,3 : iPhone 4 CDMA
iPhone4,1 : iPhone 4S
@aparrish
aparrish / understanding-word-vectors.ipynb
Last active Oct 16, 2021
Understanding word vectors: A tutorial for "Reading and Writing Electronic Text," a class I teach at ITP. (Python 2.7) Code examples released under CC0 https://creativecommons.org/choose/zero/, other text released under CC BY 4.0 https://creativecommons.org/licenses/by/4.0/
View understanding-word-vectors.ipynb
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
@MattPD
MattPD / cpp.std.coroutines.draft.md
Last active Oct 15, 2021
C++ links: Coroutines (WIP draft)
View cpp.std.coroutines.draft.md
@GuillaumeDua
GuillaumeDua / Concept-based polymorphism in modern Cpp.md
Last active Oct 10, 2021
Concept-based polymorphism in modern C++
View Concept-based polymorphism in modern Cpp.md

Concept-based polymorphism in modern C++

Date 05-05-2021 - 07-04-2021
Revision R2
Author Guillaume Dua
Reviewer Loïc Joly, Antoine Morrier
@zsup
zsup / ddd.md
Last active Sep 23, 2021
Documentation-Driven Development (DDD)
View ddd.md

Documentation-Driven Development

The philosophy behind Documentation-Driven Development is a simple: from the perspective of a user, if a feature is not documented, then it doesn't exist, and if a feature is documented incorrectly, then it's broken.

  • Document the feature first. Figure out how you're going to describe the feature to users; if it's not documented, it doesn't exist. Documentation is the best way to define a feature in a user's eyes.
  • Whenever possible, documentation should be reviewed by users (community or Spark Elite) before any development begins.
  • Once documentation has been written, development should commence, and test-driven development is preferred.
  • Unit tests should be written that test the features as described by the documentation. If the functionality ever comes out of alignment with the documentation, tests should fail.
  • When a feature is being modified, it should be modified documentation-first.
  • When documentation is modified, so should be the tests.
@ilnuribat
ilnuribat / DatePicker.qml
Last active Sep 5, 2021
Pure QML DatePicker, like android material design datePicker. QtQuick 2.7, QtQuick.Controls 2.0, Qt.labs.calendar 1.0. PS: dimensions in millimeters, so no depends on screen pixel density.
View DatePicker.qml
import QtQuick 2.7
import QtQuick.Window 2.2
import QtQuick.Controls 2.0
import Qt.labs.calendar 1.0
Rectangle {
id: mainForm
height: cellSize * 12
width: cellSize * 8
property double mm: Screen.pixelDensity
@NoobsArePeople2
NoobsArePeople2 / gist:5121597
Last active Aug 18, 2021
Configure media keys on a non-Apple keyboard to control Spotify via AppleScript and USB Overdrive on OSX.
View gist:5121597

Requirements

  1. USB Overdrive
  2. A non-Apple keyboard with media keys (or keys you want to make "media" keys). For reference, I'm using a Microsoft Sidewinder X4

Set Up

  1. Plug in your keyboard and install USB Overdrive.
  2. Open USB Overdrive. Click into the Settings tab.
  3. Click the dropdown and select "Any Keyboard, Any Application"
@acolyer
acolyer / jessfraz.md
Created Nov 19, 2017
Containers, operating systems and other fun things from The Morning Paper
View .vimrc
if empty(glob('~/.vim/autoload/plug.vim'))
silent !curl -fLo ~/.vim/autoload/plug.vim --create-dirs
\ https://raw.githubusercontent.com/junegunn/vim-plug/master/plug.vim
autocmd VimEnter * PlugInstall --sync | source $MYVIMRC
endif
" Plugins here
call plug#begin('~/.vim/plugged')
Plug 'w0rp/ale'
Plug 'keith/swift.vim'
Plug 'vim-airline/vim-airline'
@maxbucknell
maxbucknell / README.md
Last active Mar 11, 2020
Somebody hit the lights
View README.md

Alfred

I have a "lights" workflow in Alfred, that is a little AppleScript

tell application "System Events"
	tell appearance preferences
		set dark mode to not dark mode
	end tell
end tell