DEV Community: bala

Which cloud certification should you get first? AWS vs Azure vs Google Cloud (and how to study for it)

bala — Mon, 02 Nov 2026 12:14:26 +0000

"Which cloud cert should I do first?" is one of the most common questions in every cloud community. The honest answer is: it depends on three things — which cloud you'll actually use, the role you want, and how much hands-on experience you already have. This post walks through how to decide, and then how to study so you don't waste weeks rewatching videos.

Step 1: Pick the cloud before you pick the cert

Don't choose a provider because a cert looks easy. Choose the one you're most likely to touch at work.

Your company or target employers already use a cloud? Start there. A cert on the platform you use every day is easier to pass (you get free practice) and easier to talk about in interviews.
Job listings in your area mention one cloud more than others? Search the roles you want and count. That's better data than any internet opinion.
Your organisation runs on Microsoft 365, Active Directory or Windows servers? Azure is usually the natural fit.
You work with data/analytics teams already on BigQuery or Google Workspace? Google Cloud makes sense.
No signal at all? AWS is a reasonable default simply because it shows up in a lot of job descriptions — but confirm with your own search.

Step 2: Fundamentals or associate?

Each provider has an entry-level "fundamentals" exam and a more hands-on "associate" tier.

Cloud	Fundamentals	First associate
AWS	Cloud Practitioner (CLF-C02)	Solutions Architect Associate (SAA-C03) or Developer Associate (DVA-C02)
Azure	AZ-900 (also AI-900 for AI basics)	Administrator (AZ-104)
Google Cloud	Cloud Digital Leader	Associate Cloud Engineer

Take the fundamentals exam first if:

You're new to IT or switching careers.
You're in a non-engineering role (sales, PM, support, finance) and need the vocabulary.
You want a quick win to build momentum.

Skip straight to an associate exam if:

You've already deployed things in that cloud — even side projects.
You're a developer or sysadmin with networking and Linux basics.
Your goal is a technical job and you'd rather spend the study time on the cert employers ask for.

Fundamentals exams test concepts, billing and shared responsibility. Associate exams test whether you can design or operate something: networking, IAM, storage choices, scaling, troubleshooting.

Step 3: Match the associate cert to the role

Architect / generalist cloud engineer: AWS SAA-C03, Azure AZ-104, or Google Associate Cloud Engineer.
Developer: AWS DVA-C02 fits if you build on Lambda, API Gateway and DynamoDB.
Platform / DevOps: after a cloud associate, look at Terraform Associate (infrastructure as code) and CKA (Kubernetes). Both are cloud-neutral, so they pair with whichever provider you chose.
Support moving into cloud: fundamentals first, then the admin/associate track on the cloud your employer uses. Your troubleshooting experience counts — put it on your CV next to the cert.

If you want a quick answer for your situation, I built a free picker that asks those three questions (cloud, role, experience) and suggests where to start: Which cloud certification should I get first? — no login.

Step 4: Study with timed practice, not just videos

The most common mistake I see: watching an entire course twice, then booking the exam and discovering you can't answer questions under time pressure. Flip the order.

1. Take a practice quiz on day one

Before studying anything, do a short timed quiz. You'll score badly — that's the point. It shows you which domains you know nothing about, so you study those first instead of everything evenly.

2. Study by domain, then re-quiz that domain

Every exam guide lists domains (for example security, networking, storage, billing). Work through one, then immediately answer questions on it. If you can't explain why the wrong options are wrong, you haven't learned it yet.

3. Read every explanation — including for questions you got right

Lucky guesses feel like knowledge. Reading the explanation for each answer catches them.

4. Do it timed

Cloud exams are long, and scenario questions take time to read. Practising untimed hides a real weakness. Give yourself a fixed time per question and stick to it.

5. Build one small thing

Reading about VPCs and IAM is not the same as wiring them up. Even a tiny project helps a lot:

AWS: a static site on S3 + CloudFront, then a small app behind a load balancer.
Azure: a VM in a VNet with an NSG, plus a storage account with role-based access.
Google Cloud: a GKE or Cloud Run deployment with IAM set up properly.

Use free tiers and budget alerts so you don't get a surprise bill.

6. Decide you're ready with evidence

