!Map:[["42-first-principles",{"subtitle":"A New Year's resolution","title":"42 first principles","abstract":"In 2022 I am turning 42 and therefore I am writing down my 42 first principles.","date":"2022-01-04T00:00:00.000Z","html":"\n

First Principles<\\/h2>\n
\n
Privilege<\\/a><\\/li>\n
Push to deploy<\\/a><\\/li>\n
5 whys<\\/a><\\/li>\n
The 20 percent trick to continuously keep learning<\\/a><\\/li>\n<\\/ol>\n","slug":"42-first-principles","hero":"!undefined"}],["I-make-euro-101750-in-non-monetary-compensation-a-year",{"title":"I make €101,750 in non-monetary compensation a year","subtitle":"Some thoughs on salary.","abstract":"Salary is probably one of the most dreadful topics, especially because it is a hygiene factor: earning not enough money will affect your satisfaction greatly, but earning more than you need won't improve your performance equally strong.\n","date":"2016-12-27T14:00+02:00","html":"\n
\n
$\"Vegetables$ <\\/picture><\\/aside>\n<\\/p>\n
\n Salary is probably one of the most dreadful topics, especially because it is a\n hygiene factor<\\/a>: earning not enough<\\/em> money will affect your satisfaction\n greatly, but earning more than you need won't improve your performance equally\n strong.\n<\\/p>\n
What is enough?<\\/h2>\n\n Let's talk a little bit about enough<\\/em>: the actual sum that you need to live\n depends on your fixed costs for basics like food, rent and savings for your\n retirement. If you have kids or other relatives to take care of, add this on\n top. Once those are paid you usually spend money on vacation, hobbies, and other\n activities like going to a concert, eating out, etc. Your enough<\\/em> quickly\n amounts to a sum that is already greater than the average salary in Germany\n (roughly €44,000 per year gross<\\/a>). But let's take that sum as enough<\\/em>.\n<\\/p>\n
\n Of course, I don't want to make what is enough<\\/em> but optimize for what is\nadequate<\\/em> for my position. But how much exactly is that? If we take open salary\n examples from around the world, many feature a market-average base-salary<\\/em>:\n developers are rare, thus they will earn more money than accountants. It is easy\n to get an overview about the typical salary for your market by looking at sites\n like glassdoor<\\/a>; for Germany the salary overview by Robert Half<\\/a> is\n very helpful if your industry is IT.\n<\\/p>\n
\n Where you are in the range depends on many factors, mostly experience, but even\n greater, your ability to (over-)sell yourself has a big impact on your salary\n especially in Germany, where you rarely find a role which compensation is made\n public in the job offer. The motivation to make compensations an individual\n agreement seems obvious: to save the company money, because they can try to\n negotiate the lowest possible salary for each employee. This is a fallacy,\n though. Studies show<\\/a> that making compensation transparent and comparable\n within an organization, will save money.\n<\\/p>\n
The gap between enough<\\/em> and adequate<\\/em> is your playing field!<\\/h2>\n
\n It's important to remember: monetary compensation has no benefit, above the\n individual threshold that is perceived to be enough<\\/em>. For organizations that\n hire talent that is in high demand it is important to understand that you need\n to match this threshold. But:<\\/strong> the gap between enough<\\/em> and adequate<\\/em> is\n your playing field; you can't keep employees below their enough<\\/em> for a\n sustainable amount of time, but they are flexible in the range above that.\n<\\/p>\n
\n Organizations can even overcompensate here, and this is what this blog post is\n about. Don't get me wrong, it's not about sugarcoating low salaries by just\n giving them another name. It's about understanding that the money a company\n spends on salary can be spent—in parts—in better ways. For companies this can\n make a big difference, increase your runway (the amount of time until your\n startup goes out of business), hire more talent, invest more in new products,\n etc.\n<\\/p>\n
I make €101,750 in non-monetary compensation a year<\\/h2>\n
\n There is real money to make, if you find the perks, that really matter (not\n foosball tables and fruit baskets). To give you a concrete example, I compiled\n the list of my non-monetary compensations and assigned a price tag to them.\n<\\/p>\n
\n | Perk | Price tag (€\\/year) |\n | ----------------------------------------------------------------------------------- | -----------------: |\n | Shares (real shares, not VESOP) | 20,000 |\n | Work where I want (no commute!) | 10,000 |\n | A job with a purpose (we turn organizations into a place where people love to work) | 10,000 |\n | Awesome team | 10,000 |\n | No estimates | 5,000 |\n | Unlimited vacation | 5,000 |\n | Being my own boss (work self-directed, voluntarily, how and when I want) | 5,000 |\n | No stupid meetings | 5,000 |\n | Working with tech I love | 5,000 |\n | The hardware I want | 3,000 |\n | Conference + Usergroups expenses covered | 2,500 |\n | Getting to meet awesome people | 2,500 |\n | 0% Bureaucracy | 2,500 |\n | No VC-Invest | 2,500 |\n | No stupid KPIs | 2,500 |\n | Customer-driven development | 2,500 |\n | Never wear a suit | 2,000 |\n | No politics | 1,500 |\n | Google Docs | 1,200 |\n | Slack (No more emails) | 1,200 |\n | Transparency | 1,000 |\n | Company Phone Plan | 600 |\n | No time tracking | 500 |\n | Company Credit Card (no questions asked expenses) | 500 |\n | Bahncard 50 | 250 |\n<\\/p>\n
\n The total of the list above sums up to €101,750 per year in non-monetary\ncompensation!<\\/strong> Which makes me a happy man to get a compensation in total which\n is way above the market average for a comparable position.\n<\\/p>\n
\n The tricky part is, especially when talking to developers: they are\n bird-in-the-hand-people and it will take some effort to have this talk about a\n lower-than-average fixed salary with them. This will greatly affect your hiring,\n especially if you are secretive about your organization. Because no one will\n believe the advertorial speak of a founder because of what I described earlier:\n they expect tactics to reduce salary behind it. A better approach will be to be\n open about your culture and encourage your employees to evangelize working at\n your company. See? Openness and transparency, they are key for the next\n generation of organizations.\n<\\/p>\n
\n Yes, some of the perks listed above are real spendings for the company, but the\n net-worth of an Euro spent there is €1 compared to an Euro spent with my net\n salary will equal roughly €0.49. So in the end, both the company and me will\n benefit greatly from having this discussion.\n<\\/p>\n","slug":"I-make-euro-101750-in-non-monetary-compensation-a-year","hero":"!undefined"}],["advent-of-code-2020",{"subtitle":"End-of-year code katas","title":"Advent of Code 2020","abstract":"I am participating in AOC again","date":"2020-12-07T08:00:00.000Z","html":"\n
\n For the third year now I am participating in\n Advent of Code<\\/a>, which provides a daily programming\n challenge with increasing difficulty.\n<\\/p>\n
\n I am publishing my solutions written in TypeScript and following TDD\n on GitHub<\\/a>.\n<\\/p>\n","slug":"advent-of-code-2020","hero":"!undefined"}],["agile-cologne-xxl-2016",{"title":"Agile as a starter for organizational transformation?","abstract":"Impressions from the Agile Cologne XXL 2016","date":"2016-10-03T18:00:00.000Z","html":"\n
\n
$\"Agile$ <\\/picture><\\/aside>\n<\\/p>\n
\n I was a first-timer at this years Agile Cologne XXL<\\/a>, a two-day open-space\n dedicated to the exchange about the Agile Movement<\\/a>. Needless to say I was\n not sure, what to expect, given that I didn't know anybody from the roughly 80\n attendees. But it turned out to be a very well organized event and I had two\n great days, learning and sharing in an open-space format (you can find the\n session plans here: Sunday<\\/a>, Monday<\\/a>). Most of the attendees were\n either scrum masters, product owners or consultants that teach people how to\n fill this roles. Tech people were rather underrepresented, which actually is a\n good thing: I find getting to know other perspectives to be very helpful in your\n day to day work. Especially we as developers are notoriously sticking to \"our\n people\" … if we leave our workplace at all<\\/em>.\n<\\/p>\n
Agile<\\/em> as a starter for organizational transformation?<\\/h2>\n
\n Now for the part that kept me busy during these two days; a lot of the sessions\n dealt with variants of this question:\n<\\/p>\n
\n
\n How can my team and I work in an agile fashion, while the rest of my\n organisation is not agile?\n <\\/p>\n<\\/blockquote>\n
\n The experience of many attendees is, that many companies are running their agile\n projects mainly for two reasons that are driven by management\n<\\/p>\n
\n
increase the output of IT projects,<\\/li>\n
make more profit.<\\/li>\n<\\/ol>\n
\n
$\"1nwNT2FhSgjq9FHogVI87dw\"$ <\\/picture><\\/aside>\n<\\/p>\n
\n Oftentimes it seems to be a decision based on hearsay (\"We've heard about this\nnew thing, that everyone else does, so lets do it, too!\"<\\/a>). Improving\n product quality and customer satisfactions rarely are the driving factors nor is\n improving the working conditions for employees.\n<\\/p>\n
\n The missing understanding of the core values behind the agile movement and the\n disposition as experiments obviously leads to a lot of friction and conflicts\n between the agile teams and the rest of the company and puts these teams under\n extra pressure. Now they are not only quested with the success of the project\n using a new way to work with which they have no experience but with leading the\n implementing agile within the whole organization.\n<\\/p>\n
\n These endeavors are bound to fail and the failure will be attributed to\n shortcomings of the agile methodology and not to the inability of classical,\n hierarchical structures to support agile teams at all.\n<\\/p>\n
\n To ask for advice how to make these agile teams or projects \"work\" in these\n circumstances is one option, but that does not fix the root cause of the\n problem: the organization itself.\n<\\/p>\n
\n Network organizations are an enabler for agility, self-organisation and creates\n a focus on delivering customer value. These are environments in which agile\n teams can thrive and will be successful.\n<\\/p>\n
\n So I set out and collected problems agile teams face in order to show, that\n there are indeed solutions to these problem, but they usually are not that\n obvious and need to be applied at a different level in order to become\n effective.\n<\\/p>\n
\n
$\"1woxzYPiopsfBm4nwPIOT5Q\"$ <\\/picture><\\/aside>\n<\\/p>\n
\n You can find the long list here<\\/a>, and I'm sure it can easily be extended\n even further. After I had this material, I used the evening in the hotel to\n compile our tools and measures of choice we use to fix these problems. I wanted\n to show, that there is a solution to every single problem. It might not be\n simple, but we've done it in the past. This flipchart<\\/a> gives you an\n idea. \"Unfortunately\" we had a very lively discussion, so the note-taking-part\n on my side came a little short but I was able to show a fix for every problem,\n and I might go into some of them in the comments, if you are interested.\n<\\/p>\n
Agile<\\/em> is a seed, and seeds need a soil<\\/h2>\n
\n My takeaway from the conference is that agile practitioners need to identify the\n root causes for the problems and stop trying to handle the symptoms.\n<\\/p>\n
\n You can't just plant an agile project into your organization without providing\n the grounds for it to grow roots.\n<\\/p>\n","slug":"agile-cologne-xxl-2016","hero":"!undefined"}],["alle-iso-dateien-in-einem-verzeichnis-nach-utf-8-konvertieren",{"title":"Alle ISO-Dateien in einem Verzeichnis nach UTF-8 konvertieren","abstract":"Dieses Bash-Script konvertiert alle Nicht-UTF-8-Dateien in einem Verzeichnis und in allen Unterverzeichnissen nach UTF-8.","date":"2010-05-13T00:00:00.000Z","lang":"de","html":"\n
\n Dieses Bash-Script konvertiert alle Nicht-UTF-8-Dateien in einem Verzeichnis und\n in allen Unterverzeichnissen nach UTF-8.\n<\\/p>\n
find .\\/ -type f -name \".php\" \\\n<\\/span> | xargs file \\\n<\\/span> | grep ISO-8859 \\\n<\\/span> | awk '{print substr( $1, 0, length($1) - 1); }' \\\n<\\/span> | xargs -i recode ISO-8859-1..UTF-8 {}\n<\\/span><\\/code><\\/pre>\n","slug":"alle-iso-dateien-in-einem-verzeichnis-nach-utf-8-konvertieren","hero":"!undefined"}],["an-everyone-culture",{"title":"An Everyone Culture","abstract":"Book review of An Everyone Culture by Robert Kegan and Lisa Laskow Lahey\n","date":"2016-09-10T16:00:00.000Z","html":"\n
\n In An Everyone Culture<\\/a> the authors Robert Kegan and Lisa Laskow Lahey<\\/a>\n explore Deliberately Developmental Organizations<\\/em> (DDOs).\n<\\/p>\n*
\n In these organizations adult development<\\/em> is part of the core business model:\n they don't invest into the personal development of their employees because they\n must<\\/em> but because they believe that there is a fundamental different concept of\n the employee: they are part of the organization with all their warts<\\/em>. The idea\n is: in many organizations a lot of effort is invested into appearing to be\n perfect or flawless, to cover up ones insecurities and to cover for others\n insecurities (\"I let you get through with this<\\/em> because you will do the same\n for me on another occasion\"). The authors call this having a second, unpaid\njob<\\/em>. How organizations where able to eliminite this second, unpaid job by\n bringing your full self to work in order to work on your shortcomings on company\n time is explained with a lot of real-life examples.\n<\\/p>\n
\n You get to look inside three organizations from completely different industries:\n movie-theaters \\/ real estate, hedge fund managament, and IT. You get to\n experience working in such an environment basically from a first person view and\n are taken directly into real situations. All have one astounding similarity in\n common: these organizations have created a safe environment to be yourself and\n be open about your problems. They go even so far to make them publically\n available for everyone in the organization to look up. And this is the crucial\n part: creating a nurturing and helpful environment is not easy to build, and it\n changes the understanding of what being at work<\\/em> means so radically, that it\n does not fit everybody. Constantly working on yourself, personally and\n professionally, is nothing everybody is able to do. But the results are\n fascinating; they are only postive in this book, though.\n<\\/p>\n
\n The second important concept in the book is the removal of professional\n seniority. The idea that one can keep working in your job basically forever is\n discarded. Which makes perfectly sense today because of two things: no job role\n will be there forever and not change, things you've learned two years ago are\n soon outdated. But more important the longer you do a job the less creative and\n open you are for new and better ideas and change. In DDOs, as soon as you master\n your current role you are rotated to a coaching role for this position and after\n that assigned to a new role where you start over as a newbie<\\/em>. And this is true\n for every job in those organizations not only for those employees that want to\n work like this anyway. This creates a constant influx of new ideas in all parts\n of the organization and enabled the three examples in the book to become\n respected industry leaders.\n<\\/p>\n
\n I've taken away a lot of new ideas about how organizations can be run, and\n learned how attractive personal development in the context of your organization\n can be and that the benefits are bigger then I would have estimated.\n<\\/p>\n
\n This book is also a great example for the saying \"Culture eats strategy for\n breakfast\": no strategy can deal with crisis like a team where everybody knows\n everyones shortcomings and how to work with them.\n<\\/p>\n
Highly recommended!<\\/p>\n","slug":"an-everyone-culture","hero":"!undefined"}],["ant-build-commons-von-qafoo",{"title":"Ant Build Commons von qafoo","abstract":"Die qafoo GmbH aus Gelsenkirchen, ein Zusammenschluss von vier deutschen PHP-Experten liefert mit den Ant Build Commons einen Standard-Satz an Build-Task für Ant, die alle wichtigen Aufgaben zum Prüfen, Testen und Veröffentlichen in PHP-basierten Projekten abdecken.","date":"2012-09-14T00:00:00.000Z","lang":"de","html":"\n
\n Die qafoo GmbH<\\/a> aus Gelsenkirchen, ein Zusammenschluss von vier deutschen\nPHP-Experten<\\/a> liefert mit den Ant Build Commons<\\/a> einen Standard-Satz an\n Build-Task für Ant, die alle wichtigen Aufgaben zum Prüfen, Testen und\n Veröffentlichen in PHP-basierten Projekten abdecken.\n<\\/p>\n
\n
\n ABC (Ant Build Commons) aims to provide standard build tasks for web based\n projects. It started by supporting various different PHP related tools, but by\n now also support JavaScript and CSS related tools. This involves tools for\n verification, testing, static analysis, packaging, deployment and more.\n <\\/p>\n<\\/blockquote>\n
\n Sie liefern so eine einfach anpassbare Vorlage, um der Software-Qualität im\n eigenen Projekt einfach auf die Sprünge zu helfen.\n<\\/p>\n
Ausführliche Infos finden sich unter
http:\\/\\/abc.tools.qafoo.com\\/<\\/a>.<\\/p>\n
Der Quellcode des Projekts findet sich auf GitHub unter
https:\\/\\/github.com\\/Qafoo\\/build-commons<\\/a>.<\\/p>\n","slug":"ant-build-commons-von-qafoo","hero":"!undefined"}],["auslastung-januar-2012-update",{"title":"Auslastung Januar 2012 Update","date":"2012-01-02T00:00:00.000Z","html":" $\"Auslastung\"$ \n
Über die Feiertage habe ich Auslastung<\\/a> um einige Funktionen erweitert.<\\/p>\n
Die wichtigsten Änderungen im Überlick:<\\/p>\n
\n
\n Es gibt nun eine übergeordnete Spalte für Termine und Feiertage (#6<\\/a> und\n #42<\\/a>)\n <\\/li>\n
Aufgaben können als \"im HomeOffice\" markiert werden (#43<\\/a>).<\\/li>\n
\n Namen von Personen, Units und Disziplinen müssen nicht mehr mindestens 3\n Buchstaben lang sein (#38<\\/a>).\n <\\/li>\n
Pläne mit vielen Daten laden jetzt auch (#31<\\/a>).<\\/li>\n<\\/ul>\n
Die Liste aller Änderungen findet sich in der Timeline<\\/a>.<\\/p>\n
\n Eine vollwertige Test-Version der Anwendung findet sich unter\n http:\\/\\/auslastung.coderbyheart.de\\/<\\/a>.\n<\\/p>\n
Screenshots? Gerne<\\/a>.<\\/p>\n","slug":"auslastung-januar-2012-update","hero":"!undefined"}],["auszeichnung-zum-top-coder-erhalten",{"title":"Auszeichnung zum Top Coder erhalten","abstract":"Beim Top Coder Gewinnspiel der Mayflower GmbH habe ich mit meiner Einreichung den ersten Preis gewonnen: ein iPad 2.\n","date":"2011-08-04T00:00:00.000Z","html":"
\n
\n
$\"Markus$ <\\/picture><\\/aside>\n<\\/p><\\/div>\n
\n Top Coder Gewinnspiel der Mayflower GmbH<\\/a> habe ich mit meiner Einreichung\n den ersten Preis gewonnen<\\/a>: ein iPad 2.\n<\\/p>\n
Für das Gewinnspiel mussten drei Aufgaben erfüllt werden:<\\/p>\n
\n
\n Gesucht wurde ein SQL-Query mit dem die Anzahl der P und H in einem String\n ermittelt werden kann.\n <\\/li>\n
\n Gesucht wurde eine Funktion, die aus einem gegebenen String durch\n vertauschen, hinzufügen und entfernen von Zeichen den Namen einer\n PHP-Funktion ermittelt.\n <\\/li>\n
\n Gesucht wurde die Größe eines MySQL-Indexes, wenn statt Bytes Trytes\n verwendet werden.\n <\\/li>\n<\\/ol>\n","slug":"auszeichnung-zum-top-coder-erhalten","hero":"!undefined"}],["autoload-environment-variables",{"title":"Autoload environment variables","abstract":"When developing stateless microservices it can be tedious to set up the correct environment variables. You can teach your bash\\/zsh to load them on a per directory basis.","date":"2016-04-07T00:00:00.000Z","html":"\n
\n When developing stateless microservices it can be tedious to set up the correct\n environment variables. You can teach your bash\\/zsh to load them on a per\n directory basis.\n<\\/p>\n
\n If you add this to your `.bashrc<\\/code> or .zshrc.local<\\/code> environment variables will\n be set from a file called .env<\\/code> if it is present in the directory you are\n cd-ing into:\n<\\/p>\n`
`function readEnv\n<\\/span>{\n<\\/span> if [ -f $PWD\\/.env ]\n<\\/span> then\n<\\/span> cat $PWD\\/.env\n<\\/span> export $(cat $PWD\\/.env | xargs)\n<\\/span> fi\n<\\/span>}\n<\\/span>\n<\\/span>cd()\n<\\/span>{\n<\\/span> builtin cd \"$@\"\n<\\/span> readEnv\n<\\/span>}\n<\\/span>readEnv\n<\\/span><\\/code><\\/pre>\nIn my project directory I have a .env<\\/code> file with these contents:<\\/p>\n`
export MY_FOO_ENV=bar\n<\\/span>echo MY_FOO_ENV=$MY_FOO_ENV\n<\\/span><\\/code><\\/pre>\nNow everytime I run my project the correct environment is set.<\\/p>\n","slug":"autoload-environment-variables","hero":"!undefined"}],["automagically-version-javascript-libraries-with-semantic-release",{"title":"Versioning JavaScript libraries with semantic-release","subtitle":"Automation","abstract":"In this post I will explain how you can automate releasing of your JavaScript libraries to npm.","date":"2018-08-07T16:00+02:00","html":"\n \n<\\/picture><\\/aside>\n<\\/p>\n\n We use semantic-release<\\/a>\n to automatically determine the next version of a library and<\\/strong> release it to\n our npm organization.\n<\\/p>\n \n The next version is determined by scanning the commit messages. They must follow\n the Angular commit message rules<\\/a>,\n and in every library a hook<\\/a> will\n check commit messages against these rules.\n<\\/p>\n \n \n ⚠️ The package.json<\\/code> of a project should only contain 0.0.0-development<\\/code> as\n the version<\\/code> property, semantic-release will ignore the value. ⚠️ Only the published package on npm will contain the correct version number.\n <\\/p>\n<\\/blockquote>\nHow to release a new version of a package<\\/h2>\nLet's assume we have a library, which has the npm version 2.3.4<\\/code>.<\\/p>\n\n A new version will be publish by the respective project's CI run. All you have\n to do is to use commit messages that follow the\n schema describe here<\\/a>.\n<\\/p>\n There are three commit messages that will trigger a release:<\\/p>\n Patch release:<\\/strong><\\/p>\n fix: <commit message>\n<\\/span><\\/code><\\/pre>\nFeature release:<\\/strong><\\/p>\nfeat: <commit message>\n<\\/span><\\/code><\\/pre>\nBreaking Release:<\\/strong><\\/p>\n<scope>: <commit message>\n<\\/span>\n<\\/span>BREAKING CHANGE:\n<\\/span>\n<\\/span><description of breaking change>\n<\\/span><\\/code><\\/pre>\n⚠️ Note that any other<\\/strong> commit message format will not trigger<\\/strong> a release.<\\/p>\nPatch release 🐞 (fix<\\/code>) 2.3.4 -> 2.3.5<\\/code><\\/h3>\n\n 👉 A fix is a change to the implementation which removes a bug without\nchanging the public API<\\/strong> (method names and signatures, exports) of the library.\n The consumer of the library must not need to change their implementation when\n installing the fixed version.\n<\\/p>\n \n \n<\\/p>\n \n To release a fix (which will update the version from 2.3.4<\\/code> to 2.3.5<\\/code>, use the\n type fix<\\/code> in the commit message:\n<\\/p>\nfix: <commit message>\n<\\/span><\\/code><\\/pre>\n\n You can optionally add a scope, which is a lowercase string used to identify the\n affected component<\\/em>.\n<\\/p>\nfix(<scope>): <commit message>\n<\\/span><\\/code><\\/pre>\nScopes are useful when the project is rather big.<\\/p>\nFeature release 🚀 (feat<\\/code>) 2.3.4 -> 2.4.0<\\/code><\\/h3>\n\n 👉 A feature is a change to the implementation of a library which adds\n additional functionality without changing the public API<\\/strong> of the library. You\n may add new exports, methods and even extra, optional method arguments, but the\n consumer of the library must not need to change their implementation when\n installing the library with the new feature.\n<\\/p>\n \n \n<\\/p>\n \n To release a feature (which will update the version from 2.3.4<\\/code> to 2.4.0<\\/code>, use\n the type feat<\\/code> in the commit message:\n<\\/p>\nfeat: <commit message>\n<\\/span><\\/code><\\/pre>\nYou can optionally add a scope as well.<\\/p>\nBreaking Release 🚨 (BREAKING CHANGE:<\\/code>) 2.3.4 -> 3.0.0<\\/code><\\/h3>\n\n 👉 Every time the public API of the library changes in a way that requires the\n consumer to update their implementation you must mark the change as\nbreaking<\\/strong>. This can happen if method names and arguments are renamed,\n previously optional arguments become required, arguments get removed, classes\n get renamed. Even if the change is very small, as soon as you are breaking the\n library's contract<\\/em> (it's public API) it is considered a breaking change,\n according to semver<\\/a>.\n<\\/p>\n \n \n<\\/p>\n \n To release a breaking release (which will update the version from 2.3.4<\\/code> to\n 3.0.0<\\/code>, use the text BREAKING CHANGE:<\\/code> (followed by a space of two new-lines)\n in the commit message:\n<\\/p>\n refactor: <commit message>\n<\\/span>\n<\\/span>BREAKING CHANGE:\n<\\/span>\n<\\/span><description of breaking change>\n<\\/span><\\/code><\\/pre>\nYou can optionally add a scope as well.<\\/p>\n \n Not that in the case of a breaking release the message type (here refactor<\\/code>)\n can be any valid type.\n<\\/p>\nTypical changes<\\/h2>\nUpdated dependencies<\\/h3>\n\n If you are manually updating dependencies in a library, you should commit the\n change as a fix, so that consumers are also using the updated dependencies.\n<\\/p>\n Refactoring<\\/h3>\n\n If you do a pure refactoring of a library without changing the features and the\n public API but<\\/strong> want to use the refactored version in your consumers, commit\n the refactoring as a feature. After all, you are improving the library which\n qualifies as a feature, e.g. it could be a performance-improvement.\n<\\/p>\nHow releases are published<\\/h2>\n\n After you have pushed your changes to the remote repository, a job will be run\n on the CI runner. If the job completes successfully (e.g. if all tests pass and\n the linter does not report any errors), semantic-release<\\/code> will determine the\n next version to be released.\n<\\/p>\n \n The \"highest\"<\\/em> commit will win<\\/em> (fix<\\/code> > feat<\\/code> > breaking change<\\/code>). This\n means if the list of commit messages since the last release contains only<\\/em>\n fixes, the patch version will be incremented (2.3.4 -> 2.3.5<\\/code>). If the list of\n commits contains at least one new feature, then the minor version will be\n incremented and the patch version will be set to 0<\\/code> (2.3.4 -> 2.4.0<\\/code>). If the\n list of commits contains at least one breaking change, then the major version\n will be incremented and the minor and patch versions will be set to 0<\\/code>\n (2.3.4 -> 3.0.0<\\/code>).\n<\\/p>\n\n This new version will be written to the package.json<\\/code> and the package will be\n published to the npm registry<\\/a>.\n<\\/p>\n Happy releasing!<\\/h2>\n\n \n<\\/p>\n","slug":"automagically-version-javascript-libraries-with-semantic-release","hero":"!undefined"}],["aws-sdk-v3",{"subtitle":"Cloud Native","title":"Migrating to AWS SDK v3 for JavaScript","abstract":"Notes on migrating Bifravst to the completely rewritten AWS SDK for JavaScript\\/TypeScript","date":"2021-01-05T16:00:00.000Z","html":"\n \n <\\/picture><\\/aside>\n<\\/p>\n\n AWS recently\n announced the general availability<\\/a>\n of the\n version 3 of their SDK for JavaScript<\\/a>.\n<\\/p>\n The most notable changes are<\\/p>\n \n \n the switch to providing modular packages: this allows to reduce the overall\n size of the dependencies and makes bundling, for example for web applications,\n faster,\n <\\/li>\n first-class Promise support: the infamous .promise()<\\/code> is no more,<\\/li>\n \n first-class TypeScript support: the SDK has now been written in TypeScript, so\n the definitions (which are maintained in\n DefinitlyTyped<\\/a> for\n version 2 of the SDK) will not longer lag behind,\n <\\/li>\n a new middleware stack that improves debuggability,<\\/li>\n \n the ability to abort pending requests<\\/a>\n which is especially interesting for web applications.\n <\\/li>\n<\\/ul>\n\n In this blog post I will summarize my findings when migrating the AWS flavour of\n Bifravst<\\/a> to version 3 of the AWS SDK.\n<\\/p>\n Command<\\/em> is the new method<\\/em><\\/h2>\n\n Instead of calling methods on the client instance directly, e.g.\n s3.putObject().promise()<\\/code>, in v3 the client's send()<\\/code> method has to be called\n with an instance of a command<\\/em> for the operation:\n s3.send(new PutObjectCommand())<\\/code>.\n<\\/p>\n So the general pattern to migrate to v3 is:<\\/p>\n-<\\/span> service.operation()\n<\\/span><\\/span><\\/span><\\/span><\\/span>+<\\/span> service.send(new OperationCommand({}))\n<\\/span><\\/span><\\/span><\\/code><\\/pre>\n\n This worked in without issues in most cases. The arguments for the command class\n stay the same. Operations without arguments need to get passed an empty object\n ({}<\\/code>).\n<\\/p>\nConstructing a client<\\/h3>\n\n Client instances are constructed as before using new<\\/code>. You always need to pass an object to the constructor, even if not providing any\n configuration.\n<\\/p>\nconst<\\/span> iot =<\\/span> new<\\/span> IoTClient<\\/span>(<\\/span>{<\\/span>}<\\/span>)<\\/span>;<\\/span>\n<\\/span><\\/code><\\/pre>\nCalling an operation<\\/h3>\nOperations are now called by sending<\\/em> a command<\\/em>:<\\/p>\nconst<\\/span> {<\\/span> things }<\\/span> =<\\/span> await<\\/span> iot.<\\/span>send<\\/span>(<\\/span>new<\\/span> ListThingsCommand<\\/span>(<\\/span>{<\\/span>}<\\/span>)<\\/span>)<\\/span>;<\\/span>\n<\\/span><\\/code><\\/pre>\n\n Here, again, you always need to pass an object to the constructor of the\n command, even if not providing any parameters to the operation.\n<\\/p>\nA complete example:<\\/h3>\n-<\\/span> import { Iot } from 'aws-sdk'\n<\\/span><\\/span><\\/span><\\/span><\\/span>+<\\/span> import {\n<\\/span><\\/span><\\/span><\\/span>+<\\/span> \tIoTClient,\n<\\/span><\\/span><\\/span><\\/span>+<\\/span> \tListThingsCommand,\n<\\/span><\\/span><\\/span><\\/span>+<\\/span> } from '@aws-sdk\\/client-iot'\n<\\/span><\\/span><\\/span><\\/span><\\/span>\n<\\/span>-<\\/span> const iot = new Iot()\n<\\/span><\\/span><\\/span><\\/span><\\/span>+<\\/span> const iot = new IoTClient({})\n<\\/span><\\/span><\\/span><\\/span><\\/span>\n<\\/span>-<\\/span> const { things } = await iot.listThings().promise()\n<\\/span><\\/span><\\/span><\\/span><\\/span>+<\\/span> const { things } = await iot.send(new ListThingsCommand({}))\n<\\/span><\\/span><\\/span><\\/code><\\/pre>\nUpdating imports<\\/h3>\n\n Instead of pulling the dependency from\n aws-sdk<\\/code><\\/a>, find the needed client\n package in the\n API reference for the v3 SDK<\\/a>,\n in the case above we need the\n @aws-sdk\\/client-iot<\\/code><\\/a>.\n<\\/p>\n \n Note:<\\/em> IoT<\\/code> now has a capital T<\\/code> at the end.<\\/p>\n<\\/blockquote>\n\n The IotData<\\/code> client from v2 is now located in\n @aws-sdk\\/client-iot-data-plane<\\/code><\\/a>\n and called IoTDataPlaneClient<\\/code>.\n<\\/p>\n IoT: Payload is now Uint8Array<\\/code><\\/h2>\n\n Some operations, like DescribeThingShadowCommand<\\/code>\n return a JSON string now as Uint8Array<\\/code><\\/a>.\n These need to be decoded using the TextEncoder util in Node.js:\n<\\/p>\n +<\\/span> import { TextDecoder } from 'util'\n<\\/span><\\/span><\\/span><\\/span><\\/span>\n<\\/span>-<\\/span> const { statusCode, body } = JSON.parse(Payload?.toString() ?? '')\n<\\/span><\\/span><\\/span><\\/span><\\/span>+<\\/span> const { statusCode, body } = JSON.parse(\n<\\/span><\\/span><\\/span><\\/span>+<\\/span> new TextDecoder('utf-8').decode(Payload),\n<\\/span><\\/span><\\/span><\\/span>+<\\/span> )\n<\\/span><\\/span><\\/span><\\/code><\\/pre>\n\n or the\n @aws-sdk\\/util-utf8-browser<\\/code><\\/a>\n helpers for browser applications:\n<\\/p>\n +<\\/span> import { toUtf8 } from '@aws-sdk\\/util-utf8-browser'\n<\\/span><\\/span><\\/span><\\/span><\\/span>\n<\\/span>-<\\/span> const { statusCode, body } = JSON.parse(Payload?.toString() ?? '')\n<\\/span><\\/span><\\/span><\\/span><\\/span>+<\\/span> const { statusCode, body } = JSON.parse(toUtf8(Payload?.toString() ?? ''))\n<\\/span><\\/span><\\/span><\\/code><\\/pre>\nNot in v3: StepFunctions<\\/h2>\n\n The StepFunctions client has not been ported to v3 because the service\n does not support CORS<\\/a>,\n because browsers cannot interact with it.\n<\\/p>\n S3<\\/h2>\ncreatePresignedPost<\\/h3>\nS3.createPresignedPost() is now in @aws-sdk\\/s3-presigned-post<\\/code><\\/p>\n-<\\/span> import { S3 } from 'aws-sdk'\n<\\/span><\\/span><\\/span><\\/span><\\/span>+<\\/span> import { S3Client } from '@aws-sdk\\/client-s3'\n<\\/span><\\/span><\\/span><\\/span>+<\\/span> import { createPresignedPost } from '@aws-sdk\\/s3-presigned-post'\n<\\/span><\\/span><\\/span><\\/span>+<\\/span> import { CreateJobCommand, IoTClient } from '@aws-sdk\\/client-iot'\n<\\/span><\\/span><\\/span><\\/span><\\/span>\n<\\/span>-<\\/span> const s3 = new S3()\n<\\/span><\\/span><\\/span><\\/span><\\/span>+<\\/span> const s3 = new S3Client({})\n<\\/span><\\/span><\\/span><\\/span><\\/span>\n<\\/span>-<\\/span> const { url, fields } = s3.createPresignedPost({\n<\\/span><\\/span><\\/span><\\/span>-<\\/span> Bucket: bucketName,\n<\\/span><\\/span><\\/span><\\/span>-<\\/span> Fields: {\n<\\/span><\\/span><\\/span><\\/span>-<\\/span> key: `${jobId}.json`,\n<\\/span><\\/span><\\/span><\\/span>-<\\/span> },\n<\\/span><\\/span><\\/span><\\/span>-<\\/span> })\n<\\/span><\\/span><\\/span><\\/span><\\/span>+<\\/span> const { url, fields } = await createPresignedPost(s3, {\n<\\/span><\\/span><\\/span><\\/span>+<\\/span> Bucket: bucketName,\n<\\/span><\\/span><\\/span><\\/span>+<\\/span> Key: `${jobId}.json`,\n<\\/span><\\/span><\\/span><\\/span>+<\\/span> })\n<\\/span><\\/span><\\/span><\\/code><\\/pre>\n\n Note:<\\/em> It was made async and the Key<\\/code> field needs to be at the top level.<\\/p>\n<\\/blockquote>\nSignatureDoesNotMatch error when uploading a file<\\/h3>\n\n There is currently a bug<\\/a>\n when uploading a file with a custom content-type. The workaround is to\n add a custom middleware that removes the extra header<\\/a>:\n<\\/p>\n s3.<\\/span>middlewareStack<\\/span>.<\\/span>add<\\/span>(<\\/span>\n<\\/span> (<\\/span>next<\\/span>)<\\/span> =><\\/span> async<\\/span> (<\\/span>args<\\/span>)<\\/span> =><\\/span> {<\\/span>\n<\\/span> delete<\\/span> args.<\\/span>request<\\/span>.<\\/span>headers<\\/span>[<\\/span>\"content-type\"<\\/span>]<\\/span>;<\\/span>\n<\\/span> return<\\/span> next<\\/span>(<\\/span>args)<\\/span>;<\\/span>\n<\\/span> }<\\/span>,<\\/span>\n<\\/span> {<\\/span> step<\\/span>:<\\/span> \"build\"<\\/span> }<\\/span>,<\\/span>\n<\\/span>)<\\/span>;<\\/span>\n<\\/span>\n<\\/span>await<\\/span> s3.<\\/span>putObject<\\/span>(<\\/span>{<\\/span>\n<\\/span> Bucket<\\/span>:<\\/span> bucket,<\\/span>\n<\\/span> Key<\\/span>:<\\/span> key,<\\/span>\n<\\/span> Body<\\/span>:<\\/span> body,<\\/span>\n<\\/span> ContentType<\\/span>:<\\/span> contentType,<\\/span>\n<\\/span>}<\\/span>)<\\/span>;<\\/span>\n<\\/span><\\/code><\\/pre>\nCustom signed HTTP requests<\\/h2>\n\n In case you need to construct your own signed requests, the AWS.Signers.V4<\\/code>\n have also been moved:\n<\\/p>\n-<\\/span> import * as AWS from 'aws-sdk'\n<\\/span><\\/span><\\/span><\\/span>-<\\/span> import { Credentials, Endpoint, HttpRequest } from 'aws-sdk'\n<\\/span><\\/span><\\/span><\\/span><\\/span>+<\\/span> import { SignatureV4 } from '@aws-sdk\\/signature-v4'\n<\\/span><\\/span><\\/span><\\/span>+<\\/span> import { Credentials, Endpoint } from '@aws-sdk\\/types'\n<\\/span><\\/span><\\/span><\\/span>+<\\/span> import { HttpRequest } from '@aws-sdk\\/protocol-http'\n<\\/span><\\/span><\\/span><\\/span>+<\\/span> import { parse } from 'url'\n<\\/span><\\/span><\\/span><\\/code><\\/pre>\nCredentials now longer have a class, but a type:<\\/p>\n-<\\/span> const credentials = new Credentials(AccessKeyId, SecretKey, SessionToken)\n<\\/span><\\/span><\\/span><\\/span><\\/span>+<\\/span> const credentials: Credentials = {\n<\\/span><\\/span><\\/span><\\/span>+<\\/span>\t accessKeyId,\n<\\/span><\\/span><\\/span><\\/span>+<\\/span>\t secretAccessKey,\n<\\/span><\\/span><\\/span><\\/span>+<\\/span>\t sessionToken,\n<\\/span><\\/span><\\/span><\\/span>+<\\/span> }\n<\\/span><\\/span><\\/span><\\/code><\\/pre>\nAlso the Endpoint<\\/code> class has been removed, so some URL parsing is nedded.<\\/p>\n-<\\/span>\tconst httpRequest = new HttpRequest(new Endpoint(endpoint), region)\n<\\/span><\\/span><\\/span><\\/span><\\/span>+<\\/span>\tconst httpRequest = new HttpRequest(\n<\\/span><\\/span><\\/span><\\/span>+<\\/span>\t\t((p: ReturnType<typeof parse>): Endpoint =>\n<\\/span><\\/span><\\/span><\\/span>+<\\/span>\t\t\t({\n<\\/span><\\/span><\\/span><\\/span>+<\\/span>\t\t\t\t...p,\n<\\/span><\\/span><\\/span><\\/span>+<\\/span>\t\t\t\tport: p.port !== null ? parseInt(p.port, 10) : undefined,\n<\\/span><\\/span><\\/span><\\/span>+<\\/span>\t\t\t} as Endpoint))(parse(endpoint)),\n<\\/span><\\/span><\\/span><\\/span>+<\\/span>\t)\n<\\/span><\\/span><\\/span><\\/code><\\/pre>\nFinally a signer can be created:<\\/p>\n-<\\/span>\tconst signer = new AWS.Signers.V4(httpRequest, 'appsync', true)\n<\\/span><\\/span><\\/span><\\/span><\\/span>+<\\/span>\tconst signer = new SignatureV4(httpRequest, 'appsync', true)\n<\\/span><\\/span><\\/span><\\/code><\\/pre>\nRemoved types<\\/h2>\n\n Some types have been removed or better, replaced with their idiomatic TypeScript\n equivalent.\n<\\/p>\n \n For example in the Timestream client, previously there was a\n type Records = Record[]<\\/code>, which now no longer exists:\n<\\/p>\n-<\\/span> import { TimestreamWrite } from 'aws-sdk'\n<\\/span><\\/span><\\/span><\\/span><\\/span>+<\\/span> import { _Record } from '@aws-sdk\\/client-timestream-write'\n<\\/span><\\/span><\\/span><\\/span><\\/span>\n<\\/span>-<\\/span>\treturn Records.filter(isNotNullOrUndefined) as TimestreamWrite.Records\n<\\/span><\\/span><\\/span><\\/span><\\/span>+<\\/span>\treturn Records.filter(isNotNullOrUndefined) as _Record[]\n<\\/span><\\/span><\\/span><\\/code><\\/pre>\n\n This needs a little bit of digging through the TypeScript definitions to figure\n out which types still exist and which need to be replaced.\n<\\/p>\n \n\n The migration was relatively straight forward and because of the BDD tests in\n the project this refactoring could be done without a hassle. I will keep\n updating this post in case there are more noteworthy findings.\n<\\/p>\n","slug":"aws-sdk-v3","hero":"!undefined"}],["backend-languages-panel-at-code-talks-hamburg-2018",{"title":"Backend languages panel at code.talks Hamburg 2018","subtitle":"Panel","abstract":"Extracts of a panel on backend languages at code.talks Hamburg 2018.","date":"2018-11-18T13:00+01:00","html":"\n \n <\\/picture><\\/aside>\n<\\/p>\n\n At code.talks Hamburg 2018<\\/a> I was in the panel about\n backend languages.\n<\\/p>\n https:\\/\\/twitter.com\\/coderbyheart\\/status\\/1053254437026914304?embed<\\/a><\\/p>\n You can see the whole session on YouTube:<\\/p>\n https:\\/\\/www.youtube.com\\/embed\\/7n3ROn3yABY<\\/a><\\/p>\n \n Here are the sections where I speak on behalf of the language that I love:\n JavaScript<\\/strong>!\n<\\/p>\n https:\\/\\/twitter.com\\/coderbyheart\\/status\\/1064131345058856961?embed<\\/a><\\/p>\n Where will JavaScript be in 5 years?<\\/h2>\nhttps:\\/\\/twitter.com\\/coderbyheart\\/status\\/1064131350767288321?embed&conversation=none<\\/a><\\/p>\n And will JavaScript still<\\/em> be there in 5 years?<\\/h2>\nhttps:\\/\\/twitter.com\\/coderbyheart\\/status\\/1064131358879031296?embed&conversation=none<\\/a><\\/p>\n Does JavaScript scale both in the technical sense and within teams?<\\/h2>\nhttps:\\/\\/twitter.com\\/coderbyheart\\/status\\/1064131366416195584?embed&conversation=none<\\/a><\\/p>\n Is JavaScript a good language for programming beginners?<\\/h2>\nhttps:\\/\\/twitter.com\\/coderbyheart\\/status\\/1064131378634268672?embed&conversation=none<\\/a><\\/p>\n \n Check out CodeDoor<\\/a> - they help people from\n underrepresented groups learn to program!\n<\\/p>\n Not everything<\\/em> is perfect with JavaScript<\\/h2>\nhttps:\\/\\/twitter.com\\/coderbyheart\\/status\\/1064131386318176257?embed&conversation=none<\\/a><\\/p>\n","slug":"backend-languages-panel-at-code-talks-hamburg-2018","hero":"!undefined"}],["backup-your-business",{"title":"Backup your business: Advice for non-technical co-founders","abstract":"How to make sure you never lose the source code of your business.\n","date":"2015-03-07T22:30:00.000Z","html":"\n \n <\\/picture><\\/aside>\n<\\/p>\n\n Software is an amazing thing: a few thousand lines of text can power an entire\n business. One thing should be obvious: make sure you never lose the source code\n of your business. This is something your technical co-founder will take care of\n from day one. And that creates a problem that I want to shed some light on.\n<\\/p>\n \n Making proper backups of software is a complicated task. And it usually involves\n setting up tools and processes that are created with developers in mind. It\n involves things like encryption, off-site copies, grandfathers, fathers and\n sons.\n<\\/p>\n \n If one day you and your technical co-founder part ways in a bad way, you will\n find it impossible to get hold of a copy of your companies most valuable asset\n that can be used to keep operating your business with another partner.\n<\\/p>\n \n You can prepare for this unlikely event, though. Do it in the beginning of your\n business and your technical co-founder will happily assist you in setting this\n up. He gets another level of safety and if you are not in an evil mindset there\n is no real argument why not to constantly ensure every co-founder of a business\n has unlimited access to a copy of the current source code.\n<\\/p>\n \n Your mileage may vary but here are some practical ideas how to set up an easy to\n use system:\n<\\/p>\n\n \n If you can, open-source your software and put it on GitHub. Make sure that\n this is your primary source code repository used by the development team to\n ensure it's up to date all the time.\n <\\/li>\n \n Have a daily ZIP archive of all your source code on a backup server. Make sure\n that this server is rented by your company not by your co-founder or his\n buddies. If you don't mind third-parties snooping through your files, use\n Google Drive, Dropbox or Amazon S3 for the backup. Then make daily backups of\n the files there to storage devices that only you have access to (flashdisk,\n external hard drives or your laptop).\n <\\/li>\n<\\/ul>\n\n Trust but verify<\\/strong>: Let a tech-savvy friend you trust verify the backups you\n have once in a while to get the extra certainty that you can't be left out in\n the cold.\n<\\/p>\n \n\n Photo credits:\n Five Days' Backup<\\/a> by\n daryl_mitchell<\\/a> (CC BY-SA 2.0)\n<\\/p>\n","slug":"backup-your-business","hero":"!undefined"}],["bash-absoluten-pfad-des-aktuellen-scripts-auslesen",{"title":"Bash: Absoluten Pfad des aktuellen Scripts auslesen","abstract":"Oft ruft man Bash-Scripte ja mit relativen Pfaden auf:","date":"2010-06-18T00:00:00.000Z","lang":"de","html":"\n Oft ruft man Bash-Scripte ja mit relativen Pfaden auf:<\\/p>\n $ .\\/util.sh\n<\\/span><\\/code><\\/pre>\n\n Dieses kleine Snippet liefert einem in diesem Fall den absoluten Pfad zum\n aktuellen Script.\n<\\/p>\n#!\\/bin\\/bash\n<\\/span>MYDIR=\"`cd $0; pwd`\"\n<\\/span>echo $MYDIR\n<\\/span><\\/code><\\/pre>\n\n Möchte man den absoluten Pfad zu einem Verzeichnis weiter oben, nimmt man dieses\n Snippet:\n<\\/p>\n#!\\/bin\\/bash\n<\\/span>MYDIR=`dirname $0`\n<\\/span>PARENT=\"`cd $MYDIR\\/..\\/; pwd`\"\n<\\/span><\\/code><\\/pre>\n","slug":"bash-absoluten-pfad-des-aktuellen-scripts-auslesen","hero":"!undefined"}],["bash-bestimmte-dateien-oder-verzeichne-beim-auto-vervollstandigen-ignorieren",{"title":"Bash: Bestimmte Dateien oder Verzeichnisse beim Auto-Vervollständigen ignorieren","abstract":"Die Bash hat eine tolle Funktion: Mittels der Tab-Taste erhält man eine Liste mit Dateien und Verzeichnissem im aktuell eingegeben Pfad-Abschnitt.\n","date":"2010-09-28T00:00:00.000Z","html":"\n\n Die Bash hat eine tolle Funktion: Mittels der Tab-Taste erhält man eine Liste\n mit Dateien und Verzeichnissem im aktuell eingegeben Pfad-Abschnitt.\n<\\/p>\n \n Allerdings nerven da z.B. Verzeichnisse wie .svn<\\/code> von Subversion, in die man\n normalerweise nie hinein navigieren möchte.\n<\\/p>\n Zu Hilfe kommt da die Umgebungsvariable FIGNORE<\\/code>.<\\/p>\n\n \n A colon-separated list of suffixes to ignore when performing filename\n completion (see READLINE below). A filename whose suffix matches one of the\n entries in FIGNORE is excluded from the list of matched filenames. A sample\n value is .o:~<\\/code>.\n <\\/p>\n<\\/blockquote>\n \n Ein praktischer Eintrag für Subversion ist dementsprechend: .svn<\\/code>. Unter Mac OS\n bietet sich noch an, .DS_Store<\\/code> hinzu zu nehmen.\n<\\/p>\n Diese Zeile wird dann in der Datei ˜\\/.profile<\\/code> oder ähnlich eingetragen:<\\/p>\n export FIGNORE=\".svn:.DS_Store\"<\\/code><\\/p>\n","slug":"bash-bestimmte-dateien-oder-verzeichne-beim-auto-vervollstandigen-ignorieren","hero":"!undefined"}],["bdd-book-formulation-review",{"title":"The BDD Books: Formulation","subtitle":"Book Review","abstract":"An indepth guide for software teams to engage all stakeholders in creating up-to-date documentation that drives tests","date":"2021-04-22T23:00+01:00","html":"\n \n <\\/picture><\\/aside>\n<\\/p>\n\n Let me start by stating something most of you most likely know, I am a big fan\n of Behavioural Driven Design (BDD),\n I have spoken about it at multiple conferences<\\/a>\n and I use it on a daily basis. Therefore I was really excited to learn from\n Gáspár<\\/a> and Seb<\\/a>\n who are without a doubt some of the most knowledgeable people to write about\n this topic ... which they are not shy to tell you directly in the beginning of\n the book:\n<\\/p>\n \n \n Together Seb and Gáspár have over 60 years of software experience which they\n put to good use developing and delivering training and coaching for\n organizations worldwide.\n <\\/p>\n<\\/blockquote>\n \n It's a somewhat bold disclaimer in the beginning of the book, and I wish they\n wouldn't have chosen this \"let me tell you...\" move, because the content in this\n book really speaks for itself.\n<\\/p>\nThe Book to understand the toolset Gherkin provides<\\/h2>\n\n Gherkin<\\/a> is a language to describe behaviour\n of any system<\\/em> in feature files with three words: Given<\\/strong>, When<\\/strong>,\n Then<\\/strong>. There, now you have learned<\\/em> the language, however it takes a lot of\n practice to apply this tool in practice. And here is where the book takes us on\n a journey with a team implementing a pizza ordering software.\n<\\/p>\n \n Along this example we learn the fundamentals of the language, and many hands-on,\n very well explained best practice on how to use Gherkin to not only describe the\n properties of the software system, but also how to do it in a way that enables\n all stakeholder to take part and in such a way that it creates a living\ndocumentation<\\/em>; one that never is outdated.\n<\\/p>\n \n This promise is magically and the authors manage to lift the curtain and share\n their years of experience with this tool.\n<\\/p>\n BDD is reverse decoupled TDD<\\/h2>\n\n Start with the end in mind.<\\/p>\n<\\/blockquote>\n \n As with test-driven-development (TDD), BDD is ideally written before the\n implementation, and this is one of the big take-aways for me: where I would TDD\n with small examples working towards a complete feature, BDD works best if the\n end-result is written first: if the Then ...<\\/em> is defined first, it is easier to\n focus only on the absolute necessary Given<\\/em>s and When<\\/em>s—a point that the\n books stresses at multiple occasions: focus on keeping scenarios brief (or\n BRIEF<\\/code>, the acronym that is used in the book).\n<\\/p>\nBDD is for everyone, and any time<\\/h2>\n\n You should pick up this book today and learn about this tool, because it can be\n introduced in a project at any time: a chapter about legacy code is included.\n<\\/p>\n \n I especially liked their description of how feature files can serve different\n audiences and pick them up where they need the documentation to be, for example\n using a different domain language, or (how I typically use BDD) on a lower\n level, without implementing steps but driving an API client.\n<\\/p>\n \n While most of the book centers around writing feature files that can be used to\n drive automation tests, the author specifically mention the importance of\n testers and their expertise, because it is not about automating tests, but about\n aligning all stakeholders and the software that is getting build:\n<\\/p>\n\n \n Never underestimate the domain knowledge of the people who worked on the\n project. Testers in particular will have acquired a deep understanding of the\n product through their time spent testing it.\n <\\/p>\n<\\/blockquote>\nWhen I read The BDD Books: FormulationThen I become a better Software Crafter<\\/h2>\n\n I really like the overall structure of the book, the chapters are not too long\n and don't overstretch their topic. Throughout the book the authors provide their\n personal view which helps to underline important aspects. It will be a good\n source to revisit again and again.\n<\\/p>\n\n The BDD Books: Formulation<\\/a> is available\n on LeanPub<\\/a> and\n on Amazon<\\/a>.\n<\\/p>\n \n I've read the Kindle version of the book which I would not fully recommend\n because even the smallest font size would not fit the feature listings on my\n screen (a 10th generation Kindle Paperwhite). This is fine if you are familier\n with the Gherkin syntax and can skim the feature definitions. I would recommend\n to read the PDF version which has a better layout, or get the printed version\n (from the PDF).\n<\\/p>\n","slug":"bdd-book-formulation-review","hero":"!undefined"}],["become-a-certified-software-craftsperson",{"title":"Become a Certified Software Craftsperson","subtitle":"One weird trick","abstract":"Follow this one weird trick to become a Certified Software Crafter","date":"2018-04-28T20:30+02:00","html":"\n \n <\\/picture><\\/aside>\n<\\/p>\nHere is a question for you to think about:<\\/p>\n\n How can I make a better job tomorrow?<\\/p>\n<\\/blockquote>\n \n Congratulations, I hereby certify you to be a full-fledged, badass Software\n Craftsperson. You are welcome! \n<\\/p>\n \n Do not let book authors, speakers, consultancies or anybody tell you which steps\n are required to be considered a true Software Crafter. It usually involves\n giving them money as the first step, so I would call them biased.\n<\\/p>\n \n\n Quite literally: we welcome everybody to join\n our community Slack<\\/a>, regardless of\n profession, experience, skin color, gender, or other attributes because we\n believe that only diversity will help us to find the best solutions to the big\n and small problems we are lucky to be facing every day.\n<\\/p>\n","slug":"become-a-certified-software-craftsperson","hero":"!undefined"}],["boosterconf-2023",{"title":"BoosterConf 2023","subtitle":"Conferences","abstract":"A review of BoosterConf 2023 in Bergen","date":"2023-04-07T14:00+01:00","html":"\n \n Last year was the first time for me attending\n BoosterConf<\\/a> and I was happy to re-visit it again this\n year.\n<\\/p>\n \n Around 400 participants gather in one of Norway's most beautiful cities:\n Bergen<\\/a>. During three conference days, the\n BoosterConf program offers keynotes, lightning talks, experience reports,\n workshops and even an OpenSpace during one afternoon. The program is very\n varied, and offers content and inspiration for the entire team. That is also the\n reason why the audience was a good mixture of all roles involved in digital\n projects.\n<\\/p>\n \n The agenda offers a nice pacing and long enough breaks so there is time to\n connect with other attendees and reflect on what was just heard.\n<\\/p>\n \n I really liked the opportunity to discuss relevant topics with participants\n during the open space, which this year was 3 hours long without any program at\n the side, so there was no distraction. I wished the OpenSpace was however split\n in multiple rooms and not run as multiple chair circle in the big hall.\n<\\/p>\n \n The conference has already published the video recordings on\n Vimeo<\\/a>, so you can get yourself an impression of\n the talks. However, the workshops and the OpenSpace was not recorded.\n<\\/p>\n \n Lisi has also written about her impressions on her blog:\n Lisi Hocke: Booster Conference 2023 - Changing Perspectives<\\/a>.\n<\\/p>\n \n Here are the sessions that I attended; I shared them live on Mastodon using the\n hashtag #BoosterConf<\\/a>.\n<\\/p>\n Day 1<\\/h2>\nhttps:\\/\\/chaos.social\\/@coderbyheart\\/110105299932319333\\/embed<\\/a><\\/p>\n https:\\/\\/chaos.social\\/@coderbyheart\\/110105348296102607\\/embed<\\/a><\\/p>\n Opening keynote<\\/h3>\nhttps:\\/\\/chaos.social\\/@coderbyheart\\/110105403371093294\\/embed<\\/a><\\/p>\n \n The #BoosterConf opening keynote is by\n Anne Landro<\\/a>, a Norwegian service\n designer, and she talks about how to build innovative solutions that people\n really want (however they won't honestly tell you).\n<\\/p>\n \n She gave us a quick assignment: talk to each other 2 minutes about a specific\n time when you were showering.\n<\\/p>\n \n Very interesting to see how few managed very essential things like: were you wet\n when you left the shower, were you dry when you entered?\n<\\/p>\n That shows that users, when interviewing them, can't share many important facts.<\\/p>\n \n Users are too used to the (suboptimal) processes that they are using, they can't\n see the problems with it.\n<\\/p>\n \n In order to find good solutions we need to dig deep into the problem and resist\n the urge to jump to the immediate, obvious solution.\n<\\/p>\n \n But just talking is not enough, and getting to the true needs of a user is\n challenging, because users are often not honest about their true needs.\n<\\/p>\n \n [ I love the 5 Why's for that: https:\\/\\/en.m.wikipedia.org\\/wiki\\/Five_whys<\\/a> ...\n and she just mentioned it. ]\n<\\/p>\n \n There is a less offensive way to dig into the root cause (5 Why's can feel\n offensive), you can ask users about the benefits they solution they have in mind\n will yield for them. This can lead onto the path of finding out why they have a\n specific solution in mind.\n<\\/p>\n \n Nevertheless, the best way to find out what your users need is to observe them\n find the user's pain points.\n<\\/p>\n \n But make sure that does not influence them too much. Because users that are\n aware that they are watched, often behave differently.\n<\\/p>\n https:\\/\\/vimeo.com\\/812976108\\/embed<\\/a><\\/p>\n Lightning talks<\\/h3>\nhttps:\\/\\/chaos.social\\/@coderbyheart\\/110105689011221411\\/embed<\\/a><\\/p>\n \n First set of lightning talks at #BoosterConf starts with\n Einar W. Høst<\\/a> who reminds us\n that developers should be emancipated enough to understand their role with the\n same confidence as the so called business people do. They are, in the end, the\n ones who need to take ownership over the decisions they make and how they\n influence the business.\n<\\/p>\n https:\\/\\/chaos.social\\/@coderbyheart\\/110105729764807207\\/embed<\\/a><\\/p>\n https:\\/\\/vimeo.com\\/812979855\\/embed<\\/a><\\/p>\n \n The second talk is by\n Daria Kostiuk<\\/a> who speaks\n about the dangers of scope creep.\n<\\/p>\n \n Don't forget that any new feature you accept has a tendency to cause unintended\n side-effects and cause other things to take longer than expected.\n<\\/p>\n https:\\/\\/chaos.social\\/@coderbyheart\\/110105773885756845\\/embed<\\/a><\\/p>\n https:\\/\\/vimeo.com\\/812979950\\/embed<\\/a><\\/p>\n \n The third talk is by Kjersti Berg<\\/a>, who talks\n about reviving a code base from a state where it was practically unmaintainable.\n<\\/p>\n \n She used an ensemble approach to get out of this mess. They used one hour every\n day to get everyone together. Ensembling helps here because it improves\n knowledge sharing and decision making; both are key to make confident decision.\n<\\/p>\n \n After a year this improved code quality, ability to fix bugs and overall team\n happiness!\n<\\/p>\n https:\\/\\/vimeo.com\\/812980074\\/embed<\\/a><\\/p>\n https:\\/\\/chaos.social\\/@coderbyheart\\/110105819627330976\\/embed<\\/a><\\/p>\n \n Finally in this slot of Lightning Talks at #BoosterConf\n Dalibor Jovic<\\/a> has also a talk about\n technical debt and he proposes a few things you can do about it (because\n sometimes it is not avoidable).\n<\\/p>\n https:\\/\\/chaos.social\\/@coderbyheart\\/110105991859742366\\/embed<\\/a><\\/p>\n https:\\/\\/vimeo.com\\/812980178\\/embed<\\/a><\\/p>\n \n Now in the second slot of Lightning Talks at #BoosterConf\n Nora Gjøen-Gjøsæter<\\/a> gives us a very\n important reminder how biased AI models are.\n<\\/p>\n \n They all are, but some are more than others and effort is needed to not\n reinforce and proliferate the biases the models get from their source data.\n<\\/p>\n https:\\/\\/chaos.social\\/@coderbyheart\\/110106029163172924\\/embed<\\/a><\\/p>\n https:\\/\\/vimeo.com\\/812978922\\/embed<\\/a><\\/p>\n \n Karianne Berg<\\/a> shares her best practices for\n making awesome database indexes. Some strong language included 🤣.\n<\\/p>\n \n Make sure to understand your database schemas when building your applications,\n otherwise your performance will suck!\n<\\/p>\n \n Monitor in production to spot queries that need to be optimized (often the\n problem only becomes apparent with production data).\n<\\/p>\n https:\\/\\/chaos.social\\/@coderbyheart\\/110106317749585353\\/embed<\\/a><\\/p>\n https:\\/\\/vimeo.com\\/812979000\\/embed<\\/a><\\/p>\n \n Very cool lightning talk by Embla Flatlandsmo<\\/a>\n explaining how keyboards just™️ work when you plug them into your computer. Love\n the hand-drawn slides!\n<\\/p>\n https:\\/\\/vimeo.com\\/812979094\\/embed<\\/a><\\/p>\n Architecture Workshop with Oliver Zeigermann<\\/h3>\nhttps:\\/\\/chaos.social\\/@coderbyheart\\/110106420255302087\\/embed<\\/a><\\/p>\n \n we are working on a car insurance architecture Kata. First we are looking at a\n very simplistic implementation.\n<\\/p>\n \n Then we are reviewing potential solutions by trying a few simple examples on\n https:\\/\\/ml-playground.com\\/<\\/a> which is a really great idea to explain\n architectural tradeoffs.\n<\\/p>\n \n Finally, we got 30 minutes to discuss potential solutions in teams. That was\n fun!\n<\\/p>\n Fishbowl<\\/h3>\nhttps:\\/\\/chaos.social\\/@coderbyheart\\/110105827972761842\\/embed<\\/a><\\/p>\n https:\\/\\/chaos.social\\/@coderbyheart\\/110106940802730380\\/embed<\\/a><\\/p>\n \n Now it's time for the fishbowl at #BoosterConf with controversial questions from\n the audience:\n<\\/p>\n \n Is HTML a programming language? Doesn't matter.<\\/li>\n Uncertainty is mandatory: yes<\\/li>\n Should we fear AI? No, potential is real.<\\/li>\n There is no such thing as a full-stack developer: right, there is not.<\\/li>\n \n There is nothing every developer must know: probably Git today is a common\n denominator. But for every given profession there is a set of tools you need\n to know.\n <\\/li>\n Technology should not be seen as magic.<\\/li>\n \n Psychological safety is just a lazy excuse for doing nothing: absolutely not.\n There is research that shows that high performance and psychological safety\n correlates.\n <\\/li>\n \n Cloud vendor independence is not needed and wasteful: maybe, but some\n standardization is useful.\n <\\/li>\n<\\/ul>\nDay 2<\\/h2>\nhttps:\\/\\/chaos.social\\/@coderbyheart\\/110111000689327084\\/embed<\\/a><\\/p>\n \n Second day of #BoosterConf starts with a #refactoring workshop run by Karoline\n Skylstad and\n Siv Midtun Rollup<\\/a>, we\n are going to dive into a #Java codebase while applying some constraints.\n<\\/p>\n The project source we work with is https:\\/\\/github.com\\/kantega\\/refaktorama<\\/a>.<\\/p>\n OpenSpace<\\/h3>\nhttps:\\/\\/chaos.social\\/@coderbyheart\\/110112027695532354\\/embed<\\/a><\\/p>\n Really cool to have two slots for #OpenSpace sessions at #BoosterConf.<\\/p>\n https:\\/\\/chaos.social\\/@coderbyheart\\/110112058673684939\\/embed<\\/a><\\/p>\n The topics.<\\/p>\n https:\\/\\/chaos.social\\/@coderbyheart\\/110112137524008976\\/embed<\\/a><\\/p>\n First round: talking about quality.<\\/p>\n https:\\/\\/chaos.social\\/@coderbyheart\\/110112642743962719\\/embed<\\/a><\\/p>\n \n Second round at the #BoosterConf #OpenSpace: why do do many companies require CS\n degrees?\n<\\/p>\n \n This is where I learned about\n https:\\/\\/www.vilbli.no\\/nb\\/nb\\/no\\/informasjonsteknologi-og-medieproduksjon\\/program\\/v.im\n which teaches media and programming skills which allows workers to enter the\n workforce much earlier with relevant skills. It's still a certified training, so\n companies get a reliable level of education.\n<\\/p>\n Talk by Elisabeth Whiteley about side-projects<\\/h3>\nhttps:\\/\\/chaos.social\\/@coderbyheart\\/110112691160134601\\/embed<\\/a><\\/p>\n \n Elisabeth Whiteley<\\/a>\n shares great insights on how she deals with finding a way for side projects so\n it doesn't feel like work.\n<\\/p>\n Make it fun, and don't replicate the same constraints that you have for work!<\\/p>\n https:\\/\\/vimeo.com\\/814008986\\/embed<\\/a><\\/p>\n Day 3<\\/h2>\nTalk by Hege Dreiem about API Design<\\/h3>\nhttps:\\/\\/chaos.social\\/@coderbyheart\\/110116700672549731\\/embed<\\/a><\\/p>\n \n Final day of #BoosterConf and I am starting with a session on API Design from\n Hege Dreiem<\\/a>.\n<\\/p>\n \n She talks about the challenges of designing a ticket booking API for the\n Norwegian railway.\n<\\/p>\n \n It's important to design an API that gets used by many clients that you don't\n control to be open for extensions from the start.\n<\\/p>\n \n Developing a ubiquitous language is important in the beginning to develop an\n understanding of what the API needs to express.\n<\\/p>\n Talk by Aleksander Olavsrud about Machine Learning<\\/h3>\nhttps:\\/\\/chaos.social\\/@coderbyheart\\/110116753113476303\\/embed<\\/a><\\/p>\n \n Marius Aleksander Olavsrud<\\/a>\n explains how he and his team used Machine Learning to reduce the number of\n wasted breads at a Norwegian supermarket chain.\n<\\/p>\n \n Building a ML solution that works requires the right data. However that often is\n not there. Make sure to get the input data right. The implementation is only\n half of the project. Don't underestimate the effort needed to change their\n processes according to the findings.\n<\\/p>\n \n They used Facebook Prophet because it can account very good for seasonal and\n holiday events (and it's open source).\n<\\/p>\n Unfortunately he did not share how successful this project was in the end.<\\/p>\n https:\\/\\/vimeo.com\\/814014896\\/embed<\\/a><\\/p>\n Talk about GraphQL by Pål Thomassen<\\/h3>\nhttps:\\/\\/chaos.social\\/@coderbyheart\\/110117215000547075\\/embed<\\/a><\\/p>\n \n Pål Thomassen<\\/a> now\n shares his bad experience with GraphQL for building an API for traffic data at\n Statens Vegvesen.\n<\\/p>\n \n He starts with a basic introduction to #GraphQL. The bug advantage he mentions\n is that it is great to document the contract between server and clients, and\n there are many tools that can generate consumer code.\n<\\/p>\n \n The goal was to provide public access to the data they collect, and in 2018 when\n they need to pick a new technology it looked like a good choice, addressing the\n shortcomings of REST. The initial evaluation and internal tests went quite well,\n and even though there was some hesitation because it was uncertain if it was the\n right choice over REST, it was decided to continue with the approach. It was\n easy to model the API according to the business domain. And they went on to\n launch it.\n<\\/p>\n Now for the downsides:<\\/p>\n \n it introduces a bunch of new and complex concepts for implementing it properly<\\/li>\n \n from a client point of view it can be challenging to build clients that need\n to retrieve a lot of deep, nested data\n <\\/li>\n \n Many users often want spreadsheet exports, that's hard to match from a nested\n structure\n <\\/li>\n \n Because of the complexity the internal adoption of the new API was not a full\n success, which is a good indication that it's not an optimal solution\n <\\/li>\n \n a lot of consumers wanted access to Gigabytes of data, and transferring this\n via #GraphQL creates a huge overhead.\n <\\/li>\n<\\/ul>\n\n So it turned out that it a traditional REST API would have been a better choice,\n both it would be easier to maintain with a smaller team, and it's a more\n established technology that would scale better for this specific project.\n<\\/p>\nhttps:\\/\\/vimeo.com\\/814015103\\/embed<\\/a><\\/p>\n Talk by Andrew Harmel-Law about Architecture<\\/h3>\nhttps:\\/\\/chaos.social\\/@coderbyheart\\/110117723882154948\\/embed<\\/a><\\/p>\n \n In his session at #BoosterConf\n Andrew Harmel-Law<\\/a> talks about how\n architects can change their behaviour to not keep teams back, but to enable them\n making their own architecture decisions. #AnybodyArchitecture\n<\\/p>\n He proposes The Advice Process:<\\/p>\n \n \"Anyone can make any decision But before doing so they must: seek advice from\n all affected parties & people with expertise in the matter.\"\n<\\/p>\n \n But how to keep people from making bad decisions? Use ADRs to document the\n decision to be made and iterate on it.\n<\\/p>\n \n In the draft phase the team pulls in advice from all affected parties and\n document this advice.\n<\\/p>\n \n All of this effort gets synchronized in weekly meetings of the Architectural\n Advice Forum.\n<\\/p>\n \n It's important to track progress of ADRs to have an eye on those ADRs that get\n stuck.\n<\\/p>\n Finally he points out to watch out for potential causes this approach can fail:<\\/p>\n \n \"Bad\" decisions (there are none really)<\\/li>\n Old guard == New guard (not giving room for others to make decisions)<\\/li>\n Off-the-grid decisions (teams not using the process)<\\/li>\n No trust<\\/li>\n<\\/ol>\n\n This is the detailed blog post for this talk:\n https:\\/\\/martinfowler.com\\/articles\\/scaling-architecture-conversationally.html<\\/a>\n<\\/p>\n https:\\/\\/vimeo.com\\/814014311\\/embed<\\/a><\\/p>\n Closing<\\/h3>\nhttps:\\/\\/chaos.social\\/@coderbyheart\\/110117947182962966\\/embed<\\/a><\\/p>\n Daan van Berkel closes #BoosterConf for this year.<\\/p>\n https:\\/\\/chaos.social\\/@coderbyheart\\/110118043651086506\\/embed<\\/a><\\/p>\n Thanks to the #BoosterConf organizers and team, that was a blast!<\\/p>\n","slug":"boosterconf-2023","hero":"!undefined"}],["bring-your-inexperience-to-a-conference",{"title":"Bring your inexperience to a conference","subtitle":"On contributing to a community","abstract":"As a newbie you have something to contribute to a conference as well!\n","date":"2017-04-23T13:00+02:00","html":"\n \n <\\/picture><\\/aside>\n<\\/p>\n\n In August there will be the 7th\n International Software Craft and Testing Conference<\\/a>\n in Soltau, Germany. For me, the SoCraTes is the most important event in my\n profession every year, because I get to so see so many inspiring people.\n<\\/p>\n \n But it’s not only the high concentration of incredibly skilled professionals\n that gather in this remote location in northern Germany that provides so much\n value to me.\n<\\/p>\n It’s the Newbies as well.<\\/strong><\\/p>\n \n It might not be obvious to you as a first-time attendee or if you are new to the\n field of professional software development: you have something to contribute,\ntoo!<\\/strong>\n<\\/p>\n \n Since 2016, tickets for the SoCraTes are raffled and this provides a much higher\n influx of participants which haven’t attended any conference before that focuses\n on software as a craft. If you are one of those, I’d like to encourage you to\n offer a session, ask for support on a topic (this is called a pull session<\\/em>),\n and not to hesitate to offer your opinion during other sessions.\n<\\/p>\n Because your are adding value, even by asking a question!<\\/strong><\\/p>\n \n Your How?<\\/strong> questions are making us better teachers. Being a Software\n Craftsperson one of the most important goals is to become great at explaining\n the value of certain behaviour or technique. Because we loathe dogmatic\n application of \"best practices\" but strive for developing an understanding of\n the underlying principles of software development, so we can find the best\n solution for a problem, not the most obvious one. We can’t expect this from our\n peers, if we fail to explain it to them.\n<\\/p>\n \n Your Why?<\\/strong> questions are making us more effective. There are many biases that\n favor repeating decisions that have worked in the past, but in a chaotic market\n this strategy of our mind is not always a good fit. Being confronted with an\n honest question about the reasons for a certain decision forces us the make our\n oftentimes only implicitly known reasons and assumptions that lead to that\n decision explicit. It’s very helpful to shake one's belief system openly once in\n a while, because we are then challenged to do this honestly.\n<\\/p>\n \n You get to do all what's mentioned above (offering knowledge, asking questions,\n challenging decisions) in a safe environment which is very unique to the\n Software Craft Community: everybody understands that there is never only one\n good solution to a problem, because in Software everything depends<\\/em>. Therefore\n you will never hear someone dismissing an idea as wrong, even if their own idea\n about it is highly controversial to what they are presented.\n<\\/p>\n \n They will offer their advice and experience in a non judgemental way. And that’s\n why the SoCraTes and this community is awesome for Software Craftspeople of\nevery skill level<\\/strong>.\n<\\/p>\n","slug":"bring-your-inexperience-to-a-conference","hero":"!undefined"}],["build-a-professional-network",{"title":"Build a professional network","subtitle":"Markus, How do I ...","abstract":"My recommendations on how to build a professional network if you are early in your career.","date":"2017-11-05T14:00+01:00","html":"\n \n <\\/picture><\\/aside>\n<\\/p>\n\n Since I just was interviewed about this topic, I'll try to write down some of my\n recommendations on how to build a professional network if you are early in your\n career and how to progress from there. Actually I am practicing all of these\n actions even today.\n<\\/p>\n \n I'll focus on building a network to other professionals in your industry, since\n this will enable you to learn about new technologies, improve you skills based\n on experiences they are sharing and ask for support, find mentors and later on\n jobs and hires.\n<\\/p>\n\n In my experience the tech scene is especially good approachable on Twitter<\\/strong>.\n I find myself following a lot developers<\\/a> there\n and this way I get daily access to what is going on tech-wise. The real-time\n character of the network has it's advantages: you can easily interact on a given\n topic but it rarely happens that someone resurrects a old post. It's very easy\n to approach someone with a question there, and they usually will answer right\n away.\n<\\/p>\n \n But make now mistake, following<\\/em> someone on Twitter is a one-way street, to\n build a network you have to share something<\\/strong> so people can become aware of\n you. And since connections are built on trust, it means you have to expose\n yourself to some degree. And this exposure needs to happen in the physical\n world, only there will you be able to build connections that support exchange\n about personal and confidential matters which is the basis for finding good\n advisors and mentors.\n<\\/p>\n \n The first step is to go to local meetups. Do not fear to go there as a\n beginner<\\/em>, the first step to learning something is to embrace the unknown. It's\n a great opportunity to learn to know new people and find out who you would be\n interested to talk to. You will find that approaching someone there is a lot\n easier compared to a contacting them only e.g. through LinkedIn. Since you are\n both part of the same interest group, and you took the time to be present at the\n meetup will give you already some credibility. Also, it's harder to turn down\n someone who is approaching you face to face.\n<\\/p>\n \n Early in your career you should develop the confidence to give your first\ntalk<\\/strong>. Watch other speakers and try to find someone with experience as a\n speaker to give you feedback on your talk. Most meetups will be happy to host a\n beginner talk,\n since they always provide really valuable input<\\/a>.\n Giving talks will put you in the spotlight—doing it at a small meetup where you\n know people can be even more uncomfortable compared to a huge conference—but it\n also gives you a lot of visibility. I can highly recommend\n the software crafter communities<\\/a> around the\n world as a very inclusive and beginner-friendly community of professionals.\n<\\/p>\n \n Every talk creates the opportunity to reuse the content in multiple ways. You\n can use it to share your findings on your blog, but even better: submit it to a\n conference.\n<\\/p>\n \n The next step of building a valuable network is to attend conferences<\\/strong>. At\n conferences you will be able connect with a great variety of people. Those that\n share the same problems as you do and other beginners which will be a great\n resource when learning a new topic since you can exchange about your findings\n and problems. Since last year, it became common to connect through a Slack\n instance for that conference. Here you can also easily approach speakers, with\n your questions or on general to just give them feedback on their talk. In both\n case they will usually be very open and happy to help you. It's a good idea to\n check out a conference schedule beforehand and follow the speakers on Twitter,\n doing that you can start building a connection to them even before the event.\n<\\/p>\n \n You should submit your beginner talk<\\/strong> to conferences, because giving a talk\n will teach you so many great things that improve your skills on many levels. You\n can find conferences that accept proposals (Call for Papers, or CfP<\\/em> for short)\n on papercall.io<\\/a> or through\n lanyrd<\\/a>. Karolina has a great post on\n How to write a successful conference proposal<\\/a>.\n Becoming a speaker on a conference will give you a lot of visibility and\n provides a great opportunity to meet other industry experts on eye-level.\n<\\/p>\n","slug":"build-a-professional-network","hero":"!undefined"}],["build-this-opendata-hackers-and-datanauts",{"title":"Build this, OpenData Hackers and Datanauts [Updated]","abstract":"OpenData projects must be useful not just interesting, so here is my idea\n","date":"2015-05-31T13:00:00.000Z","html":"\n \n I recently participated in the first meeting of the\n Open Knowledge Lab Frankfurt<\\/a>.\n The verdict of the meeting was that local OKLabs should focus on building\n projects that serve a real need and not just be interesting from a developers\n perspektive … otherwise it wont get noticed by the public and ultimately by\n local authorities–which are an important source of open data.\n<\\/p>\n So here is my idea: find the best place to live given the criteria that are important to me and\nvisualize this on a map.<\\/strong><\\/p>\n \n Let me show you some pictures to illustrate my idea: heat maps help to visualize\n geologically coded events. The first example from\n umwelthaus.org<\\/a> is\n a heat map of the aircraft noise measured during the day:\n<\\/p>\n \n <\\/picture><\\/aside>\n<\\/p>\n\n The second example from crime-radar.com<\\/a> is the\n number of crimes committed in Frankfurt's city limits:\n<\\/p>\n \n <\\/picture><\\/aside>\n<\\/p>\n\n If you combine those two you'll get a good idea which neighbourhoods to avoid if\n you were to move into this region.\n<\\/p>\n \n And those are just two possible datasource. For me I'd like to see visualization\n for:\n<\\/p>\n\n public transport time to my workplace<\\/li>\n prices for land and houses<\\/li>\n availability of fast internet access<\\/li>\n proximity to bioreserves, hiking trails, lakes<\\/li>\n population density<\\/li>\n election results<\\/li>\n<\\/ul>\n\n This would enable me to pan around a map and find places that would fit my\n preferred living conditions.\n<\\/p>\n\n Feel free to submit it to the\n TEDxRheinMain Datanauts Contest<\\/a>, I won't\n because I'd be forced to comply to their\n overly one-sided terms and conditions<\\/a>.\n<\\/p>\n \n Also there is the\n Open Data Hackathon<\\/a> this\n Saturday at the best coworking space around:\n Die Zentrale<\\/a>. A perfect event to getting this\n started …\n<\\/p>\n Update<\\/strong><\\/h2>\n\n One of the 10 winning ideas of the event is\n settlement spotter<\\/em><\\/a>–which\n is exactly what I asked them to build!\n<\\/p>\n \n \n Use big data and feedback from various independent sources, leverage federal\n and public sources, open sources from the industry to create a map that will\n allow a user to draw a picture. Create an online environment to help an\n individual decide and plan his move to a place where his living requirements\n are met perfectly.\n <\\/p>\n<\\/blockquote>\n I'm looking forward to seeing this project come to life.<\\/p>\n","slug":"build-this-opendata-hackers-and-datanauts","hero":"!undefined"}],["call-for-proposals-lightning-talk",{"title":"About: Call for Proposals","subtitle":"Lightning Talk","abstract":"At 2019's Global Diversity CFP Day I gave a lightning talk about Call for Proposals.","date":"2019-03-02T11:00+01:00","card":"..\\/media\\/call-for-proposals-lightning-talk.png","html":"\n\n At 2019's Global Diversity CFP Day<\\/a> I\n gave a lightning talk about Call for Proposals.\n<\\/p>\n https:\\/\\/www.youtube.com\\/embed\\/jzqCzGXT7hw<\\/a><\\/p>\n \n The slides are available\n here<\\/a>.\n<\\/p>\n Below is are the main talking points I cover<\\/p>\n Structure of a Proposal<\\/h2>\n\n In order to prepare a good proposal we need to look at what conference\n organizers expect from a submission.\n<\\/p>\n These are the elements that you need to prepare:<\\/p>\nSpeaker Profile<\\/h3>\n\n You might think that only what<\\/em> you talk about matters, but it is actually the\n other way around. Conference organizers create a space to network, and the time\n around<\\/strong> the talks is actually where most attendees will see the value in. It\n matters very much to find a diverse set of speakers and that is why you should\n not miss out the oportunity to answer the question: Why should I talk to you?<\\/em>.\n<\\/p>\n A good speaker profile should have:<\\/p>\n\n less than 100 words<\\/li>\n \n be written in third person (conference organizers will copy&paste this to\n their website)\n <\\/li>\n \n have a mix of background information on your experience and interesting trivia\n about you\n <\\/li>\n<\\/ul>\nHere is how my speaker profile looks like (92 words, 596 characters):<\\/p>\n\n \n Markus is a coder by heart and an organizational hacker by passion. As a\n software crafter he uses his 20+ years of experience working as a software\n developer, consultant, coach, mentor, and founder to build cloud-based\n solutions for the Internet of Things using JavaScript. His professional career\n has been greatly influenced by taking an active role in communities, whether\n as a participant, contributor, initiator, or speaker. He especially enjoys the\n diverse and deep discussion of the Software Craft Community. He lives in\n Trondheim, Norway and enjoys plowing through deep snow on snowshoes.\n <\\/p>\n<\\/blockquote>\nAbstract<\\/h3>\n\n A great abstract distilles down the main takeaway of your talk into a very\nshort form<\\/strong>. It takes a lot of work to remove the unneccessary fluff from the\n text and highlight what the main takeaway of your talk is<\\/em>.\n<\\/p>\n Part of the abstract is the title which also needs to be an eye-catcher.<\\/p>\n \n Remember, your proposal can be one of hundreds so you need to catch the\n attention of the conference committee member within a few seconds.\n<\\/p>\n In your abstract<\\/p>\n\n make the title 100 characters or less<\\/li>\n fit the main idea in a tweet 280 characters<\\/li>\n<\\/ul>\n\n On many submission forms there is often not much more space for the abstract.\n 500 characters is still safe, and if you absolutely cannot fit your idea in a\n tweet, prepare multiple variants of the abstract.\n<\\/p>\n \n Here is how my abstract looks like (title has 63 characters, text has 288\n characters):\n<\\/p>\n\n \n Integration testing a cloud-native application with JavaScript<\\/strong> In this talk I will take you through the challenge of testing a cloud-native\n application. I will cover the challenges when developing solutions on top of\n serverless components which you cannot run on your own machine and how I\n designed a BDD driven approach to run the integration tests.\n <\\/p>\n<\\/blockquote>\n Notes<\\/h3>\n\n Once you have prepared this abstract, basically all conferences allow for to\n provide additional notes. This is your opportunity to provide more context to\n your abstract and also a second chance<\\/strong> to highlight the most important\n aspects of your talk. This is also a good place to provide more background\n information on why you are passionate to share this talk.\n<\\/p>\n The notes for my submissions look like this:<\\/p>\n \n \n In my current project at Nordic Semiconductor I am building a RESTful API for\n interacting with the next generation of IoT devices. This solution is build on\n top of AWS using serverless components. Not only the implementation of the\n business logic is done in JavaScript, but I have developed the entire CI\\/CD\n solution in JavaScript. In this talk I will cover the challenges when\n developing solutions on top of serverless components which you cannot run on\n your own machine and how I designed a BDD driven approach to run the\n integration tests, because I absolutely love tests. It showcases that\n JavaScript can be used in a truly full-stack manner today and that we can\n cover Development, DevOps and Testing with the one language we love. I am also\n really passionate about showcasing the BDD approach to testing which is in my\n opinion a fantastic way to drive test and at the same time have a living\n documentation.\n <\\/p>\n<\\/blockquote>\n 5 key learnings<\\/h3>\n\n I see conferences which have started to explicitely ask for it, but in my\n experience providing this list in the notes is really helpful for the conference\n committee. Explain in 5 bullet points what your audience will take away from\n your talk, the most important one first.\n<\\/p>\n \n The first key learning is easy, rephrase your abstract and you are done.<\\/li>\n I spoke about this because it really helps to understand the topic.<\\/li>\n This is also important, but might not apply everywhere.<\\/li>\n If you were really listening this is a cool bit to remember.<\\/li>\n Stretch goal!<\\/li>\n<\\/ol>\nHere is the real example from my talk:<\\/p>\n \n \n How the cloud native test-pyramid looks like<\\/li>\n \n Infrastructure as code is key, because configuration of cloud-native\n services are part of the solution\n <\\/li>\n how BDD can be used to write re-usable test instructions<\\/li>\n \n to write tests that behave like real users (retry if failed multiple times)\n instead of programming shortcuts, because this will give better information\n to system design\n <\\/li>\n use “real” test doubles backed by queues to monitor outcome of test cases<\\/li>\n <\\/ol>\n<\\/blockquote>\nKeywords<\\/h3>\n\n The SEO<\\/em> for talks is mainly used to cluster talk submission for the commitee,\n but some websites also publish them for the attendees to filter talks. They are\n not used that often, but you should prepare 5-10 keywords in advance.\n<\\/p>\n These are the keywords for my talk:<\\/p>\n \n JavaScript IoT BDD Serverless AWS<\\/p>\n<\\/blockquote>\n Where to find CfPs<\\/h2>\n\n Once you have your proposal ready it is time to submit it. The most important\n place to find out about Call for Proposals is Twitter. Follow conferences and\n speakers because this will be the first place were you will learn about new\n announcements.\n<\\/p>\n \n There are also sites that aggregate CfPs and provide a list and a regular email\n about new CfPs. Check out:\n<\\/p>\n \n seecfp.com<\\/a><\\/li>\n papercall.io<\\/a><\\/li>\n callingallpapers.com<\\/a><\\/li>\n cfpland.com<\\/a><\\/li>\n<\\/ul>\nSubmitting<\\/h2>\nhttps:\\/\\/twitter.com\\/mary_grace\\/status\\/1090988453226074113?embed<\\/a><\\/p>\n \n Once start submitting remember that you will receive rejections, and quite a lot\n of them. It's hard to give a ratio, because it depends on your talk and which\n conferences you select, but getting 9 out of 10 submissions rejected is totally\n normal. So oversubmit!\n<\\/p>\n \n Another reason for that is that it is hard to plan month ahead. Some CfP end\n more than half a year in advance. It is impossible to know whether you will be\n actually able to attend. You always will be asked after your proposal has been\n accepted to confirm your attendence. This typically happens at a time where it\n is easier to plan ahead and figure out those conflicts. Don't feel bad to turn\n down an opportunity to talk, the conference will not have a hard time finding a\n replacement, especially if you decline right away.\n<\\/p>\n \n It helps to track your submissions, I use a\n Trello board<\\/a>\n to keep an overview. Because you also do not want to submit to the same\n conference twice...\n<\\/p>\n #paytospeak<\\/h2>\n\n I also need to mention\n #paytospeak<\\/a> here, because\n it's important to understand that we as speakers are actively hindering the\n diversification of the speaking community if we accept speaking opportunities\n for which we pay the expenses out of our own pockets.\n<\\/p>\n If you are not getting reimburst for your expenses as a speaker there is a\nhigh chance that you are benefiting off someone who cannot afford to attend.<\\/strong><\\/p>\n \n There are two great blog posts on this topics which I highly recommend you to\n read:\n<\\/p>\n \n nataliewarnert.com\\/askforpay-instead-of-paytospeak\\/<\\/a><\\/li>\n www.cassandrahl.com\\/blog\\/why-i-dont-pay-to-speak\\/<\\/a><\\/li>\n<\\/ul>\nCode of Conducts<\\/h2>\nhttps:\\/\\/twitter.com\\/pati_gallardo\\/status\\/1058282328177471488?embed<\\/a><\\/p>\n \n If you apply to a conference I highly encourage you to check out their Code of\n Conduct. Having no<\\/strong> is a red flag, but having a single-paragraph one mit even\n be worse.\n<\\/p>\n There are Code of Conducts, like<\\/p>\n \n “Don’t be a jerk.”<\\/p>\n<\\/blockquote>\n and there are good<\\/strong> Code of Conducts because they are<\\/p>\n\n concrete, so it is clear to everyone what inacceptable behaviour is<\\/li>\n \n enforcible, so there are clear guidelines on what will happen in case\n something happens\n <\\/li>\n and everyone has of the staff has been trained on how to handle incidents<\\/li>\n<\\/ul>\n\n A good example is the\n JSConf Code of Conduct<\\/a>.\n<\\/p>\n Now, go and become a speaker!<\\/h2>\nhttps:\\/\\/twitter.com\\/devdevcharlie\\/status\\/1090367939889397760?embed<\\/a><\\/p>\n You can find more resources on public speaking here:<\\/p>\n \n speaking.io<\\/a><\\/li>\n twitter.com\\/AgileTD\\/status\\/1098262053519835139<\\/a><\\/li>\n agiletestingdays.com\\/blog\\/it-always-starts-with-an-idea\\/<\\/a><\\/li>\n<\\/ul>\n\n I am also always\n happy to help<\\/a>.\n Feel free to reach out to me! If I can help you with your talk proposal, send me\n a Google Doc!\n<\\/p>\n","slug":"call-for-proposals-lightning-talk","hero":"!undefined"}],["call-for-your-first-conference-proposal",{"title":"Call for your first conference proposal","subtitle":"My segment on why YOU should propose a talk to a conference NOW! from J On The Beach 2018","abstract":"My segment on why YOU should propose a talk to a conference NOW! from J On The Beach 2018","date":"2018-09-16T21:00+02:00","html":"\n https:\\/\\/twitter.com\\/coderbyheart\\/status\\/1041408149276774400?embed<\\/a><\\/p>\n \n If you think you want to talk about something you are passionate<\\/em> about you are\n already a step further than 99%.\n<\\/p>\n Write a proposal — 99.9% don’t.<\\/p>\n \n See speaking.io<\\/a> for great resources on how to get\n started. Also check out\n this thread<\\/a> on\n Twitter.\n<\\/p>\n \n Submit to conferences that cover travel expenses\n (#paytospeak<\\/a>) and\n have a good<\\/strong> Code of Conduct.\n<\\/p>\n If they don’t, ask why!<\\/p>\n \n Find conferences who are calling for proposals on: SeeCFP<\\/a>\n or Papercall<\\/a>.\n<\\/p>\n More resources on public speaking:<\\/p>\n \n \n Speak Easy<\\/a> mentors speakers to encourage\n diversity at tech conferences\n <\\/li>\n<\\/ul>\n","slug":"call-for-your-first-conference-proposal","hero":"!undefined"}],["clean-architecture",{"title":"Clean Architecture","subtitle":"Book Review","abstract":"Despite its excess Uncle Bob Grandeur and idiotic and pointless cartoons I would recommend this book to experienced architects and software developers since it reinforces and clarifies proven concepts, which I am using on a daily basis.","date":"2018-01-03T06:00+01:00","html":"\n\n <\\/picture><\\/aside>\n<\\/p>\n\n Clean Architecture<\\/em><\\/a> is the latest book in the Clean\n[...]<\\/em> series, following Clean Code<\\/em>, and The Clean Coder<\\/em> written by the\n Software Craftsman<\\/em> Robert C. \"Uncle Bob\" Martin who most recently became an\n outcast of the worldwide Software Crafters Community for opinions he expressed\n in his personal blog regarding diversity.\n<\\/p>\n \n In the book we are spared from his personal opinions, and only slightly\n confronted with a tiny dose of everyday sexism, and another big portion of\n \"Uncle Bob has seen it all<\\/em>\" in the 50 page Appendix on Architecture\nArchaeology<\\/em> in which Martin uncovers stories about his work dating back to the\n early 70s which merely serves to support the validity of the ideas and concepts\n that have been presented in the previous chapters. It reads like another attempt\n to infuse Martin's legend with substance, which is odd, since he spent the\n Preface and Introduction chapters on this topic already.\n<\\/p>\n \n What I liked about the book is his attempt to guide the reader through\n techniques and principles that lead to good<\\/em> architecture but also provide a\n slightly superficial explanation of these topics. He debunks object-operation\n and is able to reveal the core principles of every software and what good\n architecture should enable:\n<\\/p>\n good architecture makes software easy to change<\\/h2>\n\n and easy to change means that the cost of change is magnitudes lower than the\n value the change provides. His concepts are designed to enable a very long\n software lifetime by keeping developer productivity high of years into a\n software project.\n<\\/p>\n \n For me personally there weren't any new revelations to be discovered but I liked\n Martin's way to re-define and sharpen existing ideas using simple language. The\n chapters surf just below the surface and never dive too deep, which will be\n problem for unexperienced software developers and architects since they will\n most likely not be able to connect the dots.\n<\\/p>\nwhat matters is the domain<\\/h2>\n\n I especially like Part IV of the book in where Martin stresses the idea that\n good architecture abstracts away concrete implementations<\\/em> from the beginning.\n This idea has been presented in the previous chapters already with a focus on\n implementation on the module level. Part IV makes this idea more tangible by\n explaining why and how secondary components (I'd call them that) like databases,\n UI and frameworks should be separated from the software core.\n<\\/p>\n \n By page 210 you have already encountered all there is to know in the book so\n don't be taken away away by the page count. The remaining chapters flesh out the\n main idea:\n<\\/p>\n\n \n Write high-level abstractions for everything that is not your core business\n domain, and don't let secondary component concepts leak into your business\n domain.\n <\\/p>\n<\\/blockquote>\n \n Despite its excess Uncle Bob Grandeur<\\/em> and idiotic and pointless cartoons I\n would recommend this book to experienced architects and software developers\n since it reinforces and clarifies proven concepts, which I am using on a daily\n basis.\n<\\/p>\n","slug":"clean-architecture","hero":"!undefined"}],["clean-gitignore-files",{"title":"Clean .gitignore files","subtitle":"Best practice","abstract":"A .gitignore in a project should only cover artifacts caused by the contained source code, not those caused by the personal choice of editor and\\/or environment of a developer.","date":"2025-12-28T12:38+01:00","html":"\n\n A .gitignore<\\/code> in a project should only cover artifacts caused by the contained\n source code, not those caused by the personal choice of editor and\\/or\n environment of a developer. Use\n a global git ignore file<\\/a>\n for that.\n<\\/p>\n \n Yes, you can solve it also with a well maintained .gitignore<\\/code> file that covers\n everything in all projects but this can get\n quite extensive to cover all cases<\\/a>.\n<\\/p>\n \n I consider it noise if entries are in the .gitignore<\\/code> that have no relation to\n the specific project: I want a clean<\\/strong> .gitignore<\\/code> file.\n<\\/p>\n \n Maintaining a global .gitignore<\\/code> file for your personal setup<\\/em> also has the\n advantage that it affects all existing and future projects on your machine, thus\n eliminating the possibility of accidentally committing those files. Otherwise\n you would need to remember to add your IDE files to EVERY projects .gitignore<\\/code>.\n<\\/p>\n \n Additionally, changes to the .gitignore<\\/code> of a project are not free: they\n trigger CI runs, releases, reviews. Having people constantly add their favourite\n rules creates noise. I don't want that.\n<\\/p>\n \n Having a huge catch-all .gitignore<\\/code> is no solution either, it will only cover\n known files. Additions trigger noise.\n<\\/p>\n \n Adding files to a git repository is a deliberate action, if developers add files\n that do not belong to a feature or change they need to be better educated about\n it. If this is done, an accident-preventing-gitignore is no longer needed.\n<\\/p>\n Good example<\\/h2>\ndist\\/\n<\\/span>node_modules\\/\n<\\/span><\\/code><\\/pre>\nBad example<\\/h2>\n.idea\n<\\/span>.vscode\n<\\/span>.DS_Store\n<\\/span><\\/code><\\/pre>\nTip<\\/h2>\nHave a local folder to put your crap in which won't get accidentally committed<\\/a><\\/p>\n","slug":"clean-gitignore-files","hero":"!undefined"}],["clone-all-repos-of-a-github-team",{"title":"Clone all repositories of a GitHub team","subtitle":"snippets","abstract":"This is a small snipped that clones all repositories of a GitHub team","date":"2022-11-01T13:00:00+01:00","html":"\n \n First, ensure you have your GitHub token available. If you are using a .netrc<\\/code>,\n you can acquire it from there:\n<\\/p>\n GITHUB_TOKEN<\\/span>=<\\/span>`<\\/span>cat<\\/span> ~\\/.netrc |<\\/span> grep<\\/span> 'machine github.com'<\\/span> |<\\/span> awk<\\/span> '{ print $6; }'<\\/span>`<\\/span><\\/span>\n<\\/span><\\/code><\\/pre>\nThen, using the organization name and team slug, clone all repositories:<\\/p>\nORG<\\/span>=<\\/span>my-org\n<\\/span>TEAM<\\/span>=<\\/span>my-team\n<\\/span>http https:\\/\\/api.github.com\\/orgs\\/${ORG}<\\/span>\\/teams\\/${TEAM}<\\/span>\\/repos\\<\\/span>?per_page\\<\\/span>=<\\/span>100<\\/span> \\<\\/span>\n<\\/span> Authorization:\"token ${GITHUB_TOKEN}<\\/span>\"<\\/span> |<\\/span> jq '.[].clone_url'<\\/span> |<\\/span> xargs<\\/span> -I@ git<\\/span> clone @ --depth<\\/span> 1<\\/span>\n<\\/span><\\/code><\\/pre>\n","slug":"clone-all-repos-of-a-github-team","hero":"!undefined"}],["cloud-connectivity-and-protocols-for-the-internet-of-things",{"title":"Cloud connectivity and protocols for the Internet of Things","subtitle":"Webinar","abstract":"This is a webinar for everyone who wants to get an introduction to protocols to consider when developing a cellular IoT product.","date":"2020-10-21","card":"https:\\/\\/webinars.nordicsemi.com\\/60650860\\/64311747\\/957cd4b4fcdc7aebf637ffbe16e10720\\/large\\/download-5-thumbnail.jpg","html":"\n\n This is a webinar I did for\n Nordic Semiconductor Tech Webinars<\\/a>\n together with my colleague Carl Richard Fosse, but it applies to everyone who\n wants to get an introduction to protocols to consider when developing a cellular\n IoT product.\n<\\/p>\n \n It provides an overview over the important factors that need to be considered\n when it comes to picking the right solution for sending your products' data to\n the cloud.\n<\\/p>\n https:\\/\\/www.youtube.com\\/embed\\/pNaBB_OFbgg<\\/a><\\/p>\n \n You can find the interactive, browser-based slides\n here<\\/a>, and a PDF\n with all notes\n here<\\/a>.\n<\\/p>\n","slug":"cloud-connectivity-and-protocols-for-the-internet-of-things","hero":"!undefined"}],["code-craft",{"title":"Code Craft","subtitle":"Book Review","abstract":"A critique of the book Code Craft by Pete Goodliffe","date":"2018-07-16T20:00+02:00","html":"\n \n <\\/picture><\\/aside>\n<\\/p>\n\n It's amazing what Pete Goodliffe managed to compile in the 558 pages of\n this book<\\/a> on software development (subtitle The\nPractice of Writing Excellent Code<\\/em>) which was published back in 2007.\n<\\/p>\n \n The author takes the long road of not only explaining how software is made but\n also detailing which individual skills and techniques are needed to produce\n software which is of high quality in all aspects. He tackles software-related\n topics like architecture, maintainability, documentation, performance,\n optimization, source-code management, but does not miss the opportunity to\n highlight the importance of communications and that great teamwork is paramount\n to producing great software.\n<\\/p>\n \n I especially liked the way every chapter is structured like a course: following\n a short overview, we are taken from the fundamentals of every topic to the state\n of the art, and closing with a set of tasks and questions to get the reader\n thinking, in parts alone but also as a team.\n<\\/p>\n \n The book has aged well, everything is still relevant today and I can highly\n recommend this book for any aspiring software developer. It is also a great\n workbook<\\/em> if you are developing an internal apprenticeship program or software\n developer curriculum.\n<\\/p>\n It may be the best software developer compendium available today.<\\/p>\n","slug":"code-craft","hero":"!undefined"}],["code-of-conducts",{"title":"Code of Conducts","abstract":"I recently proposed to establish a Code of Conduct for the BarCamp RheinMain. Here is my rationale why.\n","date":"2016-08-15T23:00:00.000Z","html":"\n I recently proposed to establish a Code of Conduct for the\nBarCamp RheinMain<\\/a>. Here is my rationale why.<\\/em><\\/p>\n \n\n tl;dr: Your every word<\\/em> influences other humans. I believe it is worth\n scrutinizing your own behaviour.\n<\\/p>\n\n Germany is a society dominated by CIS<\\/a>\n white males. Who doesn't acknowledge this as a deficit is part of the problem<\\/em>.\n Acknowledgement is the first step if we want to change the status quo. A Code of\n Conduct like this one<\\/a> with a very stark\n focus on sexual harrassment puts a spotlight on the fact that it is actually a\n huge problem how our society treats humans that do not identify with the simple\n black and white idea of man \\/ woman = strong \\/ weak.\n<\\/p>\n \n Behaviour is always influenced by experiences, only if we change the environment\n in which we interact with other and challenge the way how we do so, change can\n be achieved. In my opinion it is our duty as event organizers to take on this\n task.\n<\\/p>\n \n Given that we welcome many young participants at our BarCamps we have the chance\n to support them in the development of their personality in a good way or at\n least to not harm them.\n<\\/p>\n \nFor further reading on the topic, check out\nthis awesome list of resources<\\/a>\nby Lena Reinhard<\\/a>.<\\/em><\\/p>\n","slug":"code-of-conducts","hero":"!undefined"}],["codedoor-apac",{"subtitle":"Mentoring","title":"CodeDoor and Asia Pacific College","date":"2020-12-03T09:16:00.000Z","abstract":"I am mentoring 4 teams from the Philippines","html":"\n \n I'm really excited to be mentoring 4 teams (of 50) from the\n Asia Pacific College<\\/a> on the Philippines as part of a\n three months CodeDoor<\\/a> and\n IBM SkillsBuild<\\/a> bootcamp that teaches students how\n software can be used to tackle important problems. They will be focusing on\n natural disasters. This is going to be amazing!\n<\\/p>\n https:\\/\\/twitter.com\\/coderbyheart\\/status\\/1334426175565934592?embed<\\/a><\\/p>\n","slug":"codedoor-apac","hero":"!undefined"}],["codefreeze-brings-the-magic-of-socrates-to-lapland",{"title":"codefreeze brings the magic of SoCraTes to Lapland","subtitle":"A conference about Software Craft like no other","abstract":"About codefreeze, the software craft and testing conference in the arctic circle","date":"2017-01-21T10:00+02:00","html":"\n \n <\\/picture><\\/aside>\n<\\/p>\n\n For the last week we have been in Kiilopää<\\/a>, a national park in the\n arctic circle to attend codefreeze<\\/a> which brings the Software Craft and\nTesting Conferences<\\/a> to one of the most remote places I have ever\n visited. I was drawn there by the pictures I saw on Twitter<\\/a> of last\n year and this year, I could contribute a fair share of my own.\n<\\/p>\n \n The conference has been a breathtaking experience and we will definitely be go\n there again, not only for the conference, but for the beautiful nature that the\n national park offers. And with a direct flight from Frankfurt to Ivalo, which is\n just a 40 minute bus drive from Kiilopää it is easy to go there for us. We even\n had Finns, that had longer journeys to reach this remote spot in the arctic\n circle where there is basically nothing for hundreds of kilometers.\n<\\/p>\n \n The national park itself is around 40 kilometers in diameter and preservers a\n natural fern forest with very old trees, they can reach up to 300 years before\n they die and will then keep standing for another 50 or more years.\n<\\/p>\n \n Soumen Latu<\\/a> is a charitable organization in Finland that aims to preserve\n the nature which operates the Fjell Center where we stayed. It's a small village\n with a main building where you will get great food basically all day, which has\n a rental shop and a public sauna that is on all day. Next to it is a hostel for\n groups and a hotel with rooms for one to two persons. We stayed in one of the\n roughly 40 cabins that house two to ten people. Our log cabin of 50 m² was\n equipped with it's own sauna and a fireplace.\n<\\/p>\n Absolute Silence<\\/h2>\n\n With the next supermarket being 26 km away and the airport around 40 km, no\n industry a ban for snowmobiles in the area the nights were absolutely silent.\n And even at day, when being just a few hundred meters away from the main\n building, you would hear not a thing<\\/em>.\n<\\/p>\n \n The masses of snow, that blanketed the area created an incredible atmosphere and\n a fascinating black and white backdrop for the many outdoor activities you could\n have: between 1000 and 1500 the sun was above the horizon—not visible from the\n fjell center, though—and here we did nordic skiing, snowshoe trips and\n backcountry ski trips guided by the volunteers of the Soumen Latu association\n that come to Kiilopää to stay there for two or more weeks receiving free\n accommodation for their services. The trips were free of charge, you only had to\n rent the necessary equipment in the rental shop at the main building for a\n reasonable price—e.g a pair of snowshoes and poles for 10 € per day.\n<\\/p>\nPerfect winter vacation: snow and sauna<\\/h2>\n\n The trips would take you to the area around which offers a lot of variety: dense\n forests with deep snow, prepared tracks for nordic skiing or you could go above\n the treeline on top of the Kiilopää—the 600m high mountain that the center is\n named after. Usually you would start in the morning around 10—that's when\n breakfast ends—and be home in the early afternoon—it got dark around 1500—to\n take a nap and then go to the sauna. And even with sauna there is variety: you\n have the normal<\\/em> finnish sauna in the cabin with an electric oven, it heats up\n quickly to 100° and you can set it up in advance, to time it perfectly for your\n return. But there is also smoke sauna, a big sauna for roughly 30 people that is\n warmed at noon with a open wooden fire which heats up a big pile of stones that\n keep the warmth for hours. The smoke sauna can then be used between 1500 and\n 2000 and has a totally different heat which is less intense and you can stay\n there for three hours—once in a while you will go out and take the dip<\\/em>, a\n small pond that is kept ice-free by a flowing water source and has a temperature\n of around 1°. It sounds scary at first, but it's actually a great feeling,\n especially when your feet start to freeze to the ground after leaving the water\n …\n<\\/p>\nThe codefreeze unconference<\\/h2>\n\n To be honest, we never planned to make this trip about the conference, it was a\n great occasion to be there but it was clear that this would be more of a leisure\n trip, which is why I didn't make this trip on the company budget. But we had\n three and a half days, starting on Monday afternoon where we had a proper<\\/em>\n unconference, you can see for yourself on the trello board for the\nweek<\\/a>, given the small group—around 20 attendees—we still managed to\n fill the timetable with a great variety of topics. But a lot of discussion\n happened outside of the sessions and that's what made it especially great to be\n here. Although you had so many outdoor activities, everybody would always return\n to the main building for food, or the sauna, or some of the cabins where the\n discussions continued or new topics arised.\n<\\/p>\n \n For me it was the best conference experience I could imagine and it was also the\n best winter vacation I ever had. We will definitely return to Kiilopää and not\n only during codefreeze season but also in the summer, to hike in the woods there\n from hut to hut. I'm very grateful for Aki<\\/a> adding this experience to my\n life. I will never forget my first codefreeze.\n<\\/p>\n","slug":"codefreeze-brings-the-magic-of-socrates-to-lapland","hero":"!undefined"}],["conferencebuddy-at-socrates-2018",{"title":"ConferenceBuddy at SoCraTes 2018","subtitle":"No one needed a ConfBuddy, and why this is a good thing","abstract":"I was a Conference Buddy at SoCraTes 2018—but nobody needed one.","date":"2018-09-01T16:00+02:00","html":"\n \n <\\/picture><\\/aside>\n<\\/p>\n\n The SoCraTes conferences are dear to my heart, and\n the one in Soltau<\\/a> every year is my most\n important conference date every year. This year some of us shared that we were\n attending and happy to be a ConferenceBuddy<\\/a>:\n<\\/p>\n https:\\/\\/twitter.com\\/benjamin\\/status\\/1029742801767067648?embed<\\/a><\\/p>\n https:\\/\\/twitter.com\\/coderbyheart\\/status\\/1030010907840192513?embed<\\/a><\\/p>\n \n I also created a public #buddies<\\/strong> channel in the\n conference Slack<\\/a>, where I posted\n opportunities for buddies to meet at the first night of the conference (the\n evening where everyone arrives). 26 people joined.\n<\\/p>\n \n On the first day of the open-space at the marketplace in the morning, I\n announced that if somebody felt that they would like to meet a buddy, I would be\n happy to meet during lunch.\n<\\/p>\n And then, nobody showed up.<\\/strong><\\/p>\n \n But this is totally what I expected to happen. SoCraTes Soltau is by far the\n most inclusive tech event I know, and everybody behaves incredibly welcoming and\n respectful. It is a safe space and also still kind of an insider-event, since it\n is organized by the community and non-profit. You usually know about SoCraTes\n because you know someone, who knows it.\n<\\/p>\n \n But (!) I have received positiv feedback explicitlty referring to\n ConferenceBuddy and how it reduced the barrier for newcomers to feel welcome at\n the event.\n<\\/p>\n \n So, this is actually a success story for ConferenceBuddy, because it's like the\n phone number in a conference code of conduct: it needs to be there and you have\n to make sure that somebody answers it all the time, but its a good thing if\n nobody calls.\n<\\/p>\n And here is how a participant put it:<\\/p>\n https:\\/\\/twitter.com\\/tdpauw\\/status\\/1030076022153199616?embed<\\/a><\\/p>\n https:\\/\\/twitter.com\\/tdpauw\\/status\\/1033731158918475776?embed<\\/a><\\/p>\n","slug":"conferencebuddy-at-socrates-2018","hero":"!undefined"}],["connect-to-dead-com-connection-timed-out",{"title":"connect to dead.com: Connection timed out","abstract":"Wie könnte es auch anders sein?!","date":"2010-05-11T00:00:00.000Z","lang":"de","html":"\n Oct 21 10:08:07 jayla postfix\\/error[24545]: B13623382E: to=<8b067c20a9cccde27038d13a1c1df64a@dead.com>, relay=none, delay=36297, delays=36267\\/30\\/0\\/0.01, dsn=4.4.1,\n<\\/span>status=deferred (delivery temporarily suspended:\n<\\/span>connect to dead.com[66.240.173.8]:25: Connection timed out)\n<\\/span><\\/code><\\/pre>\nWie könnte es auch anders sein?!<\\/p>\n","slug":"connect-to-dead-com-connection-timed-out","hero":"!undefined"}],["covid-19-guide-for-aid-workers-built-with-gatsbyjs-from-a-google-drive",{"title":"COVID-19 guide for Aid Workers built with GatsbyJS from a Google Drive folder","subtitle":"resources.distributeaid.org","abstract":"resources.distributeaid.org provides a browser-friendly UI for a Google Drive folder.","date":"2020-05-19T18:00+02:00","html":"\n \n <\\/picture><\\/aside>\n<\\/p>\n\n Last year in October I joined Distribute Aid<\\/a> as a\n volunteer. I craft software for them which helps with their mission: build tools\n that help refugee aid groups discover and connect with each other, collaborate\n on aid shipments, share knowledge, and engage volunteers.\n<\\/p>\n \n End of March we launched a landing page for a collection of information about\n COVID-19 and how to safely organize community aid during the outbreak which has\n been reviewed by front-line medical and refugee aid workers and which was\n provided for readers in\n this Google Drive folder<\\/a>.\n<\\/p>\n \n Google Drive is amazing for collaborating on these resources but is a heavy web\n application which includes a lot of features for editing<\\/em> content, which is not\n needed when reading<\\/em> the content.\n<\\/p>\n \n In April I started experimenting towards a solution that would keep the great\n editing capabilities of Google Drive (which are essential for incorporating\n feedback from dozens of contributors) but on the same hand improve the usability\n for readers.\n<\\/p>\n \n After implementing an exporter, which uses pandoc<\\/a> to\n convert the HTML files which\n can be exported using the Google Drive API<\\/a>\n to Markdown, I fed them into GitBook<\\/a>, a great\n service which turns a collection of Markdown files into a nice website. GitBook\n is ideal for content heavy, documentation style projects. However for use the\n options to customize the design of the generated website was too limited.\n<\\/p>\n \n I then turned to GatsbyJS<\\/a>, a great static site\ngenerator<\\/em> which allows to customize every aspect of the generated website and\n helped me to build a nicely designed guide that follows Distribute Aid's\n corporate identity, including a great mobile experience.\n<\\/p>\n \n Because of the richt ecosystem of Gatsby adding full text search with\n Algolia<\\/a> was done very quick and could be integrated\n exactly where it makes sense for a guide.\n<\\/p>\n \n Please check out and share<\\/strong> the guide:\n resources.distributeaid.org<\\/a>.\n<\\/p>\n \n The source code for the project can be located\n on GitHub<\\/a>.\n<\\/p>\n","slug":"covid-19-guide-for-aid-workers-built-with-gatsbyjs-from-a-google-drive","hero":"!undefined"}],["daring-greatly-talking-about-shame-is-inevitable-if-we-want-to-change",{"title":"Daring Greatly: Talking about shame is inevitable if we want to change","abstract":"Book review of Daring Greatly by Brené Brown\n","date":"2016-03-13T16:30:00.000Z","html":"\n \n <\\/picture><\\/aside>\n<\\/p>\n\n Daring Greatly<\\/a> by\n Brené Brown<\\/a> message is simple: We use other\n people's shame to protect ourselves from shame. A vicious circle that starts as\n early as kindergarten and becomes part of our everyday behaviour. It is so\n powerful that we build armory around our personalities that change who we are\n and limit what we could become.\n<\\/p>\n \n Watch her TEDx talk<\\/a> for an\n introduction to her topic. But I recommend you to read this book, too. It is\n highly readable and provides important insights backed by years of research and\n thousands of interviews.\n<\\/p>\n \n The message is clear: we need to embrace shame and put ourselves out there. We\n will be criticized, we will fail, we will struggle but if we don't we are\n missing out.\n<\\/p>\n \n In times where big corporations are shifting they way the operate towards an\n open and transparent culture this book is especially important. Giving employees\n the power to decide on their own when, how and on what they will work also\n shifts the responsibility for their actions from their former bosses towards\n them. More and more will they make their daily work public and open for\n scrutiny. But for decades we have learned and perfected the finger-pointing\n game. If organizations fail to understand that the change not only requires new\n ways to organize work but also requires everyone to develop new communication\n skills and empathy, change will fail.\n<\\/p>\n \n A remarkable quote from the book is this one from Kevin Surace, Inc.com's\n Entrepreneur of the Year 2009. Below is a verbatim copy from\n this article in fastcompany.com<\\/a>\n which is freely available:\n<\\/p>\n Brené asked him: What's the most significant barrier to creativity and\ninnovation?<\\/em><\\/p>\n \n \n I don't know if it has a name, but honestly, it's the fear of introducing an\n idea and being ridiculed, laughed at, and belittled. If you're willing to\n subject yourself to that experience, and if you survive it, then it becomes\n the fear of failure and the fear of being wrong. People believe they're only\n as good as their ideas and that their ideas can't seem too ‘out there' and\n they can't ‘not know' everything. The problem is that innovative ideas often\n sound crazy and failure and learning are part of revolution. Evolution and\n incremental change is important and we need it, but we're desperate for real\n revolution and that requires a different type of courage and creativity.\n <\\/p>\n<\\/blockquote>\n \n I can recommend this book to everyone who is trying to change how people behave\n in organizations. But this book will not only help you with your work but also\n help you understand your own behaviour better.\n<\\/p>\n","slug":"daring-greatly-talking-about-shame-is-inevitable-if-we-want-to-change","hero":"!undefined"}],["darstellung-von-git-diff-verbessern",{"title":"Darstellung von git diff verbessern","abstract":"Hier sind ein paar Einstellungen die die Darstellung der Ausgabe von git diff und weiteren git-Kommandos lesbarer machen:","date":"2012-06-27T00:00:00.000Z","lang":"de","html":"\n \n Hier sind ein paar Einstellungen die die Darstellung der Ausgabe von git diff<\\/code>\n und weiteren git-Kommandos lesbarer machen:\n<\\/p>\n Farbige Ausgabe aktivieren, für alle Ausgaben:<\\/p>\n git config --global color.ui true<\\/code><\\/p>\n Lange Zeile umbrechen:<\\/p>\n git config --global core.pager 'less -r'<\\/code><\\/p>\n \n Hat man wenige Änderungen in langen Zeilen vorgenommen, ist der Switch\n --word-diff<\\/code> sehr hilfreich. Dieser Zeigt in geänderten Zeilen zusätzlich die\n geänderten Wörter an:\n<\\/p>\n git diff --word-diff<\\/code><\\/p>\n","slug":"darstellung-von-git-diff-verbessern","hero":"!undefined"}],["default-werte-fur-methoden-argumente-sollten-null-sein",{"title":"Default-Werte für Methoden-Argumente sollten null sein","abstract":"Oft genug sieht man Methodendefinitionen mit Standardwerten für Argumente, da viele Programmiersprachen das Überladen von Methoden, wie z.B. in Java, nicht unterstützen.\n","date":"2011-08-04T00:00:00.000Z","html":"\n \n Oft genug sieht man Methodendefinitionen mit Standardwerten für Argumente, da\n viele Programmiersprachen das Überladen von Methoden, wie z.B. in Java, nicht\n unterstützen.\n<\\/p>\n Ein einfaches Beispiel einer Methode mit zwei optionalen Argumenten: function connect($host, $port = 1234, $timeout = 60) { ... }<\\/code><\\/p>\n \n Möchte man nun diese Methode verwenden, und den letzten der beiden Parameter\n überschreiben, ist man gezwungen, auch den zweiten an zu geben, connect('server', 1234, 10);<\\/code>\n<\\/p>\n Eigentlich meint man aber connect('server', {default}, 10);<\\/code><\\/p>\n \n Und genau hier liegt das Problem: das Übernehmen des Standardwertes aus der\n Definition führt dazu, dass bei einer Änderung des Standardwertes<\\/em> sich diese\n Änderung nicht auf den Teil des Codes auswirkt, in dem die Methode aufgerufen\n wird — obwohl das eigentlich das Verhalten ist, dass der Verwender\n erwartet hätte.\n<\\/p>\n Deswegen sollten Standardwerte immer mit null<\\/code> definiert werden:<\\/p>\nfunction connect($host, $port = null, $timeout = null) {\n<\\/span> if ($port === null) $port = 1234;\n<\\/span> if ($timeout === null) $timeout = 10;\n<\\/span> ...\n<\\/span>}\n<\\/span><\\/code><\\/pre>\n\n So muss der Aufrufer Standardwerten nur Beachtung schenken, wenn er sie explizit\n überschreiben will. Ansonsten kann er einfach null<\\/code> übergeben: connect('server', null, 10);<\\/code>\n<\\/p>\n\n Übrigens hat Python, in dem das Überladen von Methoden nicht unterstützt wird,\n eine clevere Lösung dafür: beim Aufrufen einer Methode kann man die Argumente\nexplizit mit ihrem Namen ansprechen<\\/a>.\n<\\/p>\n","slug":"default-werte-fur-methoden-argumente-sollten-null-sein","hero":"!undefined"}],["define-a-communication-policy-so-slack-doesnt-kill-you",{"title":"Define a communication policy so Slack doesn't kill you","subtitle":"Distributed Teams","abstract":"Not matter which tool you use to communicate, one of the most important actions to tackle communication chaos is defining a communication policy.","date":"2017-06-20T10:00+02:00","html":"\n \n <\\/picture><\\/aside>\n<\\/p>\n\n Twist<\\/a> is the Doist team's answer to the overwhelming\n amount of real-time interaction\n they have experienced<\\/a>\n using Slack:\n<\\/p>\n \n \n It wasn’t healthy for our team, and it wasn’t helping us focus on the hard\n work that really moves projects forward.\n <\\/p>\n<\\/blockquote>\n \n Ironically, instead of changing their habits, which are the root cause for their\n issues, they set out to solve the problem by building a new tool, essentially a\n forum, with stricter rules applied to how communication should<\\/em> work.\n<\\/p>\n \n Every powerful tool, like Slack, comes with the responsibility to learn<\\/em> how to\n use it properly. And if you do, it's general purpose makes it so easily\n adaptable for many use cases. It's the same with Trello where boards can become\n very chaotic and overwhelming for users that don't know how which features are\n there to organize cards.\n<\\/p>\n\n Not matter which tool<\\/em> you use to communicate, one of the most important\n actions to tackle communication chaos<\\/em> is defining a communication policy<\\/strong>.\n (You can read about the rules at one of my former workplaces here.<\\/a>)\n This means that you establish a common, (written!), understanding within your\n team, which communication tool you use for what and what the expected response\n times are.\n<\\/p>\n Especially for a highly invasive tool like Slack rules like these can help:<\\/p>\n \n \n we don't expect to answer to Slack messages immediately, but within 4 hours on\n a work day\n <\\/li>\n \n we use the Do Not Disturb feature to signal if we need uninterrupted time to\n work\n <\\/li>\n we don't send Slack messages an Weekends or Holidays<\\/li>\n we rarely ever use @channel<\\/code> in general topic channels<\\/li>\n we switch to Video Chat if we observe that a ping-pong discussion is happening<\\/li>\n<\\/ul>\n\n It's also important to educate every team member about the features of each tool\n to manage notifications, and how to turn them off.\n<\\/p>\n \n So the next time when you start blaming a tool for limiting your ability to be\n productive, try taking a step back and find the root cause for the symptom.\n<\\/p>\n","slug":"define-a-communication-policy-so-slack-doesnt-kill-you","hero":"!undefined"}],["developer-happiness-questionnaire",{"title":"(developer) happiness questionnaire","abstract":"I use the (developer) happiness questionnaire to collect honest feedback about the happiness of my colleagues\n","date":"2016-01-26T15:00:00.000Z","html":"\n\n I use the (developer) happiness questionnaire to collect honest feedback about\n the happiness of my colleagues. It is based on the book\n First break all the rules<\\/a> by the Gallup Institute but\n has been slightly modified.\n<\\/p>\n \n Gallup tested thousands of questions<\\/a>\n on millions of employees to find the right questions with the exact wording that\n provided the highest correlation to business results most companies regularly\n measure — profitability, productivity, turnover, and safety.\n<\\/p>\n My modified version alters the phrasing of question 9, which originally reads<\\/p>\n \n Are my associates or fellow employees committed to doing quality work.<\\/p>\n<\\/blockquote>\n This is split into two questions:<\\/p>\n\n \n Are all colleagues working with all their possibilites for the company's\n goal? Is it favored to deliver high-quality work results?\n <\\/p>\n<\\/blockquote>\n \n This enables to distinguish between individual commitment to qualitity and the\n overall notion about quality throughout the organization.\n<\\/p>\n\n A new question is the\n net promotor score<\\/a> for teams:\n<\\/p>\n \n \n If I had a good friend who is looking for a new job, would I recommend them to\n apply here?\n <\\/p>\n<\\/blockquote>\n \n If there is one question that summarizes my understanding of a great place to\n work is: would I want my friends to work here, too?\n<\\/p>\n \n I let my colleagues fill out the anonymous form every other month, prior to\n all-hands meetings.\n<\\/p>\n \n I use Google Forms and give all colleagues an exact date and time when to fill\n out the form. This disables any form of tracking \\/ assigning individual answers\n to team members.\n<\\/p>\n \n During the all-hands meeting we go through the (accumulated) results and talk\n about what we can do to improve the ratings. The discussion alone is brilliant\n and the questionnaire is a great starter for this (necessary) discussion.\n Nevertheless, it helps you to keep track of the progress in tackling the issues\n that arise.\n<\\/p>\n \n These are the 14 questions, I've also translated them into German for a better\n understanding. Questions are answered in a range between 1 to 10. I keep the\n resulting median of all answers in a wiki as a history.\n<\\/p>\n\n \n Do I know what is expected of me at work? Weiß ich, was man von mir auf der Arbeit erwartet?<\\/em><\\/p>\n <\\/li>\n \n Do I have the materials and equipment I need to do my work right? Verfüge ich über die Mittel und Ausstattung um meine Arbeit richtig zu\nmachen?<\\/em><\\/p>\n <\\/li>\n \n Do I have the opportunity to do what I do best everyday? Habe ich jeden Tag die Gelegenheit, mein Bestes zu geben?<\\/em><\\/p>\n <\\/li>\n \n \n In the last 7 days, have I received recognition or praise for doing good\n work? Habe ich in den letzten 7 Tagen Anerkennung oder Lob für meine Arbeit\nerhalten?<\\/em>\n <\\/p>\n <\\/li>\n \n Does my supervisor or someone at work seem to care about me as a person? Schätzt mich mein Vorgesetzter oder jemand anderes auf der Arbeit als\nPerson?<\\/em><\\/p>\n <\\/li>\n \n Is there someone at work who encourages my development? Gibt es jemanden auf der Arbeit, der mich zur Weiterentwicklung ermutigt?<\\/em><\\/p>\n <\\/li>\n \n At work, do my opinions seem to count? Wird meine Meinung auf der Arbeit gewürdigt?<\\/em><\\/p>\n <\\/li>\n \n Does the mission \\/ purpose of my company make me feel my job is important? Gibt mir das Unternehmensziel das Gefühl, einen wichtigen Job zumachen?<\\/em><\\/p>\n <\\/li>\n \n \n Are all colleagues working with all their possibilites for the company's\n goal? Engagieren sich alle Mitarbeiter voll für das Unternehmensziel?<\\/em>\n <\\/p>\n <\\/li>\n \n Is it favored to deliver high-quality work results? Ist es gewünscht, dass qualitativ hochwertige Arbeitsergebnisse erzielt\nwerden?<\\/em><\\/p>\n <\\/li>\n \n Am I confident that the company's goals are actually achievable? Bin ich davon überzeugt, dass das gesteckte Unternehmensziel erreicht\nwerden kann?<\\/em><\\/p>\n <\\/li>\n \n In the last 6 months, has someone talked to me about my progress? Hat jemand in den letzten 6 Monaten mit mir über meinen Fortschritt\ngesprochen?<\\/em><\\/p>\n <\\/li>\n \n Do I have the opportunity at work to learn and grow? Habe ich die Möglichkeit auf der Arbeit zu lernen und mich weiter zu\nentwickeln?<\\/em><\\/p>\n <\\/li>\n \n \n If I had a good friend who is looking for a new job, would I recommend them\n to apply here? Würde ich einem guten Freund\\/in, der\\/die auf Jobsuche ist, empfehlen sich\nhier zu bewerben?<\\/em>\n <\\/p>\n <\\/li>\n<\\/ol>\n","slug":"developer-happiness-questionnaire","hero":"!undefined"}],["die-browserkompatibilitatsklausel",{"title":"Die Browserkompatibilitätsklausel","abstract":"Wenn man in der glücklichen Situation ist, ein Angebot zu schreiben, ist dessen Basis in der Regel auch eine möglichst genaue Beschreibung über den Umfang des Auftrags, im Allgemeinen Pflichtenheft genannt.","date":"2011-10-09T00:00:00.000Z","lang":"de","html":"\n \n Wenn man in der glücklichen Situation ist, ein Angebot zu schreiben, ist dessen\n Basis in der Regel auch eine möglichst genaue Beschreibung über den Umfang des\n Auftrags, im Allgemeinen Pflichtenheft<\\/em> genannt.\n<\\/p>\n \n Die Ausformulierung ist dabei entscheidend um im Fall von\n Meinungsverschiedenheiten klar bestimmen zu können, welche Partei Recht hat.\n Speziell bei Software kann aber die Beschreibung von Funktionen oft nicht exakt\n erfolgen — läuft die Software in einem vorher nicht genau bekannten Umfeld\n trifft man unweigerlich auf dieses Problem.\n<\\/p>\n \n Die Regel ist das bei Anwendungen, die im Webbrowser dargestellt werden. Die\n Vielzahl existierender Browser und Platformen macht es praktisch unmöglich, die\n exakte Darstellung in verschiedenen Browsern zu garantieren<\\/strong>. Dieser Umstand\n ist allgemein akzeptiert und inzwischen existiert das Bewußtsein dafür auch auf\n Kundenseite.\n<\\/p>\n Wie aber formuliert man solche “Ungenauigkeiten” möglichst genau<\\/em>?<\\/p>\n Den folgenden Absatz verwende ich in Pflichtenheften.<\\/p>\n\n Browser-Unterstützung<\\/p>\n Unterstützt werden:<\\/p>\n \n Internet-Explorer 7-9<\\/li>\n Firefox 3.6-6<\\/li>\n Safari 5<\\/li>\n <\\/ul>\n \n Browser-Unterstützung, der aufgelisteten Browser und Versionen, bedeutet, dass\n die volle Funktionalität der Anwendung in diesen Browsern gewährleistet ist.\n Eine pixelgenaue, identische Darstellung in allen Browsern und unter allen\n Plattformen kann nicht gewährleistet werden, jedoch wird eine, im Sinne der\n Gestaltung und aus Sicht des Benutzers, fehlerfreie Darstellung angestrebt.\n <\\/p>\n Eine Plattform ist ein Computer, Smartphone, Spielekonsole etc.<\\/p>\n<\\/blockquote>\n \n Die Wahl der Browser und Versionen ist dabei natürlich an das jeweilige Projekt\n angepasst. Als Faustregel sollte man die Browserversionen unterstützen, die in\n den Webserverstatistiken der Website (falls vorhanden) von mehr als 3% der\n Besucher verwendet werden — eine Ausnahme ist hier der IE6, eine Unterstützung\n für diesen Browser sollte in der Aufwandsschätzung für die Umsetzung in HTML und\n JS mit einem Aufschlag von 30% berücksichtigt werden.\n<\\/p>\n \n Wichtig ist noch, dass man auf keinen Fall eine Aufwärtskompatibilität\n garantieren darf, z.B. mit Formulierungen wie “IE 9+”, dies führt zu\n unkalkulierbaren Aufwänden, und der Kunde hat den Eindruck, dass seine Website\n auch noch in 10 Jahren einwandfrei funktionieren wird.\n<\\/p>\n","slug":"die-browserkompatibilitatsklausel","hero":"!undefined"}],["distributeaid-contributor-spotlight",{"subtitle":"Impact","title":"Why I contribute to DistributeAid","abstract":"In this post I introduce myself for a DistributeAid contributor spotlight and talk about the work I do for the non-profit.","date":"2022-03-14T21:00:00.000Z","html":"\n\n \n In this post I introduce myself for a\n DistributeAid<\\/a> contributor spotlight and talk\n about the work I do for the non-profit.\n <\\/p>\n<\\/blockquote>\n \n I first heard about DistributeAid at Øredev 2019 in Malmö, and was immediately\n inspired by their idea to use technology to improve the distribution of donated\n goods for displaced people. And in the last three years we have seen that the\n network of grassroots organizations which DistributeAid supports is needed to\n help people who have been affected by political and ecological disasters, caused\n after all by the global north, which I have the privilege and luck to be born\n in. Besides the ongoing imprisonment of migrants and asylum-seekers on the\n southern European borders, DistributeAid's team helped with logistics during the\n COVID-19 pandemic in Europe and the United States. And most recently got\n involved in welcoming Afghan families to the United States after Kabul was taken\n over by the Taliban in 2021. The invasion of Ukraine by the Russian dictator\n Putin in 2022 created yet another region where DistributeAid is involved to\n provide people with basic everyday items.\n<\\/p>\n \n As a code contributor to DistributeAid's projects, which you can find on their\n GitHub repository github.com\\/distributeaid<\\/a>,\n I can work on digital tools that are used to achieve the organization's goals. I\n worked on a digital COVID-19 guide for aid organizations, integrated APIs from\n shipping partners, and most recently built a low-code tools used to assess the\n needs of aid groups they support. I enjoy that DistributeAid has a people-first\n approach to contributions and we try to provide software projects that are both\n easy to get started with and easy to change. After all, done is better than\n perfect and areas of focus can change quickly. Because we contributors are\n distributed around the world, we need to keep our codebases well in shape, which\n means that we write a lot of tests, and keep our documentation up to date, so\n others can contribute big and small features without needing to be in the loop\n constantly and new contributes can start with smaller items quickly.\n<\\/p>\n \n What has kept me engaged with DistributeAid over nearly three years now is\n knowing that the code that I write is making a difference. And I am extremely\n impressed by Sara, Taylor and many other contributors who put their professional\n skills into this project without making this about themselves. Everyone is\n extremely humble and helpful. I wish all tech projects could be like this. And\n then I wish we wouldn't need DistributeAid. This is the dichotomy we all face\n when engaging with DistributAid. But this team has your back, because everyone\n knows that you can't burn the candle at both ends and you need to be in good\n mental state, before you can help others.\n<\\/p>\n \n If you are interested to contribute to our projects, just reach out to me, or\n any other Distribute Aid team member!\n<\\/p>\n","slug":"distributeaid-contributor-spotlight","hero":"!undefined"}],["do-not-change-two-different-things-in-one-pull-request",{"title":"Do not change two different things in one Pull Request","subtitle":"Best practice","abstract":"A pull request should only address one change at a time.","date":"2026-01-02T00:10:00+01:00","html":"\n A Pull Request should only address one change at a time.<\\/p>\n \n Reviewers might not have an in-depth understanding of how things relate to each\n other in a project so do not mix conceptually different changes in one PR.\n<\\/p>\n Some examples of what not to do:<\\/p>\n \n \n fix a bug AND update all dependencies. If a bug fix requires a new dependency\n or an update to one, then only add this single dependency change.\n <\\/li>\n \n implement a new feature AND fix a small bug on an unrelated file. Those should\n be two PRs.\n <\\/li>\n<\\/ul>\n","slug":"do-not-change-two-different-things-in-one-pull-request","hero":"!undefined"}],["do-not-expect-an-llm-to-think",{"title":"Do not expect an LLM to think","subtitle":"Lessons learned","abstract":"LLMs are excellent at scaffolding code that follows an existing pattern. They are not equipped to design new domain concepts. When you let one do design work, you get code that looks right, tests that pass, and an implementation that quietly misses the point. Worse: you own none of the understanding, so when something breaks, you're debugging a library you didn't write.","date":"2026-05-14T11:37:00+02:00","html":"\n\n <\\/picture><\\/aside>\n<\\/p>\n\n \n tl;dr<\\/strong> LLMs are excellent at scaffolding code that follows an existing\n pattern. They are not equipped to design new domain concepts. When you let one\n do design work, you get code that looks right, tests that pass, and an\n implementation that quietly misses the point. Worse: you own none of the\n understanding, so when something breaks, you're debugging a library you didn't\n write.\n <\\/p>\n<\\/blockquote>\n \n When all the tests are green but the implementation is wrong, you have a\n problem. And you have made that problem yourself.\n<\\/p>\n \n This week I introduced a new concept into an existing billing system. We\n currently bill on a per-project basis. The new requirement was to introduce\n organizations<\\/em>: an organization owns multiple projects, and instead of one\n invoice per project, the organization owner gets a single consolidated invoice.\n<\\/p>\n Same billing rules. Same pricing logic. Just applied to a higher-level entity.<\\/p>\n \n The existing implementation was well-tested and solid. This looked like a\n perfect LLM task: the pattern is established, the tests are clear, the scope is\n bounded. I asked the LLM to introduce the organization concept, told it to look\n at the existing tests, and make it work for an organization owning multiple\n projects.\n<\\/p>\n \n The initial results were promising. New modules, new method names, new test\n files, good coverage. There was a small bit of hand-holding needed around how we\n identify organizations—they use a different ID format than projects—but overall\n it looked like a win.\n<\\/p>\n \n Then I started wiring the new domain logic into the actual consumers, and the\n cracks appeared.\n<\\/p>\nThe tests were lying<\\/h2>\n\n The issues were not dramatic. No obvious failures. They were subtle<\\/em>—quiet\n mismatches between what the tests assumed and what the business actually\n required. I went back to the domain implementation to fix something. Then again.\n Then again. Four times in total.\n<\\/p>\n \n A concrete example: our billing has a minimum charge rule. If your total monthly\n usage comes to less than $2.00, you still pay $2.00.\n<\\/p>\n \n In the per-project billing, this is simple: sum the usage, apply the rate, check\n against the floor. The LLM ported this rule to the organization level by\n applying it per project<\\/em>. Three projects using $0.10 each would result in a\n $6.00 bill instead of $2.00, because each project individually hits the minimum.\n<\\/p>\n \n The minimum charge belongs on the organization invoice—the thing the customer\n actually pays—not on each individual project. But the concept of the invoice<\\/em>\n was implicit in the per-project implementation. It was just the natural unit. At\n the organization level it becomes a derived concept, only meaningful after\n summing across all projects. The LLM didn't understand that this rule needed to\n be lifted to a higher abstraction level. It only saw the mechanics: here is a\n rule, apply it at each step.\n<\\/p>\n \n The tests didn't catch this because the generated test data wasn't adversarial.\n Two projects, charges above the minimum, everything sums correctly—all green.\n The discrepancy only surfaced when I ran real customer usage data through both\n the old and new implementations side by side.\n<\\/p>\nDebugging code you didn't write<\\/h2>\nWhat I underestimated is the cost of not<\\/em> having written the code yourself.<\\/p>\n \n Every time I hit a bug I was in the position of debugging a third-party library\n I didn't write and don't fully understand. I'd look at the symptom, form a\n hypothesis, and ask the LLM for a targeted fix—without truly grasping whether\n that fix would hold in other situations. This is the console.log<\\/code> debugging\n mode: poking at the surface, observing behavior, inferring structure. Slow,\n fragile, and deeply unsatisfying.\n<\\/p>\n \n A feedback loop makes it worse: each fix feels small. Just change this one\nthing, then it will work.<\\/em> So you keep delegating back to the LLM. But the LLM\n can only act on what you describe. It doesn't understand your goal—it\n understands your instruction. It will dutifully add a parameter, loop over\n projects, apply the calculation, and miss the point entirely.\n<\\/p>\nScaffolding vs. design<\\/h2>\nThe mistake was misclassifying the task.<\\/p>\n \n There are things LLMs are excellent at in an existing codebase. Scaffolding a\n new REST route that follows the same pattern as the 25 others in the project?\n Perfect. Generate the handler, the CDK construct, wire it into the existing\n infrastructure. The output is obviously correct by inspection because the\n pattern is unambiguous.\n<\\/p>\n \n Introducing a new domain concept that changes how the entire billing model is\n structured is a design<\\/em> task. It requires understanding intent. It requires\n knowing which implicit assumptions need to become explicit, which rules belong\n at which level of abstraction, what the code is for<\\/em>—not just what it does<\\/em>.\n<\\/p>\n LLMs can replicate structure. They cannot reason about intent.<\\/p>\nWhat I should have done<\\/h2>\nWritten it myself.<\\/p>\n \n Not because the LLM couldn't produce working-looking code—it clearly could. But\n because the process of writing domain logic is<\\/em> how you discover the domain.\n The resistance you feel when you try to implement a rule at the wrong\n abstraction level, the moment you realize the minimum charge can't live on the\n project anymore—those are discoveries that only happen when you<\\/em> are making the\n decisions.\n<\\/p>\n \n By outsourcing the implementation, I outsourced the understanding. And\n understanding is not optional when things go wrong.\n<\\/p>\n \n The LLM saved me roughly two hours of initial implementation and cost me several\n times that in confused debugging and rework. The irony is that the task that\n looked most<\\/em> suited to LLM delegation—structured, well-precedented, bounded—\n turned out to require exactly the kind of judgment LLMs don't have.\n<\\/p>\n Use an LLM to follow a pattern. Don't use it to design one.<\\/p>\n","slug":"do-not-expect-an-llm-to-think","hero":"!undefined"}],["dont-use-global-state-like-env-vars-in-modules",{"title":"Don't use global state like env variables in modules","subtitle":"Best practice","abstract":"This hides dependencies to configuration values and makes them hard to spot.","date":"2025-12-28T12:38+01:00","html":"\n \n Don't use global state like env variables in modules, only on the very top-level\n or in one central location. Pass it in the constructor.\n<\\/p>\n This hides dependencies to configuration values and makes them hard to spot.<\\/p>\nBad<\\/h2>\nclass<\\/span> Foo<\\/span> {<\\/span>\n<\\/span> doSomething<\\/span>(<\\/span>)<\\/span> {<\\/span>\n<\\/span> console<\\/span>.<\\/span>log<\\/span>(<\\/span>process.<\\/span>env<\\/span>.<\\/span>MY_ENV<\\/span>)<\\/span>;<\\/span>\n<\\/span> }<\\/span>\n<\\/span>}<\\/span>\n<\\/span>\n<\\/span>new<\\/span> Foo<\\/span>(<\\/span>)<\\/span>.<\\/span>doSomething<\\/span>(<\\/span>)<\\/span>;<\\/span>\n<\\/span><\\/code><\\/pre>\nGood<\\/h2>\nclass<\\/span> Foo<\\/span> {<\\/span>\n<\\/span> constructor<\\/span>(<\\/span>myEnv<\\/span>)<\\/span> {<\\/span>\n<\\/span> this<\\/span>.<\\/span>myEnv<\\/span> =<\\/span> myEnv;<\\/span>\n<\\/span> }<\\/span>\n<\\/span> doSomething<\\/span>(<\\/span>)<\\/span> {<\\/span>\n<\\/span> console<\\/span>.<\\/span>log<\\/span>(<\\/span>this<\\/span>.<\\/span>myEnv<\\/span>)<\\/span>;<\\/span>\n<\\/span> }<\\/span>\n<\\/span>}<\\/span>\n<\\/span>\n<\\/span>new<\\/span> Foo<\\/span>(<\\/span>process.<\\/span>env<\\/span>.<\\/span>MY_ENV<\\/span>)<\\/span>.<\\/span>doSomething<\\/span>(<\\/span>)<\\/span>;<\\/span>\n<\\/span><\\/code><\\/pre>\n","slug":"dont-use-global-state-like-env-vars-in-modules","hero":"!undefined"}],["duplicity-fehler-ioerror-gnupg-exited-non-zero-with-code-2-unter-ubuntu-beheben",{"title":"duplicity Fehler “IOError: GnuPG exited non-zero, with code 2” unter Ubuntu beheben","abstract":"Zum Sichern von Daten auf FTP-Server bietet sich duplicity. Es bietet, ähnlich wie rdiff-backup, die Möglichkeit, volle und inkrementelle Backups zu erzeugen, aber im Gegensatz zu rdiff-Backup eben auf FTP-Server und noch dazu verschlüsselt.","date":"2010-05-09T00:00:00.000Z","lang":"de","html":"\n\n Zum Sichern von Daten auf FTP-Server bietet sich duplicity<\\/a>. Es bietet,\n ähnlich wie rdiff-backup<\\/a>, die Möglichkeit, volle und inkrementelle Backups\n zu erzeugen, aber im Gegensatz zu rdiff-Backup eben auf FTP-Server und noch dazu\n verschlüsselt.\n<\\/p>\n \n Allerdings hat die Version in Ubuntu 9.04 (Jaunty Jackalope) einen Bug, der\n bewirkt, dass duplicity mit folgender Fehlermeldung den Dienst quittiert:\n<\\/p>\n IOError: GnuPG exited non-zero, with code 2\n<\\/span><\\/code><\\/pre>\nDas lässt sich relativ einfach beheben: duplicity manuell installieren.<\\/p>\n Dazu geht man wie folgt vor:<\\/p>\n Ubuntu's duplicity entfernen:<\\/p>\naptitude purge duplicity\n<\\/span><\\/code><\\/pre>\npython-dev und librsync-dev werden zum kompilieren von duplicity benötigt:<\\/p>\naptitude install python-dev librsync-dev\n<\\/span><\\/code><\\/pre>\nDie aktuelle Version herunterladen und installieren<\\/p>\ncd \\/opt\n<\\/span>wget http:\\/\\/code.launchpad.net\\/duplicity\\/0.6-series\\/0.6.08b\\/+download\\/duplicity-0.6.08b.tar.gz\n<\\/span>tar xvzf duplicity-0.6.08b.tar.gz\n<\\/span>cd duplicity-0.6.08b\n<\\/span>python setup.py install\n<\\/span><\\/code><\\/pre>\nNun ist duplicity installiert.<\\/p>\n \n Tritt der Fehler auf, nachdem bereits eine Weile das Backup problemlos\n funktioniert hat, muss man die alten Dateien leider entsorgen und mit einem\n neuen Full-Backup starten.\n<\\/p>\n","slug":"duplicity-fehler-ioerror-gnupg-exited-non-zero-with-code-2-unter-ubuntu-beheben","hero":"!undefined"}],["eclipse-clean-refresh",{"title":"Eclipse: -clean -refresh","abstract":"Manchmal, also eigentlich regelmäßig, hängt Eclipse.","date":"2010-12-21T00:00:00.000Z","lang":"de","html":"\n Manchmal, also eigentlich regelmäßig, hängt Eclipse.<\\/p>\n\n The User Operation is waiting for background work to complete<\\/p>\n<\\/blockquote>\n\n oder ähnliche extrem hilfreiche<\\/em> Statusmeldungen hängen dann gerne mal\n ungefragt bis zum Sankt-Nimmerleins-Tag<\\/a> auf dem Bildschirm rum.\n<\\/p>\n Da hilft nur ein<\\/p>\n \n eclipse -clean -refresh<\\/code><\\/p>\n<\\/blockquote>\n \n Das dauert zwar etwas länger, beseitigt aber z.B. Deadlocks, die für die Hänger\n verantwortlich sind.\n<\\/p>\n","slug":"eclipse-clean-refresh","hero":"!undefined"}],["eclipse-standard-wert-fur-author-in-javadoc-andern",{"title":"Eclipse: Standard-Wert für @author in JavaDoc ändern","abstract":"Der Standard-Werte für den @author-Tag in JavaDoc ist der Username des Accounts, der Eclipse gestartet hat.","date":"2010-06-13T00:00:00.000Z","lang":"de","html":"\n \n Der Standard-Werte für den @author<\\/code>-Tag in JavaDoc ist der Username des\n Accounts, der Eclipse gestartet hat.\n<\\/p>\n\n Dies lässt sich einfach überschreiben, in dem man in der\n eclipse.ini<\\/a>, die sich im Programm-Ordner\n von eclipse findet, diese Zeile einfügt:\n<\\/p>\n -Duser.name=Some User <someuser@example.com>\n<\\/span><\\/code><\\/pre>\n","slug":"eclipse-standard-wert-fur-author-in-javadoc-andern","hero":"!undefined"}],["encrypt-login-links",{"title":"Encrypt Login Links","abstract":"Encrypt login links with the users public PGP key to add a simple but effective layer of security with only a small usability impact.\n","date":"2015-01-03T16:40:00.000Z","html":"\n\n I believe that logging into a web based application using a username and a\n password should be abolished. If you want to learn more about the advantages of\npassword-less logins, read this article<\\/a>.<\\/em>\n<\\/p>\n \n If you implement a password-less login, your users will receive a login link in\n ther email inbox which will be valid for some time.\n<\\/p>\n \n Unfortunately this creates a potential attack surface as anyone who has access\n to the user's mailbox or can intercept unecrypted communication of the users\n email client with their mailserver can use the link to access their account.\n There are various options to ensure that an attacker can do nothing harmful with\n the access to a users account (like creating extra out-of-band challenges for\n dangerious account modifications) but there exists an easy one: encrypt the\nlogin link with the users public PGP key<\\/strong>.\n<\\/p>\n \n If a user knows how to handle PGP you should provide an option in the\n application's dashboard to provide his public PGP key for his account. Make sure\n you verify this key bevore using it, though. Once enabled this adds a simple but\n effective layer of security with only a small usability impact.\n<\\/p>\n","slug":"encrypt-login-links","hero":"!undefined"}],["entwickler-und-projektmanager",{"title":"Entwickler und Projektmanager","abstract":"Diese zwei Kollegen stehen immer auf meinem Schreibtisch bei meinem aktuellen Arbeitgeber. Vor ein paar Monaten standen sie bei Scholz&Volkmer und als ich mit einem Kollegen darüber sprach, ist ein interessantes Bildnis entstanden.","date":"2011-11-24T00:00:00.000Z","lang":"de","html":"\n \n <\\/a>Diese\n zwei Kollegen stehen immer auf meinem Schreibtisch bei meinem aktuellen\n Arbeitgeber. Vor ein paar Monaten standen sie bei\n Scholz&Volkmer<\\/a> und\n als ich mit einem Kollegen darüber sprach, ist ein interessantes Bildnis\n entstanden.\n<\\/p>\n \n Der Große (der Marine aus dem Computerspiel “Quake II”) ist ein Entwickler<\\/strong>:\n ziemlich grobschlächtig mit dem Hang zu schnellen einfachen Lösungen, aber halt\n für die dreckige Aufgabe des codens bestens geeignet — die Waffe benutzt er um\n Bugs<\\/em> zu töten.\n<\\/p>\n \n Aber ohne den Projektmanager<\\/strong> davor ist der Entwickler aufgeschmissen. Mit\n seiner Lampe sucht und findet der Projektmanager Bugs und weißt dem Entwickler\n den Weg durch den Projektdschungel. Die Schutzausrüstung braucht er dabei vor\n allem im Umgang mit dem Kunden — das kann nämlich manchmal sehr giftig werden.\n<\\/p>\n \n Wichtig dabei ist aber, dass beide nur gut als Team funktionieren können, weil\n sie sich so gut ergänzen — arbeiten sie nicht zusammen, oder sogar\n gegeneinander, wird die Arbeit am Projekt viel schwieriger als nötig.\n<\\/p>\n","slug":"entwickler-und-projektmanager","hero":"!undefined"}],["es-and-cqrs-on-aws-simplified",{"title":"ES+CQRS on AWS: the simplest version yet","abstract":"I have been iterating on Event Sourcing and CQRS architectures for nearly a decade. When I first started with this pattern around 2016 and 2017, the implementation was considerably more complex — a lot of ceremony, a lot of infrastructure, and a lot of things that could go wrong. Over the years I have stripped it back again and again, and what I have arrived at now is something I'm genuinely happy with: a small, focused TypeScript library backed by DynamoDB that does exactly what it needs to and nothing more.","date":"2026-05-17T15:00:00+02:00","html":"\n \n <\\/picture><\\/aside>\n<\\/p>\n\n I have been iterating on Event Sourcing and CQRS architectures for nearly a\n decade. When I first started with this pattern around 2016 and 2017, the\n implementation was considerably more complex — a lot of ceremony, a lot of\n infrastructure, and a lot of things that could go wrong. Over the years I have\n stripped it back again and again, and what I have arrived at now is something\n I'm genuinely happy with: a small, focused TypeScript library backed by DynamoDB\n that does exactly what it needs to and nothing more.\n<\\/p>\n\n The code is available at\n github.com\\/coderbyheart\\/aws-dynamodb-es-cqrs<\\/a>.\n<\\/p>\n What ES+CQRS gives you<\\/h2>\n\n The core idea is simple: instead of storing the current state of a thing, you\n store the sequence of events that produced that state. Event Sourcing (ES) is\n the \"store events\" part. CQRS (Command Query Responsibility Segregation) is the\n recognition that writing and reading are fundamentally different concerns that\n benefit from being handled separately.\n<\\/p>\n \n In practice this means that when someone publishes a blog post, you don't update\n a published = true<\\/code> column. You append a BlogPostPublished<\\/code> event to the event\n log. The current state — the aggregate — is derived by replaying those events.\n This gives you a full audit trail for free, the ability to rebuild projections,\n and a natural boundary for business logic.\n<\\/p>\nThe anatomy of an event<\\/h2>\n\n Every event in the system is an AggregateEvent<\\/code>. The type is intentionally\n minimal:\n<\\/p>\nexport<\\/span> type<\\/span> AggregateEvent<\\/span> =<\\/span> {<\\/span>\n<\\/span> eventId:<\\/span> ULID<\\/span>;<\\/span>\n<\\/span> eventName:<\\/span> string<\\/span>;<\\/span>\n<\\/span> aggregateName:<\\/span> string<\\/span>;<\\/span>\n<\\/span> aggregateId:<\\/span> ULID<\\/span>;<\\/span>\n<\\/span> aggregateVersion:<\\/span> AggregateVersion;<\\/span>\n<\\/span> actorId:<\\/span> string<\\/span>;<\\/span>\n<\\/span>}<\\/span>;<\\/span>\n<\\/span><\\/code><\\/pre>\n\n A few things worth noting here. eventId<\\/code> and aggregateId<\\/code> use\n ULIDs<\\/a> — universally unique, lexicographically\n sortable identifiers. This means events stored in DynamoDB are naturally ordered\n by creation time without needing a separate timestamp index. aggregateVersion<\\/code>\n is an incrementing integer that starts at 1<\\/code> and tracks how many events have\n been applied to a given aggregate. actorId<\\/code> records who or what triggered the\n event.\n<\\/p>\n \n Domain events extend this base type and add their own payload fields. A\n BlogPostCreatedEvent<\\/code>, for example, adds title<\\/code> and whatever else the domain\n needs.\n<\\/p>\n Reducing events to state<\\/h2>\n\n The event sourcing half of the pattern lives in reduceEvents<\\/code>. It takes an\n applyEvent<\\/code> function and returns a function that folds a list of events into an\n aggregate:\n<\\/p>\nexport<\\/span> const<\\/span> reduceEvents =<\\/span>\n<\\/span> <<\\/span>A<\\/span> extends<\\/span> Record<<\\/span>string<\\/span>,<\\/span> any<\\/span>><\\/span><\\/span> &<\\/span> {<\\/span> $meta:<\\/span> AggregateMeta }<\\/span>><\\/span>(<\\/span>\n<\\/span> applyEvent:<\\/span> ApplyEventFn<<\\/span>A<\\/span>><\\/span>,<\\/span>\n<\\/span> )<\\/span>:<\\/span> ApplyEventsFn<<\\/span>A<\\/span>><\\/span> =><\\/span>\n<\\/span> (<\\/span>events:<\\/span> Array<\\/span><<\\/span>AggregateEvent><\\/span>,<\\/span> aggregate?<\\/span>:<\\/span> A<\\/span>)<\\/span> =><\\/span> {<\\/span>\n<\\/span> if<\\/span> (<\\/span>events.<\\/span>length ===<\\/span> 0<\\/span>)<\\/span> throw<\\/span> new<\\/span> Error<\\/span>(<\\/span>\"No events to reduce!\"<\\/span>)<\\/span>;<\\/span>\n<\\/span> return<\\/span> events.<\\/span>reduce<\\/span><<\\/span>A<\\/span> |<\\/span> undefined<\\/span>><\\/span><\\/span><\\/span>(<\\/span>(<\\/span>agg,<\\/span> event)<\\/span> =><\\/span> {<\\/span>\n<\\/span> const<\\/span> result =<\\/span> applyEvent<\\/span>(<\\/span>event,<\\/span> agg)<\\/span>;<\\/span>\n<\\/span> if<\\/span> (<\\/span>result ===<\\/span> undefined<\\/span>)<\\/span>\n<\\/span> throw<\\/span> new<\\/span> Error<\\/span>(<\\/span>\n<\\/span> `<\\/span>Unhandled event: <\\/span>${<\\/span>event.<\\/span>eventName}<\\/span><\\/span> (aggregateVersion: <\\/span>${<\\/span>event.<\\/span>aggregateVersion}<\\/span><\\/span>)<\\/span>`<\\/span><\\/span>,<\\/span>\n<\\/span> )<\\/span>;<\\/span>\n<\\/span> return<\\/span> result;<\\/span>\n<\\/span> }<\\/span>,<\\/span> aggregate)<\\/span> as<\\/span> A<\\/span>;<\\/span>\n<\\/span> }<\\/span>;<\\/span>\n<\\/span><\\/code><\\/pre>\n\n The domain-specific reducer wires this together. The blog post reducer handles\n three events — created, published, and title changed — using typed event guards\n (isNamedEvent<\\/code>) and assertions (assertAggregateEvent<\\/code>) to make the TypeScript\n types precise:\n<\\/p>\nexport<\\/span> const<\\/span> blogpostReducer =<\\/span> reduceEvents<\\/span><<\\/span>BlogPostAggregate><\\/span><\\/span><\\/span>(<\\/span>\n<\\/span> (<\\/span>event,<\\/span> aggregate)<\\/span> =><\\/span> {<\\/span>\n<\\/span> if<\\/span> (<\\/span>isBlogPostCreatedEvent<\\/span>(<\\/span>event)<\\/span>)<\\/span> {<\\/span>\n<\\/span> return<\\/span> {<\\/span>\n<\\/span> $meta:<\\/span> fromEvent<\\/span>(<\\/span>event)<\\/span>,<\\/span>\n<\\/span> authorId:<\\/span> event.<\\/span>actorId,<\\/span>\n<\\/span> title:<\\/span> event.<\\/span>title,<\\/span>\n<\\/span> }<\\/span>;<\\/span>\n<\\/span> }<\\/span>\n<\\/span> if<\\/span> (<\\/span>isBlogPostPublishedEvent<\\/span>(<\\/span>event)<\\/span>)<\\/span> {<\\/span>\n<\\/span> assertAggregateEvent<\\/span>(<\\/span>aggregate,<\\/span> event)<\\/span>;<\\/span>\n<\\/span> return<\\/span> {<\\/span>\n<\\/span> ...<\\/span>aggregate,<\\/span>\n<\\/span> $meta:<\\/span> updateFromEvent<\\/span>(<\\/span>aggregate.<\\/span>$meta,<\\/span> event)<\\/span>,<\\/span>\n<\\/span> isPublic:<\\/span> true<\\/span>,<\\/span>\n<\\/span> }<\\/span>;<\\/span>\n<\\/span> }<\\/span>\n<\\/span> if<\\/span> (<\\/span>isBlogPostTitleChangedEvent<\\/span>(<\\/span>event)<\\/span>)<\\/span> {<\\/span>\n<\\/span> assertAggregateEvent<\\/span>(<\\/span>aggregate,<\\/span> event)<\\/span>;<\\/span>\n<\\/span> return<\\/span> {<\\/span>\n<\\/span> ...<\\/span>aggregate,<\\/span>\n<\\/span> $meta:<\\/span> updateFromEvent<\\/span>(<\\/span>aggregate.<\\/span>$meta,<\\/span> event)<\\/span>,<\\/span>\n<\\/span> title:<\\/span> event.<\\/span>title,<\\/span>\n<\\/span> }<\\/span>;<\\/span>\n<\\/span> }<\\/span>\n<\\/span> return<\\/span> undefined<\\/span>;<\\/span>\n<\\/span> }<\\/span>,<\\/span>\n<\\/span>)<\\/span>;<\\/span>\n<\\/span><\\/code><\\/pre>\n\n The assertAggregateEvent<\\/code> call on the update and publish handlers is doing\n something important: it verifies that an aggregate already exists before trying\n to apply a state-changing event. You cannot publish a blog post that was never\n created.\n<\\/p>\nCommands: the write side<\\/h2>\n\n Commands live on the write side of the CQRS split. They are plain async\n functions that take some input and a persistence function, validate\n preconditions against the current aggregate state, produce an event, apply it\n through the reducer, persist both the resulting aggregate and the event, and\n return the updated aggregate.\n<\\/p>\n Here is what creating a blog post looks like:<\\/p>\nexport<\\/span> const<\\/span> createBlogPostCommand<\\/span> =<\\/span>\n<\\/span> (<\\/span>\n<\\/span> persistBlogPost:<\\/span> PersistBlogPostFn,<\\/span>\n<\\/span> reducer:<\\/span> ApplyEventsFn<<\\/span>BlogPostAggregate><\\/span>,<\\/span>\n<\\/span> )<\\/span> =><\\/span>\n<\\/span> async<\\/span> (<\\/span>\n<\\/span> data:<\\/span> Omit<<\\/span>BlogPostAggregate,<\\/span> \"$meta\"<\\/span> |<\\/span> \"authorId\"<\\/span>><\\/span>,<\\/span>\n<\\/span> actorId:<\\/span> string<\\/span>,<\\/span>\n<\\/span> )<\\/span>:<\\/span> Promise<\\/span><<\\/span>BlogPostAggregate><\\/span> =><\\/span> {<\\/span>\n<\\/span> const<\\/span> id =<\\/span> ulid<\\/span>(<\\/span>)<\\/span> as<\\/span> ULID<\\/span>;<\\/span>\n<\\/span> const<\\/span> event:<\\/span> BlogPostCreatedEvent =<\\/span> {<\\/span>\n<\\/span> eventId:<\\/span> ulid<\\/span>(<\\/span>)<\\/span> as<\\/span> ULID<\\/span>,<\\/span>\n<\\/span> eventName:<\\/span> EventNames.<\\/span>BlogPostCreated,<\\/span>\n<\\/span> aggregateName:<\\/span> AggregateNames.<\\/span>BlogPost,<\\/span>\n<\\/span> aggregateId:<\\/span> id,<\\/span>\n<\\/span> aggregateVersion:<\\/span> v1,<\\/span>\n<\\/span> actorId,<\\/span>\n<\\/span> ...<\\/span>data,<\\/span>\n<\\/span> }<\\/span>;<\\/span>\n<\\/span> const<\\/span> applied =<\\/span> reducer<\\/span>(<\\/span>[<\\/span>event]<\\/span>)<\\/span>;<\\/span>\n<\\/span> await<\\/span> persistBlogPost<\\/span>(<\\/span>applied,<\\/span> event)<\\/span>;<\\/span>\n<\\/span> return<\\/span> applied;<\\/span>\n<\\/span> }<\\/span>;<\\/span>\n<\\/span><\\/code><\\/pre>\n\n The reducer is injected alongside the persist function rather than imported\n directly. This keeps commands decoupled from any specific reducer implementation\n and makes them straightforward to test in isolation. A command for updating an\n existing aggregate (like publishBlogPostCommand<\\/code>) follows the same pattern:\n inject both the persist function and the reducer, load the current state, verify\n preconditions, produce a new event at the next version. Concurrency conflicts\n are detected at the persistence layer using optimistic locking, so you get a\n ConflictError<\\/code> if two commands race on the same aggregate.\n<\\/p>\nPersistence: one transaction, two tables<\\/h2>\n\n The most interesting part of this design is the persistence layer. Everything\n happens in a single DynamoDB TransactWriteItems<\\/code> call that touches two tables\n atomically:\n<\\/p>\n\n \n \n The aggregate table<\\/strong> is upserted with an optimistic concurrency check. For\n a new aggregate, the condition is attribute_not_exists(aggregateId)<\\/code>. For an\n update, it is #version = :prevVersion<\\/code>. If either condition fails, DynamoDB\n cancels the whole transaction and the application surfaces a conflict error.\n <\\/p>\n <\\/li>\n \n \n The events table<\\/strong> receives a new Put<\\/code> item containing the full event\n payload, plus a derived eventTs<\\/code> (an ISO timestamp decoded from the ULID)\n for convenience.\n <\\/p>\n <\\/li>\n<\\/ol>\n \n The error handling checks cancellation reasons across both transaction slots — a\n DuplicateItem<\\/code> on the events table (index 1<\\/code>) is just as meaningful as a\n ConditionalCheckFailed<\\/code> on the aggregate (index 0<\\/code>), and both produce an\n actionable error rather than a raw SDK exception:\n<\\/p>\nawait<\\/span> db.<\\/span>send<\\/span>(<\\/span>\n<\\/span> new<\\/span> TransactWriteItemsCommand<\\/span>(<\\/span>{<\\/span>\n<\\/span> TransactItems:<\\/span> [<\\/span>\n<\\/span> {<\\/span> Update:<\\/span> toUpdate<\\/span>(<\\/span>aggregate,<\\/span> aggregateTableName)<\\/span> }<\\/span>,<\\/span>\n<\\/span> {<\\/span>\n<\\/span> Put:<\\/span> {<\\/span>\n<\\/span> TableName:<\\/span> eventsTableName,<\\/span>\n<\\/span> Item:<\\/span> marshall<\\/span>(<\\/span>\n<\\/span> {<\\/span>\n<\\/span> ...<\\/span>event,<\\/span>\n<\\/span> eventTs:<\\/span> new<\\/span> Date<\\/span>(<\\/span>decodeTime<\\/span>(<\\/span>event.<\\/span>eventId)<\\/span>)<\\/span>.<\\/span>toISOString<\\/span>(<\\/span>)<\\/span>,<\\/span>\n<\\/span> }<\\/span>,<\\/span>\n<\\/span> {<\\/span> removeUndefinedValues:<\\/span> true<\\/span> }<\\/span>,<\\/span>\n<\\/span> )<\\/span>,<\\/span>\n<\\/span> }<\\/span>,<\\/span>\n<\\/span> }<\\/span>,<\\/span>\n<\\/span> ]<\\/span>,<\\/span>\n<\\/span> }<\\/span>)<\\/span>,<\\/span>\n<\\/span>)<\\/span>;<\\/span>\n<\\/span>\\/\\/ ...<\\/span>\n<\\/span>if<\\/span> (<\\/span>err instanceof<\\/span> TransactionCanceledException<\\/span>)<\\/span> {<\\/span>\n<\\/span> if<\\/span> (<\\/span>err.<\\/span>CancellationReasons?.<\\/span>[<\\/span>0<\\/span>]<\\/span>?.<\\/span>Code ===<\\/span> \"ConditionalCheckFailed\"<\\/span>)<\\/span> {<\\/span>\n<\\/span> throw<\\/span> new<\\/span> Error<\\/span>(<\\/span>\n<\\/span> `<\\/span>Failed to persist \"<\\/span>${<\\/span>aggregate.<\\/span>$meta.<\\/span>id}<\\/span><\\/span>\" due to version conflict!<\\/span>`<\\/span><\\/span>,<\\/span>\n<\\/span> )<\\/span>;<\\/span>\n<\\/span> }<\\/span>\n<\\/span> if<\\/span> (<\\/span>\n<\\/span> err.<\\/span>CancellationReasons?.<\\/span>[<\\/span>0<\\/span>]<\\/span>?.<\\/span>Code ===<\\/span> \"DuplicateItem\"<\\/span> ||<\\/span>\n<\\/span> err.<\\/span>CancellationReasons?.<\\/span>[<\\/span>1<\\/span>]<\\/span>?.<\\/span>Code ===<\\/span> \"DuplicateItem\"<\\/span>\n<\\/span> )<\\/span> {<\\/span>\n<\\/span> throw<\\/span> new<\\/span> Error<\\/span>(<\\/span>\n<\\/span> `<\\/span>Failed to persist \"<\\/span>${<\\/span>aggregate.<\\/span>$meta.<\\/span>id}<\\/span><\\/span>\" due to duplicate item!<\\/span>`<\\/span><\\/span>,<\\/span>\n<\\/span> )<\\/span>;<\\/span>\n<\\/span> }<\\/span>\n<\\/span>}<\\/span>\n<\\/span><\\/code><\\/pre>\n\n Because the aggregate and the event are written in one transaction, they are\n always in sync. You never end up in a state where an event was recorded but the\n aggregate was not updated, or vice versa.\n<\\/p>\n The read side<\\/h2>\n\n Queries are entirely separate from commands — that is the whole point of the CQR\n split. The read side has two shapes:\n<\\/p>\n \n Current state<\\/strong> — fetch the latest aggregate projection directly from the\n aggregate table. Because persistDynamoDB<\\/code> keeps the aggregate table current on\n every write, reads are a simple GetItem<\\/code> or Query<\\/code> against a well-known key\n schema. No event replay needed at query time.\n<\\/p>\n \n Event stream<\\/strong> — use listAggregateEventsDynamoDB<\\/code> to retrieve all events for\n a given aggregate in order. This is useful for rebuilding projections, feeding\n downstream consumers, or debugging. DynamoDB Streams integration is also\n covered: extractEventsFromDynamoDBEvent<\\/code> parses stream records back into typed\n AggregateEvent<\\/code> objects so they can be forwarded to Lambda functions or other\n processors.\n<\\/p>\n What makes this simpler than the 2016 version<\\/h2>\n\n The earlier versions of this pattern wrote the event to the event store first,\n then relied on a separate asynchronous step — typically a DynamoDB Stream\n feeding a Lambda — to update the aggregate projection. This worked, but it\n created three problems that I kept having to work around.\n<\\/p>\n \n The first was a window of inconsistency<\\/strong>. Between the moment an event was\n written and the moment the Lambda finished updating the aggregate, the two\n stores were out of sync. In practice this window was small, but it was real. If\n the Lambda failed — a cold start timeout, a throttle, a transient DynamoDB error\n — the aggregate could end up permanently behind the event log. You needed\n dead-letter queues, retry logic, and monitoring to catch and recover from these\n failures.\n<\\/p>\n \n The second was latency on the read side<\\/strong>. Because the aggregate projection\n was updated asynchronously, a caller that wrote an event and immediately read\n back the aggregate might get stale data. You had to either accept eventual\n consistency or build compensating logic to handle it.\n<\\/p>\n \n The third was CDK infrastructure overhead<\\/strong>. Every aggregate needed a Stream\n enabled on its events table, a Lambda to consume it, an event source mapping,\n IAM roles, a DLQ, and CloudWatch alarms. This was not a huge amount of code, but\n it added up and it was all load-bearing — getting any of it wrong meant silent\n data loss.\n<\\/p>\n \n The current approach sidesteps all of this with a single TransactWriteItems<\\/code>\n call. The event and the aggregate projection are written atomically. Either both\n succeed or neither does. There is no async gap, no eventual consistency on the\n write path, and no extra CDK constructs to manage. The aggregate table is always\n in sync with the event store by construction.\n<\\/p>\n \n The tradeoff is that you give up the ability to fan out to multiple projections\n in the same write path — but in practice I have found that DynamoDB Streams off\n the events table is still the right mechanism for that, and you can add it when\n you actually need it rather than building it upfront for every aggregate.\n<\\/p>\n \n\n The full source, including a working test suite that runs against DynamoDB\n Local, is at\n github.com\\/coderbyheart\\/aws-dynamodb-es-cqrs<\\/a>.\n The package is also published to npm as\n @coderbyheart\\/aws-dynamodb-es-cqrs<\\/code><\\/a>\n if you want to use it directly.\n<\\/p>\n","slug":"es-and-cqrs-on-aws-simplified","hero":"!undefined"}],["european-testing-conference-2018",{"title":"European Testing Conference 2018","subtitle":"Conferences","abstract":"A retrospective on what I learned during the European Testing Conference 2018 in Amsterdam","date":"2018-02-21T09:00+01:00","html":"\n \n <\\/picture><\\/aside>\n<\\/p>\n\n This week I went to the beautiful city of Amsterdam to attend the\n European Testing Conference 2018<\\/a>.\n This conference hasn't been on my radar previously, but what caught my attention\n was the level of detail the organizers (most notably Franzi<\\/a> and Maaret<\\/a> put\n into creating an attendee-focused, inclusive and diverse event.\n<\\/p>\n https:\\/\\/twitter.com\\/lisacrispin\\/status\\/965498092429684738?embed<\\/a><\\/p>\n \n I initially had submitted an older talk<\\/a> if mine on testing REST-APIs\n using BDD which was not accepted, but the experience during the submission\n process made me want to go to this conference any way.\n<\\/p>\n https:\\/\\/twitter.com\\/maaretp\\/status\\/900672218816032768?embed<\\/a><\\/p>\n \n Other than my usual<\\/a> conferences<\\/a>, the ticket price was\n notable (800 €) but given the fact the this conference offered free tickets to\n underrepresented groups, organized child care, and paid their speakers. This is\n (unfortunately) exceptional! I was happy to use the conference budget my\n employer Nordic Semiconductor<\\/a> grants us to support this!\n<\\/p>\n https:\\/\\/twitter.com\\/EuroTestingConf\\/status\\/936305287308472320?embed<\\/a><\\/p>\n https:\\/\\/twitter.com\\/AdharaIT\\/status\\/958464191135977473?embed<\\/a><\\/p>\n What did I learn?<\\/h2>\n\n The two-day programme was a great mixture of up-front keynotes, talks, and\n workshops as well as interactive sessions. The keynotes were carefully selected\n to not be vendor-sales-pitches but focus on high level ideas about testing,\n communication and team-dynamics.\n<\\/p>\nKeynotes<\\/h3>\n\n Gojko Adzic<\\/a> explained that we are seeing a\n revolution in the field of UI testing.\n<\\/p>\n https:\\/\\/twitter.com\\/coderbyheart\\/status\\/965511538059726848?embed&conversation=none<\\/a><\\/p>\n This was very insightful since I grew up with the notion in mind:<\\/p>\n \n <\\/picture><\\/aside>\n<\\/p>\n\n It looks like it's time to rethink this paradigm. Tools like the one Gojko wrote\n (an open-source tool called Appraise<\\/a>)\n or payed tools like Applitools<\\/a> which i learned about\n from another participant during the networking session are greatly simplifying\n visual testing.\n<\\/p>\n \n Lanette Creamer<\\/a> spoke about the importance\n of communication and how to better understand and improve the skills as a\n tester. Although this talk was mainly geared towards testers, I still enjoyed\n her insights into what it means to be a tester and improved my understanding of\n this role.\n<\\/p>\n https:\\/\\/twitter.com\\/coderbyheart\\/status\\/965622543557283843?embed&conversation=none<\\/a><\\/p>\n \n Zeger van Hese<\\/a> held a great keynote on\n being a sceptic. He stressed the point that it is important to (constantly)\n question information you have been given in order keep making the best\n decisions.\n<\\/p>\n https:\\/\\/twitter.com\\/coderbyheart\\/status\\/965870628048957440?embed&conversation=none<\\/a><\\/p>\n \n He recommended\n a set of context-free questions<\\/a>\n to identify important aspects about a project in an unbiased way.\n<\\/p>\n \n The closing keynote by Pamela Gay<\\/a> was\n meticulously executed and fascinating from beginning to end. It provided a great\n insight into the work of the Cosmoquest<\\/a> project,\n which uses crowd-sourced data to solve mission-critical problems in\n space-travel. One might think that it's a long stretch to testing<\\/em> but the\n learning of this talk for me was:\n<\\/p>\n https:\\/\\/twitter.com\\/coderbyheart\\/status\\/965984483370569728?embed&conversation=none<\\/a><\\/p>\n \n Ergo, not all problems can be solved using software. A great reminder to stay\n humble.\n<\\/p>\n Talks<\\/h3>\n\n There were four talk slots, each with four talks in parallel. I attended three\n of them, since I spent most of the fourth talk time talking with other\n attendees.\n<\\/p>\nhttps:\\/\\/twitter.com\\/coderbyheart\\/status\\/965913802951790592?embed<\\/a><\\/p>\n \n In this highly interesting talk Matthew Butt<\\/a>\n explained his way to enable testing in software that depends on services, which\n cannot be run locally. Since cloud-based services (like machine-learning) is\n becoming more and more coming, we have parts in our software which can not\n longer be run locally on a developer machine (e.g. for legal reasons). What to\n do if the provider does not provide a test-environment \\/ stub for this service?\n Adapters<\\/strong>, all the way. IMO this concept is getting to few attention. We are\n happily following the\n SOLID<\\/a>\n principle, but we are pulling interfaces from dependencies into our\n implementation. If we write adapters for them we can hide implementation detail\n of a service behind an easier (to mock) interface and can simplify testing of\n individual components. Matthew did a good job in illustrating this. You can find\n his slides\n here<\\/a>.\n<\\/p>\n https:\\/\\/twitter.com\\/coderbyheart\\/status\\/965590736669413378?embed&conversation=none<\\/a><\\/p>\n \n The talk was a tester's perspective of working with microservices, which\n provided some value for me since Emily was concerned with orchestrating the\n collaboration between different teams working in with a microservice\n architecture. Most important takeaway from her talk: version your microservices\n so other teams or individuals can run integration tests and teams are\n responsible to run the integration tests with their latest code, otherwise there\n will be pain.\n<\\/p>\n https:\\/\\/twitter.com\\/coderbyheart\\/status\\/965517620396134400?embed<\\/a><\\/p>\n \n Albeit providing no new insights to me, Lynoure tried to take a new angle on\n explaining how to write tests<\\/em>: the mindset you put yourself in. Start from the\n most minimal example you can think of and then stop and go talk to your\n (business) stakeholders to actually figure out what the component you are about\n to write is actually supposed to do. Don't let yourself get drawn into the\n rabbit hole of writing too much, and too complete<\\/em> software. Because you can\n never know when you are done on your own, and the more code gets written, the\n more resistance to change is becoming ingrained.\n<\\/p>\n Workshops<\\/h3>\n\n There were five workshops which were repeated on both days. This reduced the\n FOMO<\\/a> significantly and I\n attended a workshop on BDD and one on Test Specification.\n<\\/p>\n \n In Vernon Richard's workshop on Scripted vs. Exploratory testing we got to\n experience the pain of scripted testing first hand.\n<\\/p>\n https:\\/\\/twitter.com\\/coderbyheart\\/status\\/965564137890828291?embed&conversation=none<\\/a><\\/p>\n \n We\n were given<\\/a>\n an outdated test script and tasked with testing a changed UI. This was no fun.\n<\\/p>\n \n \n<\\/p>\n \n After 30 minutes we switched to persona based testing, where we used the persona\n to test a different website. Also we made significantly more progress here, and\n it was way less mind-numbing, it still had a flaw: the persona was lacking a\n clear goal, so it was not possible to evaluate whether the website under test\n passed or failed.\n<\\/p>\n \n Obviously the workshop was meant to show us the difference in these testing\n methods through first hand experience and what would be needed to improved in\n order to make them a useful tool.\n<\\/p>\n \n This workshop provided a great insight for me into the way testers work, and how\n we as developers can (and should) support them, as well as understanding the\n value especially of persona-based testing. It is way more flexible, does not\n need to be changed if implementation details are changed and provides\n customer-focused, easy to reason about framework for testers. On the other hand,\n it relies on testers understanding the domain and a lot of details about the\n test subject in order to execute tests. Which in the end will be to the benefit\n of the project.\n<\\/p>\n \n The second workshop by Seb Rose<\\/a> and\n Gáspár Nagy<\\/a> gave us a very well executed\n tutorial on how to write better BDD scenarios. Working in groups on suboptimal\n scenarios we worked towards writing one great at the end of the workshop. Their\n insights and tips we easy to follow and execute.\n<\\/p>\n https:\\/\\/twitter.com\\/coderbyheart\\/status\\/965889984258506752?embed&conversation=none<\\/a><\\/p>\n https:\\/\\/twitter.com\\/coderbyheart\\/status\\/965899224062791680?embed&conversation=none<\\/a><\\/p>\n \n From discussion with attendees one thing became clear though, too few teams are\n using this technique which enables discussion of features between stakeholders\n and developers and at the same time enforcing the implementation to follow these\n talking points. It seems that many teams start the implementation through Jira\n and other issue trackers instead of taking the time to formulate users stories.\n It might be because it is easy to write tickets like \"Export list of products as\n CSV\" in an issue, but hard to explain why a user needs this functionality in the\n first place.\n<\\/p>\n Open Space<\\/h3>\nhttps:\\/\\/twitter.com\\/coderbyheart\\/status\\/965939046492131328?embed<\\/a><\\/p>\n \n Being an unconf fan I especially enjoyed this two-hour slot in the programme. It\n was hard to choose from from the roughly 25 sessions:\n<\\/p>\n https:\\/\\/twitter.com\\/coderbyheart\\/status\\/965954415525064704?embed&conversation=none<\\/a><\\/p>\n \n The first session was by someone working for a big oil company and they were\n looking for a lean way to develop an alternative-energy car. It was fun to toy\n around with that idea and imagine ways to enable this. Given the knowledge I\n have collected working at Nordic and as the son of an automobile industry\n veteran I could add some insights.\n<\\/p>\n https:\\/\\/twitter.com\\/coderbyheart\\/status\\/965954967256358914?embed&conversation=none<\\/a><\\/p>\n https:\\/\\/twitter.com\\/RidingWolf\\/status\\/965954663924322304?embed<\\/a><\\/p>\n \n In the session on Continuous Deployment we talked about the do's and don'ts.\n Basically: you want your CI runners to be\n Phoenix Servers<\\/a>.\n Chris Dräger<\\/a> who hosted this session\n found LambdaCD<\\/a> to be his tool of choice. I would\n recommend Travis<\\/a> + Makefiles to solve this.\n<\\/p>\n https:\\/\\/twitter.com\\/coderbyheart\\/status\\/965962746415206401?embed&conversation=none<\\/a><\\/p>\n \n How to Kanban better<\\/em> started as a question on how to improve Kanban but this\n session quickly turned into a team clinic, where we tried to find ways for a\n team to improve their internal shortcomings, which were just being revealed by\n using Kanban:\n<\\/p>\n https:\\/\\/twitter.com\\/coderbyheart\\/status\\/965964932960354305?embed&conversation=none<\\/a><\\/p>\n Summary<\\/h2>\n\n The European Testing Conference<\\/a> was a\n fantastic experience for me, even being in the minority as a developer I felt\n very included and welcome. The atmosphere was always very friendly and never\n hostile or too opinionated. Amsterdam as a city did its best, we arrived a few\n days earlier and had awesome weather, great food and beer.\n<\\/p>\n \n I would definitely recommend to follow\n @EuroTestingConf<\\/a> and sign up for their\n newsletter. We might see a new installment of this conference in 2019. Maybe in\n Finland, given that there were so many Finns among the attendees already?\n<\\/p>\n","slug":"european-testing-conference-2018","hero":"!undefined"}],["european-testing-conference-2020",{"title":"European Testing Conference 2020","subtitle":"The pioneering tech event is no more","abstract":"What happens at European Testing Conference must not stay at European Testing Conference.","date":"2020-02-08T12:00+01:00","html":"\n \n <\\/picture><\\/aside>\n<\\/p>\n\n This is the most diverse conference I have ever been to.<\\/p>\n<\\/blockquote>\n\n While this remark my friend Patricia Aas<\\/a> makes during\n the retrospective is about the attendees of the 2020 edition of the\n European Testing Conference<\\/a>, it\n strongly resonates with me and I will extend it to the wide range of topics that\n were covered in keynotes, talks, workshops, an open-space, lean coffee, the\n hallways track, and evening get-togethers. I would use diversity further as the\n decisive reason for the experiences I had sharing two days with people from\n typically separated professions: testers and developers. Both were represented\n plentiful, with industry veterans, newcomers and all shades in between. Finally,\n attendees were coming from all over the world to meet with people who care about\n quality, customers, mental health and bring the desire to learn, share and\n teach.\n<\\/p>\n https:\\/\\/twitter.com\\/coderbyheart\\/status\\/1225330258569764864?embed<\\/a><\\/p>\n \n It is a safe place to acknowledge that we, our behaviour and our skills are far\n from perfect, to connect with others and figure out together<\\/em> how to be better\n humans who work on computers.\n<\\/p>\n \n The closing keynote by Ulrika Malmgren<\\/a>\n summarized this perfectly:\n<\\/p>\n https:\\/\\/twitter.com\\/coderbyheart\\/status\\/1225807205783527424?embed<\\/a><\\/p>\n \n It is our responsibility to have honest conversations about our work because we\n happen to be influential to the lives of other with every keystroke and we owe\n it to our users to deliver the best possible solution.\n<\\/p>\n \n You can find all the content I discovered and highlights I had this year\n in my twitter feed under the hashtag #EuroTestConf<\\/a>,\n but I would like to point out two specifically:\n<\\/p>\n Pact<\\/h2>\n\n Pact<\\/a>: Fast, easy and reliable testing for your APIs and\n microservices during development.\n<\\/p>\n \n With the help of Nelis<\\/a>,\n Matteo<\\/a>, and\n Bernardo<\\/a> I got a good impression of its\n usefulness for my area of work. I plan to look more into it for providing\n stronger documentation of my public APIs, which right now are described for\n other developers using Gherkin Scenarios. It would be straightforward to create\n pact contracts out of these scenarios which would provide a significant benefit\n for the frontend developers which consume these APIs. It would also provide a\n explicit, safe and unambiguous way to communicate API requirements and changes,\n which currently is done using Confluence, Slack and email.\n<\\/p>\n 7 dimensions of quality<\\/h2>\n\n from:\n Discover to Deliver<\\/a>\n<\\/p>\n https:\\/\\/twitter.com\\/coderbyheart\\/status\\/1225389623448342528?embed<\\/a><\\/p>\n \n This is super useful technique to uncover blind spots in a project and can be\n done with straightforward exercises which don't take up too much time. I will\n add this to my toolbox when talking about (new) features.\n<\\/p>\n \n The slides from this workshop have been uploaded\n here<\\/a>.\n<\\/p>\n The End<\\/h2>\n\n 2020 was the last year for European Testing Conference, I will miss it deeply\n and I am grateful for the three years I got to attend it, because every year\n helped me to become a better developer but also because it provides an inspiring\n proof that diversity in tech is not a pipe dream, but achievable.\n<\\/p>\nThe Future<\\/h2>\n\n On Friday we met with some of the speakers and attendees from\n Domain Driven Design Europe<\\/a>, one of them being\n Lisi Hocke<\\/a> who spoke and attended\n the European Testing Conference many times before. She could share first-hand\n how large the overlap between the three communities is that were present at the\n table: attendees and speakers of European Testing Conference, Domain Driven\n Design Europe, and\n Softwarecrafters\\/SoCraTes Conferences<\\/a> share\n the same DNA, and hopefull next year, we can bring these three communities\n closer together.\n<\\/p>\n https:\\/\\/twitter.com\\/coderbyheart\\/status\\/1225859527255392256?embed<\\/a><\\/p>\n \n \n I thank my employer Nordic Semiconductor<\\/a> for\n enabling me to attend this event on company time and cost under our competence\n improvement program.\n We are hiring!<\\/a>\n <\\/p>\n<\\/blockquote>\n","slug":"european-testing-conference-2020","hero":"!undefined"}],["expect-tobewithin-number-number",{"title":"expect.toBeWithin(number, number)","subtitle":"A matcher for Jest's expect","abstract":"Use .toBeWithin() when you want to check that a number is within a range.","date":"2017-10-29T18:00+02:00","html":"\n \n <\\/picture><\\/aside>\n<\\/p>\n\n I've just authored\n @coderbyheart\\/jest-expect-tobewithin<\\/a>\n which adds a matcher to\n Jest's expect<\\/a> that lets\n you expect that a number is between two other numbers.\n<\\/p>\n","slug":"expect-tobewithin-number-number","hero":"!undefined"}],["exploring-better-ways-to-write-tests",{"subtitle":"Talk","title":"Exploring better ways to write tests","abstract":"My approach to testing embedded firmware using real hardware.","date":"2023-06-09T13:30:00.000Z","html":"\n \n <\\/picture><\\/aside>\n<\\/p>\n\n In my talk Exploring better ways to write tests<\\/em> that I gave at this year's\n Nordic Testing Days<\\/a> 2023 in Tallinn, I\n discussed my journey from feeling dissatisfied with testing tools to creating my\n own test runner. My goal of this talk was to inspire others to explore and\n customize their tools rather than settling for the default options available.\n<\\/p>\n \n For quite some time I have been working on cloud-based software system for IoT\n devices. Initially, I used Gherkin for writing tests, but I encountered\n limitations in expressing complex scenarios, dependencies, and handling eventual\n consistency in cloud-based services. Let me explain how I began using Gherkin\n and describe its format and keywords (given, when, then).\n<\\/p>\n \n Facing challenges with Gherkin for my specific needs, I ran into issues with\n expressing dependencies between features, directly embedding JSON in feature\n files, managing eventual consistency problems, and dealing with\n context-dependent scenarios. I also realized that I needed better documentation\n beyond just tests. To address these issues, I decided to build my own custom\n test runner, a process that took me three years to develop. The key improvement\n was adopting Markdown for better formatting, hierarchical structure, code\n blocks, and comments. I introduced the \"soon\" keyword to handle eventual\n consistency in tests. Additionally, I utilized GitHub actions to summarize test\n results in a more user-friendly format.\n<\\/p>\n \n I also talked about the struggles I faced with architecture diagrams and their\n maintenance. Auto-generated diagrams fell short, prompting me to explore the\n concept of using test traces and observability to dynamically generate\n architecture diagrams based on test runs. This approach would allow for more\n focused and informative diagrams linked directly to actual usage.\n<\\/p>\n \n In conclusion, I encouraged others to create tools tailored to their own needs.\n I believe that developing personalized solutions can significantly enhance\n efficiency and understanding in both testing and development workflows.\n<\\/p>\n https:\\/\\/www.youtube.com\\/embed\\/dZX7SbGOGn4<\\/a><\\/p>\n \n The slides are available at\n bit.ly\\/better-test-tools<\\/a>.\n<\\/p>\n \n You can read up about my impression under the hashtag\n #NTD2023<\\/a>.\n<\\/p>\n \n <\\/picture><\\/aside>\n<\\/p>\n","slug":"exploring-better-ways-to-write-tests","hero":"!undefined"}],["fintech-appsolute-bankfurt",{"title":"Fintech — Appsolute Bankfurt","abstract":"I've written an article about the fintech scene in Frankfurt which you can find at hallofrankfurt.de.","date":"2016-01-04T16:40:00.000Z","html":"\n\n I've written an article about the fintech scene in Frankfurt which you can find\n at\n hallofrankfurt.de<\\/a>.\n<\\/p>\n","slug":"fintech-appsolute-bankfurt","hero":"!undefined"}],["firefox-4-und-x-509-zertifikate",{"title":"Firefox 4 und X.509-Zertifikate","abstract":"Im neuesten Firefox funktionieren einige Zertifikate nicht mehr, mit denen z.B. Zugänge zu Content-Management-Systemen oder Banking-Webseiten gesichert werden.\n","date":"2011-04-05T00:00:00.000Z","html":"\n \n Im neuesten Firefox funktionieren einige Zertifikate nicht mehr, mit denen z.B.\n Zugänge zu Content-Management-Systemen oder Banking-Webseiten gesichert werden.\n<\\/p>\n \n Diese Zertifkate (mit Dateiendungen wie z.B. .p12) lassen sich auch nicht mehr\n über den Zertifikate-Manager von Firefox importieren.\n<\\/p>\n \n Mit zwei kleinen Handgriffen kann man den Firefox aber doch wieder dazu\n überreden, mit den Zertifikaten zu arbeiten.\n<\\/p>\n \n Zuerst muss in about:config<\\/code> der Wert\n security.ssl.allow_unrestricted_renego_everywhere__temporarily_available_pref<\\/code>\n auf true gestellt werden — sonst verweigert der Fuchs jede Verbindung.\n<\\/p>\n \n Anschließend wird das Zertifikat mit Hilfe des Kommandozeilen-Tools\n pk12util<\\/a>\n importiert:\n<\\/p>\n pk12util -i <zertifikat.p12> -d ~\\/.mozilla\\/firefox\\/<profile>\\/\n<\\/span>Enter password for PKCS12 file:\n<\\/span>pk12util: PKCS12 IMPORT SUCCESSFUL\n<\\/span><\\/code><\\/pre>\nJetzt noch den Firefox neu starten und schon klappt die Verbindung wieder.<\\/p>\n","slug":"firefox-4-und-x-509-zertifikate","hero":"!undefined"}],["firmware-test-automation-using-real-embedded-devices",{"subtitle":"Talk","title":"Firmware test automation using real embedded devices","abstract":"My approach to testing embedded firmware using real hardware.","date":"2022-06-06T23:00:00.000Z","html":"\n\n In this talk I am presenting my approach on testing embedded firmware using real\n hardware which I gave at Nordic Testing Day 2022 in Tallinn<\\/a>.\n<\\/p>\n \n Testing firmware in emulators drastically limits what actually gets tested and\n it can quickly become very tedious to mock, fake and set up environments for\n embedded firmware that needs to connect to cloud services.\n<\\/p>\n \n I am taking a different route: let the firmware run on real hardware, and test\n its behavior.\n<\\/p>\n \n I show how I implemented these tests using Zephyr, AWS, and GitHub Actions.\n However, this solution can be applied in any environment which cannot be run\n inside a test runner.\n<\\/p>\n The slides are available at bit.ly\\/fwtesting<\\/a>.<\\/p>\n \n Unfortunately there was no recording of the talk, but it got featured on\n @internetofshit<\\/a>:\n<\\/p>\n https:\\/\\/twitter.com\\/internetofshit\\/status\\/1532795048084983808?embed<\\/a><\\/p>\n \n <\\/picture><\\/aside>\n<\\/p>\n","slug":"firmware-test-automation-using-real-embedded-devices","hero":"!undefined"}],["first-principles",{"title":"First Principles","subtitle":"How to share gut feeling","abstract":"How can we share the gut feeling we use when writing software?","date":"2018-09-01T17:00+02:00","html":"\n\n A question I brought to SoCraTes 2018<\\/a>\n was one that formed in the recent months when I was onboarding a new developer\n to a greenfield project. The project they going to work on is developed as a\n walking skeleton<\\/a>.\n Although the architecture is complete, there is not enough flesh on it to\n clearly see the patterns<\\/em> I have used when designing it. Right now every\n component looks like a unicorn and it is hard to see the underlying principles\n that went into the design—simply because there is not enough code to provide\n good heuristics.\n<\\/p>\n \n I was looking for a way to provide a resource outside of the code<\\/em> which\n documents the gut feelings that lead to this architecture. These gut feelings\n are a result of reading books, articles and building many different software\n projects, so there is not one school<\\/em> of thought, but a amalgamation of\n hundreds of resources and experiences that form the principles that influence my\n decisions.\n<\\/p>\n But what are<\\/em> First Principles?<\\/p> \n\n <\\/picture><\\/aside>\n<\\/p><\\/div>\nIn this session I listed mine and we collected some more:<\\/p>\n\n Push to deploy<\\/li>\n S.O.L.I.D.<\\/li>\n No global state<\\/li>\n No monolith<\\/li>\n Version dependencies<\\/li>\n Simplicity<\\/li>\n Done > Perfect<\\/li>\n Show > Tell<\\/li>\n Code Stewardship<\\/li>\n<\\/ul>\n\n While some of those are fairly easy to explain (like S.O.L.I.D. where extensive\n documentation can easily be found<\\/a>),\n others are horribly ambiguous, like Simplicity<\\/em>.\n<\\/p>\n \n In the course of the session we then collected, how principles are shared within\n teams. One recurring characteristic was that they are usually very project\n specific and are best understood if they are explained using real examples from\n the project's source code.\n<\\/p>\n \n A good method to share these principles is pairing when concrete situations\n arise.\n<\\/p>\n \n Multiple participants shared that they had good experiences using an internal\n Stackoverflow (or a home-grown solution similar to that), where developers would\n bring up principles they discover or certain implementation details they did not\n fully understand so it could be discussed what the underlying principle was, and\n whether it still applies. This forum-style aproach can also serves as a good way\n to document technical dept, and the decisions that lead to keeping it in the\n system. It provides an easy way to regularly revisit these decisions after a\n certain amount of time has passed and decide again whether to keep it or get rid\n of it.\n<\\/p> \n\n <\\/picture><\\/aside>\n<\\/p><\\/div>\n\n I was also looking for a way to provide documentation about First Principles<\\/em>\n before code is written, especially to reduce frustration during code-reviews\n when a violation of a principle is discovered and big changes are neccessary in\n order to heal the pull-request.\n<\\/p>\n \n Following the idea of continuous improvement (I think this is yet another First\n Principle) I will try to follow this process:\n<\\/p>\n \n <\\/picture><\\/aside>\n<\\/p>\n\n This will lead over time to a collection of First Principles<\\/em> which can be used\n to train new developers.\n<\\/p>\n \n The Training<\\/em> part is important so we can discover bad and harmful principles\n like Simplicity<\\/em>—if you can't train it, it is most likely a bad principle and\n we should drop it. (The number of times a principle has been violated will be a\n good indicator!).\n<\\/p>\nFirst Principles<\\/h2>\n\n Privilege<\\/a><\\/li>\n Push to deploy<\\/a><\\/li>\n 5 whys<\\/a><\\/li>\n The 20 percent trick to continuously keep learning<\\/a><\\/li>\n<\\/ul>\nBest practices<\\/h2>\n\n I also collected a set of best practices that are specific instructions rather\n then generic principles:\n<\\/p>\n\n Clean .gitignore files<\\/a><\\/li>\n Do not change two different things in one Pull Request<\\/a><\\/li>\n Don't use global state like env variables in modules<\\/a><\\/li>\n Keep code left<\\/a><\\/li>\n PRs should never contain formatting changes<\\/a><\\/li>\n master is the wrong name for the main branch<\\/a><\\/li>\n Method calls: favour argument bags over individual arguments<\\/a><\\/li>\n Rebase and ideally Squash instead of Merge Pull Requests<\\/a><\\/li>\n Separate workflows through events<\\/a><\\/li>\n Readable error messages<\\/a><\\/li>\n<\\/ul>\n","slug":"first-principles","hero":"!undefined"}],["for-usd24-podio-gives-you-the-names-faces-and-contact-details-of-their",{"title":"For $24 Podio gives you the names, faces, and contact details of their premium users","subtitle":"Privacy","abstract":"Podio discloses extensive user information and claims its users have agreed to it.","date":"2019-07-03T10:00+02:00","html":"\n\n <\\/picture><\\/aside>\n<\\/p>\n\n I've been a big fan of Podio for many years and I recently discovered a nice\n feature<\\/em>: once you sign up to Podio<\\/a> and pay for the\n Premium Plan: you become connected through more than 2,600 other premium users\n through becoming part of the same Network in order to use their automation\n product globiflow<\\/a>.\n<\\/p>\n This gives you access to extended personal information:<\\/p>\n \n Full name<\\/li>\n Title<\\/li>\n Email<\\/li>\n Phone Number<\\/li>\n City<\\/li>\n Personal description \\/ About<\\/li>\n Photo<\\/li>\n State<\\/li>\n Country<\\/li>\n Skype<\\/li>\n Location<\\/li>\n Address<\\/li>\n Postcode<\\/li>\n Website<\\/li>\n IM<\\/li>\n<\\/ul>\n\n The information is presented in a nicely formatted way, so I was able to extract\n the data for all users within a few minutes in a nice spreadsheet.\n<\\/p>\n \n I think this is highly problematic because this provides a gold mine for\n phishing attacks: I could find members who belong to the same organization and\n use Podio as a pretext to send them arbitrary emails (Hey Bratt, I shared this\nPodio View with you!<\\/em>) containing dangerous links.\n<\\/p>\nTwo months ago I reached out to the Podio support<\\/h2>\n\n I asked them to remove this feature, however they claim that this is perfectly\n fine.\n<\\/p>\n I wrote:<\\/p>\n\n \n When you purchase Podio premium, and activate Globiflow, you are joining the\n Globiflow network, which will make over 2,600 connections available. See also\n https:\\/\\/help.podio.com\\/hc\\/en-us\\/community\\/posts\\/360000702471-Mass-Delete-Connections This\n is a serious violation of user privacy since the connections show Name,\n E-Mail, Photo and Phone of the job Title is exposed to anyone (who payed\n $24). Please remove this feature immediately.\n <\\/p>\n<\\/blockquote>\n This is the answer I received:<\\/p>\n\n \n I understand your concern of having so many connections added to your profile.\n But this is not necessarily a violation of user privacy because the profile\n details that a user is adding is an information that would be publicly\n available only to other podio users you are connected to. Please refer to:\n https:\\/\\/help.podio.com\\/hc\\/en-us\\/articles\\/201019378-Updating-and-editing-your-profile\n which states that the profile details will be visible to other users as well.\n It is similar to having your contact and profile information added to your\n social or business collaboration platforms like Linkedin.\n <\\/p>\n<\\/blockquote>\n \n No, this is not<\\/strong> what I would expect from a paid product like Podio.\n Especially looking at the linked article, it does not state that \"profile\n details will be visible to other users\" but instead uses \"colleagues\".\n<\\/p>\n\n \n Having a completed Podio profile really helps you and your colleagues \"see\"\n who you're working together with.\n <\\/p>\n<\\/blockquote>\n \n Colleagues are by definition not all podio users<\\/strong>. With colleagues I (or the\n manager of the podio account I belong to) has control over who sees my data.\n This is not the case with the \"connection\" feature where I do not have ways to\n control who sees my data.\n<\\/p>\n \n I can only encourage Premium Podio users to educate themselves about this\n \"feature\"<\\/em> and reach out to the Podio support so this disclosure of extensive\n personal information will be stopped.\n<\\/p>\nUpdate 4. July 2019<\\/h2>\n\n I received a reply from Podio support to the original request I made two month\n ago:\n<\\/p>\n\n \n I understand your point of view here and thanks a lot for bringing this up. We are working towards making this more transparent to users so that users can\n decide what information they would want to keep public.\n <\\/p>\n \n Will be releasing out information once we have more clarity on the plan and\n approach.\n <\\/p>\n<\\/blockquote>\nUpdate 8. July 2019<\\/h2>\n\n Podio responded to\n the Twitter thread<\\/a>:\n<\\/p>\n https:\\/\\/twitter.com\\/Podio\\/status\\/1148152555177857026?embed&conversation=none<\\/a><\\/p>\n Update 11. July 2019<\\/h2>\n\n Podio updated the\n help article<\\/a>\n and added a section which explains that profile information is shared with\n everyone:\n<\\/p>\n \n \n Public Profile Information<\\/strong> Profile information can be seen by all of your\n connections in Podio. This means all of your colleagues, external members that\n you collaborate with, and members inside of community workspaces that you’re\n apart of will all have the ability to view your Podio Profile information. You\n can edit and remove any unwanted profile information at anytime by editing\n your profile information.\n <\\/p>\n Shared Profile Information:<\\/p>\n \n Profile Picture<\\/li>\n Email<\\/li>\n Phone<\\/li>\n Location<\\/li>\n Address<\\/li>\n <\\/ul>\n<\\/blockquote>\n\n They also added a prominent warning presnted to GlobiFlow users when joining\n that workspace:\n<\\/p>\n \n <\\/picture><\\/aside>\n<\\/p>\nIn addition they plan to upldate the \"Edit Profile\" feature:<\\/p>\n\n \n For long term, we would also be updating our in-product \"Edit Profile\" page\n later to call out what all information is public and what is not, so that\n users can take an informed decision while adding their details.\n <\\/p>\n<\\/blockquote>\n","slug":"for-usd24-podio-gives-you-the-names-faces-and-contact-details-of-their","hero":"!undefined"}],["future-of-work-in-the-wild",{"title":"#futureofwork in the wild","abstract":"On April 2nd 2015 I'll be giving a lightning talk to show some examples of organizations that have already arrived at the future of work.\n","date":"2015-03-21T15:00:00.000Z","html":"\n \n #futureofwork<\\/em> is a rather abstract term which stands for changing our\n workplaces from a concept that was conceived in the 19th century to something\n that reflects the needs of the 21st century human–at least for those of us who\n are asked to produce<\\/em> creatively and innovatively.\n<\\/p>\n \n There are a lot<\\/strong> of theoretical resources detailing what needs to be done to\n create an environment in which knowledge-workers can achieve their best possible\n output.\n<\\/p>\n But there are organizations which have already arrived at the future of work<\\/em>.<\\/p>\n\n At the next agile round table, which will take place on April 2nd 2015 at\n Die Zentrale FFM Coworking Space<\\/a>, I'll be\n giving a lightning talk to show some examples of these organizations.\n<\\/p>\n \n Sign up on\n XING<\\/a> and\n find out that the wait to change the way we work is over<\\/em>.\n<\\/p>\n","slug":"future-of-work-in-the-wild","hero":"!undefined"}],["give-your-dots-to-dotHIV",{"title":"Give your dots to dotHIV","abstract":"December 1st is World AIDS Day and we have prepared something for your homepage which will support our cause in an unobtrusive and witty way: turn the fullstops of your page into pink dots.","date":"2014-11-28T10:01:00.000Z","html":"\n \n <\\/picture><\\/aside>\n<\\/p>\n\n December 1st is World AIDS Day and we have prepared something for your homepage\n which will support our cause in an unobtrusive and witty way: turn the\nfullstops of your page into pink dots<\\/strong>.\n<\\/p>\n\n Our friends from SinnerSchrader<\\/a> built a script\n which once integrated into your site will color a random amount of dots inside\n your text elements on the page in pink. If a user clicks on a dot, a little\n popup will show up with a short info text and a link to\n click4life.hiv<\\/a>. You'll find some of those pink dots in\n this text, too.\n<\\/p>\n \n <\\/picture><\\/aside>\n<\\/p>\n\n Head over to mydotfor.hiv\\/dothivify<\\/a> to\n download the script. They even built a configurator to adapt the script to your\n needs. Afterwards you need to add it to your websites source code, just before\n the <\\/body><\\/code> tag. Make sure to test it<\\/strong>–as with all software there might be\n bugs.\n<\\/p>\n \n As always with our projects at dotHIV the source code\n is available at GitHub<\\/a>.\n<\\/p>\n \n Please let me know in the comments or by your\n preferred means of communication<\\/a> once you've got\n the script running.\n<\\/p>\n Thank your for supporting dotHIV<\\/a>!<\\/p>\n","slug":"give-your-dots-to-dotHIV","hero":"!undefined"}],["have-a-local-folder-to-put-your-crap-in-which-wont-get-accidentally-committed",{"title":"Have a local folder to put your crap in which won't get accidentally committed","subtitle":"Devhacks","abstract":"Do you always have temp \\/ scratch files lying around in your Git repo and sometimes accidentally commit them (like I do)? Here is a simple fix!","date":"2019-01-02T11:00+01:00","html":"\n \n <\\/picture><\\/aside>\n<\\/p>\n\n Do you always have temp \\/ scratch files lying around in your Git repo and\n sometimes accidentally commit them (like I do)?\n<\\/p>\n \n Add local\\/<\\/code> to your global gitignore file and now you have a place where you\n can put your not-so-temp files and they won't bother you ever again when you use\n a git add -A<\\/code>.\n<\\/p>\n You can define a global .gitignore<\\/code> in your global git config file:<\\/p>\n# ~\\/.gitconfig\n<\\/span>[core]\n<\\/span> excludesfile = ~\\/.gitignore_global\n<\\/span><\\/code><\\/pre>\n\n And in the excludesfile<\\/code><\\/a> add a\n line for the local\\/<\\/code> folder:\n<\\/p>\n # ~\\/.gitignore_global\n<\\/span>local\\/\n<\\/span><\\/code><\\/pre>\n","slug":"have-a-local-folder-to-put-your-crap-in-which-wont-get-accidentally-committed","hero":"!undefined"}],["heart-of-code-001",{"title":"❤️.of(code) \\/\\/ 001","subtitle":"Week 33 of 2017","abstract":"Week 33 of 2017 in review","date":"2017-08-20T14:00+02:00","html":"\n\n <\\/picture><\\/aside>\n<\\/p>\n\n Celebrating 2,000 followers on @coderbyheart<\\/a>\n I decided to sum up my week on Twitter from now on every weekend.\n<\\/p>\n Quote of the week<\\/h3>\nhttps:\\/\\/twitter.com\\/coderbyheart\\/status\\/898107322307936257?embed<\\/a><\\/p>\n Software Craft<\\/h3>\nWe decided to drop the \"Middleman\" in \"Softwarecraftsmanship\":<\\/p>\nhttps:\\/\\/twitter.com\\/coderbyheart\\/status\\/896679150379032576?embed<\\/a><\\/p>\n https:\\/\\/twitter.com\\/marcoemrich\\/status\\/897199629275725824?embed<\\/a><\\/p>\n and take a stand against sexists within our community:<\\/p>\n https:\\/\\/twitter.com\\/dmikeyanderson\\/status\\/897124081652293632?embed<\\/a><\\/p>\n JavaScript<\\/h3>\nFranziska writes on V8's bytecode:<\\/p>\nhttps:\\/\\/twitter.com\\/fhinkel\\/status\\/898184918286643201?embed<\\/a><\\/p>\n A new official Node.js API for headless Chrome appeared:<\\/p>\n https:\\/\\/twitter.com\\/coderbyheart\\/status\\/897864286525169664?embed<\\/a><\\/p>\n I made a finger disco:<\\/p>\n https:\\/\\/twitter.com\\/coderbyheart\\/status\\/897500349870755842?embed<\\/a><\\/p>\n \n React (and other open-source projects by Facebook) will keep\n the patent clause<\\/a> in\n their license:\n<\\/p>\n https:\\/\\/twitter.com\\/coderbyheart\\/status\\/899165362750619651?embed<\\/a><\\/p>\n Tech<\\/h3>\n\n Contentful changed it's pricing model, which is great, because\n I use it to build this website<\\/a>:\n<\\/p>\n https:\\/\\/twitter.com\\/coderbyheart\\/status\\/898062887096397824?embed<\\/a><\\/p>\n Bootstrap next major release is getting closer:<\\/p>\n https:\\/\\/twitter.com\\/coderbyheart\\/status\\/896613287038734336?embed<\\/a><\\/p>\n Tricks for the Chrome Developer tools:<\\/p>\n https:\\/\\/twitter.com\\/fox\\/status\\/898397296798203905?embed<\\/a><\\/p>\n People<\\/h3>\nOn hiring women for tech roles:<\\/p>\nhttps:\\/\\/twitter.com\\/coderbyheart\\/status\\/896688570462818304?embed<\\/a><\\/p>\n https:\\/\\/twitter.com\\/MIT\\/status\\/898199017439547392?embed<\\/a><\\/p>\n On Code of Conducts:<\\/p>\n https:\\/\\/twitter.com\\/fox\\/status\\/898046902884720640?embed<\\/a><\\/p>\n https:\\/\\/twitter.com\\/langziehohr\\/status\\/897832402361495553?embed<\\/a><\\/p>\n Why Code of Conducts are important:<\\/p>\n https:\\/\\/twitter.com\\/fox\\/status\\/899129551522979840?embed<\\/a><\\/p>\n I made a list of women in civic tech:<\\/p>\n https:\\/\\/twitter.com\\/coderbyheart\\/status\\/897564594654384129?embed<\\/a><\\/p>\n 🎧 Listening to<\\/h3>\n\n Solomun x Âme x Moderat - Ketamine Kettle<\\/a><\\/li>\n 22 by Boris Brejcha<\\/a><\\/li>\n<\\/ul>\n\n \n Remember to follow me on Twitter<\\/a>! DMs are\n open!\n I'm happy to answer your questions<\\/a>\n ...\n <\\/p>\n<\\/blockquote>\n","slug":"heart-of-code-001","hero":"!undefined"}],["heart-of-code-002",{"title":"❤️.of(code) \\/\\/ 002","subtitle":"Week 34 of 2017","abstract":"Week 34 of 2017 in review","date":"2017-08-27T14:00+02:00","html":"\n \n <\\/picture><\\/aside>\n<\\/p>\n\n Celebrating 2,000 followers on @coderbyheart<\\/a>\n I decided to sum up my week on Twitter from now on every weekend.\n<\\/p>\n Tech 🚀<\\/h3>\nYou can go to jail if you just follow the orders your managers gives you<\\/em>:<\\/p>\nhttps:\\/\\/twitter.com\\/tedneward\\/status\\/901135785969074177?embed<\\/a><\\/p>\n Facebook is fucking disgusting:<\\/p>\n https:\\/\\/twitter.com\\/dhh\\/status\\/900893798821134336?embed<\\/a><\\/p>\n \n Benjamin (a super awesome coffe-to-code organism) has created a GitHub repo\n where you can ask him questions:\n<\\/p>\n https:\\/\\/twitter.com\\/benjamin\\/status\\/900473217118240768?embed<\\/a><\\/p>\n JavaScript 🛠<\\/h3>\n\n Dudes behaving like assholes will make contributors turn away, that's why\n there is now a Node.js fork<\\/a>:\n<\\/p>\n https:\\/\\/twitter.com\\/maybekatz\\/status\\/899746713572786177?embed<\\/a><\\/p>\n https:\\/\\/twitter.com\\/ohhoe\\/status\\/899748838302302212?embed<\\/a><\\/p>\n https:\\/\\/twitter.com\\/maybekatz\\/status\\/900680829512294404?embed<\\/a><\\/p>\n It matters which behaviour you accept withing you community, because:<\\/p>\n https:\\/\\/twitter.com\\/maybekatz\\/status\\/901288355773599744?embed<\\/a><\\/p>\n I've learned to appreciate async\\/await for this reason:<\\/p>\n https:\\/\\/twitter.com\\/coderbyheart\\/status\\/900252517723930624?embed<\\/a><\\/p>\n Web 🌍<\\/h3>\nLearn how CSS is implemented in CSS (and why Rust is great for that):<\\/p>\nhttps:\\/\\/twitter.com\\/coderbyheart\\/status\\/900267620515106816?embed<\\/a><\\/p>\n Diversity 🌈<\\/h3>\nDon't be shy, your will be senior in no time:<\\/p>\nhttps:\\/\\/twitter.com\\/sehurlburt\\/status\\/901538910764793856?embed<\\/a><\\/p>\n Because:<\\/p>\n https:\\/\\/twitter.com\\/RidingWolf\\/status\\/900994562012917761?embed<\\/a><\\/p>\n Railsgirls released a report on the impact of their initiative:<\\/p>\n https:\\/\\/twitter.com\\/fox\\/status\\/901319347573891074?embed<\\/a><\\/p>\n Conferences 💡<\\/h3>\n\n \n The European Testing Conference 2018<\\/a>\n has announced\n their keynote speakers<\\/a>\n and is taking place on February 19-20 February 2018 in Amsterdam. Tickets\n start at €899.\n <\\/li>\n \n The codefreeze<\\/a> is free<\\/em> and is taking place on\n Jan 15th-18th 2018 in Kiilopää, Finland. I wrote\n here<\\/a>\n about why it is so awesome.\n <\\/li>\n<\\/ul>\n\n I'm sponsoring a diversity ticket here, so please apply also to RuhrJS (October\n 14th+15th 2017):\n<\\/p>\nhttps:\\/\\/twitter.com\\/RuhrJS\\/status\\/900285456549638144?embed<\\/a><\\/p>\n Listening to 🎧<\\/h3>\n\n Armin van Buuren live at Tomorrowland 2017<\\/a><\\/li>\n Tomorrowland Belgium 2017 | Paul van Dyk<\\/a><\\/li>\n \n QOTSA's new album\n Villains<\\/a>\n <\\/li>\n<\\/ul>\n\n \n Remember to follow me on Twitter<\\/a>! DMs are\n open!\n I'm happy to answer your questions<\\/a>\n ...\n <\\/p>\n<\\/blockquote>\n","slug":"heart-of-code-002","hero":"!undefined"}],["heart-of-code-003",{"title":"❤️.of(code) \\/\\/ 003","subtitle":"Week 35 of 2017","abstract":"Week 35 of 2017 in review","date":"2017-09-04T14:00+02:00","html":"\n \n <\\/picture><\\/aside>\n<\\/p>\n\n Celebrating 2,000 followers on @coderbyheart<\\/a>\n I decided to sum up my week on Twitter from now on every weekend.\n<\\/p>\n Tech 🚀<\\/h3>\n\n I've been using Firefox Focus<\\/a>\n now for two weeks and I really like it when reading articles from RSS feeds. It\n blocks a lot of ads and does not pollute my history with one-shot visits.\n<\\/p>\n Some asshole dude can't deal with a woman, again.<\\/p>\n https:\\/\\/twitter.com\\/jessfraz\\/status\\/902262783672291328?embed<\\/a><\\/p>\n \n The next thing regarding Facebook and licenses came up. This time:\n GraphQL<\\/a>.\n<\\/p>\n https:\\/\\/twitter.com\\/coderbyheart\\/status\\/902804396504961025?embed<\\/a><\\/p>\n This might explain why I like cooking AND Linux:<\\/p>\n https:\\/\\/twitter.com\\/douglax\\/status\\/901155475424550912?embed<\\/a><\\/p>\n JavaScript 🛠<\\/h3>\nV8 is now on Twitter:<\\/p>\nhttps:\\/\\/twitter.com\\/v8js\\/status\\/902560466291093504?embed<\\/a><\\/p>\n I've learned a new term: NPM lego.<\\/p>\n https:\\/\\/twitter.com\\/coderbyheart\\/status\\/902791900104667136?embed<\\/a><\\/p>\n I am still struggling with TypeScript:<\\/p>\n https:\\/\\/twitter.com\\/coderbyheart\\/status\\/903619298215768064?embed<\\/a><\\/p>\n Also, I haven't completely ditched Promises, yet.<\\/p>\n https:\\/\\/twitter.com\\/coderbyheart\\/status\\/902646931226275840?embed<\\/a><\\/p>\n \n With Chirr<\\/a> I can finally effortless create a Twitter\n thread. Like this one about my visit to Trondheims JavaScript UserGroup\n BartJS<\\/a>:\n<\\/p>\n https:\\/\\/twitter.com\\/coderbyheart\\/status\\/903548864384438272?embed<\\/a><\\/p>\n Web 🌍<\\/h3>\n\n Because Web<\\/em> is an ever changing target, our performance optimizations\n strategies are also in constant need of revisiting them:\n<\\/p>\nhttps:\\/\\/twitter.com\\/fox\\/status\\/903190652401451008?embed<\\/a><\\/p>\n Diversity 🌈<\\/h3>\n\n A longer article about Project Include<\\/a>\n highlights some of their methods:\n<\\/p>\n https:\\/\\/twitter.com\\/projectinclude\\/status\\/903288925485228032?embed<\\/a><\\/p>\n Culture✌️<\\/h3>\nVery well said:<\\/p>\nhttps:\\/\\/twitter.com\\/amokleben\\/status\\/903218809183535104?embed<\\/a><\\/p>\n \n \"We don't have enough experts\" You 👏 have 👏 to 👏 start 👏 training 👏 some!<\\/p>\n<\\/blockquote>\n Nordic understands that, and investe in roughly 40 paid summer interns:<\\/p>\nhttps:\\/\\/twitter.com\\/NordicTweets\\/status\\/903216628048986112?embed<\\/a><\\/p>\n Also culture, but different:<\\/p>\n https:\\/\\/twitter.com\\/kcimc\\/status\\/902229612666658816?embed<\\/a><\\/p>\n Conferences 💡<\\/h3>\nA reminder:<\\/p>\nhttps:\\/\\/twitter.com\\/uveavanto\\/status\\/902852536557871106?embed<\\/a><\\/p>\n Franzi<\\/a> has another:<\\/p>\n https:\\/\\/twitter.com\\/Singsalad\\/status\\/902626487471362048?embed<\\/a><\\/p>\n Listening to 🎧<\\/h3>\n\n \n Joachim Pastor - Promesse<\\/a> (the\n long version!)\n <\\/li>\n \n THE HAUNTED - Preachers Of Death<\\/a>\n and the rest of\n their new album<\\/a>\n <\\/li>\n \n Every Country's Sun<\\/a>,\n Mogwai's new album\n <\\/li>\n<\\/ul>\n\n \n Remember to follow me on Twitter<\\/a>! DMs are\n open!\n I'm happy to answer your questions<\\/a>\n ...\n <\\/p>\n<\\/blockquote>\n","slug":"heart-of-code-003","hero":"!undefined"}],["heart-of-code-004",{"title":"❤️.of(code) \\/\\/ 004","subtitle":"Week 36 of 2017","abstract":"Week 36 of 2017 in review","date":"2017-09-10T22:00+02:00","html":"\n \n <\\/picture><\\/aside>\n<\\/p>\n\n Celebrating 2,000 followers on @coderbyheart<\\/a>\n I decided to sum up my week on Twitter from now on every weekend.\n<\\/p>\n Tech 🚀<\\/h3>\ngit merge<\\/code> and git rebased<\\/code> lovely explained with cats:<\\/p>\nhttps:\\/\\/twitter.com\\/girlie_mac\\/status\\/906691511496011778?embed<\\/a><\\/p>\n There is a new place to find Software Craft Communities around the world:<\\/p>\n https:\\/\\/twitter.com\\/rradczewski\\/status\\/906522197602299906?embed<\\/a><\\/p>\n Don't pretend, you haven't:<\\/p>\n https:\\/\\/twitter.com\\/ifCoffeeEquals0\\/status\\/902911447293980672?embed<\\/a><\\/p>\n I needed to install Java this week:<\\/p>\n https:\\/\\/twitter.com\\/coderbyheart\\/status\\/906083160089395203?embed<\\/a><\\/p>\n Yes, please do and own your data!<\\/p>\n https:\\/\\/twitter.com\\/lila_luca\\/status\\/905757976518066180?embed<\\/a><\\/p>\n \n Germany uses software to count votes, that makes Windows XP look like a\n marvelous piece of software:\n<\\/p>\n https:\\/\\/twitter.com\\/coderbyheart\\/status\\/905753958400106496?embed<\\/a><\\/p>\n \n If you don't like Firma Fira Code<\\/a>,\n then checkout these alternative fonts for writing c0d3:\n<\\/p>\n https:\\/\\/twitter.com\\/coderbyheart\\/status\\/905310598531043328?embed<\\/a><\\/p>\n Some good thoughts on code coverage:<\\/p>\n https:\\/\\/twitter.com\\/matthewpskelton\\/status\\/904654850968965120?embed<\\/a><\\/p>

Not in v3: StepFunctions<\\/h2>\n
\n The StepFunctions client has not been ported to v3 because the service\n does not support CORS<\\/a>,\n because browsers cannot interact with it.\n<\\/p>\n

Does JavaScript scale both in the technical sense and within teams?<\\/h2>\n
https:\\/\\/twitter.com\\/coderbyheart\\/status\\/1064131366416195584?embed&conversation=none<\\/a><\\/p>\n

Is JavaScript a good language for programming beginners?<\\/h2>\n
https:\\/\\/twitter.com\\/coderbyheart\\/status\\/1064131378634268672?embed&conversation=none<\\/a><\\/p>\n
\n Check out CodeDoor<\\/a> - they help people from\n underrepresented groups learn to program!\n<\\/p>\n