Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

Every project management tool was designed by project managers, for project managers. This one was designed for ADHD, dyslexic, and autistic brains instead. And it turns out that also makes it better for literally everyone who just wants to get work done without configuring a tool for two weeks...

30,789 görüntüleme • 7 gün önce •via X (Twitter)

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

i just built a 4-agent software team. everything runs from Telegram and gets managed on a kanban board. a project manager who plans the work, a backend developer, a frontend developer, and a tester. the PM reads a goal, breaks it into linked tasks, and assigns each to the right agent. the thing that makes them a team instead of four strangers is a shared kanban board. every task is a row that survives crashes, and when an agent finishes, it writes a summary of what it built and what the next agent needs to know. the next agent reads that summary before it starts. so the frontend developer never has to guess the API shape, and the tester knows exactly what to verify. the hardest part was not the coordination. it was building an agent that could actually act like a backend engineer. a backend engineer stands up a database, wires auth, manages storage, deploys functions, and keeps all of it consistent while the rest of the team builds on top. an agent doing this from scratch drowns. it burns its context window remembering which tables exist and which endpoint it created three steps ago, and the work degrades fast. so the backend agent needs a backend built for agents, not for humans clicking through a dashboard. that is where InsForge came in. it is an open-source, agent-native backend, and i added it to my backend developer agent as a skill. a skill is a step-by-step guide that teaches the agent how to do a specific kind of work. with InsForge installed, the agent stopped improvising infrastructure and followed a reliable path: create the project, define the database, set up auth, deploy functions. to test the whole team, i had them build a working Google Docs clone, AI features included. the backend agent spun up the full service on its own. database tables, user auth, document handling, and edge functions running real TypeScript, all in one dashboard. the frontend agent read that summary and built the UI on top of it, and the tester closed the loop. the result was a backend an agent could reason about end to end, instead of one it kept getting lost inside. if you are building an AI backend engineer, InsForge is worth a look, it's 100% open-source. InsForge GitHub: (don't forget to star 🌟) the full article on Hermes Kanban: Mission Control for your Agents is quoted below.

Akshay 🚀

118,124 görüntüleme • 1 ay önce

Every day we hunt for the tools that turn “impossible” into “anyone can do it.” This morning I found something different. Not a new tool. A whole platform that’s turning Gen Z into hardware poets and accessibility pioneers in 48 hours. What we saw inside REDHackathon just quietly rewrote my mental map of where the real AI frontier is moving. Let me show you. A Chinese Gen Z team just built a full AI product from scratch in 48 hours and took second place at REDHackathon, a competition built to push young developers to ship real functional AI software under a brutal deadline. The product is called Attune and it actually works. The traditional UI was like a static map — you're the traveler, and you have to know exactly where you're going. But Attune has built a living ecosystem. The UI can sense your needs and react accordingly. The interface comes to you. Clean UI, sharp interaction design, production level output in two days. Local heuristics instantly grab clickable elements on the page and pop up a radial menu near your cursor. AI runs async as an enhancement layer, not a dependency — so no lag. In 48 hours, they also solved: style loss on cloned DOM, input sync back to original elements, and popup repositioning. Shadow DOM inline styles, a proxy input system, relayout logic — the works. This is not a school project. This is what happens when serious builders get the right environment to compete in. rednote built REDHackathon to give exactly this kind of talent a global stage and Attune is proof the standard is high. rednote #redhackathon #rednote #technology #AI Watch the demo and see it for yourself:

AI Frontliner

215,833 görüntüleme • 3 ay önce

INTRODUCING FIZZY Have you noticed that every issue and idea tracking tool you loved slowly morphed into boring, sluggish, corporate bloatware? Trello put on 40 pounds of cruft. Jira started charging by the migraine. Asana tried to become everything to everyone. GitHub Issues slipped into a steady state of decline. The whole category is a 20 car pileup of complexity. Time to route around that mess. Today we’re introducing Fizzy. Kanban as it should be, not as it has been. Fizzy is a fresh take on cards and columns, with a few twists, human-nature inspired defaults, and a vibrant interface that’s the opposite of the bland and boring software the industry has been flinging at you for years. Kanban has been around since the 1940s, and Trello brought it into the mainstream in 2011. Since then, some version of column-based kanban-style organization has found its way into any collaboration tool worth its salt. But most have over salted the dish. What was simple is now complicated. What was clear is now cluttered. What just worked now takes work. Fizzy presses reset, reconsiders what really matters, and presents a refreshing way to kanban that just feels right. It’s friendly, colorful, straightforward, and fast as hell. We still use Basecamp for our big, intensive projects, but lately we’ve been reaching for Fizzy to run the smaller ones. It’s perfect for tracking bugs, issues, and ideas, and it shines for lighter, self-contained workflows like podcasts or video production. We didn’t expect it, but Fizzy’s so good it might even cannibalize Basecamp on the lighter side of project management. We’d be thrilled. How much is it? It’s not much for so much. Everyone gets 1000 cards for free. Beyond that, we’ll host your account for just $20/month for unlimited cards and unlimited users. One price for all and everything. No tiers, no “contact us.” No pricing chart at all — just a price tag, like on a pair of jeans. And here’s a surprise... Fizzy is open source! If you’d prefer not to pay us, or you want to customize Fizzy for your own use, you can run it yourself for free forever. Have a great idea? Submit a PR to contribute to the code base and improve the product for everyone. It’s the best of all worlds. No excuses. Every idea comes back around. It’s time for take two on kanban. Fizzy’s our hat in the ring. Let’s make this platform insanely great, together. Come on in! Visit

