601 karma · joined July 11, 2012
Interesting way to see how much data is actually in an emoji, especially ones that are combinations of separate emojis
Also, in some cases, CGPT currently just isn't an option. E.g. summarize this YT video. (I realize this might age like milk with plugins on the horizon)
This is an interesting argument to make but I wouldn't say having large subsets belonging to single entities equates to it being "not decentralized."
Because a man page for how to remove a limit of 50 files in a certain directory created after a certain date is equal to an AI-powered script to make the entire almost unreadable command in 2 seconds.
I have ADHD. I was surprised to see this one. When I stopped typing and (only) recording meetings and started writing notes by hand, it forced me to pay attention and think through what I was writing. Research backs this up as well.
In fact, I rarely look back on my notes. The mental process in the moment of writing it down is far more important in my opinion.
There were plenty of grocery delivery flops before Instacart and FreshDirect got off the runway. Stop flattering yourself that your idea is that good.
https://twitter.com/covidvaxnews/status/1330783886830256128?...
So? Do they say that it does? I'm already a software engineer and can tell you that having an AI certificate from an accredited University is a great stepping stone to transitioning into this line of work even if it does not make me an expert.
Okay, graduate degrees fulfill that purpose too, but with life events now and over the horizon, I just don't have the bandwidth to commit to getting my Masters or a Ph.D. right now.
I really have no problem with this.
Yeah, that's something I've had in the back of my head...one of the reasons I've been super restrictive about image uploading.
I'm counting myself lucky that I'm getting such a positive response on HN.
Just git reset <ref> should do. The --soft flag is implicit.
Amending and rebasing is something you should be careful with. If you've already pushed, you'll now need to force push. If another person has put new commits upstream, they will be wiped out irreparably. Not saying don't do it, just that it's very risky.
Instead of deleting and recloning the repo at the end, if you're really at that point, just doing git reset --hard origin/master should be equally as effective with fewer steps and less time.
Pulling down the repo a second time, however, can be more useful for just having a snapshot of the code in a second location that is totally independent of git traffic (don't pull to it very often). Say someone force pushes something that removes code. Your snapshot or someone else's non-pulled repo is your only hope of getting it back.