Skip to content

Instantly share code, notes, and snippets.

View danielkochdakitec's full-sized avatar

Daniel Koch danielkochdakitec

View GitHub Profile
@belgattitude
belgattitude / ci-yarn-install.md
Last active May 24, 2024 22:04
Composite github action to improve CI time with yarn 3+ / node-modules linker.
@adrienjoly
adrienjoly / fix-dyld-missing-symbol-called-errors-on-m1-macs.md
Last active February 3, 2024 18:01
Fix `dyld[]: missing symbol called` errors when running Node.js programs on M1 Macs (apple silicon)

Problem

If you're getting this kind of error when running Node.js programs with binary dependencies that don't support M1 yet, e.g.:

$ yarn test
dyld[51175]: missing symbol called
dyld[51176]: missing symbol called
@danielkochdakitec
danielkochdakitec / sitemap.xml
Created March 28, 2020 09:20
Example sitemap
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.sitemaps.org/schemas/sitemap/0.9 http://www.sitemaps.org/schemas/sitemap/0.9/sitemap.xsd">
<url>
<loc>https://dakitec.de/</loc>
<lastmod>2020-01-01</lastmod>
<changefreq>weekly</changefreq>
<priority>1.0</priority>
</url>
<url>
<loc>https://dakitec.de/blog</loc>
@danielkochdakitec
danielkochdakitec / cookie-banner.html
Last active January 11, 2024 17:42
Cookie-Banner selbst erstellen - nicht mehr rechtssicher, stattdessen hier schauen: https://dakitec.de/wissen/software-dsgvo-konform#cookiebot-cmp
@danielkochdakitec
danielkochdakitec / pts to pcd
Last active June 6, 2020 07:55
Convert a PTS to a PCD file using Python line-by-line
inputFile = open("result_input.pts", "r") # Input-file
outputFile = open("result_output.pcd", "w") # Output-file
length = int(inputFile.readline()) # First line is the length
outputFile.write("VERSION .7\nFIELDS x y z rgb\nSIZE 4 4 4 4\nTYPE F F F F\nCOUNT 1 1 1 1\nWIDTH {}\nHEIGHT 1\nVIEWPOINT 0 0 0 1 0 0 0\nPOINTS {}\nDATA ascii\n".format(length, length)) # Sets the header of pcd in a specific format, see more on http://pointclouds.org/documentation/tutorials/pcd_file_format.php
currentLinePosition = 0
for line in inputFile:
@luismts
luismts / GitCommitBestPractices.md
Last active May 22, 2024 13:33
Git Tips and Git Commit Best Practices

Git Commit Best Practices

Basic Rules

Commit Related Changes

A commit should be a wrapper for related changes. For example, fixing two different bugs should produce two separate commits. Small commits make it easier for other developers to understand the changes and roll them back if something went wrong. With tools like the staging area and the ability to stage only parts of a file, Git makes it easy to create very granular commits.

Commit Often

Committing often keeps your commits small and, again, helps you commit only related changes. Moreover, it allows you to share your code more frequently with others. That way it‘s easier for everyone to integrate changes regularly and avoid having merge conflicts. Having large commits and sharing them infrequently, in contrast, makes it hard to solve conflicts.