From Engineering to Technology: My Journey into Computing
My journey from engineering, drawings, and piping into computers, automation, Information Systems, Linux, servers, programming, networking, and artificial intelligence.
My journey into technology did not begin with programming. My professional background came from engineering, fabrication, inspection, drafting, and piping. For many years, I worked with drawings, engineering data, technical documentation, materials, fabrication information, and engineering software used to support project execution.
Initially, computers were simply working tools. I used them to review drawings, process data, prepare reports, verify engineering information, and complete everyday tasks. But the more I worked with computers, the more questions I began to ask. Why should repetitive work always be performed manually when computers could potentially automate it?
That question became the beginning of my interest in automation.
Microsoft Excel was one of my first environments for experimentation. I started with formulas and eventually explored macros and VBA. Tasks that previously required many repetitive steps could suddenly be transformed into faster automated processes.
While working with engineering software such as PDMS, I also encountered PML and discovered that automation was not limited to spreadsheets. Engineering applications could also be extended through scripting.
This changed how I viewed computers. Instead of only being an application user, I became interested in understanding how applications work, how data is stored, how software interacts with operating systems, and how computers can be instructed to perform specific tasks.
That curiosity eventually led me to Linux.
Linux initially felt very different from Windows. Terminals, permissions, package managers, services, filesystems, and commands were unfamiliar. Yet I enjoyed the process because Linux provided a closer view of how computer systems actually operate.
I experimented with Debian, Ubuntu, Arch Linux, WSL, virtual machines, and other environments. What started as operating-system experimentation gradually expanded into web servers, databases, file sharing, media servers, bots, and self-hosted applications.
I later explored virtualization through Proxmox. A single computer could host multiple Virtual Machines and Linux Containers, each serving a different purpose.
This helped me understand that applications are only one part of a much larger system. Reliable applications depend on operating systems, networks, storage, databases, security, backups, monitoring, domains, and many other components.
My curiosity also expanded into networking. I began learning about IP addressing, subnets, DHCP, DNS, routing, NAT, firewalls, VPNs, tunneling, and communication between devices.
Raspberry Pi became another experimental platform. I used it to explore OpenWrt, Pi-hole, ZeroTier, Cloudflare Tunnel, and Linux services. It demonstrated how even a small computer could operate as a router, DNS server, network appliance, or server.
At the same time, I started exploring programming more seriously. Python, JavaScript, Node.js, HTML, CSS, SQL, PostgreSQL, PowerShell, and Bash gradually became part of my experiments.
I discovered that project-based learning works best for me. Rather than only reading theory, I prefer building something, running it, encountering errors, fixing them, and understanding why the system eventually works.
This approach resulted in personal projects such as Piping Stuff by AR, i-Kata Tours & Travel, ARMedias, AR Python Manager, AR CyberLab, AR-GAMES, ARCLAW, monitoring bots, and various server and automation experiments.
Some projects originated from real problems I encountered. Others began with simple curiosity: Can I build something like this? Can it run inside LXC? Can installation be automated? Can backups and restores become part of the application itself?
Simple questions like these often become the beginning of new projects.
I later pursued Information Systems studies at Universitas Terbuka. This academic journey complements my technical experimentation by helping me understand requirements, business processes, databases, systems analysis, architecture, governance, and the relationship between people and technology.
More recently, my interest has expanded into Artificial Intelligence and AI agents. I initially used AI for questions, research, and coding assistance. Eventually, another question appeared: what if AI could not only answer questions but also use tools and perform tasks?
This led me to experiment with AI agents, memory, scheduling, model routing, tool execution, bot integration, and automation. ARCLAW is one of my experiments for understanding how AI can interact with WhatsApp and other systems.
I do not consider this journey complete. The more I learn, the more I realize how much remains to be understood.
That is exactly what makes technology interesting to me.
I started in engineering and used computers primarily as working tools. I am still an engineer today, but computers have also become a laboratory where I learn, experiment, build, fail, fix problems, and try again.
OFAREDEV exists to document that journey. It is not intended to suggest that I have mastered everything, but to record what I have learned, what I have built, the problems I have encountered, and how my understanding of technology continues to evolve.