Synthesis of Spiritual Reflection, Deepened Theological Grounding, Integrated Systems Projects, and Ethical Refinement.
Doctrine and Covenants 58:26–28
“anxiously engaged in a good cause, and do many things of our own free will, and bring to pass much righteousness”
In my contemplation this week, I reflected on the valuable teachings contained in Doctrine and Covenants 58:26–28. According to the passage, we should be "anxiously engaged in a good cause, and do many things of our own free will, and bring to pass much righteousness." The scriptures have had an effect on my understanding of the concept of agency in my spiritual as well as professional life as an IT specialist.
It is relatively easy in the technology world to be passive and just follow tutorials and do things as assigned. Real change and development can take place through using our agency to construct and develop ourselves. For example, developing Exzel Consulting, learning Next.js, and deploying local multi-agent AI frameworks were things that I did not have to do; they were the things I did because of my agency. Similarly, my technical skills can reach only as far as my agency takes them. In the same way, spiritually speaking, we should lead and serve using our agency, instead of being commanded about everything. Through being active in my education as an IT professional and keeping my spiritual covenants, I have seen development that has helped me in becoming a better leader of the Systems Architect field.
Personal Reflections on Core Teachings & Leadership Resources
“Come What May, and Love It”
“In the IT field, things tend to malfunction a lot. From PostgreSQL connection issues, to failed Next.js deployments, or graphics driver problems on my custom-built machine running Linux, frustration often lurks around the corner. However, "come what may, and love it," as advised by Elder Wirthlin, helps me develop my resilience skills. Rather than getting frantic after a server goes down or my code won’t build, I try to view such challenges positively as part of the process.”
“Be Not Afraid, Only Believe”
“While developing the multi-agent AI technology within the local Exzel Consulting environment, I frequently experienced episodes of “imposter syndrome,” where I questioned my technical abilities in constructing this intricate software program. The lesson from Elder Uchtdorf emphasized that fear hinders our ability to perform at our best. Through the process of “only believing,” or having faith in my own divine capabilities, I was able to have the confidence to undertake complex hardware implementations, such as VRAM optimization on RTX GPUs.”
“Problem-Solving and Collaboration”
“In my position as Lead Systems Architect, I must develop applications that are truly going to be of benefit to my coworker, Elizabeth, who works in a sales and client relations capacity. This kit reinforces the idea that the best collaborations stem from an attitude of kindness and patience. It was made clear to me that programming to solve a problem such as automating lead generation is more than just coding efficiently.”
Harmony between Full-Stack Systems Architecture and Eternal Principles
As I develop my skills in full-stack web development, system architecture, and AI orchestration, I notice a perfect harmony between them and my spiritual ideals. The tools of technology that I learn are not separate from my spiritual ideals; instead, they are just the implementation of timeless principles.
IT development calls for meticulous organization and proper logic. The Lord has said that "My house is a house of order" (D&C 132:8). Indeed, using good coding principles such as proper architecture, version control, and databases has led me to more efficient systems that are easier to work with.
Debugging code is an endless cycle of recognizing problems, understanding the mistakes that lead to them, and fixing the system to eliminate the issue. It reflects the concept of repentance and striving to make our life better through it. When my web scraping code doesn't function properly, I do not give up but examine the log, correct the mistake, and try again. Being able to troubleshoot is a very valuable skill that made me appreciate the concept of Atonement and continuous improvement of life as a developer.
Using APIs, integrating AI, working with databases is managing sensitive data of users. I see my professional competency in this field as my belief in absolute integrity and moral obligation to be a steward for my fellow man's privacy. Since I know that it is a moral duty to treat people right and preserve their privacy, it drives me in making sure my configurations are absolutely safe.
Integrating technical architecture requirements with spiritual purpose and growth.
Lead Systems Architect
In my role as Lead Systems Architect at Exzel Consulting, I created and implemented a proprietary CRM solution built on Next.js, TypeScript, and PostgreSQL as the database. The technical requirements involved developing role-based views as well as incorporating a functioning phone system in the dashboard to keep track of leads and conversions effectively. Nevertheless, the success of this endeavor was significantly influenced by my spiritual growth. Prior to coding anything, I utilized the Co-Creation concept described in the BYU-Idaho Leadership Toolkit. Through envisioning the spiritual significance of the project—to create an orderly space in which to cultivate honest business dealings—I was able to implement a digital architecture that embodies order and transparency.
Systems Administrator & Hardware Technician
In order to protect data privacy and improve speed, I decided to make a dedicated AI workstation instead of using only cloud-based APIs. Working as both Systems Administrator and Hardware Technician, I built a powerful AMD Ryzen 7 machine, set up a Linux Mint Operating System, and made proper VRAM allocation for running the Hermes multi-agent AI software locally. This intricate combination of hardware and OS setup pushed my skills to their limit, especially when dealing with Linux graphics drivers. On a spiritual side, it taught me about patience and faith, which is similar to Nephi's directive to "go and do" (1 Nephi 3:7). Every time I came across impossible-to-solve system problems, turning to faith helped me think clearly and persistently enough to solve them, thus showing that faith is crucial in the world of high-end IT.
Lead Systems Architect & Full-Stack Developer
I created an automated web scraper that would help find the weaknesses in the digital infrastructure of our prospective customers, thereby providing us with qualified leads that we could integrate right into our CRM system. From a technical perspective, this entailed proper scripting and networking knowledge. On a spiritual plane, I approached this assignment in the light of Mosiah 2:17, which means serving others. By automating my work in order to help generate leads, I have become able to serve my co-worker Elizabeth Orrego by giving her all the time she needs for relationship building and selling.
The ethical principles essential for this situation include Honesty, Responsibility, and Integrity.
In lieu of exploiting the WAF misconfiguration in order to gain access to the internal storage buckets and download confidential information such as Social Security Numbers (SSN) and banking information, Paige Thompson, the former AWS systems administrator, should have resorted to the best practice of responsible disclosure. Once she discovered the Server Side Request Forgery (SSRF) vulnerability, Paige Thompson should have restricted herself to validating the flaw without any file download or access. Then she should have contacted Capital One's security team to inform them about the misconfiguration flaw.
This alternative strictly abides by the ethics principles of honesty and responsibility resulting in a completely different outcome.
Personal information of over 100 million people remains safe as there would be no risk of identity theft or financial losses.
It will receive a notification of vulnerability, giving the firm ample opportunity to patch its infrastructure to prevent malicious attacks on it and avoid any severe damage to its reputation and financial well-being.
It helps her maintain professional integrity; she doesn't face federal charges and imprisonment and can even get a reward for reporting the critical vulnerability.
A structured four-phase report evaluating engineering challenges, technical & ethical refinements, peer review iteration, and operational impact.
In its first iteration, the web scraper did not have proper request throttling and therefore had the potential to accidentally overload or DoS the target client's servers. It was also required to improve its fault tolerance capabilities when dealing with timeout errors during the deep scanning process.
Web scraping itself poses major ethical issues in terms of user consent, privacy, and fairness. I needed to make sure that my automated software did not break any terms of service of the target websites nor gather personally identifiable information (PII).
Given the above findings regarding the problems faced, I have improved on the TypeScript coding of the scraper to solve the technical and ethical issues.
I have incorporated an asynchronous delay mechanism for spacing out the HTTP requests. The aim is to ensure that the operation of the scraper is smooth without causing activation of server firewalls or compromising the efficiency of the website being targeted. There is also a process of logging errors to enable detection and exclusion of dead links without halting the whole scraping process.
Two main aspects of ethics were incorporated into the code. First of all, there was an inclusion of the ability to respect the robotstxt file of the target website before carrying out any crawling process. In addition, there is a privacy by design and consent aspect implemented in the form of a PII (Personally Identifiable Information) filter. Through this feature, any unapproved personally identifiable information (such as residential private phone numbers or personal emails) would be filtered using regular expression matching.
When going through peer reviews, my reviewer gave very constructive feedback. He mentioned that even though my scraper adhered to robots.txt, it did not include any specific User-Agent in HTTP requests. This could cause my tool to look like a malicious bot in the eyes of the target servers.
Considering that my reviewer raised a legitimate ethical and technical question, I decided to change the headers of my requests immediately. Namely, I added a custom and open User-Agent (ExzelConsulting-SecurityScanner/1.0; +https://angelguerra.exzelconsulting.com/bot). This solution corresponds to my principle of integrity completely. I have identified myself and provided the website administrators with a possibility to find out more about my bot or refuse from being scraped.
User-Agent: ExzelConsulting-SecurityScanner/1.0; (+https://angelguerra.exzelconsulting.com/bot)The effect of the above-mentioned changes has been very positive. On the one hand, stability of my scraper has increased substantially because of the rate limiting (less than 20% of timeout crashes occurred). On the other hand, the project has become more ethical and considers all the data privacy regulations. This experience showed me that including ethical limitations into the software development process is not going to restrict the capabilities of a project, but on the contrary, will make it more professional.
Timeout Crashes Reduction
< 20%
Significantly decreased timeout failure rate
Privacy Standards
100% PII Filtered
Compliant with privacy-by-design principles
Audit Transparency
Identified Bot
Open custom User-Agent identifying Exzel