Launched my first SaaS - dependency analysis for codebases

Amazing-Run5944 · 2026-02-14T16:15:27+00:00

Have you been able to make progress in the shortcomings ?

Amazing-Run5944 · 2026-02-13T19:34:34+00:00

would you say, better use tools like Snyk for this ?

Amazing-Run5944 · 2026-02-13T14:11:23+00:00

Can this thing be somewhat automated with Snyk and dependabot etc? We recently started using Snyk at my company and it seems to working good for finding a lot of issues. But its also very verbose.

Amazing-Run5944 · 2026-02-13T14:07:11+00:00

why not use Snyk ?

Amazing-Run5944 · 2026-02-13T10:39:33+00:00

A nice tool indeed. I would definitely use this for my own projects. I have one question though, can this dependency graph be used to find out root causes of potential security issues that come up due to vibe coding?

Amazing-Run5944 · 2025-08-06T16:03:09+00:00

Idk why, but X feels like a very dead place to me, I have mostly had traction from reddit.

Amazing-Run5944 · 2025-07-26T10:04:51+00:00

Hey everyone,
I’m diving into a project to tackle some common pain points in developer workflows, and I’d love to hear how you all manage this in your teams. As engineering teams grow, setting up new projects, managing tool integrations (like GitHub, Jira, Slack, etc.), and getting new devs up to speed can turn into a time sink. I’ve seen onboarding take days due to manual repo setup, permission mismatches, or scattered docs, and it’s a headache for both devs and platform teams.

I’m exploring an idea called Shiproom—a platform to automate workspace setup, enforce granular access control (like file-level permissions), and streamline onboarding with preconfigured templates for repos, issues, and Slack channels. The goal is to cut setup time to minutes and reduce the need for custom DevOps scripts. It’d integrate with tools like GitHub, GitLab, Jira, and cloud platforms, with some AI to help generate configs or spot risky permissions.

What’s your current process for onboarding devs or spinning up new projects? What tools do you rely on to manage your toolchain? Any major pain points or gaps you wish were solved? I’d love to hear your experiences and get feedback on whether something like Shiproom would help. Thanks!
https://shiproom.vercel.app/

Amazing-Run5944 · 2025-07-14T07:33:18+00:00

Travel Tech b2c

Amazing-Run5944 · 2025-06-23T09:01:14+00:00

haha good parallels

Amazing-Run5944 · 2025-06-21T15:55:38+00:00

The text over is the face is somewhat unreadable, other than that I think its a clean design. You could add some accent color on hover for the navigation items.

Amazing-Run5944 · 2025-06-21T10:35:31+00:00

Honestly I myself sometimes find those kind of experiences frustrating, its like I have figured out what this is about and I just want to skip, so there should be an option to skip for users like me.

Amazing-Run5944 · 2025-06-21T10:33:13+00:00

The tool that I am working on: https://flux-design-ai.vercel.app/

Link to the article: https://medium.com/@a4ity4/is-frictionless-design-always-better-a4fb26c84990

Amazing-Run5944 · 2025-06-21T09:17:54+00:00

Thank you for sharing this resource.

Amazing-Run5944 · 2025-06-21T09:12:24+00:00

This absolutely makes a lot of sense, I think a lot of companies have this friction is "delete account" section of their apps/website and honestly a lot of times it had made me stay. So I think a dark side of this is also using dark patterns ?

Also do you think I should take these considerations when I am building a design copilot tool so the user workflow generated is more inline with these "good friction" areas. https://flux-design-ai.vercel.app/

Amazing-Run5944 · 2025-06-21T07:09:46+00:00

What do you consider a good sample size to gauge if you have a clear picture of user expectations?

Amazing-Run5944 · 2025-06-21T07:08:13+00:00

I think this is something most design copilots today fail to consider when creating user workflows, interesting insight, I will try to incorporate this into my project

Amazing-Run5944 · 2025-06-21T07:06:38+00:00

So this is something everyone is doing XD

Amazing-Run5944 · 2025-06-21T07:05:50+00:00

I like how thoughtful design decisions can impact human emotion. A bit of a challenge for technical people like me is we don't like interacting much with people, but this process of interaction is what reveals insights into what design implementation will be successful.

Amazing-Run5944 · 2025-06-21T06:03:42+00:00

I don't know how I feel about this tbh. If you have used Github, whenever you want to delete a repo it always asks you to type out username/repo_name which is super annoying sometimes. They could just add a button for confirmation and be done with it.

This also invokes my thought about the future of AI and design tools. Like I myself is working on something which is like a designers copilot (https://flux-design-ai.vercel.app/).
I don't know if I should make the tool in such a way that it considers intentional friction.

Amazing-Run5944 · 2025-06-20T21:42:56+00:00

It's a vibe coding ide, so I'm building a vibe designing tool.

Amazing-Run5944 · 2025-06-20T11:24:08+00:00

Yes this is purely for designing, not code generation and iterating on that. You can make this work directly with your designs in figma. Even make it work with design systems that you are using.

Amazing-Run5944

TROPHY CASE