Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

new Sizzy - The Browser For Developers feature: dependencies 🔥 👀 browse the dependencies of your project 🔎 easily filter them 🧐 spot outdated dependencies 🌐 open github/npm link for a dependency dependency actions coming 🔜 (change version, move, etc) pls let me know if you have more ideas 🙌

13,159 Aufrufe • vor 2 Jahren •via X (Twitter)

11 Kommentare

Profilbild von kitze 🚀
kitze 🚀vor 2 Jahren

sizzy is obv. not just a browser, so I'm wondering if it's time for changing the tagline 🤔 we tried it once, and it didn't convert well. the ultimate tool for frontend devs? the studio for frontend development? pls give suggestions

Profilbild von Kasper Mikiewicz
Kasper Mikiewiczvor 2 Jahren

@sizzyapp You can take a few ideas from Dunno which api you use for package searching but Algolia registry is pretty solid (I've used npm search and one other mirror but those broke from time to time and results weren't that relevant)

Profilbild von Tobi Obeck
Tobi Obeckvor 2 Jahren

@sizzyapp How about? green = up to date orange = out of date red = out of date and security vulnerabilities detected

Profilbild von kitze 🚀
kitze 🚀vor 2 Jahren

@sizzyapp oooh, I like it!

Profilbild von Mejias
Mejiasvor 2 Jahren

@sizzyapp how can I try this?

Profilbild von kitze 🚀
kitze 🚀vor 2 Jahren

@sizzyapp in the new Sizzy update, coming soon

Profilbild von Taylor Covington
Taylor Covingtonvor 2 Jahren

@sizzyapp How do I update my Sizzy app to get these updates? I’m not seeing them yet.

Profilbild von Fran Zekan
Fran Zekanvor 2 Jahren

@sizzyapp Oh damn, this is actually super useful and a super nice UI 👏

Profilbild von kitze 🚀
kitze 🚀vor 2 Jahren

@sizzyapp you'll still edit your package json with vim or something

Profilbild von Mihovil Ilakovac
Mihovil Ilakovacvor 2 Jahren

@sizzyapp When do we get the .sizzyrc config file 🔥

Profilbild von kitze 🚀
kitze 🚀vor 2 Jahren

@sizzyapp I was thinking of adding it as a package.json entry but this would be better because it would work across languages/tech 🤔

Ähnliche Videos

#1 skill for developers in 2026: Automate everything you can using AI. I bet my lunch your team is dealing with all of these: • Stale documentation • Outdated dependencies • Poor test coverage • Deprecated APIs Every company I work with has these same problems. You can solve all of these right now. Automatically. Using AI. Here are 3 examples. Watch the attached video: I'm using Ona Automations to tackle this. These are background agents that run in the cloud, in a fully configured dev environment with your toolchain, your dependencies, and your services. You can run an unlimited number of these agents in parallel and across all your repositories. Claude Code and Codex only run locally, so they are hard to scale, and you can't run them when your computer is closed. Ona runs in the cloud. Here are the three examples: 1. Test coverage Run a nightly automation to identify any untested code paths, generate candidate tests, verify they pass, and open draft PRs. You wake up every morning to PRs that improve your test coverage. 2. Dependency upgrades Configure a weekly automation that bumps a dependency version, runs your full test suite, and reports any regressions. If everything is clean, it opens a PR. If something breaks, it opens a report so you can decide what to do. 3. Documentation auditing Set up a weekly automation that checks recent commits against your README file and setup guides, identifies broken examples and outdated instructions, and opens a PR with fixes.

Santiago

25,804 Aufrufe • vor 6 Monaten

When I’m trying to improve the user experience of my applications, one of the most valuable things is being able to see an entire user flow as a storyboard. Not just one screen or screenshot at a time. This is something I love using the `/visual-plan` skill for. You can describe any flow you want, and the agent will look through your code and wireframe out a storyboard of what the flow looks like. Then you can visualize the steps in a simplified way and spot areas to improve. Recently, I found that in certain flows we were still asking for organizations, even though I thought I had gotten rid of that and made it automatic. A quick storyboard let me see all the different code paths in a simple, visual, intuitive way. Spot the areas of the flow I didn’t want. And have the agent fix it. Sign up, onboarding, and setup flows are usually some of the most important experiences in your app. And usually the least looked at. Especially because it can be hard to reproduce every flow, for every situation, for every user type, feature flag, or whatever else you have. The `/visual-plan` skill lets you visualize any part of your code. Either to understand the current state, plan out a new state, or recap updates that were made. I’m pretty addicted to this skill. I use it for a lot of other things too, so let me know if you want to see videos on those. And of course it’s all open source. You can grab it on my GitHub. I'll link to it in the thread. If you try it, let me know your feedback.

Steve (Builder.io)

148,260 Aufrufe • vor 2 Monaten

You can’t make anyone else change; all you can do is create the conditions where change is more likely to happen. I remember speaking with an administrator and hearing him complain that his staff wasn’t moving forward. Instead of commiserating with him at that moment, I said, “Maybe it’s you?” It caught him off guard, but there was a point. Too often, myself included, when we try to lead people to new ideas, and they don’t immediately embrace them, we blame them instead of looking at where we may be deficient. Sometimes, the new “approach” is sharing the ideas over again, only louder. That approach rarely works. In this week’s newsletter, I shared 3 things that have helped me rethink how to help create better conditions for others to embrace change. 1. Truly listen to their thoughts and viewpoints, and be open to the idea that your way might not be the best. 2. Recognize that you also had resistance to new ideas, including things that you might consistently do and believe today. Be open with your own story of resistance and what made you change. 3. Start by focusing on the areas in which others are excelling, as opposed to your perception of their deficits. People who feel valued are more likely to move forward. People who feel you are trying to “fix” them will fight you non-stop. You can only control your own actions. What do others see in you that will make them want to move forward, by your side? People are more likely to take steps forward on a path if they see footprints from others already on the ground. Read the entire newsletter here:

George Couros

15,735 Aufrufe • vor 2 Jahren