<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Abdullah Naseer</title>
    <description>The latest articles on DEV Community by Abdullah Naseer (@userxnom).</description>
    <link>https://dev.to/userxnom</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4209313%2F9451ef0a-e609-4949-890b-d86e1cc5512d.jpg</url>
      <title>DEV Community: Abdullah Naseer</title>
      <link>https://dev.to/userxnom</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/userxnom"/>
    <language>en</language>
    <item>
      <title>One month of logging every shift — what the numbers actually showed</title>
      <dc:creator>Abdullah Naseer</dc:creator>
      <pubDate>Mon, 16 Nov 2026 13:38:02 +0000</pubDate>
      <link>https://dev.to/userxnom/one-month-of-logging-every-shift-what-the-numbers-actually-showed-114n</link>
      <guid>https://dev.to/userxnom/one-month-of-logging-every-shift-what-the-numbers-actually-showed-114n</guid>
      <description>&lt;p&gt;The first month I wrote down every shift — pay, fuel, tolls, parking, food, miles, and the hours each shift really took — I stopped guessing which shifts were worth it.&lt;/p&gt;

&lt;p&gt;Here is what a month of numbers shows you that a single shift never will. The figures below are an illustrative example only, to show the method — your own numbers will be different.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Your best and worst days are not the ones you expect.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Take one example month: 18 shifts, $1,240 gross pay. Costs: fuel $210, tolls and parking $45, food on shift $60, and a per-mile wear share of $90. Net profit: $835. Total real hours, including waiting and dead miles: 74. Real rate: about $11.30 per hour.&lt;/p&gt;

&lt;p&gt;The same month's best-looking shift — $95 gross on a Friday night — came out at $13.40 per real hour after costs. A quiet Tuesday shift that paid $58 gross came out at $12.90 per real hour, because there was almost no waiting and no dead miles. The gap between "best" and "worst" was much smaller than the gross pay suggested.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Dead miles are a monthly number, not a per-trip feeling.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Add up the unpaid miles for the month — to the pickup, between jobs, the empty return. In the example: 210 unpaid miles out of 690 total, about 30%. At 45 cents a mile, that is $94.50 of driving that earned nothing. You only see that when you add the month up.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;One bad habit shows up in the totals.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;In the example month the pattern was clear: shifts accepted far from home started with 20 or more unpaid miles before the first paid mile. Cutting those out was the single biggest improvement the next month.&lt;/p&gt;

&lt;p&gt;How to do your own month review, in about 15 minutes:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Add up gross pay for the month.&lt;/li&gt;
&lt;li&gt;Add up every work cost: fuel, tolls, parking, food, and a per-mile wear share.&lt;/li&gt;
&lt;li&gt;Subtract to get net profit.&lt;/li&gt;
&lt;li&gt;Divide by ALL the hours the shifts really took — paid time plus waiting, dead miles, and the drive home.&lt;/li&gt;
&lt;li&gt;Compare days of the week by net profit per real hour, not by gross pay.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That monthly number is the honest answer to "is this work paying?" — and it is the number to beat next month.&lt;/p&gt;

&lt;p&gt;I keep my own numbers in ShiftLog — it is free, works offline, and needs no account: &lt;a href="https://play.google.com/store/apps/details?id=com.shiftlog.app" rel="noopener noreferrer"&gt;https://play.google.com/store/apps/details?id=com.shiftlog.app&lt;/a&gt;&lt;/p&gt;

</description>
      <category>android</category>
      <category>productivity</category>
      <category>career</category>
    </item>
    <item>
      <title>Gas went up 20 cents — did your cost per mile change? Update it or your profit math is stale</title>
      <dc:creator>Abdullah Naseer</dc:creator>
      <pubDate>Sun, 15 Nov 2026 13:30:57 +0000</pubDate>
      <link>https://dev.to/userxnom/gas-went-up-20-cents-did-your-cost-per-mile-change-update-it-or-your-profit-math-is-stale-1jda</link>
      <guid>https://dev.to/userxnom/gas-went-up-20-cents-did-your-cost-per-mile-change-update-it-or-your-profit-math-is-stale-1jda</guid>
      <description>&lt;p&gt;Your cost per mile is not a number you calculate once and forget. Gas prices move, and when they do, your profit math quietly goes stale.&lt;/p&gt;

