Skip to content

Instantly share code, notes, and snippets.

View sebs's full-sized avatar
🌈
@127.0.0.1

Sebastian Schürmann sebs

🌈
@127.0.0.1
View GitHub Profile
@sebs
sebs / bbrp.txt
Last active August 29, 2015 14:06
--OFFICIAL BOMBERS BAR CUSTOMER SURVEY--
---YOUR SATISFACTION IS OUR GUARANTEE----
Name:
Location of incident:
Total value lost:
---------------------------------------------------------
1. Please identify the nature of the service received: (Choose one)
@sebs
sebs / xpbooks.md
Last active September 29, 2019 07:01

To pair or not to pair

That is not a Question

Pairprogramming is one of the oldest practices known from XP and probably around way longer that any agile hype has been. Architectures and projects get more complex and large year by year and there is some evidence that problem solving is indeed easier and less error prone when executed as a group effort. This talk will outline the relationship of pairing to other agile practices such as Sprints, Daily Standups and Retrospectives. It is simply putting another, short cycled, loop in place to speed up problem solving and reducing bugs in produced code. However the narrative of software development tells us a great deal of (war)stories about solo coders saving the world in a lone effort. This is very misleading and might create a number of wrong assumptions about the craft in software development in general and could scare of interested young gun developers.

Pairing and in general working as a team can puts a highly effective and fun perspective on develo

// you can use console.log for debugging purposes, i.e.
// console.log('this is a debug message');
function solution(X, A) {
// write your code in JavaScript (ECMA-262, 5th edition)
var isNotEqual = 0;
A.forEach(function(item) {
if (item !== X) {
isNotEqual++;
}
@sebs
sebs / largejs.md
Last active August 29, 2015 14:07

Surviving large scale Javascript projects

After a bunch of projects beyond the size of 500k loc in more than one decade, there is a bunch of good practices that we, the developers of 2014 can employ from from day1 in our projects to keep code maintainable after a while. The development landscape for javascript has changed drastically and this could be reflected in daily practices. I want to highlight some of the practices we can employ in 2014 with a modern development stack, such as

  • Splitting front- and backend for faster development cycles
  • Using static code analysis to keep code clean
  • Automate processes and procedures to ensure the same level of quality
  • use component and module systems to keep your code lean and mean
  • Write tests - to avoid repeating errors and allow for cooler designs
  • CI/CD all the stuff for early feedback
64 bytes from 173.194.113.152: icmp_seq=14319 ttl=56 time=905.676 ms
64 bytes from 173.194.113.152: icmp_seq=14320 ttl=56 time=321.694 ms
Request timeout for icmp_seq 14321
64 bytes from 173.194.113.152: icmp_seq=14322 ttl=56 time=69.335 ms
Request timeout for icmp_seq 14323
Request timeout for icmp_seq 14324
64 bytes from 173.194.113.152: icmp_seq=14325 ttl=56 time=112.413 ms
64 bytes from 173.194.113.152: icmp_seq=14326 ttl=56 time=34.976 ms
Request timeout for icmp_seq 14327
Request timeout for icmp_seq 14328
traceroute to google.de (173.194.113.151), 64 hops max, 52 byte packets
1 homebox (192.168.1.1) 66.961 ms 74.533 ms 85.284 ms
2 62.52.200.134 (62.52.200.134) 163.113 ms 161.013 ms 102.883 ms
3 ae4-118.01.crju.0048-01.ham.de.bb.telefonica.de (62.109.117.254) 100.709 ms 148.442 ms 62.551 ms
4 62.53.12.101 (62.53.12.101) 112.042 ms 233.268 ms 148.515 ms
5 ae1-0.0001.prrx.01.ham.de.bb.telefonica.de (213.191.66.154) 107.003 ms 122.079 ms 80.346 ms
6 72.14.223.108 (72.14.223.108) 146.073 ms 160.366 ms 155.014 ms
7 209.85.249.126 (209.85.249.126) 109.059 ms 324.148 ms 412.463 ms
8 72.14.235.215 (72.14.235.215) 127.614 ms 227.757 ms 230.225 ms
9 ham02s11-in-f23.1e100.net (173.194.113.151) 151.734 ms 222.205 ms 252.812 ms
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head> <meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
{block:Description}<meta name="description" content="{MetaDescription}" />{/block:Description}
<!-- DEFAULT COLORS -->
<meta name="color:Light" content="#fff000" />
<meta name="color:Dark" content="#19C2FF" />