Hi everyone it’s my first time building a website I started off with using the architect skill mentioned in the chat is there any tips with helping creat my first website/product?

Okay, so. Yesterday I said the next post would explain where I've been. Grab your coffee. Or the whiskey. This one earns it. I'm usually the loud one in here. The 1 AM experiments, the folder systems, the posts that run longer than some of your contracts. Then about a month ago I went quiet, and quiet is not my natural state. My natural state is "please, someone make him stop." June 24 was the day the wheels came off. That morning I sat down and let our project manager go. If you've never had to do it, no amount of business books prepares you for the part where there's a real person on the other side of the screen and you're the one changing their whole year. One of those conversations you rehearse in the shower for a week and it still comes out sideways. We handled it with as much care as we could, offered the strong recommendation he honestly earned, and it still sat on my chest the rest of the day. Except the day wasn't done. A few hours later, the strongest CMO on my team gave me a 30-day notice. Same. Day. Two seats gone before dinner. Every founder in here knows the math that starts running in your head at that moment, and none of it is about marketing. ******************************************* Then it got personal. ******************************************* My wife was two weeks past her due date with our newest baby. If you've lived a two-weeks-past-due house, you know the whole family walks around holding its breath. When labor finally started, the plan was a peaceful home birth. What we got was a chaotic ambulance ride and four days in the NICU. Not because the baby needed it. Because the medical system is run by insurance companies and litigation attorneys, and "healthy baby" apparently isn't a discharge criteria anymore. Four days of asking strangers for permission to take home our own healthy kid. When we brought up leaving against medical advice, the not-so-subtle response from the doctors included the words "child protective services." We're not talking about a sick baby.

Hey y'all. I was laid off on Friday from a company that I've been with for two years. I've known for a while that I wanted to make the switch to doing AI consultancy but was hoping to start on my own terms. Now find myself starting a little sooner than expected. I have a couple warm leads already, and in the process of massaging those. I would love some advice from anyone who has done this before. ❓❓I have one main question I would love some insight on: What pricing structures have y'all found success with, and which ones would you suggest that I avoid❓❓ I'm also open to any other advice. Thanks in advance!

I think I cracked the code on why we are all having a hard time with this second brain stuff. The real problem is that we are saving information that we think will be relevant to future endeavors, not just the stuff that is presently needed. Thus, we need rules that work in many (read "all") workspaces to make the information usable/searchable etc. These hypothetical rules would likely be more constraining than the rules that an actual use case would require. The second issue is that ICM is (correctly) very broad. Its principles map extremely well to the constraints of a task at hand, but poorly to undefined future tasks (like the goofballs making ICMs for imaginary problems) Possible solution: We stop saving unnecessary info and let our desired function determine the format (within ICM L3 Principles). That solution sucks, I still want to save info I don't need today!! I found a better solution... (If you just want the solution skip to the last paragraph. If you want some cool info on why your second brain doesn’t work, read on.) In practice, our L3 files are almost all SOPs. But the way an SOP is structured doesn't work for the way externally-authored source material should be kept for citation or lookup (which btw = split into its natural segments and indexed). This is why Tiago Forte’s PARA system doesn’t work, it’s built for helping a human decide what to do next, not have access to the relevant info. Google’s OKF fails because it's a format for shipping knowledge between tools/organizations, not the method for finding that info. Karpathy’s wiki fails because it defines only the loop (ingest / query / lint), so retrieval quality is only as good as the agents improvisation, its unreliable. RAG and vector databases are for bulk data, not a second brain. For instance, a million support tickets is a pile to query, not a knowledge base. Like our boy Jake likes to say (shout out Jake!), the principles for darn near everything have been around for decades. We're just applying timeless principles to an unrefined tool. The principle needed here is called faceted classification, developed by a librarian named S.R. Ranganathan in 1933, decades before we had a database to apply it to.

I’ve just seen Thariq on X post this and well, yes, thank you, we are already doing this https://claude.com/blog/the-new-rules-of-context-engineering-for-claude-5-generation-models