🚗🏍️ Welcome to Motoshare!

Turning Idle Vehicles into Shared Rides & New Earnings.
Why let your bike or car sit idle when it can earn for you and move someone else forward?

From Idle to Income. From Parked to Purpose.
Earn by Sharing, Ride by Renting.
Where Owners Earn, Riders Move.
Owners Earn. Riders Move. Motoshare Connects.

With Motoshare, every parked vehicle finds a purpose. Partners earn. Renters ride. Everyone wins.

Start Your Journey with Motoshare

How a Freelance DevOps Duo Tackled a Huge Job in 15-Minute Steps

Here is a story that is made up, but I would bet it is close to something you have lived. A two-person freelance team, one handling pipelines and the other handling cloud accounts, wins a contract from a small online shop. The brief is a single line: “tidy up our infrastructure and make deployments less scary”. The money is decent, the client is friendly, and for the first week the pair do almost nothing. The job is so large that every morning starts with a long coffee and a vague sense of guilt. What finally changes things is a decision to work in 15-minute steps.

Let us follow the team through the project, because the way they dig out is a handy pattern for anyone doing remote DevOps work on their own.

Week one: the fog

The pipeline specialist opens the client’s repository and finds forty scripts with names like “deploy_final_v2”. The cloud specialist logs in and finds resources whose purpose nobody remembers. Both of them, separately, think the same thing: where on earth do I begin?

They spend the first days reading, taking notes and drafting a grand plan with phases and diagrams. The plan is thorough and nobody feels better after reading it. It describes an end state but gives no clue about Tuesday morning. Freelancers know this trap well: when you are billing by outcome or by the day, an unstarted job quietly turns into stress.

The turning point: a call and a kitchen timer

On a video call at the end of the week, the pair admit the problem to each other. The cloud specialist suggests an experiment: pick the smallest possible useful action, set a timer for fifteen minutes, and stop when it rings, whatever happens. If the step is not finished, they write down what is left and decide whether to continue or switch.

They agree to try it for three days. The first step they choose is almost laughably small: make a list of every script in the repository that is actually called by the deployment. Nothing is deleted or changed. By the time the timer sounds, the list has eleven entries, and twenty-nine scripts are suddenly known to be dead weight.

What their quarter-hour list looked like

Over the following days their shared document grew into a ladder of small items. A flavour of it:

  1. Mark the eleven live scripts in the repository with a one-line comment describing their job.
  2. Move the dead scripts into an “archive” folder, in one commit, so they can be restored.
  3. Write down the order in which the live scripts run for a normal release.
  4. Replace one hard-coded server address with an environment variable and run the release in a test space.
  5. Tag every cloud resource the cloud specialist can identify with an owner label.
  6. List the resources with no identifiable owner and send that list to the client.

Each step is short, safe and visible. The client, who gets a short summary every evening, begins replying with encouraging messages and answers to the owner questions. Communication, which was the quiet casualty of the first week, springs back to life.

Why it works better for people who work alone

Freelancers lack the scaffolding that employees take for granted. There is no manager checking in, no standing meeting that forces a status update and no colleague at the next desk to notice when you are stuck. The upside is freedom; the downside is that a big, ambiguous task can sit untouched for days without anyone noticing, including you.

A 15-minute step acts as a portable scaffold. It is small enough to begin right after lunch, even when your energy is poor, and finishing it gives you a tiny proof that you are moving. Those proofs add up to confidence, and confidence is a resource that independent professionals often run short of.

If you are working on trust with new clients, the habit also supports that goal directly. The advice in an article on winning the confidence of a brand-new client leans heavily on steady, visible updates, and quarter-hour steps create plenty of material for them.

The client conversation that changed

One of the most useful side effects was how the team talked about scope. Previously, the client asked “how far along are you?” and the honest answer was a shrug. Now the team could answer with a number: nineteen steps done, nine to go for this phase. A conversation about progress became a conversation about specifics, and when the client asked for an extra feature, the freelancers could say it was roughly six more steps and show where it would fit.

