chore(posts): adjust markdown format to linter rules

Author: photonbit

_posts/2023-01-25-a-good-ending.md

@@ -8,4 +8,7 @@ description: "Why Tesselo did not succeed as a business, but still achieved many
 featured: true
 hidden: true
 ---
-Tesselo worked with satellites, space tech, AI, and in the cloud. So many buzz words united in one startup. How it it possible that there was no market for such a future oriented technology? This is a question we have posed ourselves many times. It is also the reason why we were so resilient and kept going for almost 7 years before deciding to stop.
+Tesselo worked with satellites, space tech, AI, and in the cloud. So many buzz words united in one startup.
+How is it possible that there was no market for such a future oriented technology?
+This is a question we have posed ourselves many times.
+It is also the reason why we were so resilient and kept going for almost 7 years before deciding to stop.

_posts/2023-01-26-guts-of-startup.md

@@ -9,12 +9,23 @@ featured: true
 hidden: true
 ---
 
-After 7 years of hard work, our passion project, our beloved venture, our partnership has come to an end. Like countless other startups, Tesselo has failed and died. Now that we have reached the end, we turn remembering Tesselo into a celebration. We will hold memories of our dear venture joyfully.
+After 7 years of hard work, our passion project, our beloved venture, our partnership has come to an end.
+Like countless other startups, Tesselo has failed and died. Now that we have reached the end,
+we turn remembering Tesselo into a celebration. We will hold memories of our dear venture joyfully.
 
-The first reason to celebrate the end of Tesselo is the successfuly continuation of the careers of everyone that was involved in the project. We can proudly say that nobody regrets their participation, on the contrary. We have seen the growth of everyone while Tesselo was alive, and can witness the impact it has on the humans - the Tesseras - that have worked with us over time.
+The first reason to celebrate the end of Tesselo is the successfuly continuation of the careers of
+everyone that was involved in the project. We can proudly say that nobody regrets their participation,
+on the contrary. We have seen the growth of everyone while Tesselo was alive, and can witness
+the impact it has on the humans - the Tesseras - that have worked with us over time.
 
-We know that celebrating failure is in fashion and spinned the wrong way can be harmful. By no means we wish for anyone to fail, because not every failure must be seen as an oportunity. But it so happens that Tesselo's failure does not feel like a defeat. We knew when to stop and acted decisefully to make a graceful landing. We helped everyone to find new challenges, and have seen that happen quickly. We did not go bankrupt.
+We know that celebrating failure is in fashion and spinned the wrong way can be harmful.
+By no means we wish for anyone to fail, because not every failure must be seen as an oportunity.
+But it so happens that Tesselo's failure does not feel like a defeat. We knew when to stop
+and acted decisefully to make a graceful landing. We helped everyone to find new challenges,
+and have seen that happen quickly. We did not go bankrupt.
 
-So now that Tesselo is dead, what remains? We have decided do die with honour by cutting our guts open and spreading them for everyone to see. This page is where you can find the remains, which include as much as we have time and legal rights to share.
+So now that Tesselo is dead, what remains? We have decided do die with honour by cutting
+our guts open and spreading them for everyone to see. This page is where you can find the remains,
+which include as much as we have time and legal rights to share.
 
 Enjoy weeding through the remains, we hope there is something of use for you in here!

_posts/2023-02-07-open-sourcing-our-team-wisdom.md

@@ -8,18 +8,33 @@ description: "A proposal to open source some of our codebase and our team wisdom
 featured: false
 hidden: false
 ---
-We want to share as much as we can from our insights that we gained at Tesselo. Some of the most tangible outcomes are code and written documents that we accumulated. Whatever is not personal or infringes non-disclosure agreements can be shared in principle. Here is a proposal for a process on how to do it.
+We want to share as much as we can from our insights that we gained at Tesselo.
+Some of the most tangible outcomes are code and written documents that we accumulated.
+Whatever is not personal or infringes non-disclosure agreements can be shared in principle.
+Here is a proposal for a process on how to do it.
 
 ## Ask for permission
-Before publishing anything, the people involved should be asked for their permission, even if they are not the owner of the intellectual property. It is still their work and publishing it will have some implications for their public persona. Hopefully these implications are desired and positive, but each individual should be able to decide for themselves.
 
-## Making GitHub repositories public   
-Technically this is simple, it requires adding a license to the repository and clicking a checkbox on GitHub. However, the implications are quite large for repositories with many commits and pull requests. All contributions that people made to the repository will be publicly visible.
+Before publishing anything, the people involved should be asked for their permission,
+even if they are not the owner of the intellectual property. It is still their work
+and publishing it will have some implications for their public persona. Hopefully
+these implications are desired and positive, but each individual should be able to decide for themselves.
+
+## Making GitHub repositories public
+
+Technically this is simple, it requires adding a license to the repository and clicking
+a checkbox on GitHub. However, the implications are quite large for repositories with many commits
+and pull requests. All contributions that people made to the repository will be publicly visible.
 
 - Advantage: all coders involved become an open source contributors
 - Risk: interactions and code quality will be publicly visible
 
-An alternative is to create a new repository and push the code there. Like this the contributions will become public, but not the interaction that lead to them.
+An alternative is to create a new repository and push the code there.
+Like this the contributions will become public, but not the interaction that lead to them.
 
 ## Publishing team agreements
-Througout our work we have developed interesting documents such as team agreements on how to operate. These documents live on Bahamut, our shared wiki. The agreements might be relevant for our team members in their new contexts, and possibly other teams as well. Publishing the agreements will make it easier to re-use them in the future.
+
+Througout our work we have developed interesting documents such as team agreements on how to operate.
+These documents live on Bahamut, our shared wiki. The agreements might be relevant for our team members
+in their new contexts, and possibly other teams as well. Publishing the agreements
+will make it easier to re-use them in the future.