Matěj Koubík mkoubik

This Github Action workflow along with the rest of these files/scripts will allow you to create a Tag as well as a Release with the release notes set to the text added in the body of the merge comment when a pull request is merged.

Note:

Merge comment title needs to contain the text "release" or else the workflow will not run (see line 11 of create-release.yml).

Deverus Vue.js Style Guide

Guide for developing Vue.js applications.

v. 0.0.1

Vue.js is an amazing framework, which can be as powerful as Angular or React, the two big heavy hitters in the world of front-end frameworks.

However, most of Vue's ease-of-use is due to the use of Observables - a pattern that triggers re-renders and other function calls with the reassignment of a variable.

NetworkManager WiFi Power Saving

NetworkManager supports WiFi powersaving but the function is rather undocumented.

From the source code: wifi.powersave can have the following value:

NM_SETTING_WIRELESS_POWERSAVE_DEFAULT (0): use the default value
NM_SETTING_WIRELESS_POWERSAVE_IGNORE (1): don't touch existing setting
NM_SETTING_WIRELESS_POWERSAVE_DISABLE (2): disable powersave

Applied Functional Programming with Scala - Notes

1. Mastering Functions

A function is a mapping from one set, called a domain, to another set, called the codomain. A function associates every element in the domain with exactly one element in the codomain. In Scala, both domain and codomain are types.

val square : Int => Int = x => x * x

Rough Notes about CQRS and ES

Once upon a time…

I once took notes (almost sentence by sentence with not much editing) about the architectural design concepts - Command and Query Responsibility Segregation (CQRS) and Event Sourcing (ES) - from a presentation of Greg Young and published it as a gist (with the times when a given sentence was heard).

I then found other summaries of the talk and the gist has since been growing up. See the revisions to know the changes and where they came from (aka the sources).

It seems inevitable to throw Domain Driven Design (DDD) in to the mix.

a simple git branching model (written in 2013)

This is a very simple git workflow. It (and variants) is in use by many people. I settled on it after using it very effectively at Athena. GitHub does something similar; Zach Holman mentioned it in this talk.

Update: Woah, thanks for all the attention. Didn't expect this simple rant to get popular.

	using Gtk;

	public class Main {
	class AppStatusIcon : Window {
	private StatusIcon trayicon;
	private Gtk.Menu menuSystem;
	private AboutDialog aboutDialog;

	public AppStatusIcon() {
	/* Create tray icon */

	server {
	listen 80;
	server_name example.com;
	root d:/webs/example.com/www;

	index index.php index.html;
	try_files $uri $uri/ /index.php?$args;

	location ~ \.phpt?$ {
	try_files $uri @missing;

	<?php


	/**
	* @method onAttached(BaseControl $control, Nette\Application\UI\PresenterComponent $parent)
	* @method \BasePresenter getPresenter()
	*
	* @property \BasePresenter\|BaseControl[] $presenter
	* @property-read \BasePresenter\|BaseControl[] $presenter
	* @property \Nette\Templating\FileTemplate\|\stdClass $template

	git ls-tree -r --name-only HEAD \| while read filename; do
	echo "$(git log -1 --format="%at \| %h \| %an \| %ad \|" -- $filename) $filename"
	done