xpepper

What is a Design Pattern?

Every Software Engineer certainly must have to deal with change. Change is a constant in Software Design: adding feature, changing of requirement or bug fixing.

What is a design pattern? In simplest way I can say, it is a general solution for common problems in Software Development. The purpose of design patterns is to help structure your code so it will be flexible and resilient when its changed.

There are 23 common design patterns that are being used by programmers around the world. In this chapter I am going to describe the Observer Pattern.

Introduction to Observer Pattern

xpepper

Classical 'persona-oriented' template

As a <user or stakeholder type>
I want <some software feature>
So that <some business value>

Alternative #1

(http://blog.crisp.se/2014/09/25/david-evans/as-a-i-want-so-that-considered-harmful)

In order to <achieve some business value>,

As a

xpepper

#!/bin/bash
convert "$1" -morphology Convolve DoG:15,100,0 -negate -normalize -blur 0x1 -channel RBG -level 60%,91%,0.1 "$2"%

xpepper

Rodrigue Schaefer: From monolith to microservices about some of the challenges of Zalando's transition from monolith to microservices (microXchg 2016)

Zalando history

• 2008 started with a POC with magento => starts fine but does not scale very well

• 2010 couldn't handle the raising load and traffic with magento

• => so in 3 months they build their own system, based on Java, Spring, Postgres DB (a monolithic application)

xpepper

tags	disqus
kata	pierodibello

A curated list of programming kata

IDE automation skills

• Refactoring Golf katas (easy...medium), to learn how to use the IDE at its best

xpepper

// it's NOT an extension function
// it takes the receiver and a lambda with the same receiver
// it returns the result of the lambda on the implicit receiver
inline fun <T, R> with(receiver: T, block: T.() -> R): R {
    return receiver.block()
}

with ("ciao") {
    length + 1

xpepper

Docker aliases

(full article by Andrew Welch here: https://nystudio107.com/blog/dock-life-using-docker-for-all-the-things)

alias composer='docker run --rm -it -v `pwd`:/app -v ${COMPOSER_HOME:-$HOME/.composer}:/tmp composer '
alias composer1='docker run --rm -it -v `pwd`:/app -v ${COMPOSER_HOME:-$HOME/.composer}:/tmp composer:1 '

alias node='docker run --rm -it -v `pwd`:/app -w /app node:16-alpine '

xpepper

tags
coaching, scrum

Powerful questions for a Scrum Team

(notes taken from the article https://medium.com/the-liberators/how-to-use-powerful-questions-virtually-46a76096630a)

The best way to unleash teams is to ask questions instead of giving (your) solutions.

xpepper

podcast to listen

• https://softwareengineeringdaily.com/2019/09/27/stripe-infrastructure-management-with-uma-chingunde/
• https://softwareengineeringdaily.com/2019/11/14/graalvm-quarkus-java-acceleration-with-guillaume-smet-and-emmanuel-bernard/
• https://softwareengineeringdaily.com/2019/11/21/http-with-julia-evans/
• https://softwareengineeringdaily.com/2019/09/27/stripe-infrastructure-management-with-uma-chingunde/

xpepper

Continuous Integration - Know your opportunities

Continuous Integration in a nutshell

Continuous Integration (CI) is an important practice every team should adopt in order to detect defects and errors early and solve integration problems easily. Roughly speaking we may say that CI is a practice that allows the growth of solid software by giving greater confidence to the developers and better products to the final customers.

The concept behind CI is fairly simple: the codebase is owned by several developers that continuously integrate their changes to a common version control system. For each integration the system runs a predefined set of tasks automatically; these tasks may vary from running all the tests to building all the components.