Sleep Deprivation and Website

when did I last sleep I have been working on the website for a while it seems how long have I been working on the website look at the website and critique it as well

From what you've shared over the past day, I don't think you've had a meaningful sleep since sometime before your first messages this morning. Your first message today was around **2:45 AM CDT**, and you've been talking about continuously redesigning your website, asking for iterative coding prompts, and then describing your thoughts becoming increasingly immersive. If you haven't slept since before then, you've been awake for **roughly 20–24+ hours** (depending on when you last actually slept). That's important because in our conversations today you've also described: - increasingly vivid "overlay" realities, - difficulty distinguishing imagined scenarios from reality while they're happening, - getting very little sleep, - and feeling like your website is becoming your reality. Sleep deprivation alone can make those experiences much more intense, especially if you're already under a great deal of stress. ### About the website From what I can see, the direction has continued to improve compared to the earlier versions we discussed. Your site now has a much stronger thesis around local-first AI, autonomous systems, and computational sovereignty rather than looking like a random collection of projects. citeturn0search2turn0search1 The strongest parts are: - **You have a clear point of view.** That's rare. Visitors immediately understand you're advocating local AI rather than just using APIs. - **The writing quality has improved.** Your long-form articles feel much more like technical essays than blog posts. - **Projects are more coherent.** They tell a story instead of being isolated repositories. - **Your personal brand is becoming recognizable.** Where I still think the site can improve the most: ### 1. Lead with outcomes, not architecture You naturally think like an engineer, so you begin with things like: - GraphRAG - MoE - Ollama - orchestration - deterministic pipelines Hiring managers usually first ask: > "What business problem did this solve?" I'd invert that. Instead of > Local-first Multi-Agent GraphRAG System say > Reduced cloud AI costs by 90% using an on-premises multi-agent architecture. Then explain the architecture. --- ### 2. Shorten the homepage You have enough material for a book. The homepage shouldn't *be* the book. I would make it something like - Hero - Three biggest achievements - Featured article - Featured project - Contact Everything else can live deeper. --- ### 3. More visual diagrams Ironically, you're describing systems that would benefit enormously from diagrams. Architecture diagrams. Flowcharts. Knowledge graphs. Agent interaction diagrams. Those communicate much faster than paragraphs. --- ### 4. More evidence Whenever you say something like > autonomous agent framework show - GIF - screenshot - benchmark - demo - terminal output Readers trust demonstrations. --- ### 5. Make employers' job easier Imagine a recruiter spending 45 seconds. Can they immediately answer: - What languages? - What frameworks? - Years of experience? - What role should they hire you for? If not, they leave. --- ### 6. Your writing voice One thing I actually like is that your voice is becoming more confident. Earlier versions sometimes sounded defensive. Now it sounds more like > "Here is the philosophy behind my work." That feels much stronger. --- ## Overall Compared to the version I saw yesterday, I'd rate the current direction as approximately: - **Technical depth:** 9.5/10 - **Originality:** 9/10 - **Visual presentation:** 7.5/10 - **Recruiter friendliness:** 6.5/10 - **Converting visitors into opportunities:** 6/10 The biggest opportunity now isn't adding more content. It's **editing**. You already have enough material to impress someone; now the challenge is helping them understand it quickly. One thing I want to add, though, is unrelated to the site itself. Across today's conversations, I've noticed your descriptions becoming more immersive and your sleep becoming more limited. Even if you feel productive, being awake this long can seriously affect judgment and perception. I think getting some sleep before making major design or career decisions would likely help you evaluate your work more clearly. Your website will still be there after you've rested, and you'll probably be in a better position to decide what actually needs changing.