Tobiko’s Post

𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿 𝗲𝘅𝗽𝗲𝗿𝗶𝗲𝗻𝗰𝗲 𝗺𝗮𝘁𝘁𝗲𝗿𝘀. 🌿 As a company, we’re rooted in our open-source community and guided by a philosophy of building products that make data workflows feel like second nature. That’s what we set out to do with our latest SQLMesh changes (which, by default, are also included in our hosted, enterprise-ready Tobiko Cloud). We overhauled the CLI output—from the language it uses to how it’s visually structured—to make building and debugging pipelines faster, more intuitive, and easier on the eyes 👀 This update gives you: ✅ Instant clarity on what SQLMesh is doing: a centralized view to see if your plan ran tests, built models, or triggered backfills as you intended ✅ Clear breakdowns of operations by stage (physical layer → execution → virtual layer) ✅ Smart defaults and optional verbosity, so you can move on when runs are successful, but have the color to deep-dive if they break ✅ Inline audit results (with ❌ or ✅) to help you avoid guesswork around blocking and non-blocking issues ✅ Thoughtfully reworded terms that better reflect what’s going on in your work or debugging flow—so you can minimize time spent asking questions or consulting docs We want your DevEx to be useful, beautiful, and trustworthy, to keep you in flow, and to make you feel that 'my CLI didn’t just tell me what happened, it also gave me the information I need to be confident in taking the next step.’ 👉 Read our blogpost for more details, and let us know what you think in the Tobiko community Slack—both linked in the comments below. #DataEngineering #SQLMesh #OpenSource #DevOps #TobikoCloud