DEV Community: Barbora Klusackova

Building Sprint Tracker #01

Barbora Klusackova — Thu, 29 Jan 2026 00:27:02 +0000

Introduction

This project starts from something very simple: a Google Form that collects sprint check‑ins and feedback, all ending up in a single spreadsheet.

Inside that sheet is a mix of important signals – who has finished their work, how confident people feel, and where someone might be struggling – but in its current form it’s hard to act on quickly. The aim of this series is to turn that spreadsheet into a small, reliable backend that makes those signals easier to see and work with.

I also want to use this project as a chance to experiment with spec‑driven development and with Kiro – an AI‑assisted IDE that helps me write requirements, designs, and tasks before I touch the actual implementation.

Step 1 – Starting from a spec (with Kiro)

Before writing any code, I asked Kiro to help me describe the system I wish existed. Instead of jumping straight into implementation, I worked through a spec‑driven flow: capturing requirements, shaping a design, and breaking things down into tasks I can actually build.

Kiro sits inside my editor and acts like a structured copilot: I can say “I have this form and I want to turn it into a marking/feedback tool” and it helps me turn that into a requirements document, a design with clear components, and a set of concrete tasks I can pick up one by one. It feels less like “write some code with AI” and more like “design the system together first, then implement”.

For this project, that ended up as three files:

requirements.md – what the tool should do, who uses it, and the acceptance criteria.
design.md – how the system is put together: main components, data model, and the AWS pieces it will use.
tasks.md – a checklist of implementation steps, each tied back to one or more requirements.

At this point I have a requirements file, a design document, and a generated task list – but still no running code. In the next part of this series, I’ll start turning that written design into a concrete architecture and the first implementation steps.

Devlog-OSS-Finder-03: Good First Issues and Testing

Barbora Klusackova — Mon, 26 Jan 2026 10:04:55 +0000

Date: January 26, 2026

Status: Feature Complete — Testing Added

What I Built

A major feature update that transforms OSS Finder from a repository search tool into a complete platform for open-source contribution discovery.

New Capabilities

Good First Issues page — Find beginner-friendly issues across GitHub
Tab navigation — Switch between Repositories and Issues views
TanStack Query caching — Smart data caching for better performance
Testing infrastructure — Vitest + Testing Library for both frontend and backend
Tests in CI/CD — Automated testing on every PR

What I Learned

Caching Is a Game-Changer (TanStack Query)

Before TanStack Query, every search hit the GitHub API:

User searches "react" → API call
User changes page → API call
User goes back to page 1 → API call again (even though we just fetched it)

Now with TanStack Query:

The first search triggers an API call (cached for 5 minutes)
Subsequent identical searches are instant (served from cache)
Automatic background refetching when data goes stale
Built-in loading and error states

Implementation was straightforward. I refactored useRepositories and created useIssues to use useQuery:

const { data, isLoading, error } = useQuery({
  queryKey: ['issues', params],
  queryFn: () => apiService.searchIssues(params),
  staleTime: 5 * 60 * 1000, // 5 minutes
})

Caching isn't just about performance — it's about respecting API rate limits and creating a snappier user experience. GitHub's API has strict limits, and unnecessary calls burn through them fast. Previously, I thought "I'll add caching later if needed." Now I understand: caching should be part of the architecture from the start, not a performance afterthought.

Testing

I added the testing stack and wired it into CI:

Vitest for frontend and backend
Testing Library for React
Tests + lint + format on every PR

Coverage is small, but the pipeline is there, so adding tests is cheap.

That’s it for this iteration: Good First Issue feature, caching is in, tests are running in CI, and the app is ready for the next round of features.

Cheers,
B.

Devlog-OSS-Finder-02: First Deployment Done

Barbora Klusackova — Fri, 23 Jan 2026 09:42:29 +0000

Date: January 23, 2026

Status: MVP Complete — Now Public

What I Built

A full-stack web application for discovering open-source repositories on GitHub.

Users can:

Search repositories by keyword
Filter by programming language
View repository stats and metadata

Live: https://open-source-finder-zeta.vercel.app/

GitHub: https://github.com/baradev/oss-repo-finder

Tech Stack

Frontend

React 19 + TypeScript
Vite
Tailwind CSS

