You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: docs/content/Checklists/SRS-Checklist.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ date: "2024-09-16"
7
7
title: SRS and CA Checklist
8
8
---
9
9
10
-
This checklist is specific to the Smith et al template [@SmithAndLai2005; @SmithEtAl2007] for documenting requirements for scientific software, but many of the points can be abstracted and applied to other templates.
10
+
This checklist is specific to the Smith et al template [@SmithAndLai2005][@SmithEtAl2007] for documenting requirements for scientific software, but many of the points can be abstracted and applied to other templates.
11
11
12
12
- Follows writing checklist (full checklist provided in a separate document)
@@ -273,11 +273,9 @@ and often disguised these systmems under the term "artificial super intelligence
273
273
companies that build AI systems to amplify our abilities to create and improve efficiency for our work. Companies such
274
274
as [Runway](https://runwayml.com/), [Cohere](https://cohere.com/), etc belongs to this paradigm. ^intelligence
275
275
276
-
My interests lie firmly on the second group, where we build tools that amplifies our agency. `tinymorph` is the
277
-
manifestation of these beliefs.
276
+
Our interests lie firmly on the second group, where we build tools that amplifies our agency. `tinymorph` is the manifestation of these beliefs.
278
277
279
-
Additionally, during the journey of prototyping `tinymorph`, I hope to use it as a playground to delve into the field
280
-
of [[glosar#mechanistic interpretability|mech interp]], as a pure research interests.
278
+
Additionally, during the journey of prototyping `tinymorph`, we hope to use it as a playground to delve into the field of [[glosar#mechanistic interpretability]] as a pure research interests.
281
279
282
280
#### Attendance
283
281
@@ -301,8 +299,7 @@ all concerned parties.
301
299
302
300
What process will team members follow if they have an emergency and cannot attend a team meeting or complete their individual work promised for a team deliverable?
303
301
304
-
Please let everyone know through Teams, email Dr.Smith about this specific incident so that the others members can
305
-
cover the team deliverable.
302
+
Please let everyone know through Teams, email Dr.Smith about this specific incident so that the others members can cover the team deliverable.
306
303
307
304
#### Accountability and Teamwork
308
305
@@ -322,8 +319,7 @@ Adhering to [Code of Coduct](https://github.com/aarnphm/tinymorph/blob/main/.git
322
319
323
320
We encouraged everyone to be open to new ideas and collaborate on features work. We should use constructive critism with regards doing review work.
324
321
325
-
Should any conflict arise, please discuss your concern and display your reasoning with the whole team, asynchronously
326
-
or synchronously. At the end of the day, we are all humans 😀
322
+
Should any conflict arise, please discuss your concern and display your reasoning with the whole team, asynchronously or synchronously. At the end of the day, we are all humans 😀
Copy file name to clipboardexpand all lines: docs/content/ProblemStatementAndGoals/ProblemStatement.md
+2-1
Original file line number
Diff line number
Diff line change
@@ -5,6 +5,7 @@ tags:
5
5
author: aarnphm
6
6
date: "2024-09-16"
7
7
title: Problem Statement and Goals
8
+
titleTransclude: false
8
9
---
9
10
10
11
See also: [[Checklists/ProbState-Checklist|checklist]] and
@@ -20,7 +21,7 @@ In 1972 Alan Kay [@AlanKay1972, 11] conceptualised the Dynabook, a portable devi
20
21
users of all ages to explore and learn. More than just a portable computer, the Dynabook was envisioned as a dynamic, interactive medium for
21
22
learning, creation, and self-expression, that could adapt to users' increasing skills and need.
22
23
23
-
As we progress into the $21^{\text{st}}$ century, software has become comoditised, serving as the engine of transformations that transcend every corner of our life.
24
+
Fast forward to the $21^{\text{st}}$ century, software has become comoditised and transcend every aspect in our life.
24
25
Simultaneously, we've seen exponential growth in machine learning (ML) systems'[^1] capabilities, largely due to a general push of large language models (LLMs) into the mainstream.
25
26
As these systems exihibit emergent properties of [[DevelopmentPlan/DevelopmentPlan#^intelligence|intelligence]], how should we craft interfaces that amplify
26
27
users' [[glossary#agency|agency]] and encourage a sense of personalisation through interactions, rather than providing a mere tool for automation?
0 commit comments