Jesus Christ. What kind of IDIOT tries to argyle the pintafore using hoobastank? Some "developer" this person is...
I literally said in the title I am not a developer but you’re right I should have known
How I, a non-developer, read the tutorial you, a developer, wrote for me
401–410 of 455 posts
Re: How I, a non-developer, read the tutorial you, a developer, wrote for me
#402Pretty low effort as blog posts go.
Accurate
Re: How I, a non-developer, read the tutorial you, a developer, wrote for me
#403I followed this tutorial but ran into an issue where shamrock portal kept crashing. When I checked the logs, I found it would start a beep but never finish a boop. After a few hours of Googling I discovered my Debian 12's Klingon troglodyte emulator had a known centipede reported in 2013 that's never been squashed because hoobastank 34.100-6x00 actually requires it, and Debian can't move to the newer version of hooba…
So sorry about that. I should have mentioned the DNS resolver as a potential issue because it’s always DNS. Terrible oversight on my part, probably because I am not a developer.
Re: How I, a non-developer, read the tutorial you, a developer, wrote for me
#404Earlier quoted context omitted.
Wait really?? I also wound up migrating to Fedora 75bit for basically the same reason (TopHat doesn't even support hoobastank). But then I couldn't find `file` in the specified directory. I have `library/Lib/library/llibrary/liiiiiibrarrrary/llllliiiiibrary/hidden/hidden/hiding/you can’t find me/hidden/nope/never/hahahahereiam/file` and `/hahahahereiam/file.`, but neither of these boop. Any help would be greatly appr…
It was moved to a new path so you have to create symlinks in both locations to the new path under /usr/lib/newlib1.2/newfile.so otherwise, You can download a script that will make that for you but it will only work if you have all the dependencies for that script installed and their version numbers match the ones that the script owner had when he wrote the script.
This answer is correct but it only works under a new moon if you implement while smoking a joint rolled in pink paper, which should be doable.
Re: How I, a non-developer, read the tutorial you, a developer, wrote for me
#405OPs argument is flawed. Documentation is not there to teach you from scratch. Its there to describe a projects intended behaviour under normal conditions. Often times people will cry about lacking context and expect you to basically use it for them. I would heavily recommend against that as you will end up as unpayed and burned out tech support...
OPs everything is flawed but she tries really hard.
Re: How I, a non-developer, read the tutorial you, a developer, wrote for me
#406This level of extreme hyperbole is silly and not in any way helpful. Try analyzing an actual tutorial (which will only be an analysis of that one--quality varies a lot).
Good observation. Silly is the point. You nailed it.
Re: How I, a non-developer, read the tutorial you, a developer, wrote for me
#407Thanks for this. I never knew how much I'd like it if George Saunders started a tech blog.
Omg this is high praise I’ll never be able to write anything again
Re: How I, a non-developer, read the tutorial you, a developer, wrote for me
#408This has been a very informative and entertaining evening for me. I loved reading the comments. Also thanks for all the guestbook posts, they bring me great joy. May your Snarfus boop correctly forevermore. Devs are great.
—Annie, not a dev
Re: How I, a non-developer, read the tutorial you, a developer, wrote for me
#409Earlier quoted context omitted.
Any kind of documentation has a target audience. Your test is very valuable if and only if the target audience is a total beginner. Of course it's still very hard to write good documentation even if you have identified your target, but having someone totally illiterate on the subject matter review your documentation is as useful as if I'd have to review a PhD thesis in quantum physics. It just doesn't make sense (tru…
Perhaps in addition to a description of the expected audience, it might be an idea to list some assumptions made about the reader? e.g. has installed software previously, confident with bash commands, &c
I almost systematically use BLUF (Bottom Line Up-front) when I write docs, I think I'll make TABLUF a thing from now on (Target Audience and Bottom Line Upfront) :)
Re: How I, a non-developer, read the tutorial you, a developer, wrote for me
#410Earlier quoted context omitted.
> But to find out what the default options actually are, you have to find another page, probably the FooOptions constructor. I wanted the default options to be mentioned on the "Foo(string parameter)" page, and they so rarely are. It's better for maintenance (of the documentation) if the default options are only described in one place. (If the defaults change in a new version, this ensures the documentation doesn't h…
This is only a problem if you write it twice. Instead you can write it once and display it twice. Hell, I even do this on my github.io website that uses markdown. You can just write some text in one document and read it in another. We're programmers, so we should be lazy. It's about being the right lazy. You can be lazy by putting of a task today that takes more effort tomorrow or you can be lazy by doing a task toda…
In code documentation doesn't support such thing. And documentation outside of code suffers from rot.