&lt;p&gt;Say your car costs you 45 cents a mile to run — fuel, wear, maintenance, the lot. A 60-mile shift at $55 gross looks like $55 minus $27, or $28 net. But if gas went up and your real cost is now 52 cents a mile, that same shift is $55 minus $31.20, or $23.80. Same shift, same pay, about $4 less profit — and you would never notice unless you update the number.&lt;/p&gt;

&lt;p&gt;The figures above are an example to show the math, not a promise about your car. Your own numbers will differ.&lt;/p&gt;

&lt;p&gt;How to update it in two minutes:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Take what you spent on fuel over the last month, or over your last few fill-ups.&lt;/li&gt;
&lt;li&gt;Divide it by the miles you drove in the same period. That is your fuel cost per mile.&lt;/li&gt;
&lt;li&gt;Add your other per-mile costs the same way — maintenance, tires, and wear on the car.&lt;/li&gt;
&lt;li&gt;Use the new total next time you judge a shift.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;A good habit: redo this once a month, or right after a big fuel-price jump. If you only update it when something breaks, you have been pricing shifts with last season's numbers for months.&lt;/p&gt;

&lt;p&gt;I keep mine in ShiftLog — it is free, works offline, and needs no account — and the app turns each shift's pay, costs, and miles into a real net-profit number, so a stale cost per mile shows up fast.&lt;/p&gt;

&lt;p&gt;Get it here: &lt;a href="https://play.google.com/store/apps/details?id=com.shiftlog.app" rel="noopener noreferrer"&gt;https://play.google.com/store/apps/details?id=com.shiftlog.app&lt;/a&gt;&lt;/p&gt;

</description>
      <category>android</category>
      <category>productivity</category>
      <category>career</category>
    </item>
    <item>
      <title>Your insurance and car payment are shift costs too — spread them before you call a shift profitable</title>
      <dc:creator>Abdullah Naseer</dc:creator>
      <pubDate>Sat, 14 Nov 2026 13:30:28 +0000</pubDate>
      <link>https://dev.to/userxnom/your-insurance-and-car-payment-are-shift-costs-too-spread-them-before-you-call-a-shift-profitable-d73</link>
      <guid>https://dev.to/userxnom/your-insurance-and-car-payment-are-shift-costs-too-spread-them-before-you-call-a-shift-profitable-d73</guid>
      <description>&lt;p&gt;Most gig drivers subtract fuel and tolls after a shift, then call what's left "profit."&lt;/p&gt;

&lt;p&gt;But some of the biggest costs of the job never show up at the pump. They arrive once a month: the car payment or lease, the insurance bill, the phone plan you need to take jobs at all.&lt;/p&gt;

&lt;p&gt;Those costs don't disappear just because you didn't pay them today. If they aren't counted anywhere, your profit number is higher than the truth — every single shift.&lt;/p&gt;

&lt;p&gt;Here's the simple way to count them:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Add up one month's fixed work costs. Insurance, car payment or lease, phone plan — the bills that exist because you do this work.&lt;/li&gt;
&lt;li&gt;Count how many shifts you worked that month.&lt;/li&gt;
&lt;li&gt;Divide. That is the fixed-cost share each shift has to carry.&lt;/li&gt;
&lt;li&gt;Add that share to the shift's fuel, tolls, parking, food, and other costs before you call it profitable.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;A clearly labeled illustrative example: say insurance is $120 a month, the car payment is $280, and the phone plan is $40. That's $440 a month. Work 20 shifts that month and each shift carries $22 of fixed costs. A shift that looked $30 ahead after fuel is really $8 ahead once the fixed share is counted.&lt;/p&gt;

&lt;p&gt;One honest caveat: if the same car is also your personal car, only the work share counts. Keep it simple — use the share of your miles that are work miles, and apply that share to the fixed costs. Don't count the whole car payment if half your driving is personal.&lt;/p&gt;