Book the exam when your practice scores are consistently comfortable across all domains — not just your average. One weak domain can sink a pass.

A simple 4–6 week plan (adjust to your hours)

Week 1: Diagnostic quiz, read the official exam guide, list your weak domains.
Weeks 2–4: One or two domains per week: learn, build, quiz, review explanations.
Week 5: Full timed practice sets, revisit anything still weak.
Week 6 (optional buffer): Final review, exam-day logistics (ID, room setup for online proctoring, system check).

People with existing experience often need less; career switchers often need more. That's fine — consistency beats intensity.

Free tools to try

Everything below is free and needs no account:

Free practice quizzes — 10-question quizzes with explanations for CLF-C02, SAA-C03, DVA-C02, AZ-900, AZ-104, AI-900, Cloud Digital Leader, Associate Cloud Engineer, CKA, Terraform and more.
Study plan generator — a week-by-week plan from your exam date and weekly hours.
Exam readiness calculator — enter practice scores and study hours for a transparent estimate.
Exam day checklist — for online proctored and test-centre exams.

If you want daily practice, the free ExamPro plan includes 50 practice questions a day, 30 flashcards a day and 3 free lessons per course: create a free account.

TL;DR

Pick the cloud you'll actually use.
Fundamentals if you're new or non-technical; associate if you've built things.
Match the associate cert to the role you want.
Quiz first, study weak domains, read explanations, practise timed, build something small.

Which cert did you start with, and would you choose the same one again? Let me know in the comments.

How to Split Utilities With Roommates Fairly (Without the Monthly Argument)

bala — Mon, 02 Nov 2026 12:10:59 +0000

Rent is easy. It's a fixed number, written in a lease, and everyone knows it before they move in. Utilities are where flatmate friendships go to die. The electricity bill doubles in winter, someone works from home with three monitors, and someone else showers for 40 minutes. By month three, nobody is sure who paid the internet bill, and everyone feels quietly cheated.

Here's how to split utilities with roommates fairly, which method to pick for your flat, and how to keep it from turning into a monthly argument.

Step 1: Agree on what counts as a "utility"

Before you split anything, write a list. Most flats share some mix of:

Electricity
Gas or heating
Water and sewage
Internet and Wi-Fi
Streaming subscriptions
Trash or building maintenance fees
Shared household supplies (toilet paper, dish soap, cleaning products)

Decide together which of these are shared and which are personal. A streaming service only one person watches isn't a utility. It's their subscription. Getting this list agreed on day one prevents most fights later.

Step 2: Pick a split method that matches your flat

There's no single "fair" split. Fair means everyone agrees the method makes sense for how you actually live. These are the four methods that work.

1. Even split

Total bill divided by number of people. Simple, fast, and it works well when everyone has a similar room, a similar schedule and similar usage.

Best for: flats where people live similar lives, and bills that don't vary much, like internet.

2. Split by room size

If one person has the master bedroom with an en-suite and the others have small rooms, many flats split rent and heating by square footage. A 55/45 or 40/30/30 split is common.

Best for: flats with clearly unequal rooms, and heating and cooling costs, which scale with space.

3. Split by usage

When usage is very different, like one person working from home all day while others are out, split electricity by estimated usage. You don't need smart meters. A rough agreement such as "remote worker covers 40% of electricity, others split the rest" is enough.

Best for: electricity, when one person runs heavy equipment, a home office or a gaming PC.

4. Split by days present

If someone travels half the month, a fair approach is to weight their share by nights at home. This works best for variable bills like water and gas, not fixed ones like internet.

Best for: flats with frequent travellers or partners who stay over often.

Tip: you can mix methods. Many flats split internet evenly, heating by room size and electricity by usage. That's fine as long as it's written down.

Step 3: Decide who pays the provider

Usually one person's name is on each account. That person pays the full bill and everyone else pays them back. Problems start when:

The account holder forgets to tell everyone the amount.
People pay back at different times, or partially.
Nobody remembers whether last month was settled.

Spreading accounts across people helps. One person holds electricity, another internet. That way no single person is fronting all the money.

Step 4: Track every bill in one shared place

This is the step most flats skip, and it's the one that matters most. Memory and WhatsApp scroll-back aren't a ledger. You need one place where:

