My Tiny Rocket retweeted
Before you take a hybrid job, ask where the rest of your team actually sits.
A new survey found more than 70% of office workers had at least one teammate working somewhere else on their last office day. More than 1 in 3 had only online meetings that day.
Check each job against its bid while it's still running, not after it's done.
An Arizona remodeler just went bankrupt owing about $8 million. Its lawyer said nobody checked closely if bids made money, and customer deposits ended up paying for other people's jobs.
My Tiny Rocket retweeted
Check where your alerts run. If they live in the same cloud region as your app, one outage takes out the app and the warning.
Google Cloud's London region went down this morning. Banks, court video links, and delivery apps went down with it.
My Tiny Rocket retweeted
No deploy ping doesn't mean the deploy worked.
GitHub Actions was down for over three hours this Monday. Jobs sat stuck or failed, and a lot of team channels just went quiet.
Alert when a job fails or sits stuck too long, not only when it ships.
How long before you'd notice?
Where a dollar of contract goes.
38¢ to materials, 27¢ to labor, 14¢ to the subs, 11¢ to overhead, 4¢ to "don't worry about it".
What's left? Six cents. That's a good year for a lot of you.
#contractorlife #profitmargin #generalcontractor #jobcosting #remodeling
Late pay is not only "they forgot the invoice".
A UK survey found most subs are almost always paid late, and nearly a third walk when pay-apps are a mess.
One clear pay trail beats another chase email. tryobra.com/guides/how-contr…
My Tiny Rocket retweeted
Here are the latest top ranking launches.
September 14th–September 20th
🥇Baby Monitor Timmy
🥈Talking Tree @talkingtree_app
🥉Obra @MyTinyRocket
Here are the latest top ranking launches.
September 7th–September 13th
🥇Deliveryman .ai @junaidansari
🥈Vanpelt Studio @vanpeltventures
🥉MentionBird @salilpa
Every alert should go where it belongs
Stripe failed payment alerts at 2am aren't a Slack problem.
They're a routing problem. Send "charge.failed" to on-call Telegram. Keep #billing for a daytime digest.
One source, two destinations. No overnight spam.
What wakes you that shouldn't?
My Tiny Rocket retweeted
Stripe retried the same payment event three times and your channel got three cha-ching messages?
Give each event a unique key so retries don't double notify you.
The ribbon cutting is not a payday for the trade.
As the Lucas Museum nears opening, an electrical sub says about $1.9M is unpaid while they waited on promised payment.
Keep every receipt and invoice on the job while the payment chain argues. tryobra.com
My Tiny Rocket retweeted
One noisy Slack channel is where payment failures go to die after hours.
Page a person first. Group mentions are visibility, not wake-ups.
eventsend.io
My Tiny Rocket retweeted
When a remote exception closes, the job post can look the same while the offer changes.
Disney told some remote product and tech folks Monday: four days in office. Prior tech exceptions are closing.
Screen who still hires remote vs who quietly ended the exception.
My Tiny Rocket retweeted
Slack is for morning triage. Telegram is for "wake me".
Deploy success is P3, put a unique_key on flaky CI so it doesn't double-ping.
Quiet hours: only critical overnight, held stuff is skipped and lands in the digest, not a 7am flood.
eventsend.io/docs/alerting/q…
You wait almost two months to get paid. Your GC thinks it's five weeks...
While that money's still out, keep every receipt on the job so you know what you've spent and what's still owed.
tryobra.com/guides/construct…