Backend

Fastify + TypeScript
GitHub API integration
Environment configuration with dotenv

Dev Tools

ESLint + Prettier (code quality and consistency)
GitHub Actions (CI/CD pipeline)

What I Learned

Frontend / Backend Separation & Independent Deployment

Development

Backend runs on port :3001, frontend on :5173
Frontend communicates with backend via REST API (CORS configured)
Can develop and test each layer independently
Each has its own package.json and npm scripts

Deployment

Frontend → Deployed on Vercel (static/SPA hosting)
Backend → Deployed on Render (Node.js server)
Fully independent deployment pipelines
Environment variables configured for cross-service communication:
- VITE_API_URL — backend endpoint (frontend side)
- CORS_ORIGIN — allowed frontend domain (backend side)

Why This Matters

Enables separate scaling for frontend and backend
Allows frontend updates without redeploying backend
Supports different hosting strategies
Establishes a clean API contract between services

This is a meaningful shift from the monolithic apps I used to build — much more maintainable and scalable.

Building Microservices-Ready from the Start

I was recently asked about monolithic vs microservices architectures in an interview.

Though this project is small, I intentionally structured it for future flexibility.

The backend is already:

An isolated service with its own deployment
Exposes a clean REST API
Decoupled from the frontend
Scalable and replaceable without breaking the UI

If needed, it could evolve into multiple microservices (e.g., GitHub API service, search/cache service, authentication service) — all without touching the existing frontend.

Key takeaway: Start simple but structured. Avoid over-engineering, yet keep concerns separated from the start.

CI/CD with GitHub Actions

Implemented automated checks on every pull request:

Code formatting
Linting
Type checking
Build verification

This streamlined development flow ensures quality and consistency across pushes and pull requests.

What's Next

Add pagination (supported by backend, not yet in UI)
Implement sorting options (stars / updated / help-wanted)
Display total result count
Add automated tests
Experiment with EC2 backend deployment
Experiment with Kiro

Notes to Self

Plan workflows better — avoid unnecessary context switching and time loss
Continue focusing on clarity, separation, and maintainability in future projects

Devlog-OSS-Finder-01: Git Push Origin Comeback

Barbora Klusackova — Thu, 22 Jan 2026 09:45:48 +0000

Date: January 26, 2026

Status: Feature Complete — Testing Added

In 2025, I didn’t post a single blog. Everything felt so generated and inauthentic that I completely lost my passion for writing and sharing anything online.

It was also the year I landed my first developer role and started working full time. I had zero capacity for side projects. All my energy went into keeping up with my new job and learning how to survive as a dev.

And now here I am, fresh in 2026. I feel more confident in my role and I’m no longer spending every single minute preparing for the next workday. So I decided it’s finally time to come back to my project.

I’m a big fan of open source. When I first started shifting into tech, it was my partner who told me: “If you don’t have any experience and you need some, open source will be great for you.” And he was right. I learned a lot, contributed to real projects, grew as a developer, and got stuck many times along the way — in the best possible, learning way.

That’s also how my final project started when I was finishing my software development certificate: an idea to “somehow work with open source projects” by using the GitHub API.

So that’s what I’m going to be vlogging about in the upcoming months: building my own open source software.

This project is for my learning, first and foremost. I’ll be slowly adding more and more features, trying out new tools and patterns, and sharing what I learn as I go.

This is the first vlog of that journey, and you can follow along and learn with me.

Next time, I’ll share the repo with you, how I set it up, and how it looks right now.

Cheers, and happy New Year!
B.

Where to Start as a Developer New to AWS

Barbora Klusackova — Tue, 12 Nov 2024 23:19:34 +0000

My journey into tech began two years ago through the AWS Hapori Wahine program, which supports women in tech here in New Zealand. I started with Cloud Practitioner certification and later became Solutions Architect Certified. Although I had these certifications, I realised I lacked practical experience, so I decided to change that.

I enrolled in an intensive bootcamp for software developers, which prepared me to fully understand the potential of the cloud. Now, I’m excited to share my approach with you. Remember, everyone’s journey is unique, so feel free to take what resonates with you from this article.

In This Article, You Will Find:

