FantasyDesigned Blog

One Class, Two Capstones, and the Finish Line Ahead

July 7, 2025
It feels surreal to say this:
I’m almost done with my bachelor’s degree in Information Technology.

After months of balancing school, work, certifications, and life, I’m down to just one class and two capstone projects. The finish line is finally in sight—and with it comes a flood of emotions: excitement, pride, a little nervous energy, and a lot of gratitude.

I’ve learned so much—not just about databases, systems, security, and programming—but about perseverance, time management, and believing in my own ability to grow.

What This Final Stretch Means to Me:
- 🧭 It’s proof of commitment – I started this journey unsure, but determined
- 💻 It’s the bridge to opportunity – Jobs, certifications, and career confidence are now within reach
- 🌱 It’s not the end—just the beginning – Of leveling up, specializing, and stepping fully into the tech world
These last few assignments and capstone projects will take focus and energy, but I’m ready. I’ve built a foundation, I’ve sharpened my skills, and now it’s time to bring it all together.

If you’re in your own final stretch—whether it’s school, a certification, or a long-term goal—know this:
You’ve come too far to stop now. Finish strong. You’ve got this.

And to those just starting their journey?
Keep going. One day soon, you’ll be writing your own finish line post too.

“It always seems impossible until it’s done.”
— Nelson Mandela
Picking Up Where I Left Off: It’s Okay to Take a Break (And Come Back Stronger)

July 6, 2025
Life happens. Schedules get full. Energy runs low. Sometimes, you just need a break—and that’s exactly what I took.

For a while, I stepped away from blogging and some of my usual routines. And honestly? I needed the reset. I needed time to recharge and refocus. But here’s what I’ve realized:
Taking a break doesn’t mean you’ve failed—it means you’re human.

In tech and education, it’s easy to feel like you have to keep moving constantly or risk falling behind. But growth isn’t always about speed. Sometimes it’s about sustainability.
The key isn’t to avoid breaks—it’s to learn how to return with intention and self-compassion.

How I’m Getting Back into Momentum:
- 🔄 Start small – One task, one post, one study session at a time
- 🎯 Refocus my goals – What matters now? What’s the next right step?
- 🧠 Let go of guilt – A break isn’t a setback—it’s a strategy
- 📓 Reflect before I push – I take a moment to acknowledge how far I’ve already come
Coming back after a break isn’t always easy. But it’s powerful.
It shows that you’re committed, not just when it’s convenient, but when it’s real.

So here I am—back at it, refreshed, focused, and ready for the next chapter. If you’ve taken a break too, know this:
You’re not behind. You’re building something. And you’re still in the game.

“Rest when you’re weary. Refresh and renew yourself, your body, your mind, your spirit. Then get back to work.”
— Ralph Marston
Setting Realistic Goals in IT (And Why That’s What Actually Works)

June 26, 2025
When I first started studying IT, I wanted to learn everything—fast. Certifications, programming languages, networking, security, AI… it all sounded exciting.
But I quickly realized that trying to do everything at once led to burnout, not progress.

That’s when I started learning the power of setting realistic, focused goals.

Big dreams are great, but progress comes from clear, manageable steps that you can actually follow through on—even when life gets busy. Especially as a student, a career-changer, or someone balancing work and school, setting achievable goals can make or break your momentum.

How I Set (and Stick to) Realistic Goals:
- 🎯 Be specific – Instead of “get better at networking,” I’ll set “study subnetting for 30 minutes today”
- ⏱️ Time-bound tasks – Weekly or daily goals help me measure progress
- 📉 Avoid perfectionism – Done is better than perfect
- ✅ Track progress visibly – A checklist, calendar, or app helps me stay motivated
- 🔄 Adjust as needed – If a goal no longer fits, I don’t quit—I realign
Setting realistic goals doesn’t mean dreaming small. It means being smart about how you build toward something big.
Every certification, every concept, every lesson completed adds up.

Small wins lead to big change—when you keep showing up.

“A goal properly set is halfway reached.”
— Zig Ziglar
Troubleshooting Is a Mindset (Not Just a Skill)

June 25, 2025
One of the biggest mindset shifts I’ve had while studying IT is this:
Troubleshooting isn’t just about fixing problems—it’s about how you think about problems.

Whether you’re writing code, setting up a network, or trying to figure out why a system won’t boot, your ability to troubleshoot comes down to how calmly and logically you approach the issue. That mindset is just as important as the technical tools you use.

