Skip to content

Instantly share code, notes, and snippets.

View jkiddo's full-sized avatar
🔥
🥷

Jens Kristian Villadsen jkiddo

🔥
🥷
View GitHub Profile
management:
endpoints:
web:
exposure:
include: "health,prometheus"
spring:
main:
allow-circular-references: true
#allow-bean-definition-overriding: true
flyway:
name ring quadrant isNew description
Flux adopt tools TRUE <strong>Very much needed</strong> - see <a href="https://fluxcd.io/">documentation</a>.
Canary builds trial techniques FALSE Many projects have external code dependencies ...
Apache Kylin assess platforms TRUE Apache Kylin is an open source analytics solution ...
JSF hold languages & frameworks FALSE We continue to see teams run into trouble using JSF ...
[
{
"name": "Composer",
"ring": "adopt",
"quadrant": "tools",
"isNew": "TRUE",
"description": "Although the idea of dependency management ..."
},
{
"name": "Canary builds",
spring:
main:
allow-circular-references: true
allow-bean-definition-overriding: true
flyway:
enabled: false
check-location: false
baselineOnMigrate: true
datasource:
#url: 'jdbc:h2:file:./target/database/h2'

Problem

I have two Github accounts: oanhnn (personal) and superman (for work). I want to use both accounts on same computer (without typing password everytime, when doing git push or pull).

Solution

Use ssh keys and define host aliases in ssh config file (each alias for an account).

How to?

  1. Generate ssh key pairs for accounts and add them to GitHub accounts.
@jkiddo
jkiddo / Setup.md
Created December 27, 2020 21:44
Setup Snapcast client on Raspbian Jessie lite

Setup Snapcast client on Raspbian Jessie / Stretch lite

Prerequisite

  • A Snapcast server
  • A Raspberry Pi running Raspbian Jessie/Stetch lite with SSH enabled

Setup Raspbian

  1. Login to Pi using SSH
@jkiddo
jkiddo / clean_code.md
Created September 3, 2019 18:18 — forked from wojteklu/clean_code.md
Summary of 'Clean code' by Robert C. Martin

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.


General rules

  1. Follow standard conventions.
  2. Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
  3. Boy scout rule. Leave the campground cleaner than you found it.
  4. Always find root cause. Always look for the root cause of a problem.

Design rules

@jkiddo
jkiddo / igpub maven
Created January 21, 2019 08:17
Rough initial maven file including all dependencies for igPub
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>org.hl7.fhir.igtools</groupId>
<artifactId>org.hl7.fhir.igtools</artifactId>
<version>0.0.1-SNAPSHOT</version>
<build>
<sourceDirectory>src</sourceDirectory>
<plugins>

Protokol- og model-lag for læsning/skrivning af information i HL7 modellerne CDA og FHIR:

Eksemplet her viser antallet af lag for at kunne læse/skrive ansvarlig enhed for en måling (observation) i et sæt af målinger. Sikkerhed er ikke taget med, da antallet af ekstra lag er ens for begge tilgange. Det forudsættes, at CDA dokumentet hentes over IHE XDS. Det forudsættes for begge at ID'et er kendt i forvejen.

FHIR

HTTP -> Json (HL7 FHIR) -> Bundle -> Resource -> Observation -> Performer

IHE XDS + CDA

HTTP -> SOAP + MTOM/XOP -> ebXML -> XML (HL7 CDA) -> ClinicalDocument -> component -> structuredBody -> component -> section -> entry -> act -> entryRelationship -> organizer -> participant -> participantRole -> scopingEntity