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
|
\font\twelverm=ptmr7t at 12pt
\twelverm
\baselineskip=24pt
\nopagenumbers
\headline={\hfil Rohrer \number\pageno}
{\obeylines
Holden Rohrer
Ms Rosner
Hire Me
21 Apr 2021}
% If you had to assign yourself a grade for your performance so far what
% letter grade would you assign yourself? Why?
%
% Use the questions below to help explain the grade you would give
% yourself:
%
% What is going well with your internship? What, if any, problems are
% you having?
%
% How are you getting a good balance of the ``best and the worst'' that
% this career field has to offer? Give some examples.
%
% How have your responsibilities changed since you began your
% internship?
%
% How do you feel you are doing regarding punctuality and attendance?
%
% Give at least one example of a time you have been proactive at your
% internship site?
%
% Give at least one example of another time you have stepped outside of
% your comfort zone at your internship site?
%
% Give at least one example of another time you feel like you went above
% and beyond what was asked of you at your Internship site?
\centerline{Journal Prompt \#4: Self-Assessment}
Based on my performance at the internship site, I would give myself an
A.
During my internship, I've done a lot of work on features and bugs that
actually affect users of the WellEntry project.
I've also learned a lot of domain-specific tech and more generalizeable
best practices while working with developers who are much more
experienced than me.
I've gotten a lot out of the internship, in terms of transferable skills
(learning Vue, Actionhero, some ES2015 JavaScript standards, SQL,
and others) and softer skills like interviewing, scheduling, and
collaborating on pair programming.
During my internship, the road has not been entirely smooth.
No major problems have come up, but there have been some challenges
which are natural, given the territory.
One of my changes, which was intended to, over all instances, sort the
list of roles associated with a user by which role was primary, so that
the first role was always the primary role.
However, the way that I wrote the line of code resulted in every user
being associated with every role, meaning that all existing reminders
(which are sent to remind users to fill out a survey of COVID symptoms)
were sent to all existing users.
These were sent by email, so several thousand emails were sent,
overflowing the email limit that was designated for the project.
This was quickly reversed, but it still caused error.
Throughout my internship, I've experienced much of the technical side of
a programming project and less of the logistical or customer-facing
components.
This has given me a fairly comprehensive look at the good parts, at
least in my opinion, of software development: I've gotten to work on
solving interesting problems in a well-developed codebase, and the
people I've worked with have been absolutely wonderful and very helpful
when I get blocked, like when working with vue-test-utils (the default
testing library for the web front end) and all the trouble it gives
because proper mocking isn't default in vue-test-utils, which would
probably count as the bad parts.
The work that I've been doing is mostly asynchronous, so punctuality has
not been a big concern.
However, the one or two meetings per week that I've had I've shown up on
time or early to every time.
This has worked out well because most of the work doesn't require
continuous or lengthy communication, but the problems that need
collaboration are handled within about a week's time.
The collaboration with other developers (mainly Chelsea, my team lead,
now, as the other developers rolled off the project around March or
April) has increased as I've started working on more integrated projects
across the stack.
At the beginning, I worked mostly with Ashvin (who is also interning at
7Factor) on making smaller UI changes to the portal to fix bugs or add
small features like linking from a user's name to their details page
(with only their screenings or vaccinations).
Then, throughout the internship, the features or bugs I was looking at
required more significant attention, like a bug where the API was
returning an incomplete list of organizations for superusers, so when
they tried to switch ``accounts,'' some functionality was pretty
severely broken.
Also, as I've started working on adding features/CRUD
(Create-read-update-delete) views, I've needed to work on the API to
make sure authentications are properly set up (i.e. a non-admin user can
get access to their own list of vaccinations) and that the data is being
returned in a usable format, with all necessary information.
I've also, to a limited extent, worked on the database directly, writing
SQL commands to add or syndicate data so that the database calls within
the API are simpler to understand.
\iffalse
Solid A.
What is going well with your internship?
- I've done a lot of work on features and bugs that affect users on the
WellEntry project since I started.
- Written (and removed) probably a few thousand lines of code.
What, if any, problems are you having?
- Practically none, but some issues have come up which are natural in
the territory
- Broke prod! This sounds like a bad thing, but it's actually a
milestone. Through a series of misunderstandings and misadventures
through the documentation of the database ORM, about six thousand
extra reminders got sent to WellEntry clients, and more than
twenty per each user.
\fi
\bye
|