&lt;p&gt;The point isn't perfect accounting. It's not fooling yourself. A shift that pays after fuel but not after the monthly bills is a shift that quietly loses money.&lt;/p&gt;




&lt;p&gt;ShiftLog is the free, offline app I built to do this math for gig workers — no account needed. It subtracts your costs from your pay so you can see each shift's real net profit.&lt;br&gt;
&lt;a href="https://play.google.com/store/apps/details?id=com.shiftlog.app" rel="noopener noreferrer"&gt;https://play.google.com/store/apps/details?id=com.shiftlog.app&lt;/a&gt;&lt;/p&gt;

</description>
      <category>android</category>
      <category>productivity</category>
      <category>career</category>
    </item>
    <item>
      <title>Cash tips disappear first — log them the second you get them</title>
      <dc:creator>Abdullah Naseer</dc:creator>
      <pubDate>Fri, 13 Nov 2026 13:31:26 +0000</pubDate>
      <link>https://dev.to/userxnom/cash-tips-disappear-first-log-them-the-second-you-get-them-5ah5</link>
      <guid>https://dev.to/userxnom/cash-tips-disappear-first-log-them-the-second-you-get-them-5ah5</guid>
      <description>&lt;p&gt;Cash is the easiest part of a gig shift to lose track of.&lt;/p&gt;

&lt;p&gt;You finish a delivery, the customer hands you a few dollars in cash, and you put it in your pocket. An hour later you stop for a coffee and pay with that same cash. By the end of the night, your card payments are all neatly listed in the app — but the cash is gone, spent, and never written down anywhere.&lt;/p&gt;

&lt;p&gt;That is how a shift ends up looking worse on paper than it really was. Or the other way round: you remember the cash, guess at the amount, and your records say the shift paid more than it did. Either way, the number you are making decisions from is wrong.&lt;/p&gt;

&lt;p&gt;Here is a simple fix: log cash the second it lands in your hand.&lt;/p&gt;

&lt;p&gt;It does not need to be fancy. Keep one pocket — or one compartment in your bag — just for cash tips and cash fares. Do not pay for anything out of it during the shift. At the end of the shift, count it once, write the total down, and only then move it to your wallet.&lt;/p&gt;

&lt;p&gt;An illustrative example, not a real shift: say you earn $12 in cash tips across one night and spend $6 of it on food and a drink before you get home. If you only record the card payments, that shift looks $12 worse than it really was. The work was done, the money was earned, and your records say otherwise. Over a month of nights, that is real money quietly missing from your own books.&lt;/p&gt;

&lt;p&gt;Why it matters: your real earnings are card pay plus cash, minus your costs. Miss the cash and your net profit is wrong in either direction — and a wrong net-profit number is what makes a bad shift look good, or a good shift look not worth repeating.&lt;/p&gt;

&lt;p&gt;The habit takes seconds. Cash in the pocket, count it at the end of the shift, write it down before you leave the car. Same-day numbers are honest numbers; next-day numbers are guesses.&lt;/p&gt;

&lt;p&gt;I built ShiftLog to make this kind of tracking easy: a free Android app that works fully offline, with no account needed. You log each shift's pay, cash tips, costs and miles, and it shows your real net profit per shift and per hour.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://play.google.com/store/apps/details?id=com.shiftlog.app" rel="noopener noreferrer"&gt;https://play.google.com/store/apps/details?id=com.shiftlog.app&lt;/a&gt;&lt;/p&gt;

</description>
      <category>android</category>
      <category>productivity</category>
      <category>career</category>
    </item>
    <item>
      <title>The 2-minute habit that makes every shift count: log it before you leave the car</title>
      <dc:creator>Abdullah Naseer</dc:creator>
      <pubDate>Thu, 12 Nov 2026 13:31:38 +0000</pubDate>
      <link>https://dev.to/userxnom/the-2-minute-habit-that-makes-every-shift-count-log-it-before-you-leave-the-car-5f7o</link>
      <guid>https://dev.to/userxnom/the-2-minute-habit-that-makes-every-shift-count-log-it-before-you-leave-the-car-5f7o</guid>
      <description>&lt;p&gt;The shift is over. You are tired, you drive home, and by tomorrow you have already forgotten the small stuff: the $4 parking fee, the 20 minutes waiting for the next job, the cash tip you meant to write down.&lt;/p&gt;