At first, I thought troubleshooting meant knowing everything off the top of your head. But I’ve learned that it’s actually about knowing how to isolate, test, and think through a problem—even when the answer isn’t obvious.

What I’ve Learned About Troubleshooting:
- 🧠 Start with the basics – Don’t overcomplicate the issue. Is it plugged in? Is the service running?
- 🧭 Use process of elimination – Change one variable at a time, and document your results
- 🔍 Look for patterns – What changed recently? What’s working, and what’s not?
- 🧘 Stay calm – Frustration clouds judgment. A deep breath can lead to a breakthrough
- 📚 Document the fix – Future you (or your team) will thank you
Over time, I’ve come to enjoy troubleshooting—not because it’s always easy, but because it teaches me to think critically, stay curious, and trust myself to solve problems step by step.

The more you troubleshoot, the more you realize:
You don’t have to know all the answers—you just have to know how to find them.

“The problem is not the problem. The problem is your attitude about the problem.”
— Captain Jack Sparrow
When It Feels Like Too Much—How I Handle Overwhelm While Learning IT

June 24, 2025
Let’s be honest—sometimes, learning IT can feel like too much.
A new language, a complicated system, a certification exam full of acronyms you’ve never seen before… it builds up fast. And when it does, it’s easy to freeze or question if you’re even cut out for this.

But I’ve learned that overwhelm isn’t a sign to quit—it’s a sign you’re growing.

When the learning curve feels steep, I remind myself that it’s okay to slow down, regroup, and take it step by step. The key is not to let the weight of everything stop you from doing something.

Here’s How I Manage Overwhelm:
- 🧩 Break it down – I divide big topics into small chunks and tackle one concept at a time
- 🗓️ Use a study plan – A calendar or checklist helps me see progress, even on hard days
- 🧘 Take real breaks – Not just scrolling breaks, but actual mental rest
- 🤔 Remind myself why I started – My long-term goals help me power through short-term stress
- 📚 Review what I do know – Looking back on past wins gives me strength for the next climb
The truth is, learning something hard means you’re stepping outside of your comfort zone. That’s a good thing. It means you’re stretching, leveling up, becoming the version of you who can do this.

So if it all feels like too much—take a breath. Then take one step.
You don’t need to learn everything today. You just need to keep going.

“You don’t have to see the whole staircase, just take the first step.”
— Martin Luther King Jr.
Learning to Ask Better Questions (A Hidden Superpower in Tech)

June 23, 2025
When I first started learning IT, I was afraid to ask questions. I didn’t want to sound unprepared or like I didn’t belong. But here’s what I’ve discovered:
Asking questions isn’t a weakness—it’s a skill. And in tech, it’s one of your most powerful tools.

Whether you’re troubleshooting a problem, learning a new programming concept, or working in a team, the quality of your questions can determine how quickly and clearly you find answers.

Why Asking Good Questions Matters:
- 🧠 It shows critical thinking, not confusion
- 🧩 It helps you break down complex issues into manageable parts
- 🔄 It leads to better solutions, faster
- 🤝 It builds trust in collaborative environments
What I’ve Learned About Asking Better Questions:
- 🔍 Be specific – Instead of “My code doesn’t work,” I ask, “What does this error message mean in context?”
- 📝 Provide context – Share what I’ve tried already and what result I expected
- ❓ Focus on one issue at a time – Especially in forums or group chats
- 🧭 Use questions to learn, not just solve – “Why does this work?” is just as important as “How do I fix this?”
Over time, I’ve seen how asking thoughtful, curious questions helps me grow faster. It also helps me connect with mentors, instructors, and teammates more effectively.

If you’re afraid of asking “dumb questions,” here’s the truth:
The only bad question is the one you’re too afraid to ask.

“Judge a man by his questions rather than his answers.”
— Voltaire
Stop Comparing—Your Tech Journey Is Your Own

June 22, 2025
In tech, there’s always someone who seems to know more, code faster, earn more certifications, or land a dream job before you do.

I’ve felt that pressure too—especially as a student and someone changing careers later in life. It’s easy to scroll online and feel like you’re already behind. But here’s what I’ve learned:
Comparison is a distraction. Progress is personal.

We’re all working from different starting points, with different responsibilities, schedules, and experiences. And that’s okay. Your path doesn’t have to look like anyone else’s to be valid—or valuable.

