That query you wrote three jobs ago that solves this exact problem? In CLOC it is a 15-second search, not a lost laptop. Keep your artifacts. #SQL#developers
Full API and webhooks. Sounds enterprise, actually means control.
Pull every project programmatically. Push events to @zapier or Make. Wire it into whatever else you run.
#API
Pulse started as an essay in 2021, not a product.
Sat as writing for four years.
Building it was a matter of finally being annoyed enough. Most useful software has that shape.
#buildinpublic
Bulk-import a zip of scripts. CLOC classifies them by function, learns your systems from rules you control, and silently skips exact duplicates. Even across imports. #SQL
Attachments live on private cloud storage with short-lived signed links. Nothing sits public. Your client's files deserve better than an email thread. #consulting
Make-ready contractors document completions in text-message photo threads and wait weeks to get paid. Mobile field view, GPS-pinned photos, paperwork done at the pole. Paid faster. #contractors
@github integration: import open issues as tasks, push tasks back as issues, link a repo to a project.
For consultants working in a client's repo and their own head, that gap is where things get dropped.
CLOC started in 1999 as one consultant's answer to 'what exactly did you change, and when.' 27 years later, same question, better tool. https://t.co/LwCFgTnrLm
Pro tip for client trust: hand them a live status link at https://t.co/SwmKQazz3U... Progress, task counts, optionally the ChangeLog. Always current, revocable the moment you say so. #consulting
Unpopular product opinion: a solo consultant with five clients does not have a workflow problem.
Dragging a card from Doing to Done is ceremony for a decision you already made.
They have a memory problem.
Client: "what did you do for us in March?"
You: forty minutes of archaeology through email and commits.
The work happened. The record of it did not.
https://t.co/ArwiZ18WbC
Shipped: CLOC mobile.
Open it, see what is overdue across every client, capture a task in four seconds, log what you just did.
No Gantt charts. No dashboards of dashboards.
#buildinpublic
The House just voted 308 to 117 to make daylight saving time permanent. The Sunshine Protection Act now sits in the Senate, where its odds are murky.
We build scheduling and data systems for a living, so we'll will say the quiet part: the clock change is two bad days a year. Time zone offsets are 365.
We have chased UTC-versus-local mismatches through job logs. We have watched handoffs slip because somebody's 9 Eastern was somebody else's 8 Central. No bill in Congress touches that.
Pulse does it differently. One global day. 1000 millidays. When you book @625, it is @625 for every person on the invite - High Point, Houston, or Helsinki. Nothing to convert. Nothing to spring forward.
Lock the clock. Then retire it.
https://t.co/VdmyBq7Jfq
#DaylightSavingTime #SunshineProtectionAct #Scheduling #RemoteWork #SoftwareEngineering
A statistic that surprised me:
A mid-sized EMC's joint-use department typically generates 5-10x more revenue than it costs to operate.
It is one of the highest-margin functions in the cooperative.
And it is staffed and tooled like an afterthought.
#PoleAttachment#BEAD #ElectricCooperative
Why the Southeast first: BEAD dollars hit pole owners here first, and the incumbent software is least loved here. GA, the Carolinas, TN, AL, MS. #BEAD#southeast