Thoughts, tutorials, and insights.
When people start building systems, they usually worry about speed first. That’s understandable, but it’s often the wrong instinct. Before you chase throughput, you need to understand reliability. Here’s why the order matters.
Bootcamps sell speed and certainty in an industry that has neither. Becoming a software engineer takes more than three months, more than frameworks, and more than job-ready promises. This is what usually gets left out.
This blog tells the story of a website project that was flawed from the start due to poor professional decisions. Without a signed agreement and with loose boundaries, communication issues and delays surfaced. The story concludes when the author takes responsibility, pauses the project, enforces proper process, and restores control through structure and clarity.
Modern JavaScript tooling creates friction through bloated configs, ESLint–Prettier conflicts, and slow feedback. Biome replaces that with a single Rust-based tool that unifies linting and formatting, runs 10–20× faster, and requires minimal configuration—making tooling fast, predictable, and invisible again.
AI coding agents can accidentally access sensitive files like .env. Samar creates a shadow workspace so agents can edit code safely without ever seeing your secrets.
Watching tutorials feels productive—but it’s not the same as learning. Real coding skill comes from building, breaking, and fixing things yourself.
The answer is: it depends. It depends on whether you have the opportunity. If you do, take it. If you don’t, you can still work in IT and become a software engineer.
A brief introduction to my journey in IT—how early curiosity, inspiration from hacking culture, and years of tinkering led me into software, security, and data engineering. This blog is a space where I share experiences, insights, and lessons learned while continuously exploring and building in the tech world.