posts/HackBU2024.md

@@ -37,8 +37,11 @@ So yeah before anything I wasted an hour or 2 working on setting up an ORM that
 First things first, I had to get the data. Now you'd think that reverse engineering a bus live map would be hard but as it turns out it's pretty easy at least for what I'm doing. It was literally just
 
 1. go to live map website
+
 2. open up the network tab of the browser dev tools
+
 3. refresh the page and search for the words "bus", "route" and "stop" in the requests
+
 4. click on the obvious results and use brain to figure out what json fields like "name" and "stops" and "lat" and "lon" could possibly mean
 
 conveniently the Hackathon can't really prevent prior work that isn't code so all of the api reverse engineering was done the day before the hackathon so the time wasted on ORM stuff canceled out.
@@ -93,7 +96,6 @@ services:
     depends_on:
       - backend
 ```
-
 and here's an nginx config
 
 ```nginx

posts/invidious_and_goals.md

@@ -47,7 +47,6 @@ function handlePage(authority,response){
     }
 }
 ```
-
 Yeah, pretty simple but allow me to explain what bits of these 2 functions are doing and why.
 
 ```js

posts/soft-eng-project-retro.md

@@ -41,8 +41,10 @@ This situation was not helped by me getting sick on the last week but thankfully
 ## Lessons learned
 
 1) If I care about the success of something and nobody has taken charge of that thing within a timely manner, oftentimes this means within a week, then I need to take charge
-2) Barring circumstances where it isn't possible to do so a MVP of a project should be completed as the first unit of work, in this case that would've been a week. Afterwards units of work should be visible features.
-3) Any problem which is not fixed will remain a problem. In this case a team member having low remote responsiveness will not magically change so it'd have been better to start scheduling in person meetings sooner.
+2) Barring circumstances where it isn't possible to do so a MVP of a project should be completed as the first unit of work, in this case that would've been a week.
+Afterwards units of work should be visible features.
+3) Any problem which is not fixed will remain a problem. 
+In this case a team member having low remote responsiveness will not magically change so it'd have been better to start scheduling in person meetings sooner.
 
 ## What now