Compare commits

..

2 Commits

Author SHA1 Message Date
2cabcc27fd made layout changes 2024-01-05 13:06:58 -06:00
00de992e33 intial commit 2024-01-05 12:53:30 -06:00
20 changed files with 3 additions and 198 deletions

View File

@ -1,22 +0,0 @@
%title No Tickets
---------------------------
[[index.wiki|Index]]
---------------------------
last 5 posts
---------------------------
- [[1701545547-no-tickets.wiki|No Tickets]]
- [[1700863814-auvik-trial.wiki|Auvik Trial]]
- [[1700345096-busy-week.wiki|Busy Week]]
- [[1700104768-new-job-offer.wiki|New Job Offer]]
- [[1699564352-webhooks.wiki|Webhooks]]
*Date:* 2024/01/15
*Author:* Tristan Ancelet
= No Tickets =
Unfortunately there are no tickets for us to do at the moment. The tickets that are there are too advanced for us in school to do. However, once QA goes through our other tickets they will put in tickets for bug fixes.

View File

@ -1,22 +0,0 @@
%title No Tickets
---------------------------
[[index.wiki|Index]]
---------------------------
last 5 posts
---------------------------
- [[1701545547-no-tickets.wiki|No Tickets]]
- [[1700863814-auvik-trial.wiki|Auvik Trial]]
- [[1700345096-busy-week.wiki|Busy Week]]
- [[1700104768-new-job-offer.wiki|New Job Offer]]
- [[1699564352-webhooks.wiki|Webhooks]]
*Date:* 2024/01/21
*Author:* Tristan Ancelet
= No Tickets =
Unfortunately there are no tickets for us to do at the moment. The tickets that are there are too advanced for us in school to do. However, once QA goes through our other tickets they will put in tickets for bug fixes.

View File

@ -1,22 +0,0 @@
%title No Tickets
---------------------------
[[index.wiki|Index]]
---------------------------
last 5 posts
---------------------------
- [[1701545547-no-tickets.wiki|No Tickets]]
- [[1700863814-auvik-trial.wiki|Auvik Trial]]
- [[1700345096-busy-week.wiki|Busy Week]]
- [[1700104768-new-job-offer.wiki|New Job Offer]]
- [[1699564352-webhooks.wiki|Webhooks]]
*Date:* 2024/01/27
*Author:* Tristan Ancelet
= No Tickets =
Unfortunately there are no tickets for us to do at the moment. The tickets that are there are too advanced for us in school to do. However, once QA goes through our other tickets they will put in tickets for bug fixes.

View File

@ -1,56 +0,0 @@
%title Post-Mortem
---------------------------
[[index.wiki|Index]]
---------------------------
last 5 posts
---------------------------
- [[1701545547-no-tickets.wiki|No Tickets]]
- [[1700863814-auvik-trial.wiki|Auvik Trial]]
- [[1700345096-busy-week.wiki|Busy Week]]
- [[1700104768-new-job-offer.wiki|New Job Offer]]
- [[1699564352-webhooks.wiki|Webhooks]]
*Date:* 2024/02/02
*Author:* Tristan Ancelet
== Post-Mortem ==
-----------------
As of today we have presenteed out post-mortem for out time on the Eschelon Project.
== Out-take ==
--------------
I feel like we got some really good experience in the industry (both the good and the bad).
=== The Good ===
==== Priorities ====
--------------------
During out tenure on the project we learned about the development process regarding tickets & QA of features we develop. Part of this process is where the company had prioritized their other `more official` projects over ours.
There is no issue with this, it gave us a bit more context to how we need to handle our tickets going forward and know just how long we should expect to take for QA to be able to test our change and Queue it for build.
==== The Experience ====
------------------------
With this project, there is a lot of good experiences regarding this:
- Experience in an Enterprise Company working on a upcoming project
- Learning the development process and experience with a ticketing system
- Learning the importance of effective collaboration
=== The Bad ===
==== The Inital Experience ====
-------------------------------
Initially, I had a bit of trouble learning the codebase. This was mostly due to it having literal years of work and large sections of the codebase not being very well documented. Additionally, we have very little onboarding time (about a week) and were told to just explore the codebase and get familiar with it.
This made it difficult to really get an idea of the codebase before we were assigned a ticket. If it wasn't for my fellow students and my lead I would've likely floundered for my entire time here.
==== Tickets ====
-----------------
In most cases when getting a ticket they were very unhelpful as they weren't specific to what was required from us as developers. Meerly being vaguely worded and not providing an actual explanation to what we were doing.
This often also had us walking on others toes as some of the tickets were either duplicates or couldn't be done seperately from another ticket (other ticket included the same expectation as the one you were working on).
This happened often enough that it was hard to know if this was going to cause merge conflicts down the line.

