-
Keeping it for the sake of CAS
-
Lessons learned during the development process of kineto
-
Feels like I learned a lot through Untrodden, as described in “Head that daydreams, hand that thinks”
- Innovation that starts with something interesting and gives you a sense of excitement
- Didn’t reach through deductive methods
-
The importance of user testing
- Reflecting on not being able to do more, but also realizing that if I hadn’t done things like the pre-8th meeting, I wouldn’t have seen various aspects
- Not just understanding the necessity of functions, but also deepening the understanding of phenomena
-
Since it’s unprecedented, conducting many experiments and eventually gaining insights that only you know in this knowledge world, then you feel impressed, like “wow”
- (Note from the 8th meeting social gathering)
- Unexpected discoveries
- Conflicts and such
- Clearing up the suitability of lessons in Professor Inami’s class
- Not predetermined from the start, but pivoting through loops
-
After feeling like peeking into the academic world through the paper log, I felt like the idea of finding everything by reading a lot of previous research and finding things that haven’t been done yet (around the time of submission)
- However, I also learned that it’s not necessarily the case
-
The importance of presentation
- Translating new concepts into tangible outcomes
- Explanatory text
- Graphs, etc.
The repetition of abstract concepts and testing
- Through back and forth, discussions around the timeline expanded based on the phenomena of user testing
The importance of non-quantitative experiences
-
The sense of excitement from the prototype initially created ultimately led to elastic synchronization
-
What I have grown from