Skip to content

Instantly share code, notes, and snippets.

View sebs's full-sized avatar

Sebastian Schürmann sebs

View GitHub Profile
sebs /
Last active February 21, 2023 23:59
sebs /
Last active May 4, 2022 21:33
Steve Hassans Model of Authoritarian Control applied to Agile Software Development


Behaviour Control

Information Control

Thought Control

import { Duration, RemovalPolicy, Stack, StackProps } from 'aws-cdk-lib';
import { Repository, IRepository } from 'aws-cdk-lib/aws-codecommit';
import { Construct } from 'constructs';
import { BlockPublicAccess, Bucket } from 'aws-cdk-lib/aws-s3';
import { ARecord, HostedZone, IHostedZone, RecordTarget, ZoneDelegationRecord } from 'aws-cdk-lib/aws-route53';
import { AllowedMethods, Distribution, OriginAccessIdentity, SecurityPolicyProtocol, ViewerProtocolPolicy } from 'aws-cdk-lib/aws-cloudfront';
import { Artifact,Pipeline } from 'aws-cdk-lib/aws-codepipeline';
import { CloudFormationCreateUpdateStackAction, CodeBuildAction, CodeCommitSourceAction, S3DeployAction } from 'aws-cdk-lib/aws-codepipeline-actions';
import { PipelineProject, BuildSpec, LinuxBuildImage } from 'aws-cdk-lib/aws-codebuild';
import { CodePipeline as CodePipelineTarget } from 'aws-cdk-lib/aws-events-targets';

Just a user story with some acceptance criteria is not enough when estimating stories that you implement in AWS cloud

Scrum way of doing things delays lots of design decisions into planning I - When you work with software defined infrastructure, you need to do a design earlier in the process on, in order to get results that match with reality.


Software defined infrastructure vs. given infrastructure

When Scrum and user stories were invented, infrastructure was a given thing and features assumed it to be. At some point in time, a server was purchased or rented and this was a given set of ressources then.


where is the value?

Maslows Hierarchy of Bullshit

out of your comfort zone?

User Stories for AWS/Serverless

  • Serverless is more expensive
    • re-building infrastructure every time
    • slower integration tests
    • you can parallellize
  • which services are you using ?
    • which limits are there
  • draw how messages flow
  • do not use images as documentation

Incremental and Iterative

  • a meta book
  • not using buzzwords (like agile)
  • has concrete references
  • avoids rulkes, laws atc that are stemming from (western) philosopy
    • explains why these rules are no rules
  • Gives examples for practices in inccremental and iterative organizations
  • no sudo religious BS
  • adhere to maslow (eating/sex > recreational learning)

fuckups der Ausbildung on der IT

The Jobmarket is a sellers market

Es gibt weit weniger neu ausgebildete Informatiker und Software Entwickler als der 'Markt' benötigt. Die schafft einen 'Sellers Market', wo die Anbieter die Bedingungen diktieren.

Leider scheinen dies wenige Unternehmen anzuerkennen, so scheinen mir doch diverse Haltungen und Forderungen im Umgang mit Neulingen eher vom 'alten Geist' geprägt. Anzeichen hierfür


# Präambel
1. Demokratie und Grundwerte
1. Stärkung der Unabhängigkeit des Bfg
2. Stärkung der Rechte von Opposition und Presse
3. Kein Staat für
4. Abschaffung der Vorratsdatenspeicherung
5. Politische Partizipation für nichtdeutsche Mitbürger
2. Euro und Europa
1. Ein Europa der Partnerschaften über Forschung und Bildung