Activity
Mon
Wed
Fri
Sun
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
What is this?
Less
More
Clief Notes
55.8k
5.0
Free
138 contributions to Clief Notes
Building A Billion Dollar Business 101
I decided to re-commit to my business a month ago, after a few years of what I call the entrepreneurial rumspringa. Now, I ask myself just one question everyday: what's the constraint? In the last 3 years I attempted to start 5 different businesses, all while listening to business podcasts, and taking business courses. This period could be summed up as an era of financially paralyzing shiny-object syndrome, since those distractions came at a cost. It's not a coincidence that I have not made any financial progress in the last several years while I've been stretched across multiple areas of interest. Thank goodness that I finally learned that the dabbling has to end if I am going to go far. Also over the last few years, I have had many conversations with entrepreneurs and non entrepreneurs about what leads to success. SO many people believe that success is largely luck, which doesn't sit right with me. There's a saying that "success leaves clues," which means it's gotta be a lot more than just luck, if clues = patterns of behavior. All people have the same 24 hours in a day, so how are some people running billion dollar businesses and others get stuck for years at a time? From what I can tell, the entire formula for success -- whether it's done accidentally or intentionally -- is to remove the constraint of the business every time it gets stuck. This holy-grail concept is simple but not easy. Success requires that one both *recognizes* what is stopping the business growth and *refuses* to work on anything else until that thing is resolved. Most people cannot handle this. I heard someone say that being in business is like sitting in your living room with a trash fire next to you and being fine with it. And it's true! And not only is it true, but it's a skill to learn. Every time I ask my small business owner friends if they know what their constraint is, they list 10 things at a time. I have yet to see someone in that category tell me outright "my constraint is x." I get the impression that small business owners, for the most part, would rather be naive to their constraint than be forced to identify it. Rather than narrow it down to just one bottleneck, they are more comfortable tackling multiple issues at once, even if that stalls their growth. The more I talk to them, the more I see how insanely common it is for this archetype to be ADD at full speed in multiple directions at once. This has helped me recognize it in myself, and I'm determined to put an end to that madness, cause I want that bag more than I want to indulge that ADD, if you know what I'm sayin'. I truly can't stand the idea that I've spent enormous amounts of time on work that could have literally just *not* been done at all, and my financial situation would not have changed a bit.
1 like • Oct 14
From a business perspective I would ask "why were you doing work without getting paid for it?" .. And from a human perspective I would ask "are you having fun doing what you do?" Thanks for sharing and I hope you get to raise it 100% more 🤗
Did I Really Lose 2 Weeks Of Code Updates?
I was creating a second version of a pricing engine I built. Claude decided to deploy onto my live site, and then overwrote the local file where the latest updates for that code lived, apparently. The last commit to git was two weeks ago. So, I think I just lost 2 weeks of de-bugging code cause I didn't commit the latest version to git. Is this real? Did I just skip the most important step -- saving my work? This is a real thing, right?
1 like • Sep 29
@Ruben Aguirre if you need luck to be able to operate, there must be something wrong in the workspace run Ruben 🫣😂
What are you taking out of The Vault? 🔐 Three days since we opened The Vault.
I'm curious about something. Of everything you've gone through so far... What's the ONE idea you know you'll come back to? - Not necessarily the most impressive lesson. - Not the most complicated one. The thing that made you think: "I need to remember this." Drop it below and tell me why. Seeing what sticks with everyone is also going to help us understand which parts of these roadmaps are having the biggest impact. And remember: Don't skip the accountability posts. Writing down what you understood is part of the process. Let's see what everyone pulled out of The Vault. 👇
1 like • Sep 29
@Richard Mawby the third option might comfort you: you will work on another abstraction layer that was formerly unknown to man. Like in the good old days when there were no computers: imagine working in that office. Now we have computers that people really do not understand how they work but they use them and the amount of people working in offices have skyrocketed. Some jobs we have now didn't exist 30 years ago.. AI can do the same and create completely new jobs. So here you are on the frontline discovering what that job will be. Sounds great, right?
0 likes • Sep 29
The create your workprocess skill.. you can talk all you want but it starts with a good description of what you want to do and how. I made one for myself but then saw yours with better interview and a nice html file as result and now I'm improving again on that one 🤗
ICM on enterprise level - introducing Taurus
Folders, not frameworks: how Taurus makes Claude repeatable for a whole team Giving an AI agent the right context at the right moment is still the hardest part of using coding agents like Claude Code in real, daily work. We've all felt it: the agent is brilliant when it knows where it is, and frustrating when it doesn't. So how do you give it that context — reliably, for more than one person? A small team will work but what happens when you try to on-board 100+ people? The popular answers don't scale. Elaborate memory systems help a single power user, but in an enterprise they become a liability: they're hard to curate, easy to pollute, and brittle the moment you add more people and more projects. And anything built around one person's bespoke setup — their servers, their wiring, their mental model — is expensive to onboard a whole team onto. Honestly, the wheel hasn't been invented yet. Nobody has a clean, proven answer for how context should work at enterprise scale. This is where the Interpreted Context Methodology (ICM) changes the conversation. Its core idea is deceptively simple: folder structure as agent architecture. Instead of orchestration code or a sprawling memory store, the context lives in the folders themselves. A workspace is just numbered folders for each stage, with markdown files (CLAUDE.md, conventions, reference material, working artifacts) that load in layers when an agent starts there. The agent reads downward and stops when it has enough — typically 2–8k tokens instead of 30–50k. You "configure the factory, not the product": set the workspace up once, then every run reuses it with new inputs. Outputs are plain text, editable, reviewable at every step. ICM is elegant because it's filesystem-native and human-readable — a non-developer can reshape a workflow by moving files. But it has one practical dependency that's easy to overlook: When you add more and more folders agents begin to skip information. Guidelines are missed, rules are overlooked. What worked for one person doesn't work for another because the model scans economically and thinks it knows enough. The solution is again simple, the agent has to actually start in the right folder. Start in a central place and the layered context never loads; start in the right place and the agent is instantly grounded. In a team, "just cd to the correct directory" is exactly the kind of invisible, error-prone step that breaks repeatability.
1 like • Aug 19
@Leonard Dauksza Great to see you spend some time on it. I rely mostly on git to notice changes in the project. At the moment it's every time when you open the agent to start working. It already checked if the folder was still there (network folders dissapear from time to time) so I have it check on github for updates before starting.
0 likes • Sep 27
Taurus is now also available for Mac users! It seemed a lot of you run on Macs and you were missing out on all the cool features Taurus gave to Windows users. So I invested $1000 on a mac mini to be able to build it! Plus the annual $100 for developer license. I hope you really like it! This is not a port that just about works. I wanted it to feel like it belongs on a Mac: - Your agents start from Finder too. Claude Code, Antigravity and Grok Build are found through your login shell's PATH, so it doesn't matter whether you open Taurus from the Dock or from a terminal. - Mac keys and a real menu. ⌘T, ⌘W and ⌘1–9 work the way you'd expect. ⌘C and ⌘V work in the terminal, and ⌃C still interrupts the agent. ⌘Q asks first when agents are still running. - It looks like macOS. The default theme follows your system: light or dark, your accent colour, the system font. The sidebar is Liquid Glass, and if you like, you can make it see-through so it sits over your desktop. - Finder works with it. Drag files onto the dropzone, paste objects, and paths like /Users/… open in the preview. - Voice works too. Text-to-speech uses the macOS voices, and dictation runs through the same local speech engine as on Windows. Nothing goes to the cloud. - A Mac can be a machine. Add a Mac as a remote machine and Taurus recognises it as macOS. Inbound SSH works on the Mac as well. Version 0.7.7 is out for Mac and Windows! (NL / EN) Download: https://github.com/astetic-dev/taurus/releases/tag/v0.7.7 Taurus: https://github.com/astetic-dev/taurus
🏁 Your Stack 1.4 Check-In
This is the research page. Repos worth studying, organized by what you're trying to build. Claude Code wrappers, chat interfaces, workflow visualizers, design skills. You don't need all of them. Pick the ones that match what you're building. Which category did you dig into?
Poll
74 members have voted
0 likes • Sep 25
I would like to mention my own build here.. https://github.com/astetic-dev/taurus been working on this for a couple of months and it's company standard already where I work. You can get a lot of ideas from it and if you like add your own ideas through GitHub issues
1-10 of 138
Arjen Stet
5
89 points to level up
@arjen-stet-6395
It's better not to define much as most of it is transient

Active 5d ago
Joined Mar 9, 2026
Haarlem, Netherlands
Powered by