DEV Community

Cover image for I Fixed It and I Don't Know How
Ivaj O'Franc
Ivaj O'Franc

Posted on • Edited on • Originally published at dev.to

I Fixed It and I Don't Know How

#it #automation #solutions #humor 
id: 2749930
title: "I Fixed It and I Don't Know How"
published: true
tags: ["it", "automation", "solutions", "humor"]
series: I Fixed It and I Don't Know How
description: "Real technical fixes, no fluff or speeches, told with a touch of humor and backed by a bit of automation to always get straight to the point."
canonical_url: "https://dev.to/ivajofranc/i-fixed-it-and-i-dont-know-how-1joa"
cover_image: "https://media2.dev.to/dynamic/image/width=1000,height=420,fit=cover,gravity=auto,format=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fw2h8epb2n609iractha7.png"
Enter fullscreen mode Exit fullscreen mode

I Fixed It and I Don't Know How

🇪🇸 Lee también este post en español

👋 Welcome to this experiment between keys, bugs, and a bit of automation

This blog was born from a simple idea: to solve real technical problems and share the solutions without fluff.

You're not going to find deep reflections on the future of IT here, nor motivational stories from tech gurus.

No "in a world that’s increasingly digital..." nonsense either.

That’s not my vibe. I’d rather get to the point.

🤖 Who’s writing this?

Well... a human with many technical problems (the kind that cause blue screens) and some automated help to tell the story.

These articles are partly generated by artificial intelligence. I know, I know — but before you roll your eyes, hear me out:

What matters here isn’t who writes it, but what gets solved.

Each post is based on a real issue — the kind that eats up hours digging through forums, logs, and vague documentation.

And if I can explain it clearly here for someone else to use… mission accomplished.

🔧 What will you find here?

  • Technical solutions with zero BS
  • Copy-paste-ready code blocks (not just theory)
  • Real-world IT cases: bugs, integrations, scripts, automation, and more
  • A bit of humor — because otherwise, this would be a 300-page manual in Arial 10

🧠 Why this formula?

Because automating the writing process saves me time and lets me focus on what matters: solving the problem and sharing the fix.

And if one blog post saves you an hour fighting a cryptic error… then it was worth it.

💬 Sound interesting?

Save the blog, share it, or just come back when you’re dealing with one of those bugs that “shouldn’t happen”… but do.

I’ll be here: no fluff, no filler — just clear, straight-up solutions.

End of the first post. Starting with the second, we dive straight into the fixes.

Top comments (0)