View File

@ -14,7 +14,7 @@ I am Tristan Ancelet, an aspiring technologist. I enjoy working with both softwa
== What work do I do ==
=== Unix & Linux Systems Engineering ===
------------------------------------------------
As explained above I work as a Linux Systems Engineer, at an MSP.
As explained above I work as a Unix & Linux Systems Engineer, at an MSP.
=== Development ===
-------------------

View File

@ -4,13 +4,8 @@
[[about-me.wiki|About Me]]
--------
== Blog Posts ==
## Blog Posts
-------------
- [[/1706899198-post-mortem.wiki|2024/02/02 - PostMortem]]
- [[/1706384973-no-tickets.wiki|2024/01/27 - No Tickets]]
- [[/1705864010-no-tickets.wiki|2024/01/21 - No Tickets]]
- [[1702849369-zfs-upgrade-issue.wiki|2023/12/17 - ZFS Upgrade Issue ]]

View File

@ -1,53 +0,0 @@
%title Linux Systems Engineer (Acumera)
= Unix & Linux Systems Engineer (Acumera 2023 -> Current) =
--------------------------------------------
== Employer ==
--------------
*Name:* [[https://www.acumera.com|Acumera]]
| Duration of employment | |
|------------------------|------------|
| Start Date | 2023/12/04 |
| End Date | Current |
== Job Duties ==
----------------
As a Linux Systems Engineer working at Acumera, my role is multifaceted, encompassing various responsibilities to ensure the efficient operation of our infrastructure.
Key aspects of my position include:
- Infrastructure Deployment
{{{
Proficiently utilizing Puppet to build out new equipment and virtual machines (VMs)
for customers. This involves configuring and optimizing Linux systems to meet
specific requirements.
}}}
- Cloud Infrastructure Management
{{{
Setting up new Virtual Private Clouds (VPCs) in AWS to facilitate the seamless
rollout of customer VMs. This involves configuring networking, security, and
other AWS services to create robust and scalable environments.
}}}
- Automation Scripting
{{{
Developing scripts to automate intricate tasks, enhancing operational efficiency.
These scripts empower our customer support team to address and resolve issues
promptly, ensuring a swift and effective response to customer needs.
}}}
- Escalation Handling
{{{
Handling escalations from customers when their infrastructure encounters issues.
This involves diagnosing and resolving complex problems, collaborating with
cross-functional teams to ensure the restoration of normal operations.
}}}
- Jenkins Integration
{{{
Collaborating with Jenkins to design automated buildout jobs. This process
streamlines the provisioning of customer equipment from a gold-image, reducing
manual intervention and enhancing the speed and consistency of our
deployment processes.
}}}
In summary, my role involves a combination of infrastructure deployment, cloud management, automation scripting, escalation handling, and Jenkins integration, contributing to the overall reliability and efficiency of our systems and services.

View File

@ -20,6 +20,7 @@ last 5 posts
*Author:* Tristan Ancelet
= New Job Offer =
== The offer ==
Yea, as the post suggests I got a job offer from another company that want's to hire me as a Linux Systems Engineer.

View File

@ -1,16 +0,0 @@
%title No tickets
---------------------------
[[index.wiki|Index]]
---------------------------
last 5 posts
---------------------------
*Date:* 2024/01/15
*Author:* Tristan Ancelet
= No tickets =