Table of Contents
Author and Links
Resurgens - the Latin root of the French loanword Resurgence. Meaning to be born again, return or rebound. Included here as a reference to my resurgence from illness and a path that had made me unhappy to finding a career path to a field I have long loved as a hobby and have focused my entire being into the pursuit of, despite the hurdles pursuing such that I have found obstructing my path
This README is a markdown file that accompanies my personal website, which functions as both a portfolio of my development skills in HTML5/CSS3 as well as a repository of my work thus far in the other direction fate has shown me I have some talent in, digital art that originates as photography of buildings and landscapes I am prone to staring at awe in. While separated from the forthcoming site I shall use as a means of advertising my services as a computer repair technican (my current method of obtaining sustenance), I will link the two when both are fully operational. On the site, you will find links to the many social media profiles I maintain through use of IFTTT to cross post to them from my instagram account as well as the professional profiles on Linkedin and Dribbble that advertise me as a potential contractor or a
The Resurgens site is part of a larger project that informs the style of all of my personal sites and blends the concepts of style and functionality into a distinct UI/UX paradigm I call the Electric Tantra. This paradigm is so titled as it creates the perfect union between both functionality and aesthetics by creating a pleasing to behold and easy to use whole. The colors and design cues are taken from the movement to using darkened interfaces, which I find help considering I work pretty much any time I am awake and that includes late into the early morning when a bright screen would be jarring to stare at and would damage the eyes more. This is coupled with a desire not to leave out colors which flavor the interface and give it the pop that attracts the user.
Each page has content that break down into either some standard for portfolio sights such as skills or the (as of this writing unreleased) repository gallery. I have further included most (but not all) of my pieces of visual art, generally pieces I photographed or borrowed from clipart sources and applied various filters to so that I may draw from it the emotions I either had when editing it or taking it all of which are refected in the titles. The front page should, so long as my constant tinkering hasn't ruined it, be several pictures of myself that are either edited or not but which are accurate in their capture of my person in rendering my features and mannerisms. The splash page is to be a landing page, not a full demonstration of functionality but introduces the grid format I have laid forth as the primary manner I have displayed content on these sights and sufficiently modularized to mean I need not edit much as I continue to port them into React.js modules.
One point of particular note is the sidebar, which I have spent much time perfecting and repositioning, the reason being to maximize its presence as it is a series of links to the various social media sites that I have profiles on to demonstrate candor in regardless to thhe person I am in real life as well as to give the intrepid hiring manager examples of the multitude of talents I offerand skills that I have been cultuivating for far longer than my resume seems to suggest (despite no bites thus far). For anyoen interested in my graphic design abilities should note my Dribbble account and my (soon to be added) 500px account which despite being fairly new is rabidly popular.
As discussed above in the focus section, the use of languages in the creation of this site was deliberately constrained as much as possible to demonstrate succintly an aptitude that the author has with the most basic of web development's languages, HTML and CSS. Also discussed above are the reasons for that showcasing those skills and the future of the Resurgens site in the near future if my ambitions are not frustrated by the unfolding of daily events. Though I do not plan on rewriting this Readme later and as such it maybe of utility to point out that the README you have before you is associated with the first of several such README files that are going to accompany various incarnations of my portfolio site. The repo will stand as a testiment to my efforts early in my refocused efforts to move into my passion as a career, that being development. Still I will record, as will be my habit, a bit about each language that is employed and why it was employed to acheive the sight, both for technical and design purposes. Unlike other sections you will find, this section more spartan than I usually tend.
Author and Links
Source Code Written By:
Thomas Leon Highbaugh
TLH, or Thomas Leon Highbaugh, is a relatively recent convert to the practive of development both as a hobby and a career. While spending 2 years now accumulating skills, he has moved rapidly into web development in the full stack sense since he took a bootcamp in the beginning of the year (2018) on Front End Development in which he was the only Linux user and/or Unix competent. Having a passion for Linux operating systems and not in the revert since (hence no GNU/Linux designation) he has been accumulating skills that require both and evidently place his ambitions in acquiring a DevOps role as a long term goal. Currently he is working with React.JS and attempting to learn Ansible provisioning by provisioning two old desktops he acquired earning money by his typical method, computer repair for small businesses and individuals at a reasonable rate.
Having an unrelated degree, and years of experience he often finds a hinderance to even acknowledge when pursuing a development role, he continues to take classes at local community colleges so that he may deepen his knowledge, often surpassing developers he knows due to that, as well as ddemonstrate his proficiency in transcripts if source code and jargon dense cover letters are not so convincing to the hiring managers typical of larger tech firms. Nonetheless, he is not a self-described "lazy coder" as he finds suggestions that there is some virtue in such is an illusion of those who do not work wit the lazy. He instead describes himself as effciency minded and looks for shortcuts not because he is too lazy to be bothered by the