We were a team of 5 students from Florida Interactive Entertainment Academy (FIEA) who worked on developing a clone of an existing game on the custom game engine that each of us made during the semester.

This was a 4 weeklong project, in each week there was a milestone to meet.

1. Pre-Production

2. Production 1

3. Production 2

4. Final

I learnt a great deal about the key proponents that constituents of a game engine, during the journey. I would encourage to check this out, where I outline in detail the key pieces of the engine.

I took the responsibility of developing a Prefab service for our game as the team concurred that in order to improve the process of making the game by adding content, having the ability to create and use prefabs would greatly enhance the efficiency and make us less prone to errors.

I hope I’m not underselling it when I say software engineers carry a huge responsibility toward humanity. As our interaction with the world increasingly happens through software, this responsibility grows even larger. Just like civil engineers are entrusted with building safe and durable bridges, software engineers have a similar obligation to create reliable and robust systems.

You don’t want your software to glitch when buying or selling stock options or when trying to book an Uber with only 1% battery left on your phone. Poorly written code doesn’t just lead to confusion or frustration for end users — it can create a domino effect. Even if your code is technically correct, if it’s poorly engineered, it could waste hours of development time and cause unnecessary stress for other engineers. Those who work on top of your code might struggle to iterate, integrate new features, or connect additional modules, resulting in time lost that could have been better spent on productive tasks.

In the world of software development, products typically adopt one of two architectural approaches: monolithic or microservices/distributed architecture. These days, most teams seem inclined toward microservices, while those sticking to monolithic architectures often do so due to constraints like limited resources or time.

However, after thoroughly studying system design, I realized that the decision between the two architectures should be taken with much more intention and consideration of business constraints.

I made this project in 3 weeks as part of my assembly course at Florida Interactive Entertainment Academy. The project was implemented on Eas68K, which is a simulator for 68000 made for educational purposes. I am grateful to Jeremy Paulding for mentoring me and teaching the core concepts of assembly programming.

Dance to the Vinyl is an interactive game made on Motorola 68000 microprocessor. The context of the game is that you play Michael Jackson; vinyl records fall from the top, some of which are genuine records while others are broken ones. Each time MJ catches a genuine record, he will sing one of his popular/my favorite songs, and he'll also dance to the beats. You are responsible for controlling MJ, i.e., making him dodge the broken records and catch the genuine ones, all while the counter is going on, by the end of which you must collect 10 of MJ's songs. You have 60 seconds to collect 10 songs and make sure to dance sufficiently so that you entertain the crowd with MJ's charismatic dance and singing!