{"id":2233,"date":"2026-07-14T20:51:25","date_gmt":"2026-07-14T19:51:25","guid":{"rendered":"https:\/\/entertainmentnews.site\/index.php\/2026\/07\/14\/a-dash-of-dev-to-my-blog-stats-now-live-in-the-terminal\/"},"modified":"2026-07-14T20:51:27","modified_gmt":"2026-07-14T19:51:27","slug":"a-dash-of-dev-to-my-blog-stats-now-live-in-the-terminal","status":"publish","type":"post","link":"https:\/\/entertainmentnews.site\/index.php\/2026\/07\/14\/a-dash-of-dev-to-my-blog-stats-now-live-in-the-terminal\/","title":{"rendered":"A Dash of dev.to: My Blog Stats Now Live in the Terminal"},"content":{"rendered":"
\n

The topic A Dash of dev.to: My Blog Stats Now Live in the Terminal<\/strong> is currently the subject of lively discussion \u2014 readers and analysts are keeping a close eye on developments.<\/p>\n

This is taking place in a dynamic environment: companies\u2019 decisions and competitors\u2019 reactions can quickly change the picture.<\/p>\n

Hello, I’m Maneshwar. I’m building git-lrc, a Micro AI code reviewer that runs on every commit. It is free and source-available on Github. Star git-lrc to help devs discover the project. Do give it a try and share your feedback.<\/p>\n

I check my dev.to stats more often than I would ever admit in a job interview.<\/p>\n

Reactions, views, comments, the little numbers that go up, and the ones that stubbornly refuse to.<\/p>\n

Normally that ritual means opening a browser, clicking into the dashboard, and squinting at one article at a time like I’m reading tea leaves.<\/p>\n

My top articles ranked by likes, by views, and by comments, all on screen at once, quietly refreshing itself while I pretend to do real work.<\/p>\n

It took a tiny Go program, one wonderful archived project doing the heavy lifting, and two bugs I absolutely did not order but got served anyway.<\/p>\n

There is an endpoint, GET \/api\/articles\/me, you send your API key in an api-key header, and you get back every article you have published with the fields that matter already counted for you: positive_reactions_count, page_views_count, and comments_count.<\/p>\n

You can generate a key at your dev.to settings under Extensions.<\/p>\n

Grids, colors, borders, keyboard handling, refresh loops. Life is short xD<\/p>\n

Three, therefore, I needed something that already draws pretty terminal dashboards and would happily show my numbers if I fed it nicely.<\/p>\n

devdash is a highly configurable terminal dashboard by Matthieu Cneude, better known as Phantas0s.<\/p>\n

It has widgets for GitHub, Google Analytics, Google Search Console, Travis, and more, and the entire layout is driven by a single YAML file.<\/p>\n

Two small catches. It has been archived since 2023. And it has precisely zero concept of what dev.to is.<\/p>\n

Now, I could have forked it, added a proper Forem service, wired up structs, written tests, and opened a pull request into a repo that is politely closed for business.<\/p>\n

You hand it a shell command, it runs that command, and it renders whatever the command prints as a bordered table.<\/p>\n

It splits each line of output on whitespace and slots the pieces into columns. That is the whole contract.<\/p>\n

It just needs a command that prints rows. I can be that command.<\/p>\n

If Matthieu ever reads this: thank you for building a tool flexible enough to be abused this gracefully.<\/p>\n

Go bother Matthieu on X and tell him his archived project is still out here pulling shifts.<\/p>\n

\"\"<\/figure>\n

The little Go binary in the middle is the only thing I actually had to write.<\/p>\n

It fetches all my articles (paginating 100 at a time until dev.to runs out), keeps only the published ones, sorts them by whichever metric devdash asks for, and prints clean rows.<\/p>\n

And the config just points three table widgets at three flavors of that command.<\/p>\n

Three of those blocks, colored red, green, and yellow, sitting side by side. In theory, done.<\/p>\n

I turned it on. Overview strip populated. Most Liked, glorious. Most Commented, present.<\/p>\n

The clue was in how devdash refreshes: it fires every widget concurrently, each in its own goroutine, all at the same instant.<\/p>\n

Four widgets meant four copies of devto-stats sprinting at the dev.to API at once, elbows out. dev.to did the sensible thing and replied 429 Too Many Requests.<\/p>\n

I had built a very small, very polite denial of service attack against myself.<\/p>\n

The fix is the boring, correct one: on a 429, wait and retry, with backoff plus jitter.<\/p>\n

The jitter is the important part. Without it, all four back off by the same amount and collide again, like four people apologizing and stepping the same way in a hallway.<\/p>\n

The first row looked fine, then every row below slid one column right.<\/p>\n

Here’s what devdash does under the hood: it splits each line on whitespace to get cells, joins those cells back together with commas, then splits the whole batch on commas again to chunk it into rows of N columns.<\/p>\n

A comma inside a title is indistinguishable from a comma devdash added on purpose.<\/p>\n

One title becomes two cells, the row has four pieces instead of three, and because the chunking is global, every row after it is shifted forever.<\/p>\n

The real fix belongs upstream, in a repo that isn’t taking visitors.<\/p>\n

My binary already slugifies titles to survive the whitespace split.<\/p>\n

Here is the raw feed one panel runs on, straight out of the binary, real numbers from my actual account:<\/p>\n

devdash takes three of those feeds and frames them into colored, bordered, self refreshing tables sitting shoulder to shoulder: Most Liked in red, Most Viewed in green, Most Commented in yellow, with a summary strip across the top.<\/p>\n

\"\"<\/figure>\n

Ctrl+R forces a refresh, Ctrl+C quits, and left to its own devices it repaints itself every five minutes.<\/p>\n

444 articles, all of them accounted for, no browser, no clicking, just a quiet terminal telling me the truth about which posts people actually read.<\/p>\n

The best integration is often no integration. devdash never learned about dev.to.<\/p>\n

I made dev.to speak devdash’s language instead, and a tool that stopped being maintained in 2023 rendered 2026 data without a single change to its source.<\/p>\n

The whole thing, Go helper, YAML, and Makefile, is here: lovestaco\/devto_devdash.<\/p>\n

Sometimes the best tool for the job is one somebody stopped working on years ago, sitting there quietly, still perfectly happy to dash off one more dashboard.<\/p>\n

AI agents write code fast. They also silently remove logic, change behavior, and introduce bugs \u2014 without telling you. You often find out in production.<\/p>\n

git-lrc fixes this. It hooks into git commit and reviews every diff before it lands. 60-second setup. Completely free.<\/p>\n

Any feedback or contributors are welcome! It’s online, source-available, and ready for anyone to use.<\/p>\n

GenAI today is a race car without brakes. It accelerates fast — you describe something, and large blocks of code appear instantly. But AI agents silently break things: they remove logic, relax constraints, introduce expensive cloud calls, leak credentials, and change behavior — without telling you. You often find out in production.<\/p>\n

git-lrc is your braking system. It hooks into git commit and runs an AI review on every diff before it lands. 60-second setup. Completely free.<\/p>\n

In short, git-lrc helps Prevent Outages, Breaches, and Technical Debt Before They Happen<\/p>\n

At a glance: 10 risk categories \u00b7 100+ failure patterns tracked \u00b7 every commit\u2026<\/p>\n

Templates let you quickly answer FAQs or store snippets for re-use.<\/p>\n

Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment’s permalink.<\/p>\n

For further actions, you may consider blocking this person and\/or reporting abuse<\/p>\n

Thank you to our Diamond Sponsors for supporting the DEV Community<\/p>\n

Google AI is the official AI Model and Platform Partner of DEV<\/p>\n

DEV Community \u2014 A space to discuss and keep up software development and manage your software career<\/p>\n

Built on Forem \u2014 the open source software that powers DEV and other inclusive communities.<\/p>\n

We’re a place where coders share, stay up-to-date and grow their careers.<\/p>\n