Start of 4/19

notes.org

@@ -1,108 +1,13 @@
 * Tasks
 
-** DONE Interview with Roopa Bose
+** TODO Figure out what users are affected by =#_incident-1564=
-  - 7 Years Experience
+  [2023-04-19 Wed]
-  - Go GRPC
+  - 98b54728-ca71-47f8-8a86-5326dfa94b68
-  - Docker
+  - 969eb393-ddfe-4db8-83e5-a4f6a4d1cae8
-  - DB
+  - 96293db0-1756-4a2e-97dc-3ed8051c76c3
-  - JS
+  - f31ca1b8-35c9-43b1-8abd-205157da57ab
-*** DONE Roopa Interview
+  - cc817f6e-f56f-4cae-91f2-eb1a85049847
 
-  How did you reduce deplyoment time?
-  How did you optimize for dependency?
-  What wentinto reducing latency with API calls?
-
-
-  Just moved to canada
-
-  6 years java
-  2 yrs golang
-  transition from java to golang
-  tutorials
-  had to build a feature  - used this as practical experience
-
-
-  startup experience
-
-  Got into angular as part of startup
-
-  EC2 and S3
-
-  Interested in Backends'
-
-  Difference bw authentication
-  * are you  you
-  * do you have permissions
-
-  Describe the structure of a JWT
-  token expiration
-  session managments
-  user information is encrypted
-
-  container
-  envelopes environment
-  containers
-
-
-  prod issue was reported by customer
-  missed a test case?
-  did not have a proper testing tool?
-  testing strategy?
-  QA team and developer?
-
-  what langauges are you most comfortable with?
-  leet code done in java
-
-  returned cache result
-  rotate secrets
-   -- found out from logs
-
-  diagnosing the issues
-   service had exceeded timeout.
-
-
-  marques Q:
-*** DONE Give Feedback on Roopa
-
-Roopas didn't seem like the strongest candidate to me.
-
-During the short-form questions, she understood conceptually the JWT
-and authentication vs authorization. She hasn't worked with K8s. With
-a little guidance she did seem to understand what a container was. At
-first the explanation was a "virtualenv".
-
-My read on the answers were that the information she communicated was
-decent surface level knowledge but when drilling down a bit further,
-the understanding broke down quickly.
-
-With respect to the long-form questions, she did much better.  I liked
-her answers for how she had improved the microservices in her previous
-job. She had implemented a caching layer to keep data local within
-their services as opposed to always hitting Salesforce. I would say
-that her process for identitifying the issue was a bit lacking, but
-she did provide results, so it worked out. The strategy to diagnose
-the problem was more of seeing errors in logs and then looking at the
-fix, but given that they didn't have much in terms of o11y, I think
-that's the best she could have done.
-
-She hadn't really known what we did, and wasn't able to make it very
-far in guessing how provisioning would work. Given that she hasn't
-worked in the space, I would expect her to think about what could
-possibly go into this, but she didn't get far without Sarah leading
-her through it.
-
-Overall, I think that she's not fit for the senior position.
-
-
-
-
-
-
-
-
-
-
-** TODO Add logging to RAILS for affected 1564 users
 
 ** TODO Upgrade CRDB to 22.2.7
 ** TODO look at VMC-E SDDC
@@ -110,3 +15,31 @@ Overall, I think that she's not fit for the senior position.
 ** TODO Put together POC for micro-caching RAILS
 
 ** TODO Look at "compiling" krakend configs from OpenAPI
+
+** TODO Meeting with DevRel to talk about Provisioning Failures
+
+
+Chris:
+Cluster api - failed provision
+   it shows up with a 403 - moving the project to a new project
+   if the device is not ready handling
+
+
+   there was some effort in the pass
+   jordan
+
+   should clients be polling events
+
+   if it appears in my devices list
+
+
+
+   pxe boot can time out
+
+   Phoning home
+
+
+   wouldn't want to see it
+
+
+   check on rescue and reinstall operations