Earlier quoted context omitted.
I host weekly friend-of-friend open events where some people show up most weeks, find a nice comfortable spot to doom scroll in for a couple hours, maybe take a nap, leave, sit in their car for a bit, scroll some more, then go home. I am just hoping they actually took a break from doom scrolling while driving as then at least I can say I had some non zero positive impact on their lives. 5 years phone-free and I do no…
Maybe host your event in a cave if you can, no cell coverage, no Wi-Fi. There is a bar like that where I go sometimes, it is in a cave, some people got Wi-Fi from the staff, and you have some reception if you stand near the front door, but it is mostly a network-free zone and it is great. Another thing we did from time to time at the restaurant is to put all our phones stacked in the middle of the table, anyone who p…
Stop Doom Scrolling, Start Doom Coding: Build via the terminal from your phone
371–380 of 420 posts
Re: Stop Doom Scrolling, Start Doom Coding: Build via the terminal from your phone
#372Or, I thought it was cool until this passage reminded me, "coded a prototype in my downtime" that down time is supposed to be down time.
Re: Stop Doom Scrolling, Start Doom Coding: Build via the terminal from your phone
#373I am still trying to understand how installing Tailscale and Claude Code then connecting to your home network externally and opening a mobile terminal on your phone is a novel idea that requires a full Github writeup. So, I do this when I am sitting on the couch and too lazy to boot up my laptop that I normally do work on, but it never gets much further than updating, pulling or pushing one or two containers, or more…
I’m equally surprised to see these posts pop up everywhere on X, GitHub and now also HN. Am I that old that SSHing into a server through a VPN is such a novel concept nowadays?
Re: Stop Doom Scrolling, Start Doom Coding: Build via the terminal from your phone
#374Re: Stop Doom Scrolling, Start Doom Coding: Build via the terminal from your phone
#375I am still trying to understand how installing Tailscale and Claude Code then connecting to your home network externally and opening a mobile terminal on your phone is a novel idea that requires a full Github writeup. So, I do this when I am sitting on the couch and too lazy to boot up my laptop that I normally do work on, but it never gets much further than updating, pulling or pushing one or two containers, or more…
I’m equally surprised to see these posts pop up everywhere on X, GitHub and now also HN. Am I that old that SSHing into a server through a VPN is such a novel concept nowadays?
Re: Stop Doom Scrolling, Start Doom Coding: Build via the terminal from your phone
#376Earlier quoted context omitted.
Very curious to hear how you went phone-free and what your setup looks like
I have a mini PC hooked to screens in every room other than the bedroom and bathroom, and remote controls with built in air-mouse and keyboard (pepper jobs remotes). This way anyone can pick up a controller in any room and look something up on a shared communal screen as needed, which discourages use of private screens. When I leave home for less than a day I pack no electronics of any kind and enjoy the peace in my…
I put that in the same bin as all the “Stop doomscrolling” apps. You can’t prevent doomscrolling by adding another app on your phone. Get rid of the phone (and all other screens), one does not need to be able to look up everything in a moments notice. Write it down on a paper and do it later.
Re: Stop Doom Scrolling, Start Doom Coding: Build via the terminal from your phone
#377I see the article is still on the front page, I'd ignored it yesterday so I took a quick read. I find, being older, trying to read the tiny fonts on a phone to be difficult after a few minutes, otherwise cool idea. Or, I thought it was cool until this passage reminded me, "coded a prototype in my downtime" that down time is supposed to be down time.
Life doesn't have down time. Should we avoid learning new things because no one is paying us to learn?
One of my favorite uses of AI is to quickly make some simple 'hello world' level application that I can run using a given technology.
Don't know what an MCP server is? Boot up Kiro and tell it you want to make a sample MCP server and ask it for suggestions on what the MCP server should do. A relatively short while later, with a lot of that time being spent letting AI do it's thing, and you can have an MCP server running on your computer. You have an AI waiting for you to ask questions about why the MCP server does x y or z or how can you get the server to do a, b or c etc
As someone who learns a lot better from doing or seeing vs reading specs, this has been monumentally more efficient than searching the web for a good blog post explaining the concept.
And when I'm doing these learning exercises, I naturally lean towards the domain my company is in because it's easier to visualize how a concept could be implemented into a workflow when I understand the current pain points of that workflow.
I'm not going home and pulling in story's from my board and working on them (generally), I'm teaching myself new concepts in a way that also positions be to contribute better to my employer.
Re: Stop Doom Scrolling, Start Doom Coding: Build via the terminal from your phone
#378I am still trying to understand how installing Tailscale and Claude Code then connecting to your home network externally and opening a mobile terminal on your phone is a novel idea that requires a full Github writeup. So, I do this when I am sitting on the couch and too lazy to boot up my laptop that I normally do work on, but it never gets much further than updating, pulling or pushing one or two containers, or more…
Re: Stop Doom Scrolling, Start Doom Coding: Build via the terminal from your phone
#379Re: Stop Doom Scrolling, Start Doom Coding: Build via the terminal from your phone
#380Is being able to SSH into your home machine that easy these days? I never had a strong enough reason to spend more than a few minutes trying, but I always suspected that my ISP would make this harder for me than I would hope.
FWIW typically ISP blocks port related to spamming, so usually they block ports related to emails, e.g. SMTP, I believe DNS too, but other ports no problem.
That being said it's quite a silly use case IMHO. If you want to work on a project from "anywhere" then put your project on your server accessible from anywhere, that's literally what servers are for and they cost the price of a coffee per month.