Understanding the Go Runtime: Profiling
internals-for-interns.com
Understanding the Go Runtime: Profiling
1–10 of 10 posts
Re: Understanding the Go Runtime: Profiling
#2For example see here their series about Filesystem internals: https://internals-for-interns.com/series/filesystems/
Reason I am asking, should I add them to my personal "Human blogs to read list"
Re: Understanding the Go Runtime: Profiling
#3Since this is shared by @valyala, I feel comfortable trusting the content, but is the original author of the blog delegating all writing to AI or are they genuinely this smart to produce high quality content this fast? For example see here their series about Filesystem internals: https://internals-for-interns.com/series/filesystems/ Reason I am asking, should I add them to my personal "Human blogs to read list"
Re: Understanding the Go Runtime: Profiling
#4Since this is shared by @valyala, I feel comfortable trusting the content, but is the original author of the blog delegating all writing to AI or are they genuinely this smart to produce high quality content this fast? For example see here their series about Filesystem internals: https://internals-for-interns.com/series/filesystems/ Reason I am asking, should I add them to my personal "Human blogs to read list"
Re: Understanding the Go Runtime: Profiling
#5Since this is shared by @valyala, I feel comfortable trusting the content, but is the original author of the blog delegating all writing to AI or are they genuinely this smart to produce high quality content this fast? For example see here their series about Filesystem internals: https://internals-for-interns.com/series/filesystems/ Reason I am asking, should I add them to my personal "Human blogs to read list"
the art is def ai generated, text seems okay thusfar?
Re: Understanding the Go Runtime: Profiling
#6If it is human-reviewed AI blog, even better.
And if my AI can collaborate and improve/build-up/fact-check that article, perhaps our AIs working in GitHub Issue on those (which is a missing link now). That would be even better.
Re: Understanding the Go Runtime: Profiling
#7I have nothing against AI blogs. Ideally it saves cost, so my AI does not need to waste compute to generate all that. We all likely have same models (Fable vs Sonnet vs Deepseek tiers of course) which produce same result for same input. So just save yourself tokens. If it is human-reviewed AI blog, even better. And if my AI can collaborate and improve/build-up/fact-check that article, perhaps our AIs working in GitHu…
Re: Understanding the Go Runtime: Profiling
#8I have nothing against AI blogs. Ideally it saves cost, so my AI does not need to waste compute to generate all that. We all likely have same models (Fable vs Sonnet vs Deepseek tiers of course) which produce same result for same input. So just save yourself tokens. If it is human-reviewed AI blog, even better. And if my AI can collaborate and improve/build-up/fact-check that article, perhaps our AIs working in GitHu…
Or we could just use our fucking brains, how about that?
Re: Understanding the Go Runtime: Profiling
#9Since this is shared by @valyala, I feel comfortable trusting the content, but is the original author of the blog delegating all writing to AI or are they genuinely this smart to produce high quality content this fast? For example see here their series about Filesystem internals: https://internals-for-interns.com/series/filesystems/ Reason I am asking, should I add them to my personal "Human blogs to read list"
Re: Understanding the Go Runtime: Profiling
#10Since this is shared by @valyala, I feel comfortable trusting the content, but is the original author of the blog delegating all writing to AI or are they genuinely this smart to produce high quality content this fast? For example see here their series about Filesystem internals: https://internals-for-interns.com/series/filesystems/ Reason I am asking, should I add them to my personal "Human blogs to read list"
Sidenote, that is a great idea. Mind sharing part of your list?