That clarity protects both sides. The client sees what they are paying for, and the freelancers can discuss extra work without an awkward argument, since the unit of effort is already agreed.

Fitting the steps around a full-time job

Plenty of people read a blog like this because they freelance alongside a day job. For them the quarter-hour step is almost a necessity. An evening may offer only a small window, and a task that needs “a clear afternoon” will never be started. A task that needs fifteen minutes before dinner will. Should that describe you, the piece on running a DevOps side hustle next to a regular job makes a good companion read.

The story’s pair, as it happens, both had other commitments. One taught evening classes and the other had young children, so their working time came in scraps. Slicing was the only way those scraps could add up to a finished project.

What the duo would do differently

Looking back, the pair named two things they would change. First, they would have started slicing on day one instead of burning a week on a grand plan. The plan was not useless, since it taught them the shape of the system, but a single quarter-hour of listing scripts taught them just as much with far less effort.

Second, they would have agreed on a shared stopping rule up front. When the timer rang, they sometimes argued about whether to keep going. Deciding in advance that every step ends at the bell, with a note about what remains, removed those little negotiations and spared a surprising amount of energy. The note itself became the opening line of the next step, so nothing was lost by stopping on time.

Small tools, small steps

It is not only DevOps contracts that fit this pattern. Many online services are built from compact, single-purpose pieces. For instance, MotoShareGulf is a site for borrowing and lending scooters and motorbikes, and it uses a central service for member sign-in. A freelancer building something similar would also tackle it as a chain of little jobs: a listing page, a login handoff, a search box.

The results, and the honest bumps

Come the close of the second week, the shop’s deployments ran from one documented sequence, the repository was a fraction of its former clutter, and the resource list had owners against most entries. The pair were careful not to claim miracles. Two steps ran long and had to be split. One change broke a test environment briefly and was undone within minutes, which is exactly why they had kept every step reversible.

There was also a lesson about rest. Working in short bursts made it easy to keep going all day, and by Thursday both were tired in the odd way that comes from many small decisions. They began scheduling a proper break after every four steps and found that the quality of their later steps improved.

Borrowing the pattern for your next contract

  • Write the job’s finished state in one sentence before you begin.
  • List the first five steps, each small enough for a quarter hour.
  • Do the first one right away, before the doubt sets in.
  • Send the client a one-line update at the end of each working day.
  • After a week, count the steps done and use the number to guide the next conversation about scope.

The story ends without fireworks, and that is the point. Nobody had a flash of genius; they just stopped waiting for a big block of energy and started using the small ones they already had. If you are staring at a contract that feels too large to open, give it one quarter hour today and see what the list looks like tomorrow.

Related Posts

How to Build a Reusable Project Kit for DevOps Freelancing

A step-by-step method for DevOps freelancers to assemble proven proposals, scripts and handover notes into a kit that cuts rework on every new client.

Read More

A DevOps Freelancer’s Primer to Keeping a Decision Journal

A beginner primer for independent DevOps professionals: how to record choices, reasoning and expected results, with a mini-glossary of key terms.

Read More

Why Freelance DevOps Engineers Are Moving to Themed Weeks

A look at the rise of themed weeks among independent DevOps contractors: what it is, what it fixes, the risks and a simple way to start this month.

Read More

Timer or Evening Notes? A Freelancer’s One-Week Comparison

Two ways to track freelance hours, compared head to head. Trial each for seven days, note what you learn and keep the one you will actually use.

Read More

Pencil First: A Freelancer’s Plain Guide to Sketching Client Projects

A plain explanation of why a rough drawing on day one saves DevOps freelancers days of rework, plus how to run the five-minute client call.

Read More

Seven Ways Freelancers Keep Client Notes They Can Find Later

A forgotten fix and a client waiting on email: seven small habits that help solo DevOps freelancers find their own notes in seconds.

Read More
0 0 votes
Article Rating
Subscribe
Notify of
guest
0 Comments
Oldest
Newest Most Voted
0
Would love your thoughts, please comment.x
()
x