Support Culture Clap

Narrowing the Focus

My mind is forever overflowing with ideas, and connecting them to others ideas, which compel other ideas to present themselves, which ... you get the picture.

Focus can be difficult; sometimes.

Either way, I need as much help as I can get in this regard; and so narrowing down my own aspirations to as few paths as possible seems requisite to any success.

Though I've finally whittled down each aspect to a properly manageable task with it's associated platform in preparation for a longer haul than just a few weeks or months.

Let's start from the top.

# The Full-Stack

Technically speaking, I started as a full-stack developer using [Django] & PostgreSQL. This is my bread and butter; and has been my preference from the start.

Django, because it is built using Python; a language with a broad array of libraries providing immediate aspects to highly technical, and scientific, operations.

My most recent academic training was in the field of Economics & Statistics; while my primary personal project is well complimented by knowledge of these realms.

Python allowed me obtain the data I sought thru web-scraping.

Django enabled to easily store manage and access this data without needing to change computer languages.

And PostgreSQL stored this data using a reputable, extensible and open-source data management system.

Albeit, Postgres is a relational database management system (RDMS); and the NoSQL trend seems to be all the rage. Postgres provides mechanisms to assauge these concerns for those seeking more fungability in their storage structures. Sure, not every feature is reflective of all of NoSQL's abilities, though the project continues to evolve, and pre-dates the NoSQL movement by quite a few years.

So I feel relatively comfortable focusing my efforts on growing with this tech, rather than attempting to perfect my awareness of others.

# The Client-side

While Django is capable of displaying data quite nicely, JavaScript as successfully crowded out most all of the competition when it comes to User Interfaces.

And with regard to my projects, it is a necessary skill to have in order to be a fully functional full-stack developer.

# React vs Vue vs Angular

First off, Angular isn't an option because I'm not trying to import everything, including the kitchen sink, just to make eggs and potatoes in the morning.

Both React and Vue have similar offerings though.

And while React does have considerable mindshare within the tech world, it is maintained by a organization from which I would prefer to keep a distance.

You're right, this is a personal decision based on a biased sense of ethics and morality!

And others may say that such stubborn is only hurting myself, or is it?

Given my experiences as an adoptee, arguably unsuccessfully infected with Stockholm syndrome, I have a fierceness about protecting my independence.

While Vue is the product of a former-Googler; it remains unshackled to any large entity. Furthermore, the originator source their original financial funding through Patreon of all places!

I really wanted to use Vue; I'd already decided it was my client-side framework of choice. Now the task was to use the platform to complete my own digital presence.

# Flat Files & Fortune

For those unaware, classically content management systems (CMS's) have relied on databases to store their information.

Though recently a bevy of flat-file CMS's have hit the market, most notably Jekyll, Gatsby, Grav & more.

These CMS's don't need to make database calls, which are expensive, both in time and processing power. Rather they are entirely built using simple text files. Dramatically decreasing their load time!

But I really really didn't want to have to mess with React (Gatsby), or learn a new language (Jekyll), nor work with PHP (Grav).

Remember the aim was to focus my efforts ~ not expand them!

Enter the beloved efforts of the VuePress team!!

It's pretty, simple; and as I learn more about Vue, I will be able to further customize this here blog!