«Please shut up and take my money». Jokes aside - can’t wait. Your book The Lean Startup helped me so much. I read it tens of times. It’s one of the reason I got great traction with mine startup https://playcode.io - AI App Builder on our custom cloud. Thank you Eric. - Source: Hacker News / about 1 month ago

I built a complete clone if fly.io infrastructure: VMs, networks, etc. So I have my Vercel on bare metal machines to maintain full-stack apps on https://playcode.io. It took more than a year. - Source: Hacker News / about 1 month ago

I completely rebuilt this sync engine + orm with relations, lazy loading etc, using Vue + Pinia in https://playcode.io. Google Linear’s videos, they explained in detail their architecture. Yes, I spent a few months. But it worth it. Every new field, model I need to add, it is so straightforward. I do love frameworks and foundations. They make live easier later by a lot. - Source: Hacker News / about 1 month ago

Don’t get me wrong, but 7K LoCs means it is still an early attempt to make a coding agent. It starts easy “ah it can edit and read files!”, but it requires a lot of extra effort to make properly for many edge cases, especially caching, price optimizations, etc. I’ve been implementing custom coding agent in https://playcode.io for 3 years already. Far beyond of 7K LoCs. So when you compare to “shitty slow” Claude... - Source: Hacker News / 2 months ago

- k8s is insane peace of software. A right tool for a big problem. Not for your toys. Yes, it is crazy difficult to setup and manage. Then what? - cloud has bad and slow disk. BS. They have perfectly fast NVME. Something else? That’s it. Why I am so confident? I used to setup and manage kubernetes for 2 years. I have some experience. Do I use it more? Nope. Not a right tool for me. Ansible with some custom Linux... - Source: Hacker News / 3 months ago

There's a guide on the subreddit wiki on how to format code for display on reddit. When in doubt, you can also use GitHub Gist or Hastebin, though. Source: over 4 years ago

In future, use code formatting or put your code into hastebin.com and then post a link here. It will make it easier to read. Source: over 4 years ago

If you want to post a log, you'll have to generate one first (go to settings > logging and set both logging verbosities to 0-debug and 'log to file' to ON, then do whatever you need to do to create the offending behavior; that should make the log. Then, open the resulting log in a text editor and copy/paste the contents somewhere like hastebin.com and post a link to it here). Source: over 4 years ago

Close RetroArch, then navigate to your 'logs' folder in your RetroArch user directory (if you can't find it, open RetroArch and go to settings > directory and see where your 'logs' directory is located). You should see a text file there. Copy/paste its contents somewhere like hastebin.com and then post a link to it here and I/we can take a look. Source: almost 5 years ago

Can you give me the entire command history that got you to where you are now? If you can do that, make sure there is not personal information in the history, especially passwords. Look at the output of history. If it's large, try hastebin.com . Source: almost 5 years ago