&lt;p&gt;That forgetting is the leak. One forgotten cost is nothing. A week of them is real money that looked like profit and was not.&lt;/p&gt;

&lt;h2&gt;
  
  
  The 2-minute routine
&lt;/h2&gt;

&lt;p&gt;Before you leave the car, take two minutes and write down the shift:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Pay for the shift, and cash tips separately&lt;/li&gt;
&lt;li&gt;Fuel, tolls, parking, and any food you bought while working&lt;/li&gt;
&lt;li&gt;Miles driven, including the empty miles to the pickup and back&lt;/li&gt;
&lt;li&gt;Waiting time between jobs&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That is it. Two minutes, while it is still fresh.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why the same day matters
&lt;/h2&gt;

&lt;p&gt;Same-day numbers are honest numbers. Next-day numbers are guesses, and guesses always forget the small costs first — the ones that add up fastest. A parking fee you forgot is still money you spent.&lt;/p&gt;

&lt;p&gt;Here is a clearly labeled illustrative example, not a real shift: forget a $4 parking fee on five shifts in one week and $20 of "profit" was never profit at all. The shift did not get worse. Your memory of it did.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the habit gives you
&lt;/h2&gt;

&lt;p&gt;After a week of same-day notes, your weekly total is a number you can trust. You can see which days actually paid after costs, and which ones only looked good because the costs were never written down. That is the whole point of tracking: decisions made from real numbers instead of a tired memory.&lt;/p&gt;

&lt;p&gt;I built a small free Android app called ShiftLog for exactly this — it logs each shift's pay, costs, miles, and waiting time, and shows your real net profit. It works offline and needs no account. You can find it here: &lt;a href="https://play.google.com/store/apps/details?id=com.shiftlog.app" rel="noopener noreferrer"&gt;https://play.google.com/store/apps/details?id=com.shiftlog.app&lt;/a&gt;&lt;/p&gt;

</description>
      <category>android</category>
      <category>productivity</category>
      <category>career</category>
    </item>
    <item>
      <title>The slow shift test: reposition, rest, or call it a day</title>
      <dc:creator>Abdullah Naseer</dc:creator>
      <pubDate>Wed, 11 Nov 2026 13:30:29 +0000</pubDate>
      <link>https://dev.to/userxnom/the-slow-shift-test-reposition-rest-or-call-it-a-day-n92</link>
      <guid>https://dev.to/userxnom/the-slow-shift-test-reposition-rest-or-call-it-a-day-n92</guid>
      <description>&lt;p&gt;Every gig worker knows this moment: it has been an hour, the orders have stopped coming, and you are sitting in your car burning fuel and time. The question is not 'should I keep going?' — it is 'what does staying out actually cost me right now?'&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;Check what the shift has actually made so far. Not the gross pay on the screen — pay minus what you have already spent: fuel, tolls, parking, food. If that number is small after two hours, the shift is already telling you something.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Price the next hour before you work it. An hour parked in a dead zone still costs fuel to get there, wear on the car, and food. If the area is quiet, the next hour can easily pay less than it costs.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Reposition only when the math says so. Driving 20 minutes to a busier zone is only worth it if the extra orders there clearly beat the fuel and time of getting there — and the orders you miss while driving. A move that feels busy can still lose money.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Rest is a real option. A short break costs nothing extra and lets you think clearly. Some drivers keep driving tired and make worse calls — accepting bad orders and missing the good ones.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Going home early is not quitting. A shift that loses money hour by hour is a shift that costs you. Ending it and starting fresh tomorrow is often the most profitable call of the day.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The habit that makes all of this easy: write the numbers down right after each shift — pay, fuel, tolls, parking, food, hours, miles. After a week you can see which hours and zones actually paid, and the slow-shift call stops being a guess.&lt;/p&gt;

&lt;p&gt;I built a free tool for exactly that. ShiftLog tracks each shift's real net profit after costs, works fully offline, and needs no account. You can get it here: &lt;a href="https://play.google.com/store/apps/details?id=com.shiftlog.app" rel="noopener noreferrer"&gt;https://play.google.com/store/apps/details?id=com.shiftlog.app&lt;/a&gt;&lt;/p&gt;

