Missed some occurances of Barbara that needed to be renamed to Niklaus

Author: erichgess

src/vision/status_quo/barbara_simulates_hydrodynamics.md renamed to src/vision/status_quo/niklaus_simulates_hydrodynamics.md

@@ -1,4 +1,4 @@
-# 😱 Status quo stories: Barbara Builds a Hydrodynamics Simulator
+# 😱 Status quo stories: Niklaus Builds a Hydrodynamics Simulator
 
 ## 🚧 Warning: Draft status 🚧
 
@@ -54,13 +54,13 @@ This new solution works, but Niklaus is not satisfied with how complex his code
 ### **What are the sources for this story?**
 This story is based on the experience of building the [kilonova](https://github.com/clemson-cal/app-kilonova) hydrodynamics simulation solver.
 
-### **Why did you choose Barbara and Grace to tell this story?**
+### **Why did you choose Niklaus and Grace to tell this story?**
 I chose Niklaus as the primary character in this story because this work was driven by someone who only uses programming for a small part of their work. Grace was chosen as a supporting character because of that persons experience with C/C++ programming and to avoid repeating characters.
 
 ### **How would this story have played out differently for the other characters?**
 - Alan: there's a good chance he would have already had experience working with either async workflows in another language or doing parallelization of compute bound tasks; and so would already know from experience that `async` was not the right place to start.  
 - Grace: likewise, might already have experience with problems like this and would know what to look for when searching for tools. 
-- Niklaus: the experience would probably be the same, as it's very easy to assume that `tokio` is the starting place for concurrency in Rust.
+- Barbara:  the experience would likely be fairly similar, since the actual subject of this story is quite familiar with Rust by now
 
 [character]: ../characters.md
 [status quo stories]: ./status_quo.md