KlausTrainer

ExitPolicy accept *:22        # SSH
ExitPolicy accept *:43        # WHOIS
ExitPolicy accept *:53        # DNS
ExitPolicy accept *:79-81     # finger, HTTP
ExitPolicy accept *:88        # kerberos
ExitPolicy accept *:110       # POP3
ExitPolicy accept *:143       # IMAP
ExitPolicy accept *:194       # IRC
ExitPolicy accept *:220       # IMAP3
ExitPolicy accept *:389       # LDAP

KlausTrainer

%% @author Yariv Sadan <yarivsblog@gmail.com> [http://yarivsblog.com]
%% @copyright Yariv Sadan 2006-2007
%%
%% @doc  Smerl: Simple Metaprogramming for Erlang
%%
%%  Smerl is an Erlang library
%%  that simplifies the creation and manipulation of Erlang modules in
%%  runtime.
%%
%%  You don't need to know Smerl in order to use ErlyWeb; Smerl

KlausTrainer

#include <stdlib.h>
#include <string.h>

#include <crypt.h>

#include <shadow.h>

int check_password(const char *plain_password, const char *crypt_password)
{
	return strcmp(crypt(plain_password, crypt_password), crypt_password) == 0;

KlausTrainer

#!/bin/sh

# Monitors the remaining battery capacity on a GNU/Linux system, and
# sends a desktop notification if the remaining capacity falls below a
# certain threshold.


WARNING_THRESHOLD=7 # percent
ICON="/usr/share/icons/gnome/scalable/status/battery-low-symbolic.svg"

KlausTrainer

" File: Comment.vim
"
" Purpose: functions to comment/uncomment lines
"
" Author: Ralf Arens <ralf.arens@gmx.de>
"
" Last Modified: 2001-06-06 22:20:23 CEST


" All functions support comment styles, these are:

KlausTrainer

diff --git a/test/couch_doc_json_tests.erl b/test/couch_doc_json_tests.erl
index 56587cd..85a931a 100644
--- a/test/couch_doc_json_tests.erl
+++ b/test/couch_doc_json_tests.erl
@@ -17,9 +17,10 @@
 
 
 json_doc_test_() ->
+    TestCtx = test_util:start(?MODULE),
     {

KlausTrainer

diff --git a/test/couch_doc_json_tests.erl b/test/couch_doc_json_tests.erl
index 56587cd..037886f 100644
--- a/test/couch_doc_json_tests.erl
+++ b/test/couch_doc_json_tests.erl
@@ -17,9 +17,10 @@
 
 
 json_doc_test_() ->
+    TestCtx = test_util:start_couch(),
     {

KlausTrainer

==> couch_log (eunit)
    Running test function(s):
======================== EUnit ========================
  There were no tests to run.
==> couch (eunit)
    Running test function(s):
      couch_task_status_tests:couch_task_status_test_/0
======================== EUnit ========================
CouchDB task status updates
  couch_task_status_tests:58: should_register_task...ok

KlausTrainer

==> couch_log (eunit)
    Running test function(s):
======================== EUnit ========================
  There were no tests to run.
==> couch (eunit)
    Running test function(s):
      couchdb_os_daemons_tests:os_daemons_test_/0
======================== EUnit ========================
OS Daemons tests
  undefined

KlausTrainer

Design Ops – Design Systems Ops for the rest of us

As many others I have read @kaelig's post Introducing Design Systems Ops with great joy. My head was in danger of falling off from all the nodding and seeing my past years' work reflected in it <3

But there is this one thing that doesn't sit right with me:

who will bridge the gap between the design systems team and the engineering team?

It implies that there is a "design systems team". That might be a thing for very large companies – to quote Jina's presentation on Living Design Systems: