makomweb

<?php

use React\EventLoop\Factory;
use Rx\Observable;
use Rx\Scheduler;
use Rx\Scheduler\EventLoopScheduler;

require_once __DIR__ . '/vendor/autoload.php';

$loop = Factory::create();

makomweb

<?php

declare(strict_types=1);

use Symfony\Bundle\FrameworkBundle\Test\KernelTestCase;
use Symfony\Component\Serializer\SerializerInterface;

class PropertiesTest extends KernelTestCase
{
    private SerializerInterface $serializer;

makomweb

using Newtonsoft.Json;
using NUnit.Framework;
using System;

namespace JSON_empty_string_or_null_to_false_conversion
{
    public class MyDocument
    {
        public bool MyFlag { get; set; }

makomweb

namespace Sandbox
{
    public class MyTests
    {
        [Test]
        public async Task Run_me()
        {
            var numbers = new List<int> { 1, 2, 3, 5, 8 };

            var sum = SumAsync(numbers);

makomweb

<?php

declare(strict_types=1);

namespace App\Tests\Unit;

use LogicException;
use PHPUnit\Framework\TestCase;

class MyClass {}

makomweb

1. download the ps file from https://docs.microsoft.com/en-us/dotnet/core/tools/dotnet-install-script
2. ensure the SDK is installed via dotnet --list-sdks

makomweb

<?php

class dynamic {
    private $data;
    
    public function __construct($data) {
        $this->data = $data;
    }
    
    public function __call($method, $arguments) {

makomweb

# update .gitignore properly

# after that:
git rm -rf --cached .
git add .

makomweb

#!/bin/sh

# Credits: http://stackoverflow.com/a/750191

git filter-branch -f --env-filter "
    GIT_AUTHOR_NAME='__AUTHOR_NAME__'
    GIT_AUTHOR_EMAIL='__AUTHOR_EMAIL_ADDRESS__'
    GIT_COMMITTER_NAME='__COMMITTER_NAME__'
    GIT_COMMITTER_EMAIL='__COMMITTER_EMAIL_ADDRESS__'
  " HEAD

makomweb

Mitschrift: Technology Lunch - INNOQ - Softwarearchitektur für Entscheider

Youtube: Software-Architektur für Entscheider – INNOQ Technology Lunch

Was ist Software-Architektur? (2 Beispieldefinitionen)

Die Komponenten eines Systems, ihre Beziehungen zueinander sowie die Prinzipien und Regeln, denen ihre (Weiter-)Entwicklung folgt. (ISO 42010)

Die Summe der bedeutenden Design-Entscheidungen, die das System formen, wobei >>bedeutend<< anhand der Änderungskosten gemessen wird. (Grady Booch)