Why Cloud?
Why AWS?
First Steps
Learn the Core
Explore Free Tier
Get Certified
Summary

Why Cloud?

There are countless reasons why individuals and companies choose cloud computing, but here are some of my favourites:

High Demand for Cloud Skills
Cost Savings
Pay-as-You-Go Pricing
On-Demand Access
Scalability
Global Reach

Why AWS?

It was easy for me! I didn't know any other cloud provider before I started my tech journey, and then I simply fell in love with AWS. I love the community, the services, and the customer obsession.

First Steps

To kick off your AWS journey:
Create Your Account: If you haven't already done so, set up your AWS account.
Set Up Billing Alerts: This helps you avoid unexpected charges.

Learn the Core

Ok, we set up the basics but what to do now? AWS has more than 200 services! It can be a bit overwhelming. My advice? Learn the core AWS services first.

Core services are building blocks, essential for most cloud applications. Here are the key ones to focus on:

EC2 (Elastic Compute Cloud)

What it does: Provides scalable virtual servers (compute capacity) in the cloud.
Why start here: It introduces you to concepts like regions, availability zones, instances, and security groups.

S3 (Simple Storage Service)

What it does: Scalable object storage for any type of data, from images and videos to backups.
Why start here: S3 is crucial for learning about storage solutions, data durability, and security.

RDS (Relational Database Service)

What it does: Allows users to run relational databases in the cloud.
Why start here: You learn about backups, scaling, performance optimisation, and how cloud databases differ from traditional setups.

IAM (Identity and Access Management)

What it does: Manages user access and permissions in AWS - who should be seeing what.
Why start here: Security is a priority in cloud services. Learning IAM teaches you about user roles, permissions, and best practices for securing your AWS resources.

Explore Free Tier

Take advantage of the AWS Free Tier, which allows users to explore and experiment with various AWS services at no cost, within certain usage limits.

Get Certified

This is the point I would approach differently next time, and I would recommend it to anyone. I started with the certifications and then focused more on hands-on experience. Believe me, everything in the exams makes much more sense when you have built something beforehand; learning becomes more meaningful, and it is easier to prepare for the exam! Certifications look great on LinkedIn and in your CV, but real skills, are essential!

My favourite resources

Summary

Understand the value of cloud computing
Choose AWS and familiarise yourself with its ecosystem
Set up your account and billing alerts
Focus on core services (EC2, S3, RDS, IAM)
Utilise the Free Tier for hands-on practice
Consider certifications to validate your knowledge

Remember, the key to success in AWS is continuous learning and hands-on experience. Embrace the journey, and don't be afraid to build and experiment along the way.

Good luck on your AWS journey! ☁️

Feel free to connect with me on LinkedIn 😊

AWS Certification Prep Tips

Barbora Klusackova — Sun, 30 Jun 2024 23:46:57 +0000

Hello everyone, Barbora here!

In 2022, I enrolled in the She Builds program here in Auckland, New Zealand. At that time, I was a stay-at-home mom with two little kids, no tech background, and searching for a new challenge on my career path. The She Builds program changed my life. In four weeks, I became an AWS Certified Cloud Practitioner. A year later, I became an AWS Solutions Architect Certified, and in 2024, I graduated as a Software Developer! Since then, AWS has become my favourite brand. Here is how I tackled my certification exams.

AWS Certified Cloud Practitioner

(CLF-CO2) Exam

Who should take this exam, and why?

This exam is an excellent starting point for anyone looking to use AWS services, especially those with minimal or no prior experience. In today's environment, there are high expectations for Junior Developers and cloud knowledge is often seen as an advantage. Obtaining certifications can help you stand out from other candidates.

How long does the preparation take?

I prepared for this exam with four weeks of intensive learning. I didn’t have any AWS or tech experience before. This time frame might be a bit tight for newbies, so take your time. However, schedule a due date if you want to take this commitment seriously. Mark in your calendar when you want to finish your learning, or even better, the day you want to take your exam. I decided I wanted to take the exam in four weeks, so I set up my learning plan and booked the exam (yes, I like to be a little bit under pressure 😅).

From which resources did I learn?

