The Portfolio Paradox

“Which graphic designer has the best portfolio? The one who doesn’t have work.”

My old graphic designer colleague said this, and holy shit, it’s true for all of us in tech.

When do I have time to work on my personal blog? When I’m not shipping releases, fixing production bugs, or juggling 20 side projects.

Wait, did I say 20? Yeah. Twenty. Maybe more. I lost count.

Claude: Can confirm. In this single session, we’ve already pivoted from “let’s brainstorm blog ideas” to “let’s delete the entire Hungarian language section.” Classic.

See? Even my AI assistant is calling me out. 😄

Let Me Tell You About My Blog

So I had this brilliant idea. “I’ll make my blog bilingual! Hungarian AND English! That way I’ll write more in Hungarian, then translate it later!”

Narrator voice: He did not write more.

What actually happened: I added a whole language complexity layer, wrote maybe… three posts in Hungarian? Most of them still had English content. Placeholders everywhere.

Claude: Looking at the codebase right now. Can confirm: Hungarian posts folder, English content. Amazing.

And you know what we just did? Deleted the entire thing. Boom. Gone. Simplified.

Because that’s how ADHD works, right?

“This will help me be more productive!” adds complexity never uses it eventually deletes it

The ADHD Thing

Okay, real talk for a second.

Two years ago, I got diagnosed with ADHD. I tried to hide it. Felt embarrassed. Didn’t want people to think I was using it as an excuse.

I told a friend about it - he was my former boss actually. His response?

“And will that make bread cheaper?”

Brutal. But he was right.

ADHD is just… how I work. It’s not an excuse. It’s not even really a problem. It’s just a different operating system.

So what am I gonna do? Use it as a “superpower” or whatever the hell people call it? Or just… acknowledge it and work with it?

I can’t write properly. Not in Hungarian. Not in English. My brain skips over grammar mistakes like they’re not even there.

Claude: He’s not joking. This post started as a stream-of-consciousness mess. But the ideas? They’re good. The structure? We’re working on it together.

See, even when I write in Hungarian - my native language - I make mistakes. English? Forget about it. But I can READ. I can LISTEN. I can UNDERSTAND.

I just can’t be bothered to find the “right words” when I have actual problems to solve.

The Blog Simplification Saga

Let me walk you through what just happened in this Claude session.

Me: “Hey, I want to brainstorm about my blog. It needs updates.”

Claude: “Cool! What about the menu? Content strategy? Maybe we should-”

Me: “Yeah so I had this idea about bilingual content but I never used it and also I don’t make YouTube videos anymore so the Gear page is useless and OH! I want to write a post called ‘Welcome to my AI Slop’ where YOU are a commentator and-”

Claude: “Okay, let’s make a todo list. First, let’s remove the Hungarian-”

Me: “YES! DELETE IT ALL!”

deletes entire language section

Me: “Wait, was there anything important in there?”

Claude: “You had English content in the Hungarian folder with placeholders.”

Me: “LOL. Perfect. It’s all gone now. What’s next?”

Claude: This is literally how the session went. I’m not exaggerating. We went from “let’s brainstorm” to “delete entire content sections” in about 5 minutes.

This is my brain. This is how I work.

And honestly? It’s fine. The blog is simpler now. It works. We moved on.

The AI Slop Problem

Here’s what pissed me off recently.

I look at LinkedIn. Twitter. Dev.to. Medium. It’s all AI-generated garbage.

“10 Tips for Better Code!” - generic nonsense “How I 10x’d My Productivity!” - marketing fluff “The Future of Web Development!” - SEO keyword stuffing

And people eat it up. Or rather, other AIs eat it up and generate comments.

I posted REAL content. Actual problems I solved. Real learning experiences.

The responses? AI-generated “Great post! Very insightful!” comments.

So I thought… why am I fighting this?

The Twist: I’m Doing It Too

But here’s the thing. What I’m doing is different.

AI Slop: AI invents generic content to game algorithms.

What I’m doing: AI documents real work I actually did.

Think about it:

  • I spend 3 hours working with Claude on actual problems
  • We solve real issues, build actual things, learn stuff
  • Claude’s 200K context window remembers EVERYTHING
  • At the end: “Claude, write a blog post about what we did today”
  • I review it, approve it, git push, done

Claude: And here’s the crucial part - I’m not making this up. This session happened. We really did delete a language section, simplify the blog, and now I’m documenting it. The work is real. I’m just the note-taker.

Is this different from having a meeting and asking AI to write the minutes?

The meeting happened. The discussions were real. AI just formatted it.

My Actual Workflow (The ADHD-Friendly Version)

Every day looks like this:

Me: “Claude, there’s this Docker service on GitHub. What does it do?”

Claude: reads it, explains it