</description>
      <category>career</category>
      <category>android</category>
      <category>productivity</category>
    </item>
    <item>
      <title>Chasing surge across town can cost more than the surge pays</title>
      <dc:creator>Abdullah Naseer</dc:creator>
      <pubDate>Tue, 10 Nov 2026 13:30:17 +0000</pubDate>
      <link>https://dev.to/userxnom/chasing-surge-across-town-can-cost-more-than-the-surge-pays-361d</link>
      <guid>https://dev.to/userxnom/chasing-surge-across-town-can-cost-more-than-the-surge-pays-361d</guid>
      <description>&lt;p&gt;You've seen it: a surge zone lights up across town, and the instinct is to drive straight there. Before you go, do the math — the surge only pays if you actually get there in time, and if the extra driving doesn't eat it first.&lt;/p&gt;

&lt;p&gt;The hidden cost of the chase:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The drive to the surge zone is unpaid. Fuel, time, and wear on the vehicle all count, and none of it is covered by the surge.&lt;/li&gt;
&lt;li&gt;Surge fades. By the time you arrive, the zone can be full of other drivers who had the same idea — and the surge can be gone.&lt;/li&gt;
&lt;li&gt;The trip back matters too. If the surge job drops you far from home, the empty return is another unpaid stretch.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A quick check before you chase:&lt;br&gt;
Say the surge promises an extra $8 on the next trip (illustrative example, not a real fare). The zone is 15 minutes away. Fuel and vehicle wear for that drive cost about $4, and those 15 minutes could have gone to a normal trip near you instead. If the surge is gone when you arrive, you spent $4 and 15 minutes for nothing. If it is still there, you kept about $4 of the $8 — and only if the job itself is a good one.&lt;/p&gt;

&lt;p&gt;The rule is simple: chase the surge only when the extra pay clearly beats the cost of getting there — fuel, time, and the empty miles back. If it doesn't, stay where you are and take the next good job close by.&lt;/p&gt;

&lt;p&gt;That's the habit ShiftLog is built around: knowing what each shift really earned after costs, so the decision comes from numbers, not from a glowing map.&lt;/p&gt;

&lt;p&gt;ShiftLog is free, works offline, and needs no account: &lt;a href="https://play.google.com/store/apps/details?id=com.shiftlog.app" rel="noopener noreferrer"&gt;https://play.google.com/store/apps/details?id=com.shiftlog.app&lt;/a&gt;&lt;/p&gt;

</description>
      <category>career</category>
      <category>android</category>
      <category>productivity</category>
    </item>
    <item>
      <title>One flat tyre shouldn't wipe out your whole week — build a small repair fund from every shift</title>
      <dc:creator>Abdullah Naseer</dc:creator>
      <pubDate>Mon, 09 Nov 2026 13:29:52 +0000</pubDate>
      <link>https://dev.to/userxnom/one-flat-tyre-shouldnt-wipe-out-your-whole-week-build-a-small-repair-fund-from-every-shift-4lji</link>
      <guid>https://dev.to/userxnom/one-flat-tyre-shouldnt-wipe-out-your-whole-week-build-a-small-repair-fund-from-every-shift-4lji</guid>
      <description>&lt;p&gt;Gig work looks profitable right up until the car needs something. A flat tyre, a dead battery, a brake pad — one garage visit and the whole week's profit is gone.&lt;/p&gt;

&lt;p&gt;That is not bad luck. It is a cost you knew was coming, just not which week it would land in. Repairs are not surprises; they are irregular bills. If your profit math only counts fuel and food, your number is too high — it is counting money the car will take back later.&lt;/p&gt;

&lt;p&gt;The fix is boring and it works: set aside a small fixed amount from every shift, before you call the shift's money yours. Put it somewhere you will not touch for anything except keeping the car on the road — tyres, brakes, oil, battery, a phone mount that finally gives up.&lt;/p&gt;