How I Shift My Mindset When Comparison Creeps In:
- 🧠 I focus on progress, not pace – I may be moving slower than others, but I’m still moving
- 📝 I track my milestones – Not just grades or certs, but also things like solving a tough problem or staying consistent
- ✋ I take breaks from social media when needed – Especially if it starts to feel overwhelming instead of inspiring
- 💬 I remind myself that growth is not a competition – The only person I need to be better than is who I was yesterday
You don’t need to be the fastest, the most advanced, or the most polished to succeed.
You just need to stay focused, stay steady, and stay true to your own timeline.

Remember: someone out there is looking at you and thinking, “Wow, I wish I had that kind of courage.”

“Don’t compare your chapter 1 to someone else’s chapter 20.”
— Unknown
Why Project Management and IT Go Hand in Hand

June 21, 2025
IT is about solving problems, building systems, and making technology work for people. But none of that happens in a vacuum.

Whether it’s deploying a new server, launching a website, or upgrading software across a company—every IT effort is a project. And like any project, it needs structure, planning, and follow-through to succeed. That’s where project management becomes essential.

As I’ve worked through my IT studies and learned more about Agile, Waterfall, Scrum, and other project management frameworks, one thing has become clear:
IT professionals who understand project management deliver better results.

How Project Management Supports IT Work:
- 🗂️ Scope control – Keeps IT tasks focused and prevents scope creep
- 🧩 Task breakdown – Helps turn big technical goals into smaller, actionable steps
- ⏰ Timelines and deadlines – Keep teams accountable and projects on track
- 🗣️ Stakeholder communication – Ensures clients, users, and leadership understand what’s happening
- 🔁 Change management – Guides teams through version control, rollouts, and updates
In my own journey, I’ve started using project management skills even as a student—planning my week, breaking down assignments, tracking study progress, and setting personal deadlines.

And in the real world, every IT team needs people who can not only build the solution—but also manage the process.

That’s why I see project management and IT not as separate tracks, but as two sides of the same coin.
“Plans are nothing; planning is everything.”
— Dwight D. Eisenhower
30 Posts In: I’m Just Getting Started

June 20, 2025
When I started this blog, I was stepping into the unknown. I wasn’t sure what to expect—or if anyone would even read what I had to say. But I knew I wanted to document the journey, not just the destination.

Now, 30 posts later, I’ve realized something powerful:
This isn’t just a blog—it’s my voice. My growth. My proof.

Over the past posts, I’ve written about doubt, discipline, certifications, leadership, teamwork, imposter syndrome, and starting over later in life. I’ve shared what it’s like to be a student, a career-changer, a learner, and a builder.

I may not have all the answers yet. I may still be learning, evolving, and reaching toward the next step. But I know this:
- I belong in this field
- I have what it takes to succeed
- I will keep showing up, no matter what
What’s Next?
- Continue growing in IT with focus areas like AI and cybersecurity
- Finish my degree with Capella University
- Complete my CompTIA A+ certification
- Build more real-world projects and share them here
- Help others see that it’s never too late to start
This blog isn’t the end of a journey—it’s a checkpoint. I’m proud of how far I’ve come, and I’m even more excited about where I’m going.

If you’ve been with me for one post or all thirty, thank you.
And if you’re just starting your own journey—you’re not alone. You’ve got this.

Here’s to the next chapter.
“The best way to get started is to quit talking and begin doing.”
— Walt Disney
Why Teamwork Matters in Tech (Even If You’re More Comfortable Solo)

June 19, 2025
Tech is often portrayed as a solo mission—just you, a computer, and some code. But the reality is, IT is a team sport.

Whether you’re building software, managing systems, supporting users, or implementing new technologies, you’re going to work with people. And not just other tech pros—managers, end users, clients, vendors. That’s why teamwork isn’t just a soft skill—it’s a survival skill in tech.

As someone who’s learning and growing in this field, I’ve started to realize how valuable collaboration is. Working with classmates, group projects, and leadership training through NSLS has helped me develop communication and trust—two things that can make or break a team.

What I’ve Learned About Teamwork in IT:
- 🤝 Clear communication is everything – Miscommunication causes more issues than bad code
- 🔄 Different roles, same goal – Not everyone speaks the same “tech language,” and that’s okay
- 🌱 Everyone brings something valuable – Even the newest learner can offer insight
- 🧠 Collaboration sparks better solutions – More perspectives = smarter outcomes
I still value focused solo work—but I now know that the ability to collaborate, give and receive feedback, and support a team is what turns a tech student into a tech professional.

In IT, the best solutions are rarely built alone.

“If you want to go fast, go alone. If you want to go far, go together.”
— African Proverb