Ellie Huxtable
@ellie.wtf
2 months ago Thank you so much! Another session on Friday 😁
💬 0
♻️ 0
❤️ 2
Thank you so much! Another session on Friday 😁
when a developer has to market anything they’ve made.
#ZedEditor
Download Zed and view the full changelog here:
zed.dev/releases/sta...
The Zed agent panel has received some extra polish: - Mistral tool-calling support - Improved UX for editing previous messages - Improved UX for dismissing an edit to a previous message - Improved responsiveness of mouse interactions with the agent panel
Icons now appear next to files and folders when Zed is configured to use its custom picker instead of the system-provided dialogs for `Open` and `Save As` operations ( `"use_system_path_prompts": false`).
🚀 Zed v0.188 is out! Zed can now parse and load host names from the SSH config. To disable this behavior, use `"read_ssh_config": false` in your `settings.json` file.
Scaffold your database with just a few prompts, right inside @vscode.dev.
In this video, we use the Copilot Agent via the Prisma extension to:
✅ Generate a schema
✅ Define models + relations
✅ Migrate to a fresh Prisma Postgres DB
Check it out 👇
pris.ly/yt/copilot-ppg
Help us explore the current state of continuous integration in Apple development and how it can be enhanced:
community.tuist.dev/t/whats-you...
📚 When v7 comes, we'll share comprehensive upgrade documentation so that you're well equipped for this change.
In the meantime, check out our blog post going into this topic in even more details!
pris.ly/output-article
🤨 In essence: things that worked fine in `node_modules` suddenly broke.
If you saw this warning, added an `output` path and saw errors due to that, we recommend that you simply revert to generating into `node_modules` for the time being.
🚨 But many developers hit issues after switching to a custom `output` path.
Some saw linting errors in the generated code, which broke their dev servers (because lint errors block startup).
Others ran into bundling problems, path resolution headaches, and more.
7️⃣ In the upcoming v7 major release, there'll be a breaking change: You'll need to set a custom `output` path for the generated Prisma Client instead of generating it into `node_modules`.
To help anticipate this change, we:
- added a deprecation warning
- updated our docs
⚠️ You may have seen this deprecation warning about not using a custom `output` path when using Prisma ORM lately.
We introduced this in v6.6.0 to help you prepare for a breaking change. However, the warning caused some confusion und unexpected issues.
👇 Here's what happened.
comms from the browser company, i still like their tone and candidness. an ai-chat centric web browser to me is both horrifying and boring all at the same time, a real never-ever-do-that idea browsercompany.substack.com/p/letter-to-...
pretty happy with this one still trying to practice daily, while walking around + living life ricoh gr3 is <3
strong cosign dansinker.com/posts/2025-0...
What would your marketing/content team ask for if they had a magic wand?
How about the ability to build on-brand landing pages with an AI agent in minutes vs. manually reinventing the LP wheel over the course days?
We'll show you how with our new MCP this Thursday - directus.is/d7m7oIc
new technology to chat with your old self: read your old journals
🎥 We're live on Youtube!
www.youtube.com/watch?v=KuU...
Atuin just creeped past 24,000 GitHub stars! 🥳
ah yes, you were using gemini-4o-xx1-beta-2, of course you got bad results, you have to use openai-o3-mini-xxl and toggle on the 'do it good' button
Someone needs to interview me about this! 👀