&lt;p&gt;Here is an illustrative example, not a promise: you do 5 shifts a week and set aside $3 from each one. That is $15 a week, about $60 a month. A $90 tyre then costs a month and a half of the fund — annoying, but it does not eat a whole week's earnings. Your numbers will be different; the point is the habit, not the amount.&lt;/p&gt;

&lt;p&gt;Two rules make it stick:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Take it out the same shift you earn it. If you wait until the end of the week, the money is already spent in your head.&lt;/li&gt;
&lt;li&gt;Never borrow from it for anything else. A repair fund that pays for takeaways is not a repair fund.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Start small. Even $2 a shift beats $0 a shift, because the habit is what matters — the amount grows when the work grows.&lt;/p&gt;

&lt;p&gt;At the end of the week, what matters is the profit that is actually left after the car has had its share. I log my shifts in ShiftLog — it's free, works offline, and needs no account — so I can see my real net profit per shift, and the fund comes out of that number, not out of a guess.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://play.google.com/store/apps/details?id=com.shiftlog.app" rel="noopener noreferrer"&gt;https://play.google.com/store/apps/details?id=com.shiftlog.app&lt;/a&gt;&lt;/p&gt;

</description>
      <category>android</category>
      <category>productivity</category>
      <category>career</category>
    </item>
    <item>
      <title>Your worst shift this week is your best teacher — if you write down why it lost money</title>
      <dc:creator>Abdullah Naseer</dc:creator>
      <pubDate>Sun, 08 Nov 2026 13:30:17 +0000</pubDate>
      <link>https://dev.to/userxnom/your-worst-shift-this-week-is-your-best-teacher-if-you-write-down-why-it-lost-money-1511</link>
      <guid>https://dev.to/userxnom/your-worst-shift-this-week-is-your-best-teacher-if-you-write-down-why-it-lost-money-1511</guid>
      <description>&lt;p&gt;A shift that loses money feels like a waste of a day. But it is the most useful shift of the week — if you write down why it lost money before you forget.&lt;/p&gt;

&lt;p&gt;Most gig workers just move on and repeat the same mistake: the same low-pay zone, the same long unpaid drive to a pickup, the same long wait for one order. The loss repeats because the cause was never recorded.&lt;/p&gt;

&lt;p&gt;Do a two-minute post-mortem right after a bad shift. Write down five things while they are fresh:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;What you were paid.&lt;/li&gt;
&lt;li&gt;Your real hours — driving to pickups, waiting, and dead miles, not just the busy time.&lt;/li&gt;
&lt;li&gt;Fuel.&lt;/li&gt;
&lt;li&gt;Tolls, parking, and food.&lt;/li&gt;
&lt;li&gt;Dead miles — the unpaid miles to pickups, between jobs, and the empty drive home.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Subtract the costs from the pay. If the number is negative, ask which single thing hurt the most. Usually it is one of four causes: a long unpaid drive to the pickup, a long wait for one order, a zone that paid well last week but not this week, or a job that looked big but carried hidden costs.&lt;/p&gt;

&lt;p&gt;Then change ONE thing next time, not everything. A rule like "no pickup drive longer than ten minutes" or "no jobs in that zone after 8 pm." Test it for a week and compare the net profit per shift. If the number improves, keep the rule. If not, try a different one.&lt;/p&gt;

&lt;p&gt;Keep a short list of your losing shifts. After a month you will see the pattern — the same cause repeating again and again. That is the fix worth making, and you only find it by writing the losses down.&lt;/p&gt;

&lt;p&gt;ShiftLog is the free tool I built for this: it is offline, needs no account, and logs each shift's pay and costs so it can show the net profit per shift. That turns the post-mortem into a few seconds of checking, instead of guessing from memory.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://play.google.com/store/apps/details?id=com.shiftlog.app" rel="noopener noreferrer"&gt;https://play.google.com/store/apps/details?id=com.shiftlog.app&lt;/a&gt;&lt;/p&gt;

