-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathcourses_taken.html
More file actions
236 lines (201 loc) · 15.9 KB
/
Copy pathcourses_taken.html
File metadata and controls
236 lines (201 loc) · 15.9 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
<!--
IMPORTANT!
Keep this file unchanged to use as a template for all future project pages.
For every new project you add to your portfolio, make a copy of this file in the
'project-pages' folder with a name related to the project.
-->
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<link rel="icon" href="../assets/images/3939.png" />
<title>dbunarto's website</title>
<meta name="description" content="A compilation/blog of my work.">
<meta name="viewport" content="width=device-width, initial-scale=1" />
<link rel="stylesheet" href="../css/layout.css">
<link rel="stylesheet" href="../css/typography.css">
<link rel="stylesheet" href="../css/utilities.css">
<script defer src="../js/script.js"></script>
</head>
<body>
<!-- NAVBAR -->
<div class="navbar">
<a class="nav-title-link" href="./">
<!--
TODO - Change the "Portfolio Title" to whatever you want displayed in the top left
(this should be the same across all pages)
-->
<span class="nav-title">dbunarto - au23 edition</span>
<!--
TODO - Change the email after 'mailto:' to your email address for contact
(this should be the same across all pages)
-->
<a class="button" href="mailto:dbunarto@cs.washington.edu">
<span class="button-text">Contact Me</span>
</a>
</a>
</div>
<!-- MAIN PAGE CONTENT -->
<div id="main-content">
<!-- PROJECT HEADER -->
<div id="project-header">
<!--
TODO
- Change the 'main-title' text to the name of your project
- Change the 'body-text' text to a short and sweet description of your project (maybe the same as the one on the project card)
- Change "desktop.jpeg" to the image filename you uploaded in the assets/images folder.
-->
<div class="main-title">Courses Taken</div>
<div class="body-text">Below is a list of the course I have taken and my thoughts on them. This is intended more of a what to expect rather than a definitive guide of what to take. If you have any questions feel free to contact me!</div>
<div class="centered-image">
<img width = 400 height = 550 src="../assets/images/efrain_car.jpg" alt = "Me and two other friends changing a flat tire.">
</div>
<a class="no-underline" href = "https://www.youtube.com/watch?v=0KDMdYww4VE" target = "_blank">
<span class="image-caption">A great example of why you should do more than just CSE courses with your time; it took 3 CSE majors and a youtube video to change a flat tire!</span>
</a>
</div>
<!-- PROJECT DETAILS -->
<!--
TODO
- Change the 'subheader-text' to whatever header you want for project details
- Add paragraphs using the <div class="body-text"></div> elements in the "project-details-content"
-->
<div id="project-details">
<div class="subheader-text">CSE 484/584: Computer Security, Au23</div>
<div class="project-details-content">
<div class="body-text">Currently taking this course so will update after it is done!</div>
<div class="body-text">Weekly time commitment: ???</div>
</div>
</div>
<div id="project-details">
<div class="subheader-text">CSE 333: Systems Programming, Su23</div>
<div class="project-details-content">
<div class="body-text">Learned about explicit memory management, implementing various data structures in C and C++, and brief client + server side networking.</div>
<div class="body-text">The entire course consisted of 12 exercises which had you applying concepts from lecture to the exercises and a quarter-long project for a search engine. Considered tradeoffs such as disk vs memory for storing index files and patching security vulnerabilities such as a directory attack and scripting within the search engine.
Weekly time commitment: 12 to 20 hours, depending on solo vs. partner and ability to trace memory leaks.</div>
</div>
</div>
<div id="project-details">
<div class="subheader-text">CSEM 544: Database Internals, Sp23</div>
<div class="project-details-content">
<div class="body-text">Learned about the functionality of DBMS internals and design considerations. The entire quarter is spent building SimpleDB, a simple DBMS that uses bare minimum policies such as NO-FORCE/STEAL and page-locking granularity. Implemented a buffer pool, lock manager, log manager, query parser, and operators for queries. 544 is the master's version of 444 but is co-jointly offered. The master's version has students read five important database papers throughout the quarter and write a one to two page paper responding to questions regarding the research papers read. These papers ranged from the various data model proposals, DBMS architecture, query optimization, and parallel DBMSs vs MapReduce. </div>
<div class="body-text">Coursework was alternating between a worksheet or lab every week. The labs were done in partners so this made the course possible to balance with other difficult courses. Weekly time commitment was between 3 to 8 hours.</div>
</div>
</div>
<div id="project-details">
<div class="subheader-text">CSE 446: Machine Learning, Sp23</div>
<div class="project-details-content">
<div class="body-text">Learned about various methods to design models that learn from data and improve as they continue to see more data. Course covered a wide variety of topics but here is a list of some: norms, least squares, ridge regression, Lasso, gradient descent (and stochastic gradient descent), SVMs, kernels, neural networks, nearest neighbors, trees, CIFAR-10 and MNIST using CNNs, random forests, k-means, PCA, bootstrapping, and CNNs. This course was very theory driven, and thus math heavy. Requires lots of linear algebra review to help keep up with the content.</div>
<div class="body-text">The coursework was five total psets but each one would take between twenty-five to thirty hours to complete. Be prepared to devote lots of time towards this course! Weekly time commitment was between 10 to 15 hours.</div>
</div>
</div>
<div id="project-details">
<div class="subheader-text">CSE 421: Introduction to Algorithms, Wi23</div>
<div class="project-details-content">
<div class="body-text">A proof-heavy course that focused on types of problems and techniques for how to design efficient algorithms to solve these problems. Problem types ranged from stable matching, greedy, minimum spanning trees, dynamic programming (1D and 2D), flow, reductions, and linear programs. </div>
<div class="body-text">The coursework consisted of a weekly pset that would have between four to six problems. Time commitment was between 15 to 25 hours depending on the difficulty and time spent writing the proofs.</div>
</div>
</div>
<div id="project-details">
<div class="subheader-text">CSE 442: Data Visualization, Wi23</div>
<div class="project-details-content">
<div class="body-text">Introduced theory and techniques for how to design effective visualizations of data based on principles of graphic designed. Used various software such as D3.js, Vega-Lite, Observable notebooks, and Tableau. Learned about deceptive and interactive visualization. As the final project, you get to work in a group to create an interactive visualization that teaches about a concept using concepts such as storytelling, color, animation, narratives, networks, and maps.</div>
<div class="body-text">The coursework in the first half was individual assignments but would be quick so about 3 to 5 hours each week (including the required lecture participation). The second half of the quarter you would work in groups to work on interactive visualization and a final project that teaches something using interactive visualization which was a time commitment between 10 to 15 hours per week.</div>
</div>
</div>
<div id="project-details">
<div class="subheader-text">CSE 344: Introduction to Data Management, Au22</div>
<div class="project-details-content">
<div class="body-text">Introduced database management systems and how to write applications that used these database systems. Primary focus was how to write queries and how to query effectively and correctly. The second half of the quarter was spent working on the Flights booking application which used Java and Azure as a DBMS. Other topics included relational algebra, indexes, various data models (relation, semi-structured, key-value), and BCNF.</div>
<div class="body-text">The coursework in the first half were weekly gradescope assignments where you would write queries and report the output. The second half was ER-diagrams and working on Flights. Weekly time commitment was between 3 to 8 hours since I already had DBMS experience from my summer internship.</div>
</div>
</div>
<div id="project-details">
<div class="subheader-text">CSE 331: Software Design and Implementation, Au22</div>
<div class="project-details-content">
<div class="body-text">Learned concepts and techniques for how to design, test, and construct reliable and maintainable software in Java. Learned about forward and backwards reasoning given code snippets to practice code correctness and loop invariants. Quarter was devoted to building campus maps, a webapp that used React, Spark, and Java to help find the shortest location between two buildings at UW campus.</div>
<div class="body-text">The coursework consisted of weekly worksheets and/or coding assignments. Weekly time commitment varied but already having experience was 3 to 8 hours. If I did not have prior experience with React it would be 10 to 15 hours as an estimate.</div>
</div>
</div>
<div id="project-details">
<div class="subheader-text">CSE 440: Introduction to HCI, Sp22</div>
<div class="project-details-content">
<div class="body-text">Introduction to the iterative design process in HCI (paper prototyping, design methods, design diamond, storyboarding, heuristics, patterns, inspection, critique). Also covered HCI theory and techniques such as Fitts' law, Sapir-Whorf, affordances, metaphors, and history of design.</div>
<div class="body-text">The coursework consisted of biweekly checkpoints/indicators of progress that were to be completed as a group. Typically having one person be the "PM"/leader would make this easier to allocate the workload and keep track of progress. Since I took on this role, the weekly time commitment for me was 3 to 5 hours.</div>
</div>
</div>
<div id="project-details">
<div class="subheader-text">CSE 332: Data Structures and Parallelism, Wi22</div>
<div class="project-details-content">
<div class="body-text">Focused and implemented abstract data types and structures such as dictionaries, priority queues, graphs, chaining hash tables, and balancing trees. Covered graph theory concepts such as minimum spanning trees, shortest path, topological sort, and searching. Briefly went into concurrency and parallelism specifically with forking. </div>
<div class="body-text">The coursework consisted of weekly exercises and labs (that would be done with a partner). The exercises would usually be 1-3 hours but the labs would range between 10 to 18 hours per week depending on how effective you could debug.</div>
</div>
</div>
<div id="project-details">
<div class="subheader-text">CSE 312: Foundations of Computing II, Wi22</div>
<div class="project-details-content">
<div class="body-text">Introduction to probability and how to model probability using NumPy. Covered counting, combinations, permutations, discrete and continuous distributions, MLE, MAP, MOM, bootstrapping, and bandits.</div>
<div class="body-text">The coursework consisted of a pset every other week which could be completed with a partner. (This may vary from other offerings as Alex Tsun was a guest lecturer). Weekly time commitment ranged from 10 to 15 hours where majority of the hours came from the later psets.</div>
</div>
</div>
<div id="project-details">
<div class="subheader-text">CSE 351: The Hardware/Software Interface, Au21</div>
<div class="project-details-content">
<div class="body-text">Introduction to C, various number representation schemes, assembly, memory management, and how high-level machine architecture is implemented.</div>
<div class="body-text">The coursework consisted of labs every other week (which could be done with a partner) and participation in lecture. Weekly time commitment ranged from 5 to 10 hours depending on how the lab was going.</div>
</div>
</div>
<div id="project-details">
<div class="subheader-text">CSE 311: Foundations of Computing I, Au21</div>
<div class="project-details-content">
<div class="body-text">Introduction to logic, set theory, finite state machines, and P vs NP. Also served as an introduction to proofs (similar to discrete math, math 300).</div>
<div class="body-text">The coursework consisted of weekly assignments of on average six to eight questions with writing proofs. Weekly time commitment ranged from 7 hours to 15 hours as this was my first time working with proofs.</div>
</div>
</div>
<!-- IMAGE GALLERY -->
<div id="project-gallery">
<!-- TODO - Change the 'subheader-text' to whatever you want the Gallery section header to say -->
<div class="subheader-text">These are random images that I just wanted to include</div>
<div class="project-gallery-content">
<!--
TODO
This is where the images in the gallery live. Here's a simple gallery image for you to copy:
Full Width Image:
<div class="gallery-image-container">
<img src="../assets/images/IMAGE_NAME" class="gallery-image">
<span class="image-caption">IMAGE_CAPTION</span>
</div>
Half Width Image:
<div class="gallery-image-container half-width">
<img src="../assets/images/IMAGE_NAME" class="gallery-image">
<span class="image-caption">IMAGE_CAPTION</span>
</div>
- To add an image to the this area, copy one of the above, paste it below this comment, and change the following:
- IMAGE_NAME: the name of the image file in assets/images
- IMAGE_CAPTION: to the caption of the image
-->
<div class="gallery-image-container half-width">
<img src="../assets/images/trolley.png" class="gallery-image">
<span class="image-caption">The trolley problem but wondering if he is being optimal...</span>
</div>
<div class="gallery-image-container half-width">
<img src="../assets/images/pain.jpg" class="gallery-image">
<span class="image-caption">This was how I felt during CSE 446 and CSE 421.</span>
</div>
</div>
</div>
</div>
<!-- FOOTER -->
<div id="footer">
<a class="icon-link" target="_blank" href="https://www.linkedin.com/in/dylan-bunarto-b4b9851ab">
<image src="./assets/icons/linkedin.svg" class="footer-icon"/>
</a>
<a class="icon-link" target="_blank" href="https://twitter.com/dylanbunarto">
<image src="./assets/icons/twitter.svg" class="footer-icon"/>
</a>
<a class="icon-link" href="mailto:dbunarto@cs.washington.edu">
<image src="./assets/icons/mail.svg" class="footer-icon"/>
</a>
</div>
</body>
</html>