About Iwan & SnipGeek

Current tagline: Windows dan Ubuntu: Tutorial, Troubleshooting, dan Update Penting.

SnipGeek was re-established on February 10, 2026, but its real story started much earlier. This site was not created just to publish more content. It was rebuilt to preserve useful knowledge, reduce noise, and document practical technology experience in a way that remains helpful over time. Some articles on this site may have publication dates older than the relaunch itself. That is intentional. A number of older writings were carefully selected from previous work and kept alive because they still solve real problems, answer real questions, and continue to offer value. SnipGeek exists because useful technical writing should not disappear just because the design changed, the platform changed, or the internet moved on to the next trend. SnipGeek is a practical technology publication focused on real-world Windows and Ubuntu usage. Editorial direction is now locked to the tagline above: every article should contribute to one of these outcomes: clearer tutorial steps, better troubleshooting decisions, or relevant updates with practical impact. It combines three content tracks that work together:

• series guides for structured workflows (especially dual-boot and system setup)
• relevant updates and release-impact analysis
• practical tips and troubleshooting notes from actual usage

This is not a site built around hype, content farming, or recycled headlines. The goal is simple: publish material that helps people solve problems, make better operating-system decisions, and work more efficiently day to day. I built SnipGeek as an extension of the way I work and think. My background is not limited to one narrow lane. I have spent years working across technical operations, administration, field work, troubleshooting, procurement support, and process optimization. That combination shaped the way I approach technology: not as something abstract, but as something that should make work clearer, faster, safer, and easier to manage. Because of that, I naturally care about systems that are:

• structured
• efficient
• easy to maintain
• practical in real conditions
• useful beyond theory

That same mindset shapes every page on this site. A lot of websites treat content like disposable inventory. Once a redesign happens or a project changes direction, old material gets deleted, buried, or forgotten. I take a different approach. If an older article is still accurate enough to help someone, still searchable, and still useful in practice, I would rather preserve and improve it than erase it. SnipGeek is not meant to be a stream of temporary posts. It is meant to become a growing archive of practical technical knowledge. That is why some older articles remain here: not as leftovers, but as foundations. The writing philosophy behind SnipGeek is built on a few principles:

• usefulness over novelty
• clarity over jargon
• experience over empty theory
• long-term value over short-term trends

When possible, I prefer writing content that stays relevant for longer, even if the topic is specific. I would rather publish something genuinely helpful than something merely timely. I also believe technical writing should feel human. It should explain, not perform. It should guide, not posture. Good content should make readers feel more capable, not more confused. People sometimes ask what kind of setup I use to build and manage this site. The honest answer is: nothing extravagant. I believe good work does not always require premium hardware. It requires a workflow that fits the person using it. My main machine has been with me since 2022:

Property	Detail
Device Name	SnipGeek
Processor	11th Gen Intel(R) Core(TM) i3-1115G4 @ 3.00GHz
Installed RAM	32.0 GB (31.7 GB usable)
System Type	64-bit operating system, x64-based processor
Pen and Touch	No pen or touch input is available for this display

Even though the hardware is modest by enthusiast standards, it has been more than enough for the kind of focused work I value: writing, building, debugging, testing, and refining. My workflow is flexible by necessity, not by fashion. For most writing, development, and site-building tasks, I prefer Linux. It gives me the environment, speed, and control I need. It feels clean, productive, and aligned with the kind of focused technical work I enjoy. At the same time, I do not force ideology into workflow. I still rely on Windows when specific tasks demand it, especially work involving Microsoft Excel or certain compatibility-heavy office needs. In practice, the best workflow is not about loyalty to one platform. It is about choosing the right tool for the right task. That philosophy carries into SnipGeek as well. That is also why you will see both evergreen guides and selected update coverage here: tutorials solve recurring problems, while updates help you adapt when the platform changes. If you spend time on this site, you can generally expect content that aims to be:

• practical instead of performative
• direct instead of bloated
• experience-based instead of generic
• useful for both immediate problems and future reference

Some articles may be highly specific. Some notes may be short and technical. Others may be broader and more reflective. But the common thread is the same: each piece should earn its place by being genuinely useful. SnipGeek is still evolving. The site will continue to grow not just through new articles, but through better structure, better tools, better archives, and better ways of organizing knowledge. I want it to become a place where technology content feels grounded, helpful, and worth returning to. If you have been reading, sharing, or finding value here, thank you. That support is part of what keeps this project alive and worth improving. SnipGeek is not just a blog to me. It is a long-term work in progress built around the belief that practical knowledge deserves a good home.