🚗🏍️ 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

Six Myths About Rereading Your Freelance DevOps Goals

Independent DevOps work comes with a freedom that quietly turns into a hazard: nobody schedules your reflection for you. There is no manager to say “let us check whether this still makes sense.” So the goals you set at the start of a freelance year, whether about rates, niches, certifications or client mix, can sit untouched while the market and your own preferences move on. A monthly reread of those written goals is a simple correction. Yet several persistent myths stop freelancers from doing it. Here are six of them, along with the corrections I would give a fellow freelancer.

The advice is about working habits only. It is not business, tax or legal guidance, and individual circumstances differ widely.

Myth 1: “Good freelancers pick goals once and stay the course”

Persistence is valuable, but persistence toward the wrong target is expensive. A freelancer who set a goal to specialise in one container platform may find, within a few months, that clients are asking about something adjacent. Sticking rigidly to the original aim means declining work that the market is offering. A monthly reread does not weaken commitment. It lets you commit to what is currently true.

The correction: treat each goal as a hypothesis with a review date. Should the evidence back it up, you carry on with extra confidence. If not, you have lost one month, not one year.

Myth 2: “I am too busy with client work to review goals”

You hear this objection constantly, and it tells you a lot. Busyness is exactly when goals drift fastest, because urgent client tasks absorb attention and nothing else gets a vote. Yet a reread takes twenty to thirty minutes. If that is too much, the cause is rarely a lack of time; it is usually that the review feels vague and potentially uncomfortable.

The correction: shrink the session. Read only the goals, answer three questions for each, write the decisions and stop. Put it in the calendar as if it were a client call, and protect it the same way.

Myth 3: “Dropping a goal means failing”

Many independent professionals carry an unspoken rule that abandoning an aim is a character flaw. In practice, retiring a goal is a planning decision. Suppose you aimed to build a content channel to attract clients, and after three months you have discovered that your best leads come from referrals. Continuing to invest in the channel at the same level is a choice you should make deliberately, not by inertia.

The correction: record dropped goals in a “retired” list with the date and the reason. Over a year, that list becomes a record of what you learned about your own business.

Myth 4: “A reread is the same as a yearly planning session”

Annual planning is big, slow and often ceremonial. A monthly reread is small and focused on one question: does each existing goal still fit? You are not brainstorming new directions, setting new targets or redesigning your service pages. That distinction matters because it keeps the session light enough to repeat twelve times a year.

The correction: keep the two rituals separate. Use the monthly reread to prune and adjust, and save the larger thinking for the yearly session, where the pruned list gives you a clearer starting point.

Myth 5: “My goals are only about money, so numbers are enough”

Revenue-related aims dominate many freelancer lists, but a spreadsheet only shows what has happened. It does not tell you whether the aim still matches what you want. Perhaps you set a goal to take on more clients, and then discovered that your preferred way of working involves fewer, longer engagements. The number looks fine while the goal quietly stops fitting your life.

The correction: include at least one goal about the way you want to work, such as hours, kinds of project or the amount of learning time, and let the reread test that goal in words as well as figures. For a look at how others balance independent work with other commitments, there is a sensible discussion in a discussion of how to freelance responsibly while holding a salaried post.

Myth 6: “Learning goals can wait until work slows down”

Skill goals are the ones most likely to be postponed indefinitely, and they are also the ones most likely to become outdated. A framework you planned to learn may be falling out of favour; a tool you ignored may now appear in half the briefs you see. If learning goals are only reviewed when the diary is empty, they tend to be reviewed too late.

The correction: review learning goals alongside everything else. Ask whether what you planned to study still appears in the work you want. If you use external courses, remember that a platform is only a vehicle. AirCrewU is a website where aviation professionals study online, and it states that it is independent. It is mentioned only as a reminder that every industry has venues like it, and that the goal, not the venue, should drive your monthly check.

A worked example from one quarter

Here is one way a quarter might go for an independent engineer who began the year with four goals: raise the day rate, move toward infrastructure-as-code engagements, finish a cloud study programme and write one article a month. At the first monthly reread, all four looked reasonable. At the second, the article goal was already slipping, but the reasons were unclear.

By the third reread, the engineer looked at the notes file and saw a pattern: the hours spent writing were being taken from the study programme, and neither goal was moving. The decision was to retire the article goal for the quarter and to protect two study evenings a week instead. A line in the “retired” list read, “writing returns when study finishes.” Two months later the study programme was complete, and the article goal came back in a smaller form: one short post every other month.

Nothing dramatic happened in that story. There was no crisis and no breakthrough. A goal was allowed to wait, and the engineer’s effort followed what mattered. That quiet adjustment is what the monthly reread is for.

A compact routine that works

  1. Collect. Open one document with every goal on it, work and learning alike.
  2. Read slowly. Treat each goal as if a stranger wrote it. Does the wording still describe what you want?
  3. Test against recent work. Look at your last month’s projects. Which goals did they support, and which did they ignore?
  4. Decide per goal. Leave, rewrite or retire. Write one line of reasoning for each.
  5. Pick this month’s single focus. Of the survivors, choose the one you will move first.

What good evidence looks like

A freelancer’s evidence is practical: enquiries received, projects declined and why, hours spent on unpaid admin, invoices paid late, and the kinds of problems that gave you energy. None of these needs a dashboard. A simple notes file with a line per week will do. When you reread, skim the notes for patterns that either support or undermine each goal.

For newcomers, the general questions people ask when they begin are collected in a beginner-oriented FAQ for new DevOps freelancers. It is useful reading while you decide which of your starting goals were realistic.

Closing thought

Every myth above rests on one assumption: that goals are fixed things you either achieve or fail. They are better understood as drafts that earn their place each month. Set a recurring date, keep the session short and be willing to cross a line out. A freelance practice stays healthy when its goals are as current as its client work.

Related Posts

Freelance DevOps Near Misses: A Six-Step Capture Routine

Freelancers have no safety net but themselves. Six practical steps for capturing close calls and converting them into small, tested guards.

Read More

Tidying a Freelance DevOps Practice as You Work: Your Questions

Answers to the questions freelance DevOps engineers ask about keeping client access, files and project debris under control during the work rather than afterwards.

Read More

What a Finished Freelance DevOps Proposal Teaches You

Take a finished four-page freelance DevOps proposal apart, page by page, and pick up the career skills hiding in how it was written and ordered.

Read More

Five Myths About Jargon in DevOps Freelance Proposals

Does technical vocabulary make a freelancer look more capable? Five common beliefs about client writing, tested with plain reasoning.

Read More

A Freelancer’s Constraint Audit: Seven Limits Worth Trying

A storytelling-style checklist for remote DevOps freelancers who want sharper proposals and calmer weeks by choosing a few creative limits on purpose.

Read More

Closed Door or Open Notebook? Two Ways to Freelance in DevOps

Two freelancers, one hiding work until it is polished and one sharing it as it grows. A human comparison of what each habit does to trust, scope and referrals.

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