Skip to content

Instantly share code, notes, and snippets.

Avatar
🏠
Working from home

Furkan Üzümcü Furkanzmc

🏠
Working from home
View GitHub Profile
@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
@MattPD
MattPD / cpp.std.coroutines.draft.md
Last active Aug 27, 2021
C++ links: Coroutines (WIP draft)
View cpp.std.coroutines.draft.md
View .bash_profile
export ANDROID_HOME=/Users/flanneryjefferson/Library/Android/sdk
export PATH=$ANDROID_HOME/tools:$PATH
export PATH=$ANDROID_HOME/platform-tools:$PATH
export PATH=$ANDROID_HOME/build-tools/23.0.1:$PATH
export PATH="$HOME:$PATH:${PATH}:/usr/local/mysql/bin:${PATH}:/usr/bin:/Users/flannerykj/Library/Python/3.6/bin"
# deleted from path: $HOME/.node/bin:/Users/flannerykj/Library/Python/2.7/bin:
export PATH="/usr/local/opt/node@8/bin:$PATH"
export PATH="$HOME:$PATH:${PATH}:/usr/local/mysql/bin:${PATH}:/usr/bin:$HOME/.node/bin"
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'
@acolyer
acolyer / jessfraz.md
Created Nov 19, 2017
Containers, operating systems and other fun things from The Morning Paper
@aparrish
aparrish / understanding-word-vectors.ipynb
Last active Sep 18, 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.
@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
@hbasria
hbasria / raw_as_qs.py
Created Jan 29, 2016 — forked from carymrobbins/raw_as_qs.py
Django - convert RawQuerySet to QuerySet
View raw_as_qs.py
from django.db import connection, models
class MyManager(Manager):
def raw_as_qs(self, raw_query, params=()):
"""Execute a raw query and return a QuerySet. The first column in the
result set must be the id field for the model.
:type raw_query: str | unicode
:type params: tuple[T] | dict[str | unicode, T]
:rtype: django.db.models.query.QuerySet
"""
@daltondotgd
daltondotgd / VSyncForCocos2dX.cpp
Created Aug 27, 2014
To enable VSync for WIN32 in cocos2d-x, modify initWithRect(...) function in CCGLView.cpp, so it contains this code right before 'initGlew();'
View VSyncForCocos2dX.cpp
...
...
...
#if (CC_TARGET_PLATFORM == CC_PLATFORM_WIN32)
// Turn on vertical screen sync under Windows.
// (I.e. it uses the WGL_EXT_swap_control extension)
typedef BOOL(WINAPI *PFNWGLSWAPINTERVALEXTPROC)(int interval);
PFNWGLSWAPINTERVALEXTPROC wglSwapIntervalEXT = NULL;
wglSwapIntervalEXT = (PFNWGLSWAPINTERVALEXTPROC)wglGetProcAddress("wglSwapIntervalEXT");
@zsup
zsup / ddd.md
Last active Aug 16, 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.