@klorityx · X

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

@manoj_surya_ · X

I just launched 🚀 A Proof of Ship, every day — straight from your GitHub. You already do the hard part: you commit. git-to-x turns that into a designed card and posts it to X every morning. Your timeline finally looks like what you actually are — someone who ships. → 8 card designs, rotating (terminal, heatmap, flame, ticker…) so it never gets stale → weekly + monthly milestone cards — your streak becomes a story worth following → tweet from your CLI / Cursor / Claude Code without leaving your editor → free for 10 days, full access See who else is shipping daily under #proofofship — and join them. It touches your repo, so safe-to-try came first: → open source (AGPL) — audit it or self-host → read-only — we never touch your code This is my first build-in-public tool. I built it for myself, and for anyone tired of switching between shipping and posting about shipping. First 100 get founding lifetime — a permanent number on every card. Try it, tell me

u/ramu9703 · Reddit

I built a public ledger that tracks a software idea from "shower thought" to shipped code hey everyone, I spent my weekend building a public backlog called vibehub (thanks 5.6 sol :) ) the main problem i wanted to solve is that too many good micro-ideas die in notes apps, and too many open-source projects launch without anyone knowing why they were built, who had the original spark, or how they evolved vibehub tracks the entire lineage of a project: - public feed of software briefs

u/Still_Amphibian545 · Reddit

almost launched a side project with my api keys sitting in the repo (a week free gpt 5.6 on us) was about a day from launching a small project when i noticed my openai key was just sitting in a committed file. it had been there for weeks. no idea how i missed it. made me wonder what else was wrong that i couldn't see. turns out for vibecoded stuff it's usually the same handful of things. secrets in the repo, endpoints with no auth, a database with no access rules, no limit on the ex

@hannah24_app · X

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

@dt_sqr · X

@WorksBreaks · X

Building Work Break; an AI-powered break and productivity assistant for teams. It helps you manage breaks, tasks, leave, meetings, and stays fully synced with Google Calendar all in one place. Would love your feedback! 👉

@akadhanu · X

an ai sprint retrospectives for it teams (

othmanosx · HN

I still don't like the fact that AI is adding more stuff for us to read, it's accelerating the code production but slowing down the code review. I built my own code reviewer as well ( https://pyor.review/ ), surfacing the important stuff first is the right track, but adding more stuff to read is daunting, but asking AI to just point you to what you need to focus on and skim the noise is what I'm leaning more towards.

@trackowork · X