DEV Community: The Duchess of Hackers

Linux Week 2: Learning, Practicing & Figuring Things Out

The Duchess of Hackers — Mon, 28 Sep 2026 04:53:23 +0000

Last week, I shared my first update from my Linux journey with Akwannya Hub’s Skill Pods, where I had just completed Chapters 1–3.
This week, I moved on to Chapters 4–6, and honestly, I’m starting to feel a little more comfortable with the terminal.
Open Source finally started making more sense to me.

I learned more about what happens behind the software we use and what it actually means for something to be open source.
GPL, copyleft, FOSS, FSF, OSI and Creative Commons were some of the things I came across. At first, it was a lot of new terms 😭, but breaking them down slowly helped.
Then came more command-line practice.

I worked with commands like:
echo — displays text or values
history — shows commands I’ve used before
type — tells me what type of command something is
which — shows where a command is located
man — opens the manual for a command

And Chapter 6 taught me something I really needed to know:
I don't have to know everything. I just need to know how to find help. 😂
I learned how to use:
man ls → read the manual for a command
whatis → get a quick description
man -k / apropos → search for help by keyword
whereis → find a command and its documentation
locate → find files and directories
info → get more detailed documentation
--help → get quick help from the terminal

I also did the labs and actually typed the commands myself instead of just reading about them. I’ll be adding some screenshots from my practice because chale, seeing the commands actually work makes a difference. 😂
The challenging part is still the amount of new vocabulary. Sometimes I'm reading something and thinking, “Wait, what does this one mean again?” 😭
But I’m learning that I don't need to rush. I read, practice, get confused, check the documentation, try again… and eventually it starts to click.

My biggest takeaway from these three chapters?
Linux isn't about memorising every command. It's about understanding what you're doing and knowing how to find your way when you don't know something.

Linux #LinuxEssentials #OpenSource #Cybersecurity #TechJourney #AkwannyaHub #SkillPods

From "What's a Kernel?" to Actually Using the Terminal — My Linux Week 1 (Chapters 1–3)

The Duchess of Hackers — Mon, 21 Sep 2026 04:35:01 +0000

I've been going through Linux Essentials as part of Akwannya Hub's Skill Pods, and this is a write-up of what stuck from chapters 1–3: understanding Linux, the terminal, package management, security, and virtualization.

1. Linux is a kernel, not an OS

The first thing that reframed everything for me: Linux itself is just the kernel — the core layer that talks to hardware and manages system resources (CPU, memory, processes).

What we call "Linux" day-to-day (Ubuntu, Debian, Fedora) is actually a distribution — the kernel bundled with a package manager, utilities, and often a desktop environment.

2. GUI vs CLI, and the commands I actually used

A GUI lets you interact through windows and clicks. A CLI means typing commands directly to the shell. Servers and sysadmin work lean heavily CLI-first, since it's faster and scriptable.

Commands I practiced:

pwd     # print current working directory
ls      # list files/folders in current directory
cd      # change directory
mkdir   # create a new directory
touch   # create a new empty file
cat     # print a file's contents to stdout

Basic, but typing them repeatedly is what made the mental model click — not just reading about them.

3. Shells and editors

The shell is the interface between the user and the kernel — it parses your commands and passes them along for execution. Bash is the default on most distros, though zsh, ksh, and tcsh exist too.

I also got introduced to terminal-based editors: nano (simple, beginner-friendly) and vim (powerful, steep learning curve). Learning at least one terminal editor is apparently non-negotiable for serious Linux/server work.

4. Package management, by distro family

Debian-based (Ubuntu, Mint, Debian itself):

apt install <package>
dpkg -i <package>.deb

RPM-based (Fedora, RHEL, CentOS):

yum install <package>
rpm -i <package>.rpm

The part that clicked for me: a package manager's real job isn't just "install this," it's resolving dependencies — making sure everything the software needs is present before it runs.

5. Security basics

Root has full system privileges, so managing who gets root (and how) is central to Linux security. Beyond that: strong passwords, 2FA, permissions, encryption, HTTPS, VPNs, and firewalls.

On Ubuntu specifically, UFW (Uncomplicated Firewall) handles this at the CLI, and Gufw gives it a GUI. Good security, as I learned it, is less about a single tool and more about consistent habits around access and updates.

6. Linux in the cloud, and virtualization

