Hey Maria, this is a long shot, and most people will put it in the scam basket, but I've heard of developers significantly improving their skills by applying PhotoReading to code. One might even instruct the other-than-conscious mind to help them look for bugs (or typos in general text).
Do note that, when involving the subconscious, you *always* need a clear purpose of what you want to achieve. It won't work otherwise. Forget going into the book just because "you want to read it." Also, if you want to be effective at reading, both this technique and work by Tony Buzan strongly discourage simply reading books from cover to cover. If your goal is to read more books more effectively (that's how to get most out of it, I reckon), you might wanna familiarise yourself with their opinions and test them out. If such things interest you, feel free to give it a shot. Photoreading does take time to master, though, especially without someone to guide you. You alone decide how your time is best invested. In any case, you'd learn a lot by reading other peoples' code, be it regular- or photoreading. Regards, -- Maja On Thu, 26 Oct 2023 11:48:43 +0600 Maria Morisot <maria.mori...@icloud.com> wrote: > Hi, > I've been frustrated in trying to find a way to help the project and > thanks to several people's replies I've been considering what I like > to do with the operating system. > > My needs are simple, as far as personal usage goes; give me an > offline system with vi and hard drive access and I'll happily write > poetry to my heart's content in my favorite café. > > But I really want to help the project. I like the idea of trying to > break things and get them to malfunction in order to expose bugs that > have been overlooked. > > I like to smash things. > > Does anyone know of any good resources for this, or recommended > software in ports that I should study and learn? I have an O'Reilly > subscription, so and book recommendations from on there I should have > access to. Blogs are great too. > > I have a pretty good understanding of randomness and know about the > concept of fuzzing. I've done testing in my software courses and know > a little about writing code for explicit bad cases. But my schooling > was very lax and was easy to get A's so I didn't put much effort in. > > Thanks again to everyone who has tried to help me find my path here > in the community, I know that I am a tough pill to swallow, that is > why I generally play alone. -- Google doesn't need to > know every time I fart.
