It has been nearly a year since I last opened Xcode, Apple’s development environment for iOS and watchOS. One day, when I was rushing to an early morning class, I subconsciously patted my left pocket and realized that I had left my phone in my dorm room. I also took notice that I was wearing my Apple Watch, the device that I frequently use to ping my iPhone when I misplace it. While the watch does help me find my phone by allowing me to play a ringing sound on my phone, it doesn’t do so proactively. Wouldn’t it be nice to have an app on my Apple Watch that notifies me when the iPhone is out of range, I thought.
In my previous blog post, I briefly mentioned the differences between a Virtual Private Server (VPS) and Shared Web Hosting service and cross compared the three major VPS providers. In this blog post, I will continue my tutorial by detailing the process of setting up a Droplet (DigitalOcean’s way of calling their VPS instances) with DigitalOcean.
A friend of mine and a regular reader of this blog recently requested that I write a tutorial on setting up a web server. To honor his request, I will devote this week’s blog post to the subject of web hosting. I will not, however, cover the programming aspect of web development as I assume that the readers of this tutorial already know how to write a website in HTML, CSS, PHP, Java, etc. I will also not be writing about the all-in-one website builders such as Squarespace and Wix for the same reason.
Maybe it is too early for me to make a dinner dance proposal, but I did receive an invitation from T. Carrie Brodsky, the senior class advisor, who asked me to create a ticketing system for the 2017 Dinner Dance. In this blog post, I will explain what the ticketing system was like in 2016 and briefly introduce the new ticketing system I am currently developing.
Polaris began its beta testing on February 22, 2017. Over the past two weeks, over 250 students, duty crew members, duty administrators (DA), and weekend coordinators have started using Polaris. From such as diverse group of users, I have received much valuable feedback and made adjustments to Polaris accordingly. In this week’s blog post, I will detail some of the user responses and how they are addressed.
A lot of people have asked me about Polaris since its launch. The question is usually brought up during brief conversations:
A person would ask, “Hey Kevin, how’s Polaris going?”
My reply is always very terse: “Pretty well!”
“Good! When is it going to be available?”
Over the past week, I have been working very closely with the technology office to deploy Polaris. To my surprise, my first week’s work has turned out to be very challenging. I have encountered numerous problems with both the server and Polaris itself. In this blog post, I will be discussing some of these problems as well as the lessons I learned from them.
WEST CHESTER, Pennsylvania — January 20, 2017 — The Polaris Team today announced Polaris, a revolutionary departure management system designed specifically for the Weekend Program at Westtown School. Polaris replaces the current SignUpGenius®, an event organizer, and offers a responsive design, Google® integration, Alchemy℠, manageability optimizations, data analytics along with many other features.
Instead of writing a routine update, I’d like to dedicate this blog to a reflection on the work I have done for the past eight weeks. I will first discuss what I have learned from the project. Then, I will identify, if not address, the problems I have encountered over the course of this quarter. Finally, I will plan for further projects and establish a set of more attainable goals.
Aside from the unique features Snapchat originally offers, its routine updates and monetization strategies have also contributed to its success.