From 40debcfaced1bf252388eaf46eae23e03bc7fc00 Mon Sep 17 00:00:00 2001 From: Anson Biggs Date: Tue, 28 Sep 2021 08:07:45 -0700 Subject: [PATCH] work on #1 --- ...tinuous-integration-and-systems-engineering.Rmd | 14 +++++--------- ...inuous-integration-and-systems-engineering.html | 9 ++++++--- 2 files changed, 11 insertions(+), 12 deletions(-) diff --git a/_posts/2021-09-27-continuous-integration-and-systems-engineering/continuous-integration-and-systems-engineering.Rmd b/_posts/2021-09-27-continuous-integration-and-systems-engineering/continuous-integration-and-systems-engineering.Rmd index 343acb0..74d8aca 100644 --- a/_posts/2021-09-27-continuous-integration-and-systems-engineering/continuous-integration-and-systems-engineering.Rmd +++ b/_posts/2021-09-27-continuous-integration-and-systems-engineering/continuous-integration-and-systems-engineering.Rmd @@ -10,15 +10,11 @@ output: distill::distill_article: self_contained: false draft: true +categories: + - Systems Engineering + - Capstone --- +Working on a complex project that spans multiple domains can be really challenging for a small team. The small team size makes it hard not to keep every team member completely up to date on the inner workings of every system but that can add a ton of overhead and make progress slow to a halt. My [Capstone](https://projects.ansonbiggs.com/#category:Capstone) team makes this even harder since all but one of us are Astronautical Engineers. Astronautical is just a fancy way of saying "Systems, but every problem is a satellite" so a project like ours that has a massive Embedded software aspect can be really challenging since the most important part of the project is essentially a black box to a majority of the team. -```{r setup, include=FALSE} -knitr::opts_chunk$set(echo = FALSE) -``` - -Distill is a publication format for scientific and technical writing, native to the web. - -Learn more about using Distill at . - - +To combat most of the team having zero knowledge of writing C++ for a microcontroller I opted to use Gitlab's CI to build and post results for every single commit that the repository sees. So far this has worked really well. The people in charge of other subsystems can look at the readme of the GitLab repo and see diff --git a/_posts/2021-09-27-continuous-integration-and-systems-engineering/continuous-integration-and-systems-engineering.html b/_posts/2021-09-27-continuous-integration-and-systems-engineering/continuous-integration-and-systems-engineering.html index 359e174..aabd967 100644 --- a/_posts/2021-09-27-continuous-integration-and-systems-engineering/continuous-integration-and-systems-engineering.html +++ b/_posts/2021-09-27-continuous-integration-and-systems-engineering/continuous-integration-and-systems-engineering.html @@ -111,7 +111,7 @@ code span.wa { color: #5e5e5e; font-style: italic; } /* Warning */ @@ -1467,6 +1467,10 @@ code span.wa { color: #5e5e5e; font-style: italic; } /* Warning */

Continuous Integration and Systems Engineering

+
+
Systems Engineering
+
Capstone
+

A short description of the post.

@@ -1478,8 +1482,7 @@ code span.wa { color: #5e5e5e; font-style: italic; } /* Warning */
-

Distill is a publication format for scientific and technical writing, native to the web.

-

Learn more about using Distill at https://rstudio.github.io/distill.

+

Working on a complex project that spans multiple domains can be really challenging for a small team. The team size being small makes it hard not to keep every team member completely up to date on the inner workings of every system but that can add a ton of overhead and make progress slow to a halt. My Capstone team makes this even harder since all but one of us are Astronautical Engineers.