

Jay Long
Software Engineer & Founder
Published January 10, 2024
Updated March 5, 2026
I've been thinking a lot about how to make my online presence work harder for me. Not in a "personal brand" LinkedIn influencer way, but in a practical way. When someone searches for a software engineer with specific skills, like AWS or SaaS development, I want my name to show up. And I want what they find to be real.
Here's what I've landed on: two blogs, working together.
The first blog is basically a detailed record of everything I've done professionally, organized by year, starting from the most recent and working backward. Each project gets a short paragraph covering my role, what I learned, and what I actually built. I include the names of people I worked with, the teams, and the specific tech I used. PHP, AWS infrastructure, whatever it was. Each entry is dated by year, sometimes by quarter if it matters.
This acts as a digital portfolio. By listing specific projects and the people I collaborated with, it gives anyone checking me out actual evidence of what I've done. Not vague claims about being a "results-driven engineer." Real projects, real people, real tools.
The second blog runs in the other direction. It's real-time, dated entries about what I'm working on right now, what I'm exploring (digital marketing, generative AI optimization), what problems I'm solving, and where I'm headed. It cross-references the biographical blog so there's a clear thread between past experience and current work.
This one shows I'm active. I'm not just coasting on a resume from 2019. I'm in it, building things, learning new tools, and thinking about where the industry is going. The goal is to attract opportunities by writing about the exact problems potential clients are trying to solve.
There are two games to play now. Traditional SEO is about getting indexed by Google through clean code, proper tags, and good page structure. That still matters. But there's a newer game: generative optimization. LLMs like ChatGPT and Perplexity don't just crawl your page and rank it. They read your content deeply and decide whether to surface it as an answer.
For generative optimization, the content needs to be clear, factual, and well-structured. I'm writing everything in Markdown because LLMs digest it cleanly. I'm also building validation across platforms. LinkedIn, social media, references to past projects and collaborators. When an LLM sees consistent information about me across multiple sources, that consistency becomes its own form of authority.
On the analytics side, I'm using Google Analytics on all blog pages to track traffic and engagement, plus social media insights to get a read on how visible I actually am.
One thing I hadn't thought about before is how much professional networking feeds into all of this. I'm going back through every project I've worked on and documenting who I worked with, their roles, and what we built together. Then I'm finding those people on LinkedIn, Twitter, wherever, and reconnecting.
This isn't just networking for the sake of it. When multiple people in the same industry are connected to me and can vouch for the work, that creates a web of references that both search engines and LLMs pick up on. It makes me harder to ignore.
The implementation is straightforward. I'm compiling every past project and collaborator into the biographical blog, writing it up with dates and specifics, and publishing in Markdown. The present-to-future blog is already running with real-time updates that link back to the biographical entries. Google Analytics is tracking everything, and I'm systematically reaching out to past collaborators to rebuild those connections online.
The whole strategy is about making it easy for both humans and AI to find me, verify that I'm legit, and understand exactly what I bring to the table.