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: content/blog/entries/2024-07-12-automating-quantifying/contents.lr
+9-1
Original file line number
Diff line number
Diff line change
@@ -76,7 +76,7 @@ As I mentioned in the previous sections, starting to code the initial file was a
76
76
new technologies and libraries on-the-go. As a matter of fact, my struggles began when I couldn't even import the
77
77
shared module correctly. However, slowly but surely, I found that consistent research of available documentation as well
78
78
as constant insights from Timid Robot made it so that I finally understood everything that I was working with. There were
79
-
two specific things that helped me especially, and I would like to share them here incase it helps any software
79
+
a few specific things that helped me especially, and I would like to share them here incase it helps any software
80
80
developer reading this post:
81
81
82
82
1.**Reading Technical Whitepapers:** As I mentioned earlier, I studied a technical whitepaper by AWS to help me design my DFD.
@@ -91,6 +91,12 @@ was the closest thing to my own project that I could reference. Although not all
91
91
there were many aspects of the codebase I found very helpful to take inspiration from, especially when online research led to a
92
92
dead end.
93
93
94
+
3.**Writing Documentation for the Code:** As a part of this project, I assigned myself the task of developing a documentation for
95
+
the Automating Quantifying the Commons project (**[can be accessed here!][documentation]**). Heavily inspired by the "rubber duck debugging"
96
+
method, where explaining the code or problem step-by-step to someone or something will make the solution present itself, I decided to create documentation
97
+
for future developers to reference, in which I break down the code step-by-step to explain each module or function. I found that in
98
+
doing this, I was able to better understand my own code better.
99
+
94
100
As for the license data retrieval process using the Google Custom Search API Key,
95
101
I did have a little hesitation running everything for the first time.
96
102
Since I had never worked with confidential information or such large data inputs before,
0 commit comments