There are many approaches to preparing for the exam. One of the most important things is to choose your learning path and stick to it. There are so many resources and people who can give you plenty of advice that you might start to feel nervous in the middle of your learning journey, wondering if you are following the best approach. So, stick to your chosen approach and do not jump from one resource to another. Also, consider finding a study buddy, this can make a big positive difference in your learning journey.

I started with official AWS study materials - some of them are free, and some of them are open with a subscription.
I used these two free resources:

The other part of my learning involved using the Tutorial Dojo Tests, which I purchased on Udemy. There are six tests in the package. Once you finish a test, you can go through each question with detailed explanations about why the correct answer is right and why the others are not. I learned the most from this process. After going through the explanations for every question from the first test, I applied the same approach to the rest of them. My pace was two tests per week.

Whenever an AWS service was mentioned in a test, I went to the console to explore it further. This hands-on practice helped me understand the services better. I believe this part is crucial for future success—while the certificate looks great on LinkedIn, what really matters are the actual skills and knowledge.

I started with a 42% success rate on the first test 😬. By the time I finished the last one, I had reached 82%, showing significant improvement.

It's important not to try to memorize the questions and answers, as the official exam questions are similar but not identical. AWS tests are designed to ensure a genuine understanding of the concepts.

👩‍💻 Exam Day

You have the option to choose between taking the exam from home or at a testing centre. If you decide to take it from home, you need to ensure your internet connection is stable, there are no interruptions, and you'll have to show your surroundings to the supervisor by moving your computer around the room. Personally, I opted to take the exam at a testing centre for convenience and peace of mind. I received my result in 42 hours.

How much does the exam cost?

As of June 30, 2024, the exam costs $100 USD. Sometimes AWS offers discounts for Cloud Practitioner exams, especially when you participate in programs like She Builds or similar. Last year, there was an opportunity to retake the exam for free, but I'm uncertain if this option is still available. If you need to retake your exam, before purchasing another voucher, consider researching this option through Google or asking in the AWS community or on LinkedIn.

There is a chance that you may not pass the exam. It can be disappointing, I know. Once you receive the results, you'll see the areas where you weren't successful. This will guide you on what to focus on when reviewing. If this happens, don't give up. I know many fantastic people who didn't pass on their first try but succeeded on their second attempt.

Recap

Build a learning plan and set a deadline
Stick to your learning path
Find your exam buddy - this can really help!
Do not memorize questions and answers
Hands-on practice in AWS Console
Share your Certificate Badge!!

Conclusion

Remember, certification exams can be challenging, but they are also opportunities for growth. Whether you pass on your first attempt or not, each step in your learning journey matters. Stay focused, utilize the resources available to you, and don't hesitate to reach out to the vibrant AWS community for support and guidance.

Best of luck on your certification journey! Embrace the challenge, celebrate your progress, and keep striving for your goals in cloud computing and beyond!!

DEV Community: Barbora Klusackova

Building Sprint Tracker #01

Introduction

Step 1 – Starting from a spec (with Kiro)

Devlog-OSS-Finder-03: Good First Issues and Testing

What I Built

New Capabilities

Links

What I Learned

Caching Is a Game-Changer (TanStack Query)

Testing

Devlog-OSS-Finder-02: First Deployment Done

What I Built

Tech Stack

Frontend

Backend

Dev Tools

What I Learned

Frontend / Backend Separation & Independent Deployment

Development

Deployment

Why This Matters

Building Microservices-Ready from the Start

CI/CD with GitHub Actions

What's Next

Notes to Self

Devlog-OSS-Finder-01: Git Push Origin Comeback

Where to Start as a Developer New to AWS

In This Article, You Will Find:

Why Cloud?

Why AWS?

First Steps

Learn the Core

EC2 (Elastic Compute Cloud)

S3 (Simple Storage Service)

RDS (Relational Database Service)

IAM (Identity and Access Management)

Explore Free Tier

Get Certified

My favourite resources

Summary

AWS Certification Prep Tips

Hello everyone, Barbora here!

AWS Certified Cloud Practitioner

Who should take this exam, and why?

How long does the preparation take?

From which resources did I learn?

👩‍💻 Exam Day

How much does the exam cost?

Recap

Conclusion

Resources List

Other good quality resources for consideration which I didn't use but my friends did!

People and Pages to Follow

AWS Meetups in Auckland