</description>
      <category>android</category>
      <category>productivity</category>
      <category>career</category>
    </item>
    <item>
      <title>Set a minimum pay floor for your shifts — and stop accepting anything below it</title>
      <dc:creator>Abdullah Naseer</dc:creator>
      <pubDate>Sat, 07 Nov 2026 13:29:09 +0000</pubDate>
      <link>https://dev.to/userxnom/set-a-minimum-pay-floor-for-your-shifts-and-stop-accepting-anything-below-it-1o76</link>
      <guid>https://dev.to/userxnom/set-a-minimum-pay-floor-for-your-shifts-and-stop-accepting-anything-below-it-1o76</guid>
      <description>&lt;p&gt;Most gig workers accept almost every offer that comes in, then wonder why the week felt busy but paid badly. The fix is a floor: a minimum net profit per real hour you will accept, decided before the shift starts, not in the middle of it.&lt;/p&gt;

&lt;p&gt;A floor is not a wish. Work it out from your own numbers. Start with what you need to earn in a week after costs, divided by the real hours you can work. Then test each offer against it: pay minus fuel, tolls, parking, food, and a share for vehicle wear, divided by real hours. Real hours include driving to the pickup, waiting, and dead miles — not just the paid part of the job.&lt;/p&gt;

&lt;p&gt;Here is a clearly labelled example, not a real shift: an offer pays $24 for what looks like 1.5 hours. Fuel and tolls take $6, and waiting plus driving to the pickup add 30 minutes of real time. That is $18 over 2 real hours, or $9 per real hour. If your floor is $15 per real hour, that offer is a no, even though $24 sounded fine on its own.&lt;/p&gt;

&lt;p&gt;Saying no is the hard part. Two things make it easier. First, decide the floor when you are calm, not while an offer is flashing on your screen. Second, keep a small count: how many offers you declined this week, and what you earned on the work you took instead. After two weeks, compare. Did declining below-floor offers actually raise your weekly net, or did you sit idle too long? Adjust the floor from that evidence, not from a feeling.&lt;/p&gt;

&lt;p&gt;A floor also protects your week from one bad habit: chasing a big single payout that eats the whole evening. A $60 job that takes four real hours after costs is worse than two $35 jobs that take two real hours each. The floor makes that comparison automatic, before you accept.&lt;/p&gt;

&lt;p&gt;Try it for two weeks. Pick your floor, write it down, and test every offer against it. If the week ends with fewer hours worked and more money kept, the floor is doing its job.&lt;/p&gt;

&lt;p&gt;I built a free tool that does this math for me. ShiftLog is a free Android app for gig workers and drivers: it tracks each shift's pay, costs, and real hours and shows your actual net profit, so you can see which shifts are worth taking. It works offline and needs no account. You can get it here: &lt;a href="https://play.google.com/store/apps/details?id=com.shiftlog.app" rel="noopener noreferrer"&gt;https://play.google.com/store/apps/details?id=com.shiftlog.app&lt;/a&gt;&lt;/p&gt;

</description>
      <category>android</category>
      <category>productivity</category>
      <category>career</category>
    </item>
    <item>
      <title>You drive for two apps? Compare them by net profit, not per-trip pay</title>
      <dc:creator>Abdullah Naseer</dc:creator>
      <pubDate>Fri, 06 Nov 2026 13:29:59 +0000</pubDate>
      <link>https://dev.to/userxnom/you-drive-for-two-apps-compare-them-by-net-profit-not-per-trip-pay-566i</link>
      <guid>https://dev.to/userxnom/you-drive-for-two-apps-compare-them-by-net-profit-not-per-trip-pay-566i</guid>
      <description>&lt;p&gt;Many gig drivers run two apps at once — or switch between them during the week. And most of them compare the apps the wrong way: by which one pays more per trip.&lt;/p&gt;

&lt;p&gt;Per-trip pay is the noisiest number you can compare. One app might pay $18 for a trip that took 25 minutes with a 4-mile drive to the pickup. The other pays $14 for a trip that took 12 minutes with the customer right next door. The $18 trip looks better on the earnings screen. After fuel, waiting time, and the empty miles to the pickup, it often isn't.&lt;/p&gt;

