There's an anecdote from Art and Fear (great book, and very short, highly recommended) similar to that. Half of a pottery class was told they'd be graded on the single best pot they produced that semester, the other half was told they'd be graded solely on weight of pots produced. At the end of the semester, the "graded on weight" half was producing better pots.
>but recently I was doing a course about the way our brains/minds warp information to suit our self-image and one of the ways is that when learning something, particularly when rereading, we can trick ourselves into thinking we've mastered a subject because we recognize information, but we can't actually bring that information to mind as easily without seeing it
I've been reading a book that talks about some of the common cognitive biases we make when learning. What you just described sounds very similar to what the authors in the book call "fluency illusions", which is the tendency to confuse fluency in your reading with actual mastering of the content of what you're reading.
Regarding adverbs, the point is to choose stronger verbs rather than needing to modify them all the time. "Ran quickly" versus "sprinted," for example. There's a place for adverbs, but most new writers tend to drown prose in them because it's easier.
Regarding said, the words themselves and the dialogue beats should be able to articulate what overwritten dialogue tags are saying.
I highly suggest Self-Editing for Fiction Writers. It really breaks down a lot of the whys and hows behind common writing advice with examples.
Art and Fear is a very good book that approaches some of these topics. I think you would like it.
I don't have an answer, but perhaps these ideas could help.
First, review the schematics (there may be clearer ones elsewhere--this one is a bit rough). How does what you're experiencing compare to what's on the block diagram? Are you able to rule out any particular sections? Left or right only, or both? Does it happen when only headphones and no speakers are attached (no speaker wires connected at all)? That should help get you into the right zone to test components.
If you have an oscilloscope you can feed a signal into the amp and trace it (don't just grab a scope and do this arbitrarily--there are things inside that can really zap you or the scope!). I recently scoped a Kenwood KR-3060 that was making a buzzing sound only on the right speaker after about 1/4 volume. Things sounded fine up to that point with speakers, and no issues at all when only using headphones. Perhaps the speaker impedance caused a bigger pull through the circuit compared to phones-only? This narrowed the issue down to the first even-numbered (right channel) transistor in the power amp stage. (I'm still new-ish to debugging and haven't actually tested the transistor yet.)
If you want to get more into electronics debugging, How to Diagnose and Fix Everything Electronic could be useful. It's not a perfect book, and it's long, but it's a pretty easy read and you could skip the sections on video, cameras, MP3 players, etc.
I used to do the same and I learned loads from watching Dr Alex Young’s videos on YT they are probably the on the better side of YT study I go video and are pretty practical. Also check out the book Make it Stick
https://www.amazon.com/Japanese-Short-Stories-Beginners-Captivating-ebook/dp/B08FDXBPT3
This is the first "Japanese book" I read, comes with furigana and English translation, very good for beginners imo.
thats right, using genki books + anki is enough i think. and also i used app called "bunpo" (in app store), it basically like grammar practice that they give you repetition like when using anki and it helps me a lot. and also for mastering your reading, after you mastered all Nx kanji dan know the Nx grammar, you can buy book such as This, it helps me a lot when reading in kana + kanji and also to practice how to understand japanese sentence and how native use it. hope it helps ^^
https://www.amazon.com/dp/B0042JSQLU/ref=dp-kindle-redirect?_encoding=UTF8&btkr=1
Art & Fear. I think Robert Rodriguez told me about it.
I came across a great book called "Japanese Short Stories for Beginners" by Lingo Mastery. It makes for a great Kindle book. You get a series of short stories in Japanese followed by the same story in English with notes. Highly recommended!
Math guy here:
Far too few people understand grey areas, "odds" if you will, especially in the past year or two.
It's called innumeracy. More people should read that book, Innumeracy: Mathematical Illiteracy and Its Consequences
You're really asking an electronics questions, not a camera one. If there's an electronics repair subreddit this question would be better suited there. Old electronics just sometimes conk out, but they're usually able to be repaired, and not turning on at all is often a relatively easy problem to fix, especially if it still worked a few years ago.
But you're going to need at least some familiarity with electronics. I found this book really helpful (this is an Amazon link but I got it from my local library).
I want to preface this by saying that I don't want to come off as mean at all. I want every writer to succeed, no matter their road to publication. Writing is amazing and hard and fun and everything else in between... except easy. But you asked what's going wrong here, and I think your cover and your blurb (as other people have cited) aren't the biggest issues.
I read your Look Inside and I think the writing itself may be part of your problem with conversions. Did you work with a pro editor? If so, I would find someone different for your next book. For example, the first sentence has a really unnecessary adverb. The second paragraph starts with a very problematic sentence structure (and one you seem to favor a lot). There are noun/verb errors, way too many non-said dialogue tags, and awkward sentences in the first few pages I skimmed.
The "-ing verb, other action" construction is really common among amateur writers, but it usually doesn't work. For example, "Heaving myself up to the next branch, I rested a bit" is not a good sentence. It essentially says that your MC heaved themselves up to another branch while simultaneously resting. "Heaving myself up to the next branch, I surveyed my surroundings" works, despite being clumsy, because these two actions can happen in tandem. But heaving and resting are at complete odds so that sentence reads poorly. Same with "grabbing my cane, I turned to leave." Is your MC grabbing their cane or turning to leave? These two things can't generally happen at once.
I know not all readers will care about this kind of thing, but when the issues I noted are so prevalent in your first few pages, it will definitely turn some people off.
If you haven't read Self-Editing for Fiction Writers, I can't recommend it enough.
I train internal alchemy in the Dragon Gate lineage (longmen pai). I have checked out a lot of different schools and in terms of knowledge and availability of information this is where I spend my time.
Anyway, one of Wang Liping's senior students (and a teacher himself) released a training manual! The writing is great and I'm obviously hyped on it. Amazon link, non-referral.
The book covers the laying the foundation practices as well as some core work for the lineage. You see a lot out there on secret of the golden flower, forming a golden pill, or the immortal spirit, but this lineage is the only one that I have seen providing actual methods for those practices.
If you want some background on the lineage check out Opening the Dragon Gate. It's a biography of Wang Liping.
Keep those legs crossed and those minds clear!
Hey gang!
I recently published my first Amazon international best seller. Years of grinding finally paid off! It is entitled, Creativity is Everything: Rethinking Technology, Schools & Humanity, and is available now for $5. https://www.amazon.com/dp/B082QSTXTC
I have put together a step-by-step package to help others do likewise that I am happy to share a free code for to anyone interested. Feedback and perhaps testimonials would be a great way of showing appreciation should you feel so inclined 😉.
DESCRIPTION
In an age where it can feel as though true satisfaction and accomplishment are in short supply, this book has been lovingly crafted to share the insights and experiences of a father, educator and self-proclaimed frustrated-artist-at-heart to inspire and educate through a tale that doesn’t take a long time to share but covers the whole span of human history.
This is a book written for everyone. You should read it to develop a fuller understanding of this often overlooked (if not outright forgotten and completely misunderstood!) human necessity. You should read it because it’s uplifting, informative and funny. You should read it for the inspiration to get up and find or rekindle your passion. It’s always there, waiting to be picked up, stretched, used and loved.
Thanks everyone!
Sean
There's a lot of debate about panting vs planning and writing. Not outlining and going full pants is perfectly fine. There's always editing later. Self-Editing For Fiction Writers is a great book on how to edit your own work. Structuring Your Novel is also a good book on writing-craft. You can use the techniques in SYN before or after you actually have a rough draft. If getting a first draft done and out of the way is how you write, it's how you write. You can go back in later and tease out arcs and develop plots. I know one writer who writes out her first draft with no planning, prints it out, reads it, takes copious hand written notes in a notebook, then deletes the file on her computer and burns the MS she printed out. Then she writes her second draft using only the notes she took in her notebook. Whatever works for you, so long as you finish it. If you want to publish it, you will want outside eyes on it first. But to get started, you can definitely get out a few drafts on your own first without needing to write outlines or have character page.
If you read the book For White People who Teach in the Hood Chris Emdin did this during his first class he taught at Harvard. Everyone in the class was doing the "10 minute countdown" until they could bail on the class. Hilarity.
I looked it up - I'm slow on mobile - and his last name is Emdin. Here's the book http://www.amazon.com/White-Folks-Teach-Hood-Rest-ebook/dp/B00Z3E2LVO/ref=sr_1_1?s=books&ie=UTF8&qid=1455904288&sr=1-1&keywords=christopher+emdin I will give it a shot!
I'm reading an excellent book about making art called "Art and Fear" by David Bayles and Ted Orland. This is one of the topics that they discuss at length. Very motivating and highly recommended.
For textbooks, you would need to be more specific on what topics you are interested in.
As for books you could find in Barnes & Noble (or similar stores), try The Math Book. It has short blurbs on a lot of really important mathematical ideas in chronological order. Also, the series "A Very Short Introduction to..." is really good.
EDIT: Also, this
I highly suggest that you read <em>Make It Stick: The Science of Successful Learning</em>. It has really altered the way I learn languages. I'm software engineer and I've found that the best way to learn new programming languages and technologies is to prepare for a professional level certification in that technology. I had a pretty simple study methodology:
Find real-world examples on GIT Hub by developers who are well regarded in the language's community.
Go through the "skills measured" section of the exams and identify areas I felt I was weakest in.
Use the examples and the exam skills outline and study.
Any areas that continued to be difficult for me I would lab repeatedly. I would also go to StackExchange sites and answer questions on the topics.
Take practice exams and repeat using the feedback from the practice exams to guide my learning.
I never did that with languages, though. I kind of did it with Irish as I wanted to take the TEG but I was very lazy about it. Make It Stick made me realize that I wasn't being efficient enough in my language learning. I wasn't doing the types of things that helped me learn other skills. What I was missing was that I wasn't generating enough out-put and getting feedback on it but most importantly I was not testing myself enough. By that I mean putting myself in unfamiliar situations and having to use the language accurately to get a specific result.