Every bill gets logged with the amount and who paid it.
The agreed split is applied automatically.
Everyone can see a running balance of who owes whom.

A shared spreadsheet works if someone is disciplined about it. Most flats find a simple app easier, because nobody has to maintain formulas.

IPaid was built for exactly this. You add a bill, choose an even or custom split (like 55/45), and everyone sees what they owe. You can share a public settle-up page with your flatmates on WhatsApp, and they can join the flat in one tap. It's free, with no card needed.

Step 5: Settle up on a fixed day

Pick a day, like the 1st of each month or the day rent is due, and settle all balances at once. A fixed date turns "can you pay me back?" from a personal request into a routine. Nobody has to be the nag.

Step 6: Review the split every few months

Life changes. Someone gets a remote job, someone's partner moves in half-time, winter arrives. Every three months, look at the numbers and ask: does this still feel fair? Adjusting early is far easier than resenting quietly for a year.

Common situations, and fair answers

"My roommate's partner basically lives here." If they're over more than three or four nights a week, it's reasonable to ask them to chip in on utilities. Water, electricity and supplies are the usual ones. Raise it early and frame it around the bills, not the person.

"One of us uses way more electricity." Agree a usage-based split for electricity only, and keep everything else even.

"Someone moved out mid-month." Pro-rate by days for variable bills. For fixed bills, follow whatever the move-out agreement says. If it says nothing, pro-rating is the fairest default.

"Someone keeps paying late." A shared, visible balance does most of the work here. When everyone can see the number, late payers usually catch up without a confrontation.

The short version

List which bills are shared.
Pick a split method per bill: even, room size, usage or days present.
Spread the accounts so no one fronts everything.
Log every bill in one shared place.
Settle on a fixed day each month.
Review every quarter.

Fairness between roommates isn't about perfect maths. It's about a method everyone agreed to, and a record nobody has to argue about.

Ready to stop doing bill maths in your head? Set up your flat on IPaid for free. It takes about two minutes, and your flatmates can join from a link.

How to tell a client no to extra work (and keep the client)

bala — Mon, 02 Nov 2026 11:49:09 +0000

"Can you just add one small thing?"

Every freelancer has heard it. The small thing is rarely small, and it's never just one. Say yes too many times and a fixed-price project quietly becomes unpaid overtime. Say no badly and you risk the relationship.

The good news: you almost never need to say a flat "no". You need to say "yes, and here's what it costs", in a way that feels professional rather than defensive. Here's how.

Why saying no feels so hard

Most freelancers struggle with this for three reasons:

Fear of losing the client. Especially when the pipeline is thin.
The request seems tiny. Refusing a 20-minute task feels petty, until there are fifteen of them.
No clear scope. If the original agreement was vague, you can't point to what's in and what's out.

The fix for all three is the same. Make the scope explicit, and turn every extra request into a choice the client makes, not a favour you grant.

Step 1: Know your scope before the request arrives

You can't defend a boundary you never drew. Every project should have a written scope covering:

The deliverables, listed specifically.
How many rounds of revisions are included.
What's explicitly out of scope.
What happens when new work is requested, like a change order at your hourly or day rate.

That last line is the most important sentence in your contract. It means that when the "small thing" arrives, you're not improvising a policy. You're following one the client already agreed to.

Step 2: Don't answer immediately

When a client asks for extra work on a call or in a message, the pressure is to say "sure" on the spot. Don't. A simple holding reply buys you time:

"Good idea. Let me check how that fits with the current scope and timeline, and I'll come back to you today."

This isn't stalling. It's what professionals do. It also gives you time to estimate the work properly.

Step 3: Use "yes, and" instead of "no"

The most effective way to tell a client no to extra work is to not say no at all. Offer options instead. Here are three scripts you can adapt.

Script 1: The change order

"Happy to add that. It's outside the original scope, so I've estimated it at 4 hours, which is $320. If you approve, I'll start after the current milestone, and it moves delivery by two days. Want me to go ahead?"

Script 2: The trade-off

"We can absolutely include that. To keep the same budget and deadline, we'd need to drop or simplify X. Or I can add it as a separate item at $Y. Which would you prefer?"

Script 3: The phase two

