What technical books do you read/recommend?
- If it's a technical book (that's usually what I'm reading), I use SQR3 (look it up). While it requires you to do multiple passes, you get a lot more out of it and rarely have to go back and visit it again later.
I program stuff for a living so mostly just my relevant fields. Often times it'll be for learning a new language. Other times for software architectural stuff. I can't really make recommendations without knowing what you're interested in. I've never seen a bad book from O'Reilly, Wrox or Robert C Martin, though.What technical books do you read/recommend?
Instead of reading each individual word, try to take in chunks of text (multiple sentences) at once.
Start small and build up, your brain will learn to absorb the info without needing to read each and every word separately.
Listen to ol' Grandpa Stalin here: read a lot and vary the subject matter as you go along. It's best to develop a bit of flexibility so you can go from things that are fairly abstract to things that are technical, etc. Once you've broadened your horizons you won't find yourself so disoriented while you're reading.Never move the lips, never subvocalize, just move your eyes down the page and let the words flow into you.
If you want to become a better reader, read, read, read. If you want to become a better writer, read, read, read, then write, write, write.
How do you know when your ready to write than read?If you want to become a better reader, read, read, read. If you want to become a better writer, read, read, read, then write, write, write. These days am doing more writing than reading.
That's up to the person. You can do both, and I encourage everyone to read and write. The better you get at one, the better you will get at both. Get out there are do it. The only shot guaranteed to fail is the shot not taken. So take the shot.How do you know when your ready to write than read?