DEV Community: Daniel Moya

How Vim in AI-era would looks like?

Daniel Moya — Sat, 07 Nov 2026 16:17:03 +0000

I just revamped AIVim, my open-source terminal editor built with Python and Textual.

The part I care about most isn’t generating code. It’s keeping control afterward: reviewing individual changes, rejecting them, and rolling back when needed.

The GIF shows a simpler flow: write an instruction, leave a blank line, and keep typing while it becomes code. Each accepted block is one undoable edit.

I use agentic tools nowadays but at work, sometimes I do small edits in scripts using small local models, and this is useful (and better when the model has high token throughput .. and TTFT is low)

Enjoy, BR,
Daniel

Scoring wiki pages for staleness, with reasons you can read

Daniel Moya — Thu, 29 Oct 2026 10:34:07 +0000

I'm Daniel Moya, the developer of LiveWiki.

A score alone doesn't help much. "This page is 0.7 stale" tells a writer nothing. So each LiveWiki page gets an AI staleness score with the reasons it may be out of date, and the reasons are what people act on.

How teams use it:

Sort pages by score to build a review list.
Read the reasons to decide whether to update, merge or retire a page.
Let AI propose the edit if you like; it stays a draft until a person approves it.
Answers keep linking their source, so readers can check what they're told.

Try it: open the sample workspace at https://livewiki.foor.tech (no signup) and compare a page's reasons with your own judgement. The free plan covers up to 5 members.

– Daniel Moya, developer

Three ways to move a Confluence space into LiveWiki (and what I'd check first)

Daniel Moya — Thu, 22 Oct 2026 09:37:20 +0000

I'm Daniel Moya, the developer of LiveWiki. This post covers how its Confluence import works.

LiveWiki accepts Confluence content three ways: an XML export, an HTML export, or directly through the Confluence Cloud API. MediaWiki sites import from their XML export.

What I'd check before migrating

Start with your most-viewed pages, not the whole space.
After import, look at each page's AI staleness score. It lists reasons a page may be out of date, which gives you a review list instead of a guess.
Ask a few real questions. Answers come only from published pages and link their source, so a wrong answer points straight at the page to fix.
Turn on the team: co-editing is real time, and AI edits stay drafts until a person approves them.

Try it: open the sample workspace at https://livewiki.foor.tech (no signup) to see imported pages, staleness reasons and sourced answers. If it fits, the free plan covers up to 5 members, or take the 30-day trial with no card.

– Daniel Moya, developer

The 6 checks I run before sending a single cold email

Daniel Moya — Fri, 16 Oct 2026 08:21:47 +0000

You wrote the email, picked the list, and hit send. A week later the replies are near zero and you can't tell whether people ignored you or never saw it. Usually it's the second one. Here's the checklist I go through before any cold campaign:

SPF: dig TXT yourdomain.com should return exactly one v=spf1 ... record that includes every service sending for you, ending in ~all or -all. Two SPF records means SPF fails.
DKIM: find your provider's selector (for example google._domainkey) and run dig TXT selector._domainkey.yourdomain.com. No key means mail you can't prove is yours.
DMARC: dig TXT _dmarc.yourdomain.com. Start at p=none; rua=mailto:... so you get reports, then move to quarantine once things line up.
MX: the sending domain needs working MX records. A domain that can't receive mail looks disposable.
Spam words and formatting: words like "free!!!", "guaranteed", all-caps subject lines, image-only emails and link shorteners all hurt.
Warm-up and throttling: a new mailbox sending 200 emails on day one is a red flag. Ramp up slowly and spread sends through the day.

Try this today: run the three dig commands above on your sending domain before your next campaign. It's a short check, and it can save the whole send.

Disclosure: I'm the developer of MarkOn, an AI SDR in free private beta. It runs these SPF/DKIM/DMARC, MX, spam-word, warm-up and throttling checks for you, then writes personalised sequences without templates. If you'd rather not run dig by hand, it's a private beta: leave a comment and I'll send you an invite.