It happens in client work more than people admit: a small change that is called urgent, sent at the end of the week, on a live site. Most of the time it is a text edit, but sometimes it touches checkout, a form or a plugin.
My own rule is still changing. I lean towards doing it only if I can test it and undo it quickly, and otherwise offering Monday morning. But some clients lose money while they wait, so it is not always that simple.
I ve been knee-deep this week in optimizing front-end state management for a real-time data table, and I ran into a frustrating bottleneck that I'm curious how others have solved.
Specifically, when polling or receiving high-frequency updates for fast-changing data sets (like live status grids), re-rendering the entire DOM tree causes noticeable input lag on mobile browsers, even with memoization.
Are you guys relying more on virtualized lists (like TanStack Virtual) to handle heavy DOM rendering, or shifting toward Web Workers to process payload diffs off the main thread?
Knowing keyboard shortcuts is literally a super-power. I have been trying to avoid the mousepad and use shortcuts wherever possible. For the last few days, I've got habitual to ( + + / ) for shuffling through Brave tabs. It's super convenient! Share your favourite keyboard shortcut or a productivity hack shortcut that very few people know
If you're a SaaS, digital product, agency or freelancer what payment gateways do you use to handle local methods, taxes and subscriptions?
PayPal charges me 5% per transaction and their support is unwilling to reduce it to 3% for me while I know they do lower the transaction fee for certain accounts.
The perfection of creations generated by artificial intelligence makes it difficult to distinguish fiction from reality.
The precision of AI images has advanced to the point that even professionals (graphic designers, video-makers) are sometimes not 100% sure of their authenticity.
I look at my GitHub profile and sometimes wonder if I'm doing this wrong
Here's what I currently maintain, solo:
WP Bones a Laravel-like framework for WordPress plugins. PHP, Composer, Blade templates. 169 stars, v2.0.3, active since 2018.
20+ Mantine UI Extensions React components for Mantine: Parallax (Apple TV card effect), Split Pane, Window (draggable/resizable), Rings Progress (Apple Watch style), QR Code, Onboarding Tour, and more. TypeScript, published on npm.
FinderGit a native macOS app that turns Finder into a Git-aware file browser. SwiftUI, no Electron, with inline diffs, Git actions, and AI commit messages. Free, in public beta.
octoscope a terminal dashboard for GitHub. Go + BubbleTea, with 7 themes (including a CRT phosphor mode), single binary via Homebrew.
Four languages. Four ecosystems. Four very different user bases. One person.
Our free invoice generator takes a JSON post with no account behind it and hands back a PDF. So it has limits on everything.
At most a hundred line items. At most twenty taxes on any one item. A length cap on every text field, a byte cap on the logo, and checks that run before anything expensive is decoded. Each limit was chosen by asking how large one field can reasonably be, and each one was sensible on its own.
Then we measured a request that respected every single one of them: a hundred items, each carrying twenty taxes. It answered 200, and it held a worker for about 62 seconds. The same hundred items with one tax each took about 2.4.
Nothing was broken. The limits multiplied. A hundred items times twenty taxes is two thousand line and tax pairs, and each one is printed in its line and, when the names differ, again as its own row in the totals. The item limit counts items. The per item tax limit counts what sits inside one item. Nothing counted the document.
Facebook finally moved on hiding likes but it's an opt-in feature rather than complete removal. On Instagram there's a per post option. Do you intend to hide your likes or hide your likes? Why or why not? What do you think of the update being "opt-in"?
