Time flies and it has been a week already working at Aeste Works. In this blog, I would mainly talk about the tasks given to me, what I have learnt through working on those tasks and also what I have learnt from Dr Shawn.
Since this is my first post here, so I would like to give some first impressions of Aeste Works. After spending a week here, I found that the place is very conducive for work. Even though the size of the office is not that big, but it has everything it needs to keep the works going. Besides, colleagues are also very friendly and helpful.
Now I will talk about the tasks given to me in my first week. Basically, there are two major tasks assigned to me. My first task was to learn about git and understand how Aeste uses git in house so that we can manage all the projects in a systematic manner. On the other hand, the second task given to me was to help my colleague, Nadia to test the “Competition Marks System”.
So let me further explain on what I have learnt throughout the week working on those tasks. It was not the first time I hear about git, but it definitely was my first time using git while working at Aeste. I was really amazed by what git can do and wonder why I have never thought of learning this super useful tool. So, what is git? Basically, git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. For example, let’s say a team of 4 members have a project which involves a lot of coding work. Those work are divided equally between them and it would be very difficult for them to keep track of what other members have done if they do not use any of those version control systems. It would be a mess at the end when they are trying to combine everything manually. With git, all of them are able to work on their parts at the same time and they are able to merge all of their works easily. In addition, git also provides a very clear history of what everyone has done using the commit function, and that is really helpful for developers. With this knowledge, I believe that I will be able to work on my future project in a more systematic manner.
On the other hand, for my second task working on the competition marks system, I have to make a laptop acting as a server which will allow tablets to pull information from the server through WiFi connection. The main challenge for this task is that I have to make sure everything works well without internet connection. This is because there might be no internet connection during the competition day therefore I have to download every files manually and save it into the laptop so that it does not pull anything from the internet. Things are almost done and Dr Shawn wanted me to give everything a test run just to make sure everything works fine.
Finally, I would like to talk about some of the things I have learnt from Dr Shawn during my first week working as an intern at his company. There are quite a lot of them but I would just state a few of them here. I was really impressed by one of the quote from Dr Shawn, “Working correctly and working not wrong are two different things”. This is very important especially for engineers, we must make sure we are working correctly but not working “not wrong”. Besides, I have also learnt from Dr Shawn that we must always have a plan B for everything we do, do not settle when you are done, keep in mind that everything might go wrong at any point, so it would be really helpful to always have a plan B. Lastly, Dr Shawn had also shared with us that as an engineer, we must know in detail on what we are working on, so that with those boundary conditions in mind we can do anything within the boundary conditions but not over it.
That’s all for now and I could not wait to learn more while working here.