Cloud computing runs on servers, storage, and compute resources — deployed as public, private, community, or hybrid models. Linux dominates here because it's open-source, scalable, cost-effective, and automatable.

Virtualization ties into this: a host machine runs multiple guest VMs via a hypervisor, letting one physical machine do the work of several. This is also the conceptual root of container tech like Docker and Kubernetes — different implementation, same underlying idea of resource isolation.

Takeaways

The concepts weren't hard individually — the vocabulary density was. Kernel, shell, hypervisor, repository, dependency, distro — a lot of new terms in a short span. Breaking each one down to "what does this actually do" helped more than trying to memorize definitions.

Also: reading about Linux and using Linux are very different learning curves. Typing the commands, even the trivial ones, is what made this stick.

Chapters 4+ next. 🐧

must read!!!

The Duchess of Hackers — Tue, 28 Jul 2026 18:37:59 +0000

The Duchess of Hackers

Jul 28

How to Actually Spot Phishing (Before It Spots You)

#cybersecurity #defence #awareness #duchesswrites

2 min read

How to Actually Spot Phishing (Before It Spots You)

The Duchess of Hackers — Tue, 28 Jul 2026 18:37:44 +0000

Hi Cyber Lovers

We talked tools last time, but honestly? No tool protects you as much as your own awareness. And phishing is still the #1 way people get hacked, not because attackers are geniuses, but because phishing plays on trust, urgency, and a moment of not paying attention.

I've almost fallen for one myself. So let's break down what to actually look out for.

1. Check the Sender, Not Just the Name

Names can be faked. Email addresses tell the real story.

"Support Team" can still come from a random Gmail address
Look closely for misspelled domains — paypa1.com instead of paypal.com
Hover over the sender name to see the actual email

Tip: If something feels slightly "off" about the sender, trust that instinct and dig deeper.

2. Watch for Urgency and Pressure

Phishing thrives on panic.

"Your account will be suspended in 24 hours"
"Immediate action required"
"You've won something — claim now"

Tip: Real companies rarely give you a countdown to act. Urgency is a red flag, not a reason to rush.

3. Inspect Links Before You Click

This one habit alone saves you constantly.

Hover over links to preview the actual URL
Look for slight misspellings or extra characters
If it looks weird, don't click — go to the site directly instead

Tip: On mobile, press and hold a link to preview it before tapping.

4. Be Wary of Unexpected Attachments

Especially ones you didn't ask for.

