dpc94 · HN

Devthropology – Better Insights for GitHub Repos

@brankopetric00 · X

I've got two 😀: - automate your X presence - helps you break into DevOps

bhagyeshsp · HN

First things first: On the landing page, click on the "demo" link below the Hero section to try it without jumping any hoops ** I'm a long-time Basecamp user and satisfied with its overall functionality. Of course, there are many things that can be improved but that is not the point of this post. *Background* Basecamp lets users create "Projects". These projects are isolated workspaces that contain: members, todos, chat, files, message board, and calendar, etc. My issue was with the scattered calendars. Because I (and every other Basecamp user) creates a dedicated project for different scope of work, even if it is for the same client. For example, at any given time, I may have 4 projects for client-X and 3 projects for client-Y. *My pain point* I have experienced that most clients (especially the decision-makers) do not use Basecamp as often as we--the agency folks use it. They just use it when some reviews or comments are required or some file access. The clients organize their

@akadhanu · X

an ai sprint retrospectives for it teams (

vuphanse

@SyedHuz61085101 · X

Please visit to see my work. Thank you.

tahazsh · HN

Hi! I’m Taha. In many agentic products that support workflows (including one I worked on), I noticed they either don’t support node-based editors, or use React Flow and go through the difficult work of integrating it into their product to run it and work with their existing logic. So I thought about creating a tool that could help with this by closing the gap between the editor and the runtime. That’s why I created Wayflow. The basic architecture is simple: you just need to create a graph (which is a JSON object) that the runtime knows how to run. The runtime doesn’t care where that graph is coming from, it just needs the right schema. And with the help of the editor, you can create the graph, and then export it or directly save it on your backend in your database. And then when you want to execute it, you just hand it to the runtime. The runtime can either stream the execution (which is useful for the editor), or give you the final result. How you execute the graph is up to you: t

@klorityx · X

One workspace for project management, documentation, test management & CRM. Enterprise features without enterprise pricing.

@kngkng182542 · X

If you're paying for Canny, give FeedLog a look. Same workflow for collecting feedback and managing feature requests, but free during launch.

@japangor · X