I know what one does manually, but how does stack make decisions here when there’s a conflict? The reason we use a rebase flow is to allow for adjusting commits that are no longer valid.
I vibed up a chrome extension that sets a timer, hides shorts, redirects home to subscriptions, and hides comments and recommendations.
It’s all toggleable so I don’t disable the extension when I do want some neuronal junk food. But just the micro friction being added back in is such a huge help to becoming more aware when using it.
What about the impact of EMF pollution? The book "the invisible rainbow' goes into that, though I don't expect this type of position to be well received in HN. I find it very healthy that this type of "invisible" pollution gets at least some discussion, however. We have to start somewhere.
Practical, but radical enough to take on IBM when their PC looked unassailable. Being first to the table with a 386 and working with others to make sure micro channel was DOA set the standards for the industry for decades.
Not to downplay, but is it wrong to assume you're self sufficient in daily life? Work a job and pay your bills?
You list your site and have a seemingly lots of professional experience.
Some of these conditions do make life harder, but there's a big difference between high functioning Autism and disabilities that make someone 100% dependent on others.
Something about a scheduling/productivity app (one of the most common vibe-coded projects people make) being the subject of this is funny to me. I wonder how many tokens have been wasted making apps like this, let alone time.
I was given a 44 hour rate limit and haven't had a response to my support ticket yet. I've been little to no progress done on some of my hobby projects.
But that is not what is happening, and they have stated that they were at the event for a short period of time, quite possibly at the portion that didn’t occur inside the event.
The willingness to assume one version of events, and then go down that path to award consequences, is premature.
This means there are always 32 octets to a reverse-IPv6 address, and there are no shortcuts or macros to overcome this! That means if you wish to assign a singular name that maps from a legitimate /64 Network ID, you must populate 64 bits worth of octets in a zone with this data. It is an absurd non-solution. This never should've been allowed to happen, but it will basically mean that ISPs abandon reverse DNS entirely when they migrate to IPv6 implementations.
“All” might be a stretch but the idea that they just do what they want regardless of what the courts say is just incorrect propaganda. And continuing to find creative ways to defy court orders is something every administration does. And my opinion of the administration is low also, I just don’t like the propaganda and have never understood why we need to make up things about them when there’s so much to dislike that isn’t fictional.
Per Blaise Pascal, no they cannot: “All of humanity’s problems stem from man’s inability to sit quietly in a room alone.”
We need to keep growing, building, making, taking. Some people seem to really love the bustle and creative destruction. I'm in my 40s, and I've always hated it. When I was a child, I wondered if when I grew up, I would fit naturally into the world the way that so many others seemed to. The answer was no. I don't know why people need to be the way they are. I don't feel comfortable in so many normal situations. The things that bother the animals bother me too, but for most people this is unthinkable in the same way that other modes of thought are unthinkable. (eg, when someone who thinks mostly in words learns that some people think only in pictures)
If you put codex in Xhigh and allow it access to tools, it will take an hour but it will eventually give you back quality recompiled code, with the same issues the original had (here quality means readable)
