I personally try to dismiss sentiments that regard a particular year as an “entity” for which to either be frowned upon or celebrated. That is to say, I find it distasteful to say things like:
“2020, you suck!”
“I can’t wait for this to year to end!”
On the surface the next day is another day. The world didn’t suddenly change because of that. All life’s issues don’t suddenly disappear. If you wait for an arbitrary day to start to take a meaningful action in your life then you’ve simply procrastinated for the sake of a sentimental event that bears to practical significance.
Carpe Diem - Seize the day
I blogged a couple weeks ago about looking forward to the immediate future. A lot of things occurred in 2020 to really shake me emotionally, but the benefit of those events was the fire and motivation I found as a result of that impact. I defined an immediate action plan from then on into 2021, because I wasn’t going to pretend like December 21, 2020 wasn’t the same opportunity for a new day like January 01, 2021 was, and I took that action immediatlye because I know the world on the surface which motivated me to do so wasn’t going to change in ten days. That mentality for me is, quite frankly, a waste of time.
In the time since that blog I’ve mostly completed one of my stated goals which is to complete the migration of Hobby Collection Django to native AWS. At this point is pretty much ready to go:
Hobby Collection Django built on Django V3 and running on native AWS infrastructure
There are still some polishing touches I’d like to make, mostly with regards to responsiveness of the sample image carousel on the homepage but nothing worth holding back public exposure for. As you can see I’ve made a new and simple logo representing my identity and will be re-introducing my audio collection. I’m also pleased that it’ll be more useful for public perusal as I’ve reintroduced multidimensional filtering in each section. There is however one last significant task I need to complete before opening it up to the public (also one of the motivations for me moving off the Heroku stack) which is securing the site via TLS. It has stood out to me like a sore thumb for some time as the only insecure subdomain I currently expose and has bothered me every time I’ve taken an administrative action on the stack. As is best practice with the web going forward and a personal prerequisite for the REST API I’m planning to build in the future I will be certifying the domain prior to opening it up.
That’s really the last task. For all intents in purposes the site is ready to launch and is my daily driver now. Looking forward to showcasing it soon.