The Singapore Management University Business Intelligence and Analytics Club approached me with a request to share about data analytics with undergraduates. These undergraduates–which were mostly from a non-technical background–had the following questions in mind:
- What is data analytics?
- Why data analytics?
- How to pick up data analytics? (covered in a previous blog post)
- How did I enter the data analytics field?
Here’s what I shared with them. Any feedback and suggestions for improvement welcome =)
Recently, I completed the Georgia Tech OMSCS Software Development Process (SDP6300) course over the summer. It was very enriching—I learnt about proper software engineering practices and created apps in Java and Android. Here’s an overview of my experience, for those who are considering taking it.
Why did I take this course?
Since entering the data and technology industry a couple of years ago, I’ve always felt the need to improve my skills in software engineering. This is compounded by my lack of (i) a computer science degree (I studied psychology) and (ii) hardcore software industry experience.
Via online course and work experience (at IBM and Lazada), I picked up decent coding and engineering skills. While I’m able to build robust and maintainable data products in Python and Scala (Spark), I felt the need for a formal class on software engineering fundamentals so as to develop more sophisticated applications with greater efficiency. This includes learning about good architecture design, software development cycles, etc.
What did we build during the course?
For the summer 2017 run of SDP6300, the bulk of the work revolved around two main projects and multiple smaller individual assignments:
- Team project: Teams of 3 – 4 built an Android App where users could login and solve cryptogram puzzles. Solutions and scores for each puzzle were to be persisted locally as well as updated on an external web service. Users can then view a global leaderboard with top player scores. It also required functionality for administrative users to add new players and cryptograms. This had to be built over 3 weeks—many teams found this barely enough.
Player features and screens
Admin features and screens