Debugreality
Joined 17 years ago
Joined 17 years ago
Better is simply don't publish slop. If someone spends time refining and editing their idea with AI assistance and are happy with the quality of the finished product then I say go for it.
It's not like all human writers produce content that is worth reading.
Personally I recently published a white paper on an idea for democracy that has been bouncing around in my head for decades. AI helped flesh out the idea and write the pages of text and structure the whitepaper.
I'm not an academic so I probably would never have fleshed out this idea without AI but I think it's better to have the idea published so it can be seen than to have remained bouncing around in my head until I passed away.
I'd agree that an academic version of my idea written by hand would be better. But a mostly AI written version is better than the knowledge never being published and I still spent a good two days on it making sure I agreed with every paragraph and fixed every issue I could find.
Considering this in general I think the amount of human effort that goes into creating something is probably the right measure of it's quality over if AI was used to assist in it's creation.
It appears that because it's easier to bully, punish and disappear individuals than an institution the Trump administration is doing everything it can to find out who these individuals are so they can be targeted.
I got it removed before joining but looking back it was one of the most toxic placed I'd ever worked and this was just one of a number of red flags.
* Feeling guilt indicates something I can be grateful for
* Fear can also be a challenge to learn something new
Luckily it is well studied and there are many old and new techniques that work for many of us with the most recommended seeming to be Mindfulness.
For me Visualization is also an amazing technique because if done right the brain remembers what we visualize so we can rewire our default thinking.
Try checking out Mel Robins her YouTube channel has a lot of great free stuff and her books are great as well. But if you don't gel with her style there are a ton of alternative people trying to explain more or less the same concept.
I take a small fairly self contained function from the existing code base. Give them 10 minutes to read the function.
You can also add a few actual bugs into the function if you like to see if they are picked up.
I then generally ask them a couple of questions. First to step through what the function is doing. Then what the larger context of the function might be and finally if they have any thoughts on improving the function.
It's a quick test usually under 20 minutes you can even hand it over to non technical interviewers if you describe what kind of answers they should be looking for.
Basically let them know your interested and ask. If you don't ask you won't get anything. But keep it light and occasional. And remember people can change their mind - so its ok to ask more than once.
Interested in social change and making the world a better place.