Jason Fried

561,372 görüntüleme • 7 ay önce

Elon Musk just described the extinction of death. Not in a white paper. Not in a press release. Dropped mid-summit like it was a footnote. Musk: “You’ll have kind of a whole brain interface that is perhaps a form of immortality. Your brain state is essentially stored. You’re backed up on a hard drive.” The timeline still thinks Neuralink is a medical device. A clever trick to help paralyzed patients move a cursor with their thoughts. They are grading a civilization-ending technology on its first feature. Musk: “You can always restore that brain state into a biological body or maybe a robot or something.” Your memories. Your personality. Your conscious identity. Stored. Backed up. Transferred to a new vessel when the first one fails. That is not medicine. That is the termination of the oldest contract in human history. Every civilization ever built was organized around one immovable certainty. You are born. You get a handful of decades. You disappear. Religion was built on that certainty. Inheritance law was built on it. Every economy, every legal framework, every philosophy ever built was downstream of one non-negotiable fact. People expire. Remove that fact and you do not reform society. You pull the pin on every structure it stands on. Then Musk connected it to the intelligence race. Musk: “The rate at which we’re building digital superintelligence, it may just be that we’ll have digital superintelligence and it’ll just solve the problem for us. But in the meantime, we’ll keep progressing with our meat computers.” Meat computers. That is not dark humor. That is the engineering spec. The real reason billions are flooding into superintelligence is not productivity. Not chatbots. Not enterprise software. It is the oldest and most desperate problem in the history of the species. How to not die. Every founder pouring capital into the intelligence race is not just building a company. They are building a clock that might outrun their own biology. The old world accepted an ending. Planned around it. Saved for retirement. Built structures designed to outlast the person who made them. The builders are not planning to be outlasted. They are engineering around the ending itself. And here is the part nobody is confronting. Every urgent thing you have ever done. Every risk you ever took. Every moment that felt like it mattered. All of it was powered by the quiet knowledge that your time was running out. Mortality was never just the thing that killed you. It was the thing that made you move. The builders are trying to remove it. And nobody has asked what replaces the only deadline the species ever respected.

Dustin

359,015 görüntüleme • 2 ay önce

Elon Musk just said out loud what the entire robotics industry spent thirty years refusing to see. Musk: “Humanity has designed the world to interact with a bipedal humanoid with two arms and ten fingers.” Every staircase. Every doorknob. Every factory floor. Every hospital corridor. Civilization is not an open environment. It is a monument built around one specific body. The industry spent decades engineering quadrupeds, wheeled machines, exotic locomotion systems. Then spent more years asking how to retrofit the world around them. Tesla never asked that question. Musk: “If you want to have a robot fit in and be able to do things that humans can do, it must be of roughly the same size and shape and capability.” This is not a design philosophy. It is a pass key to every structure humanity has ever built. Optimus does not navigate civilization. It inherits it. Musk: “Work that is repetitive, boring, dangerous. Basically, work that people don’t want to do unless they’re paid to do it.” Remove every task performed out of obligation rather than choice. What remains is pure cognitive output. Not automation. The liberation of human attention at species scale. The interviewer pushed back directly: “I thought four legs are better.” Musk laughed. Musk: “Four legs good, two legs bad.” Someone in the room said exactly what the entire industry believed. He dismissed it with an Orwell joke and moved on. Whoever fields this first does not gain a labor advantage. They inherit the physical layer of civilization itself. Every structure ever built. Every tool ever forged. Every corridor ever designed. Already engineered for this exact body. The world was never neutral ground. It was always waiting for the right body to walk through it. Someone was always going to see it. Most just spent thirty years looking away.

Dustin

420,169 görüntüleme • 4 ay önce

Pi was built when there were already agent harnesses around. Here’s why Mario Zechner(Mario Zechner), found them suboptimal and built Pi, a minimalist self-modifying agent: #1 - Mario initially was a believer in Claude Code: "I was a believer in Claude code because they were the first that packaged agentic search up in a really compelling package. And at the time that fit my workflow really well. Everything around the LLM was kind of nice and tidy and easy to understand. I was super happy. I was proselytising Claude code." #2 - Reverse engineering Claude Code highlighted the degradation that Mario felt as a user: "I personally like simple tools that are stable and that I can rely on. Even if they have non-deterministic parts, all the deterministic parts should be as stable as possible. That was just not the experience with Claude Code around summer 2025. They would take away your control of the context. They would inject stuff behind your back, which is bad. Then, your workflows stopped working because there's now a system reminder that you don't even see in the UI that would modify the behaviour of the model. They would also do this to the system prompt. I built a little service where I can track the progression or evolution of the system, prompt and tool definitions and, with every release, it was messing with stuff. That just messed with my workflows and I don't appreciate that." #3 - PI was built with an appreciation for simple and reliable tools: "If I commit to a development tool, I want it to be a stable, reliable thing like a hammer. I don't want my hammer to break a different spot every day. That's terrible. We need somebody who goes the full velocity kind of way. But I don't want to work with a tool like that."

The Pragmatic Engineer

62,825 görüntüleme • 2 ay önce