Invoices, receipts, or documents "you need to review"
Files from senders you don't recognize
Attachments paired with urgent language (see #2 👀)

Tip: When in doubt, confirm with the sender through a different channel before opening anything.

5. Trust Your Gut, Then Verify

If something feels a little too convenient, or a little too urgent, or just... not quite right:

Don't click, don't reply, don't download
Go directly to the official website or app instead
Report and delete

Tip: It's always safer to double-check than to explain a mistake later.

A Little Reminder

Phishing isn't about being "smart enough" to avoid it , even experienced people get caught off guard sometimes. It's about slowing down for those extra five seconds before you click.

Up Next

Next post, we're going deeper into password security , why "strong passwords" aren't actually enough anymore, and what to do instead.

Stay curious, stay consistent

The Duchess of Hackers
Full-Stack Developer | Digital Marketer | Cybersecurity Enthusiast

Check out my latest write-up on CoderLegion: "Essential Cybersecurity Tools Every Beginner Should Know" Read the full article here: https://coderlegion.com/23098/essential-cybersecurity-tools-every-beginner-should-know #DevCommunity #Tech

The Duchess of Hackers — Mon, 20 Jul 2026 23:23:25 +0000

Essential Cybersecurity Tools Every Beginner Should Know - Coder Legion

Last time we talked about building your roadmap. Today, let's get practical , what tools should you actually start with? When I began, I made the mistake of thinking I needed Kali Linux, ten different scanners, and a whole hacker setup on day one. You...

coderlegion.com

Check out my latest write-up on CoderLegion: "How I’m Building My Cybersecurity Learning Routine (Without Getting Overwhelmed)" Read the full article here: https://coderlegion.com/21094/how-im-building-my-cybersecurity-learning-routine-without-getting-

The Duchess of Hackers — Mon, 22 Jun 2026 01:00:14 +0000

coderlegion.com

Check out my latest write-up on CoderLegion: "Why Should a Login Screen Be Boring? — Building StreakFlow" Read the full article here: https://coderlegion.com/19696/why-should-a-login-screen-be-boring-building-streakflow #DevCommunity #Tech

The Duchess of Hackers — Thu, 04 Jun 2026 20:35:49 +0000

Why Should a Login Screen Be Boring? — Building StreakFlow - Coder Legion

So I kept asking myself… why should a login screen be boring? I’ve been working on something called StreakFlow — a habit tracker, streak counter, and reflection journal. I built it because honestly, spreadsheets and random notes just weren’t...

coderlegion.com

Access Granted: Breaking Barriers as the Duchess of Hackers

The Duchess of Hackers — Sun, 05 Apr 2026 22:06:04 +0000

Inspiration

When I think about gender equity in tech, I don’t just think about inclusion I think about access.

For a long time, women have had to fight to be seen, heard, and given opportunities in the tech space. It often feels like there are invisible barriers like systems that say “access denied.”

So I decided to represent this idea using something I’m passionate about: cybersecurity and ethical hacking.

In my project, the user starts in a restricted system.

They have to attempt access, symbolizing the effort, resilience, and courage it takes to break into spaces that weren’t always built for us.

As the system runs, it simulates:

bypassing security
decrypting barriers
breaking the “glass ceiling”

And finally:

ACCESS GRANTED

This moment represents more than just entry it represents belonging, growth, and power.

The final reveal The Duchess of Hackers — is a symbol of identity, confidence, and ownership in tech.

It’s a reminder that:

Women are not just asking for space in tech…

we are building, securing, and leading it.

My Code

You can view and interact with my project here:

👉 https://codepen.io/gracequaye1/pen/VYKMzwq

Final Thought

Gender equity in tech is not just about opening doors

it’s about breaking barriers and redefining who gets to lead.

We are not waiting for access.

We are claiming it.

Signature:
The Duchess of Hackers
Full-Stack Developer | Digital Marketer | Cybersecurity Enthusiast

Becoming the Duchess of Hackers: My Journey Through Tech, Cybersecurity, and Growth

The Duchess of Hackers — Mon, 23 Mar 2026 00:21:44 +0000

When I first stepped into tech, I was overwhelmed.

There were so many paths frontend, backend, UI/UX, cybersecurity and I didn’t know where I truly belonged.

It felt like everyone else had it figured out… except me.

I started with backend development, trying to understand how systems work behind the scenes. Later, I explored frontend, and eventually found myself growing into full-stack development.

But I didn’t stop there.

I became curious about how systems are protected and how they can be broken. That curiosity led me into cybersecurity and ethical hacking, where I began learning how to think like both a builder and a defender.

The truth is it wasn’t a smooth journey.

Moments I doubted myself
Moments I compared my progress to others
Moments I felt like I was moving too slowly

Still, I didn’t stop.

Through learning, practice, and opportunities like Tech4Girls, PLP, I began to grow not just in skill, but in confidence.

I also discovered something powerful:

Tech is not just about coding.

With my background in digital marketing, I started helping small businesses grow — combining tech with real-world impact. That’s when everything began to make sense.

Today, I’m not just learning how to build systems —

I’m learning how to secure them, improve them, and use them to create impact.

I’m still learning. Still growing. Still becoming.

But one thing has changed I now believe I belong here.

What I’ve Learned

You don’t need to have everything figured out from the start
Growth is not a race — it’s personal
Exploring different paths can help you discover your true strength
Tech is broad — there is space for all your interests

To Every Girl in Tech

It’s okay to feel lost sometimes.

It’s okay to start small.

What matters is that you keep going.

Whether you’re coding, designing, securing systems, or still figuring things out

there is space for you here.

Your voice matters.

Your journey matters.

And one day, your story will inspire someone else too.

Final Thought

We are not behind. We are building.

Signature:
The Duchess of Hackers
Full-Stack Developer | Digital Marketer | Cybersecurity Enthusiast

My Journey Into Cybersecurity: A Beginner’s Guide

The Duchess of Hackers — Mon, 12 Jan 2026 20:41:16 +0000

When I first started learning cybersecurity, I had no clue where to begin. I was just a developer curious about protecting data, systems, and people. It felt overwhelming at first, but I quickly realized something: you don’t have to be perfect to start you just have to start.

What Cybersecurity Really Is

Cybersecurity is the practice of protecting and recovering data, networks, devices, and programs from threats. These threats can target digital systems, people, or even physical assets.

At the core of cybersecurity are three main objectives, called the CIA triad:

Confidentiality: Keeping information private
Integrity: Ensuring information stays accurate and unaltered
Availability: Making sure systems and data are accessible when needed

Understanding these three goals gives you a solid foundation to begin your journey.

Tips From My Experience

Start small: Experiment in labs, virtual machines, or safe environments.
Document your progress: Keep notes of what you learn.. even mistakes count.
Learn consistently: Daily or weekly practice beats cramming.
Follow the community: Cybersecurity enthusiasts, blogs, and forums are goldmines.

A Little Encouragement

Cybersecurity can feel intimidating I know it did for me. But every step you take, no matter how small, builds your confidence and skill. Mistakes aren’t failures; they’re lessons.

You don’t have to be an expert today. You just have to stay curious, keep learning, and keep growing.

Up Next:
In my next post, I’ll break down the key elements of cybersecurity what I’ve learned, tips that actually work, and how to build a strong foundation for your journey.

Stay tuned, stay motivated, and remember: every small step counts.

Signature:

The Duchess of Hackers

Full-Stack Developer | Digital Marketer | Cybersecurity Enthusiast

If You Learn to Code, Who Will You Teach?

The Duchess of Hackers — Mon, 22 Dec 2025 23:08:14 +0000

A Conversation Every Learner Should Be Having

If you’re learning how to code right now, let me ask you one simple question:

Who are you learning it for..just yourself, or others too?

Because coding isn’t just a personal skill.
It’s a transferable power.

And when knowledge is shared, impact multiplies.

Why Learning Coding Isn’t Enough

Learning to code is great.
Building projects is amazing.
Getting better every day? Even better.

But the real magic happens when you pass it on.

When you explain a concept to someone else:

You understand it deeper
You simplify complex ideas
You build confidence (yours and theirs)

Teaching doesn’t require perfection.
It only requires willingness.

My Take: Learn → Practice → Teach

This is the cycle I believe in:

1️⃣ Learn something new

2️⃣ Practice it until it makes sense

3️⃣ Share it in the simplest way possible

You don’t need a classroom.
Sometimes it’s just:

a WhatsApp message
a short post
a quick explanation to a friend

That’s how communities start.

Coding Is a Tool for Impact

Coding isn’t just about writing syntax.
It’s about:

opening doors
solving problems
helping others believe “I can do this too”

When one person learns and teaches another, the ripple effect begins.

Over to You

If you’re learning to code today:

Who could you help tomorrow?
What simple thing could you explain?
What impact could your knowledge create?

That’s how real tech communities grow
one person learning, one person teaching, one person inspiring.

The Duchess of Hackers

Full Stack Developer | Digital Marketer | Community Builder

If You Could Add ONE Feature to a Design Portfolio, What Would It Be?

The Duchess of Hackers — Sat, 13 Dec 2025 03:11:50 +0000

A Conversation Every Designer Should Be Having
If you were building your design website or portfolio today, let me ask you one simple question:

What’s the one feature you’d add to make it truly stand out?

Not ten features.
Not “everything.”

Just one.

Because in design, clarity always beats clutter.

Why This Question Matters
Most portfolios look… fine.

Clean layouts.
Nice mockups.
A few case studies.

But fine doesn’t always get remembered.

The portfolios that stand out usually have one strong moment — something that makes a visitor pause and think:

“Okay… this designer knows what they’re doing.”

My Pick: A Live Before/After Slider
For me, it’s simple.

A live Before/After slider.

Why?

Because nothing sells skill like visible transformation.

Seeing:

the raw version
the improved design
the thinking behind the change
tells a stronger story than words ever could.

It shows problem-solving, not just aesthetics.

Design Is About Impact, Not Decoration
Good design doesn’t just look good — it works better.

A standout portfolio feature should:

show your thinking
prove your value
communicate impact quickly
Whether it’s motion, interaction, storytelling, or clarity — the goal is the same:
make your skill undeniable.

Now, Over to You
(I’m curious to hear how other designers think about this — what would you add?)

If you were designing your own portfolio today:

What single feature would you add?
What would make your work unforgettable?
What would show how you think, not just what you make?
Your idea might inspire another designer reading this.

And that’s how communities grow — one shared insight at a time.

Signature:

The Duchess of Hackers

Full-Stack Developer | Digital Marketer