Welcome to Reverse Everything

My real name is Ihor July, but online you can usually find me as Ighor July. I was born in Ukraine and now live in California. I have always had some difficulty introducing my name to people outside Ukraine. In Ukrainian, there is the letter “Г”, and its sound is somewhere between how many English speakers hear “g” and “h”. That is why I started using Ighor as my online name.

There is also a small personal memory behind it. When I got a Windows Longhorn disc, the letters “ghor” were inside that name, and that made the spelling feel familiar to me. My memories of Longhorn are still warm. It was the time when downloading a new beta version of Windows with a redesigned interface could take many hours, but seeing that different UI made those moments stay with me forever.

I am a C++ developer, reverse engineer, cybersecurity researcher, tester, and solo indie software developer. My work is independent. I do not have a large company behind it, and some of my projects are supported by the community, donations, and sales of the apps I build.

For most of my life, I could not just use software or hardware without asking how it worked inside. Before I started writing software seriously, I was already curious about systems, devices, interfaces, and the small design choices that make technology feel either exciting or frustrating.

That curiosity became a habit. I take things apart, study how they work, look for weak points, and try to understand why something was built in a specific way. That can lead to security research, bug hunting, investigating problems that affect real users, or building my own tools because the tool I want does not exist yet.

Over the years, I found vulnerabilities in companies and organizations such as NVIDIA, PayPal, Amazon, government organizations, and many others. Some of that work cannot be discussed publicly because of non-disclosure agreements, but I still have many things I can write about. I also keep finding new things, which makes me excited to see what I will discover and share next.

I do not do this as paid work, and I do not accept paid offers to test or bug hunt private services. I mostly hack for curiosity and fun, but never to harm or steal. When I find serious issues, I report them responsibly, and sometimes those reports lead to rewards. I do not work for the companies or organizations I research.

Why I started this site

I created Reverse Everything as a permanent place for my stories, research, technical notes, and personal experience with software and hardware.

For over a decade, I published posts across different websites, including Medium, Reddit, and other platforms. Over time, those posts became scattered. I decided it was time to collect everything together and keep my articles, stories, and notes available in one place.

This site will also be where I share future projects and discoveries once they are ready. Some ideas and stories need more space than a short social post, especially when they involve debugging, reverse engineering, disclosure timelines, technical evidence, or decisions made while building a product. I want those longer explanations to live somewhere I control. Since my work is independent and community-supported, I also want this site to make that work easier to follow and support directly.

Why “Reverse Everything”

The name of this site is very literal for me.

For as long as I can remember, I wanted to understand how things worked inside. At first it was toys and small devices. Later it became computers, operating systems, apps, protocols, and software products used by many people.

Over time, that became more than curiosity. It became a way of thinking I cannot really turn off.

That mindset helped me as a developer because understanding how software can be broken also helps me understand how to make my own software harder to break. It also helped me as a bug bounty hunter because I learned to look at products not only as a user, but also as someone trying to understand what is happening under the surface.

I find bugs everywhere. Sometimes that is useful. Sometimes it is annoying. But it helps me see how things can be made better.

What I will write about

I want this site to cover the full range of things I usually think about, test, study, use, and build.

The posts will mix technical writing, personal stories, software behavior, user experience, bugs, security research, reverse engineering, old devices, operating systems, apps, and the small details that make technology either pleasant or frustrating to use. I also want to write about the path from noticing a problem to proving it, understanding it, reporting it, fixing it, or building something new around it.

My life stories also include projects the world never saw, startups that failed and were never revived, and successful projects that quietly reached millions of users. I want to share many aspects of those stories here in more detail than I could on social platforms.

I do not want every post to fit into one narrow category. I may write as a developer, a tester, or a user who has spent years with a tool and finally has enough long-term experience to explain what worked, what failed, and what stayed useful.

What to expect

This site will not be only a portfolio, and it will not be only a technical blog. It will be part archive, part blog, part technical notebook, and part personal history.

I want to write about apps and devices from the point of view of someone who used them for years, pushed their limits, tested them, fixed them, and replaced them. But my own work is driven by something more specific. I want to create new things, technologies, and architectures that did not exist before. That is the part that excites me the most.

I also want to keep honest long-term feedback about software I use. Not just quick impressions, but what remained useful after months or years, what broke under real use, and what I learned from looking deeper than the surface.

That is what Reverse Everything will be. It is my place to collect those stories, notes, discoveries, and impressions in one archive.