News for hackers. Stuff that matters.
Re:Build Your Own Docker with Linux Namespaces, Cgroups, and... by ghostfoxgod on Tuesday June 27, 2023 @01:30AM (#36489234)
Yep, I do use GPT as one of the tools in my workflow. I write these blogs in markdown locally and have a helper script which takes the raw content and with a prompt it helps me generate a title, summary, Intro and conclusion (personal preference to keep these consistent on all blogs) and proofread the whole raw content for any mistakes (replaces grammarly completely now).

Quite happy with this workflow because it helps me publish articles more frequently where I don't have to worry about stuff other than just dumping my thoughts in raw format.

Its similar to how I use Astro as a tool to generate static pages from these markdown files to easily deploy on web or TailwindCSS etc etc you get the point.

https://media.tenor.com/1PMq-CFZno4AAAAC/avengers-endgame-hu...

Re:Build Your Own Docker with Linux Namespaces, Cgroups, and... by kreetx on Tuesday June 27, 2023 @01:50AM (#36489335)
You might want to specify that on the title or in intro.
Re:Build Your Own Docker with Linux Namespaces, Cgroups, and... by ghostfoxgod on Tuesday June 27, 2023 @01:57AM (#36489367)
Noted. Although, adding that on top of each blog is very repetitive info and not specifically related to the blog. I will find a better place to add this info but will definitely add this by today, most likely under the `/uses/` page.
Re:Build Your Own Docker with Linux Namespaces, Cgroups, and... by kreetx on Tuesday June 27, 2023 @11:03AM (#36493893)
I would still put it in some prominent place, similar to how newspapers put "sponsored". I.e I wouldn't want unknowingly to read a blog written (in large part) by chatgpt and would feel deceived when it wasn't clear from the start.
Re:Build Your Own Docker with Linux Namespaces, Cgroups, and... by bestcoder69 on Tuesday June 27, 2023 @12:33PM (#36495194)
> very repetitive info and not specifically related to the blog

Hey man I don't think it's necessarily bad what you're doing (like I said elsewhere, I like what ChatGPT has to say much of the time! Dunno enough about your post to comment on it itself tho).

But, readers are not going to react well if they read an article and then later find out it was AI-generated. You're also not being very slick about this -- you should be prompting ChatGPT to use a different voice than its own. You could be stitching together blog posts from multiple prompts, asking ChatGPT to challenge its own ideas, simulate a reader or editor conversing with the simulated author, etc... then you could blog about your process and hit HN #1 with a clear conscience - just an example. But as it is, it looks like content marketing spam you churned out in minutes.