I never knew that waking up at 8 o'clock and leave 30 minutes later and come back to 5:30ish would be so tiring since then I have to eat a quick dinner, shower, and do a whole bunch of chores then sleep. Not the best schedule, but now I learned that you may wanna manage your time not in blocks per day. Instead of doing it like this, you have days of rest (despite not even happening during the internship) where you can have a full(ish) day of freetime.
While I'm working for roughly 9 hours, you get quite a bit of time learning the ropes. I got a nice refresher on how GitHub works -- it supports not just a group, but it can come in handy for yourself to understand what updates you made and which created some serious errors.
It's worth mentioning the work itself: It's very independant. This internship currently just feels like an English research paper as you have to go look up your topic and engage into doing your work. Kevin, himself, doesn't have a large knowledge about this information... so tests and research is key.
What I've learned within these 3 days (besides the mechanics of work) is how sensors and servos work and programming in an "invisible" environment where you have to guess and check your errors. Some things I didn't know is that you can (rather than plugging in directly) plug in different sensors in the same slot and they'll recieve all the actions. I also understand how it feels to be limited in your own code because of how much your machine can compute and handle.
Hopefully next time I can actually stay awake to write my next blog post! In fact, this first report is written during the time I should be working because of how everything laid out. Next time, you'll get a shorter post on what I've learned. Can't guarantee you that, tho ^^'.
EDIT: I should really talk about the actually sensors next time. It'd be nice to be talking about me sitting on a chair for 20 minutes figuring out the problem.
Wednesday, July 1, 2015
Subscribe to:
Comments (Atom)