fabianhertwig / fabianhertwig.github.io

My blog

Fabian Hertwig's Blog

https://fabianhertwig.com

This is the repository for my blog. It is setup with jekyll and github pages.

Local setup

Install Ruby, best with rbenv. Check the latest stable version here: https://jekyllrb.com/docs/installation/macos/ (currently 3.1.3)

rbenv install 3.1.3
rbenv local 3.1.3

Install Bundler.

gem install bundler

Run

cd docs
bundle install
bundle exec jekyll serve --drafts

Start from scratch

This blog is based on github pages and jekyll, checkout the guide here: https://docs.github.com/en/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll

It uses the minimal mistakes theme

Changes:

• Link to the data privacy and imprint site in the footer, this is needed by german law. These sites are markdown files in the pages folder.
• The data/navigation.yml is configured to only show the posts and about link in the header.
• Cookie consent banner. The banner got generated with Osano. The scripts for the banner are in the _includes/custom.html file and assets/scripts/js/cookie-consent.js file.

Comment System

For comments giscus is added. The setup is based on this blogpost.

For the setup:

• discussions got enabled in the github repo
• giscus got installed as a github plugin
• the variables from the script got moved in the _config.yaml in a comments and giscus section

Domain Setup

I registered the domains fabianhertwig.com and fabianhertwig.de with google domains.

For fabianhertwig.com I setup the DNS entries according to this guide, so first the apex domain and then as well the CNAME for the www subdomain: https://docs.github.com/en/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site#configuring-an-apex-domain

For fabianhertwig.de I have setup a forward to the fabianhertwig.com domain.

fabianhertwig.github.io's Issues

Add comment section

This might help: https://www.aleksandrhovhannisyan.com/blog/jekyll-comment-system-github-issues/

Blog Post: Elon Musks design process

Elon musk 5 step process

Make the requirements less dumb

Delete the part or the process

Lot of people want to add stuff in case you need it. But you can make an in case argument for anything. You need to delete so much, that you feel the need to add thing back in later at a minimum of 10% of the cases. Otherwise you are are not deleting enough.
Requirements or constraints must come from a person and not a department.

Simplify or optimise

Only do that after deleting parts and processes. Spending time optimising something that should not exist is the worst time spent. We are trained in Highschool to not question the requirements but just come up with solutions.
Example: Falcon One had an upper stage with expensive fuels. They tried to optimise that, but it should just have been an upper stage that could use inexpensive fuels.

Accelerate cycle time

If you are going to slow, go faster. Only do that after the first three steps.

Automate

Common Errors

Elon made the mistake of going backwards through that process multiple times. Eg. on Model 3 there is a mat on top of the battery pack. They tried to optimise the production process by making the robots move faster and use less bolts and glue to fix the mat. At the end they asked what the mats are for. The battery department claimed they are for noise reduction but not needed for fire safety. The noise department said they are needed for fire safety. It turned out these mats are not needed.

Process line testing in between is not needed. Put it at the end.

Source https://youtu.be/t705r8ICkRw @13:30

Blog Post: How does Python import a file

Explain PYTHONPATH mystery

Blogpost: Designing great Data Products

Blog Post: The importance of business understanding in a data project

Blog Post: first principles thinking

Blog Post: Data Centric AI