惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

G
Google Developers Blog
D
Docker
Stack Overflow Blog
Stack Overflow Blog
GbyAI
GbyAI
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
Google DeepMind News
Google DeepMind News
M
MIT News - Artificial intelligence
H
Help Net Security
T
Tailwind CSS Blog
Engineering at Meta
Engineering at Meta
L
LangChain Blog
MongoDB | Blog
MongoDB | Blog
腾讯CDC
H
Hackread – Cybersecurity News, Data Breaches, AI and More
S
SegmentFault 最新的问题
博客园 - 司徒正美
C
Check Point Blog
B
Blog
Y
Y Combinator Blog
Microsoft Azure Blog
Microsoft Azure Blog
P
Proofpoint News Feed
F
Fortinet All Blogs
美团技术团队
D
DataBreaches.Net

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
A repeatable workflow for paper figures so you stop redra...
FigCanvas · 2026-05-31 · via DEV Community

FigCanvas

If you've shipped a paper, you know the figure tax: you build a beautiful schematic, a reviewer asks you to move one box, and you spend an afternoon re-aligning everything by hand. Do that across three revisions and you've spent more time nudging vectors than running the analysis.

I started treating figures the way I treat code: as something that should be regenerable from a source, not hand-crafted once and patched forever. Here's the workflow that stuck.

1. Write the figure as text first

Before opening any drawing tool, I write the figure as a plain description in the repo:

ligand -> receptor (binding)
receptor -> kinase (activation)
kinase -> targetA, targetB (phosphorylation)
targetA -| receptor (inhibition, feedback)

This forces the logic to be explicit. If you can't write the relationships down cleanly, the figure isn't ready — and that's a science problem, not a drawing problem.

2. Generate a first draft instead of starting from a blank canvas

I feed that description into a tool that will create scientific figures with AI and get a laid-out first draft. The point isn't "AI does my figure." The point is the boring geometry — consistent boxes, even spacing, arrow routing — is done before I start, so my time goes into the parts that need judgment.

3. Keep the output editable and vector

The non-negotiable: the result has to be editable vector, not a flattened PNG. When the reviewer asks to move a box, I move a box. When a journal wants a different size, it scales without turning into mush.

4. Treat revisions as diffs

Because the source description lives in the repo, "revision 2" is a diff, not a rebuild. I change the text, regenerate, fix the few labels that matter, export. Twenty minutes instead of an afternoon.

What this doesn't solve

It won't make a bad figure good — encoding, color logic, and what you choose to show are still on you. And the first draft always needs cleanup; anyone promising one-click publication figures is selling something.

But moving the source of truth from "a fragile vector file" to "a text description plus a generator" changed figures from a dreaded last step into something I can iterate on as fast as I iterate on the writing.

How do you handle figure revisions? Still hand-editing in Illustrator, or have you found a more reproducible setup?