tristan/journal
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Added a few new details in me.md

Browse Source
This commit is contained in:
Tristan Ancelet 2023-11-10 21:35:10 -06:00
parent 533895fcfa
commit 4d770a10c6
1 changed files with 10 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
Me/me.md
View File

@ -2,3 +2,13 @@
## Who Am I?
I am Tristan Ancelet, a Unix & Linux Systems Engineer working for an ISP (Fastwyre Broadband).
## What do I do?
As state above, I work primarily in the engineering field. By that I mean I'm expected to know more about our infrastructure and applications than a regular sysadmin would. By that I mean I am expected to understand the stack of all of the applicatons & servers running in our network. Alongside that, I'm expected to be able integrate new systems and applications with our current network. I spend a lot of time trying to migrate much of the scripts from our outdated servers to one that supports much more "modern" applications and allows for much easier admin.
Many of the servers I've had to take responsibilty of were in use MANY years before I was a teen. Many of them regulated to only using aged iptables as a firewall. Not sying anything bad about iptables, it's just not easy to standardize (and read) as firewalld. Not to mention that most of the servers I've had to admin don't even support tooling that would allow me to make it easier to automatically/automatedly admin them. Many of them only supporting python 2.4 and below (with the bare required version of python being 2.7 for ansible).
Meaning I've had to use bash to setup a automation server. Which allowed me to (at least) be able to have one codebase that would function on both modern and legacy systems. As both python and other codebases (compiled or otherwise would fail to function cohesively accross our servers). Especially since we have a hodge-podge of VM's and hardware servers, meaning that most of our legacy servers were running on machines supporting i686 or previous processors, meaning I couldn't just make a python scrit and compile/package it into a executable (using pyinstaller) to run accross our servers.
The only thing I've been able to do is to write my scripts soley in bash, as it's the most super-setted language/shell there is. Meaning that it never depricates syntax or features from previous versions of the interpreted language. Meaning that both OLD an NEW scripts would function on the newer versions of the interpreter (not so much the other way around but still).