"That's a great addition. Rather than squeezing it into this phase and risking quality, let's put it on the list for phase two. I'll send a quick quote so you can plan for it."

Each of these says yes to the client's goal and is clear about the cost. The client stays in control, and you stay paid.

Step 4: When the answer really is no

Sometimes the request is outside what you do, or it would wreck your schedule. Then say no clearly and kindly, and offer a path forward:

"That's not something I offer, and I'd rather be upfront than do it half-well. I can recommend someone who specialises in it, or we can revisit it once the current project wraps."

Keep it short. Over-explaining sounds like guilt and invites negotiation.

Step 5: Put a price on it every time, even small things

The biggest scope-creep trap is the "freebie". You do one tiny extra task for free to be nice, and it sets the expectation that small things are free. You don't have to charge for everything, but you should show the value every time:

"I've added the extra banner size. That's normally about $60, but I've included it this time at no charge."

Now the client knows extras have a cost, and your generosity is visible, not invisible.

Step 6: Track every request in one place

Scope creep is hard to fight when it's scattered across email, Slack, calls and comments. Keep a running log of every extra request, its estimate and whether the client approved it. At the end of the project, that log is your proof, and often your invoice.

ScopeLine is built for exactly this. When a client asks for "one small change", you log it against the original scope, see what it adds in time and cost, and send a clear change order the client can approve. The free plan covers 3 active projects, and clients can approve or decline a change order from a link without making an account. No card needed.

If you want a starting point, there's also a free change order template you can fill in and copy.

Mistakes to avoid

Apologising for having a scope. You're not being difficult; you're being clear.
Quoting vaguely. "It'll be a bit extra" invites pushback. A specific number gets a decision.
Doing the work before approval. Get a written "yes" first, even if it's just a one-line email.
Letting resentment build. If you're already annoyed, you've waited too long to raise it. Address it at the first request, not the tenth.

The short version

Write a clear scope with a change-order clause.
Don't answer extra requests on the spot.
Reply with options and a price, not a flat no.
When it's truly a no, say it briefly and offer an alternative.
Show the value of every extra, even the free ones.
Log every request in one place.

Clients rarely leave because you priced extra work. They leave when they feel surprised. Clear scope and a calm "here's what that costs" protects your time and the relationship.

Stop doing unpaid "small changes". Try ScopeLine free and turn your next extra request into a paid change order.

5 follow-up emails that revive cold freelance leads (copy-paste)

bala — Mon, 02 Nov 2026 06:56:14 +0000

Most freelance leads don't say no. They go quiet. A short, well-timed follow-up gets a surprising number of them back. Here are five templates you can paste into Gmail or Outlook. Swap the bracketed bits before sending.

Timing rule of thumb: wait 3–5 business days after a proposal for the first nudge. Two or three touches over two or three weeks is plenty. After that, send a break-up email.

1. Proposal follow-up (day 5)

Subject: Quick follow-up on the proposal

Hi [Client],

I sent the proposal last week and wanted to check whether you had questions or if priorities shifted. Happy to adjust scope or walk through it on a short call.

Thanks,
[Your name]

2. No-reply bump

Subject: Circling back

Hi [Client],

Bumping my note from [X days] ago in case it got buried. Still interested in chatting about [service]?

[Your name]

3. Close the loop

Subject: Should I close this out?

Hi [Client],

I haven't heard back since the proposal. If timing isn't right, no problem — just let me know and I'll stop following up.

[Your name]

4. Break-up email

Subject: Closing the loop

Hi [Client],

I'll assume this isn't a priority unless I hear from you. Feel free to reach out anytime if things change.

[Your name]

It often gets a reply because it gives the client an easy way out.

5. Past client reconnect

Subject: Checking in

Hi [Client],

It's been a while since we worked together. How's everything going? If [service] is on your roadmap again, I'd love to hear what you're planning.

[Your name]

Friendly or direct?

Match the relationship. Warm clients respond to friendly notes; busy executives usually prefer one short paragraph with a clear ask.

Originally published on SteadyPipe, which has three more templates (retainer pitch, post-project thank-you, referral intro) and a free in-browser generator.

Templates are step one; remembering to send them is step two. I built SteadyPipe, a free tracker that tells you who to follow up with today. No card needed.