&lt;p&gt;The fair comparison is net profit per real hour, per app:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;For each shift, write down the gross pay from that app.&lt;/li&gt;
&lt;li&gt;Subtract the costs of that shift: fuel, tolls, parking, food on the job, and a per-mile cost for wear on your vehicle — tyres, brakes, servicing. Use your own estimate, and expect it to move month to month.&lt;/li&gt;
&lt;li&gt;Count ALL the hours the shift really took: driving, waiting between jobs, the drive to the pickup, and the empty return — not just the paid minutes.&lt;/li&gt;
&lt;li&gt;Net profit divided by all real hours is the number that actually compares.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;A quick illustrative example — not real earnings, just the maths: App A pays $90 for a shift. Costs are $22, and the shift really took 4.5 hours. Net is $68, about $15 an hour. App B pays $75. Costs are $12, and the shift took 3 hours. Net is $63, about $21 an hour. App A paid more. App B left you better off per hour.&lt;/p&gt;

&lt;p&gt;Two rules before you switch apps on the strength of one night: track both columns for at least two weeks, and compare weeks, not single shifts. One busy Friday can flatter either app. A pattern over two weeks is much harder to argue with.&lt;/p&gt;

&lt;p&gt;That's the whole point of logging shifts properly: the app earnings screen tells you what you were paid. It doesn't tell you what you kept, or which app kept you better off.&lt;/p&gt;

&lt;p&gt;I built a small free tool for exactly this — ShiftLog logs each shift's pay, costs, and hours offline, with no account needed, so you can see the real net profit per shift and per hour: &lt;a href="https://play.google.com/store/apps/details?id=com.shiftlog.app" rel="noopener noreferrer"&gt;https://play.google.com/store/apps/details?id=com.shiftlog.app&lt;/a&gt;&lt;/p&gt;

</description>
      <category>android</category>
      <category>productivity</category>
      <category>career</category>
    </item>
    <item>
      <title>Your payout never matches the app's earnings screen — here's how to track the gap</title>
      <dc:creator>Abdullah Naseer</dc:creator>
      <pubDate>Thu, 05 Nov 2026 13:29:40 +0000</pubDate>
      <link>https://dev.to/userxnom/your-payout-never-matches-the-apps-earnings-screen-heres-how-to-track-the-gap-3j5j</link>
      <guid>https://dev.to/userxnom/your-payout-never-matches-the-apps-earnings-screen-heres-how-to-track-the-gap-3j5j</guid>
      <description>&lt;p&gt;The number on the app's earnings screen and the money that actually lands in your bank are rarely the same. If you plan your week on the app number, you are overstating your income.&lt;/p&gt;

&lt;p&gt;The gap comes from a few ordinary things. The platform takes a service fee before payout. Instant payouts charge a fee. Some tips arrive days later. Adjustments and refunds change the total. And cash tips never appear in the app at all.&lt;/p&gt;

&lt;p&gt;The fix is a second column. For each shift, write down two numbers: what the app says you earned, and what actually landed — bank deposit plus cash in hand. The difference between them is the gap. It is fees and timing, not money you kept.&lt;/p&gt;

&lt;p&gt;Add the gaps up at the end of the week. That total is real money, and it changes which platform or shift type is actually better. A platform that pays $120 with a $12 gap is worse than one that pays $115 with a $2 gap — even though the first one looks better on the earnings screen.&lt;/p&gt;

&lt;p&gt;Here is an illustrative example, not a real driver's week: the app shows $120 for the week, but the bank plus cash shows $108. The $12 gap is an instant-pay fee and one tip that lands next week. Real net profit is $108 minus fuel and other costs — not $120 minus costs.&lt;/p&gt;

&lt;p&gt;That is the number worth tracking. The app's earnings screen is a starting point, not the final answer.&lt;/p&gt;

&lt;p&gt;I built a free tool for exactly this kind of shift-by-shift tracking. ShiftLog logs each shift's pay and costs, works fully offline, and needs no account. You can get it here: &lt;a href="https://play.google.com/store/apps/details?id=com.shiftlog.app" rel="noopener noreferrer"&gt;https://play.google.com/store/apps/details?id=com.shiftlog.app&lt;/a&gt;&lt;/p&gt;

</description>
      <category>android</category>
      <category>productivity</category>
      <category>career</category>
    </item>
  </channel>
</rss>