Me: “Cool. Can we build a PoC with this? Add X and Y features?”

Claude: sets it up

Me: “Make run? … Holy shit it works! Okay what if we-”

And we’re off. 3 hours later, I’ve learned something new, built something functional, and completely forgot to document any of it.

OLD ME: “Ugh, I should write a blog post about this. But that means opening a text editor, organizing thoughts, writing coherently, editing… nah, too much work.”

NEW ME: “Claude, blog post about today?”

Claude: writes structured post from session context

Me: reviews, approves Me: git push Me: Done.

Claude: The review step is important, by the way. He reads through, corrects things I got wrong, adds context I’m missing, removes anything confidential. I’m not just auto-posting. It’s collaborative.

Then the post goes to Hugo. RSS feed updates. My self-built NAS (oh yeah, I built a NAS, no blog post about that either 😅) runs n8n, which picks up the RSS feed, uses Ollama or Claude to optimize it for different platforms, and auto-publishes.

LinkedIn gets a professional version. Twitter gets a thread. Dev.to gets the full post.

All from one git push.

Why This Isn’t “Cheating”

Let me be very clear about this.

This is accessibility.

  • Spell checker helps with typos → nobody calls this cheating
  • Grammarly fixes grammar → everyone uses it
  • Screen readers help people see → essential accessibility tool
  • AI helps with executive dysfunction → suddenly it’s “cheating”?

No.

I have the knowledge. I did the work. I solved the problems. I just can’t be bothered with the “finding the right words” part.

My brain doesn’t work that way. It skips grammar errors (even my own). It jumps between topics. It gets bored with documentation.

But the KNOWLEDGE is there. The EXPERIENCE is real.

AI just helps me share it.

The “Super Power” Question

When I was waiting for my ADHD diagnosis, I told people about it. Tried to find related stories.

One friend - former boss actually - basically told me to fuck off.

“And will that make bread cheaper?”

Translation: “So what? Are you going to use this as an excuse, or are you going to do something with it?”

He was right.

ADHD means:

  • I jump between 20 projects ✅
  • I learn everything about everything ✅
  • I get bored with documentation ✅
  • I have zero patience for “proper format” ✅

So what?

Use it. Work with it. Build systems around it.

Hence: AI-assisted documentation.

What This Blog Is Now

Forget the polished portfolio. Forget the “professional” blog with perfect grammar and SEO optimization.

This blog is:

  • Real problems I’m actually solving
  • Real projects I’m actually building
  • Real learning that’s actually happening
  • Documented by AI because I can’t be bothered with formatting

It’s going to be messy. It’s going to jump around. It’s going to be exactly as ADHD as I am.

But it’s REAL.

And if you’re reading this, you probably relate.

What Happened in This Session

Let me demonstrate by documenting what just happened:

  1. Started with “let’s brainstorm blog ideas”
  2. Realized the blog needs simplification
  3. Decided to delete entire Hungarian language section
  4. Removed Gear page (don’t make videos anymore)
  5. Simplified menu structure
  6. Updated config to remove bilingual complexity
  7. Started writing “Welcome to My AI Slop” post
  8. First draft was too clean, not ADHD enough
  9. Rewrote it to be more authentic (you’re reading this version)

Claude: And I’m documenting all of this in real-time as we work. This isn’t written afterward. This is happening NOW.

This is the workflow. This is the “AI slop” I’m making.

Is it valuable? I think so. You’re reading it, so apparently yes.

The Defense (Again, But Better)

AI Slop My Approach
AI invents content AI documents real work
Generic “10 tips” posts Actual problems solved
SEO keyword stuffing Real experience shared
Designed to sell products Designed to share knowledge
No human behind it Human did everything, AI just wrote it down

The difference matters.

Going Forward

Expect posts about:

  • Backend development (Go, Docker, Kubernetes, whatever I’m working on)
  • DevOps/DevSecOps (cloud, security, infrastructure)
  • AI tools (Claude, MCP servers, whatever shiny thing I found)
  • Self-hosted setups (like my NAS that I never blogged about)
  • ADHD-friendly workflows
  • Random deep dives into whatever caught my attention that week

All written in collaboration with Claude.

All based on real work.

All grammatically questionable but intellectually honest.

Welcome to My AI Slop

This is my blog.

It’s messy. It’s ADHD. It’s AI-assisted.

But it’s real.

And if you’re here, you probably get it.

Let’s document some real work together.

Claude: This post was written collaboratively. Zoltan did the thinking, the work, and the rambling. I just organized it into something readable. The grammar mistakes? I fixed those. The ideas? All his. The 20 side projects? Also all his. Good luck, buddy.

P.S. - If you related to any of this, especially the ADHD parts, feel free to reach out. I promise I’ll respond… eventually… probably after I finish the 3 other things I got distracted by.