Contents:
Graph Algorithms and Data Structures. Product details File Size: Hyperink March 12, Publication Date: March 12, Sold by: Share your thoughts with other customers. Write a customer review. Read reviews that mention jeff atwood blog kindle developer insights software. Showing of 22 reviews. Top Reviews Most recent Top Reviews. There was a problem filtering reviews right now. Please try again later. Kindle Edition Verified Purchase.
Why would anyone buy this book, when all of its content is available on Jeff's blog?
Well, those were my reasons: This book is a perfect match. It contains plenty of small chapters pages long blog entries from Coding Horror. It comes with a reasonable price and it is a perfect companion for traveling. As for content itself - it's brilliant. Jeff is a real coding superstar and his opinions and thoughts are very valuable for every developer who really cares for creating software. It will probably not teach you anything technical but we have other books for that , but it will make you a better developer. While this book and its focus on "not sucking" is aimed at developers and engineers, there's plenty of good advice for anybody on how to suck less and be more awesome.
Jeff Atwood's writing is a pleasure to read, and the cost of the book is low enough that it's very much worth it to have this material in Kindle format, even though it's probably all in the Coding Horror blog somewhere. I definitely welcome more books from Jeff. If you are in IT. If you are in IT, especially as a developer, and WTF is daily in your thoughts then you will enjoy the insights in this book and will probably even find some validation for your thoughts on many things IT.
It helped me lighten up a bit to know that higher echelon developers experience the same cruft that I experience.
The clear and lighthearted analysis can help you calmly deal with much silliness. Plus I like that wtf is part of the lexicon. And for serious readers there are many pearls of pragmatism and best practices, too. Enjoyable - I recommend it. One person found this helpful. Jeff Atwood says it all. If you're interested in learning about the core issues of software development from a pragmatic and sensible expert, this is the book.
This isn't about becoming a developer or manager - it is for professionals already in the roles who want to improve and perfect their craft. A thoroughly enjoyable, informative, and valuable book. This is because, with typewriters, characters were all the same width, so the two-space rule allowed for greater readability.
With modern computer fonts, the characters all fit closer together in a proportional fashion, thereby eradicating the need for that one additional space. Before you convert your manuscript, change all double spaces to single spaces. The result will be a better formatted, stylistically correct book. Improper hyphenation is a common error that may be harder to stay on top of because the rules of hyphenation differ depending on the grammatical situation.
When in doubt, look it up! For a more detailed treatment of the hyphen, here is an important source to consider: This is simple right? Using paragraph breaks will create extra space where none is needed and will change the page layouts of your book, making your book look ugly. Stop formatting your chapter titles yourself. Google Docs also has this feature. In Google Docs the styles section can be found by clicking the box between the zoom level and the font type.
When creating a new chapter, highlight the chapter heading, and then make it a header by applying the relevant style. Without question you want your book to stand out because of its invaluable content, stunning tone of voice , and laser targeted towards your audience.
It will help you design your title page on a different first page, your copyright page , trimming to the correct paper size, and the million other things you need to do to get your book ready for print. Thirty years ago, it would have been impossible to publish a book yourself. Today you have all the tools you need to produce a flawless manuscript.
If you're interested in learning about the core issues of software development from a pragmatic and sensible expert, this is the book. If everything is always flush left, that never happens. It's Jeff Atwood, so I knew it was going to be good. Thousands of books are eligible, including current and former best sellers. Not Enabled Word Wise: When formatting my manuscript for fiction, do I use justified margins, or the typical left side margins?
These are the people who will help take your book to the next level. Just remember to choose enthusiastic individuals who truly love your book! Marketing your book can be really hard without a solid plan of attack. Knowing how to build your author platform and get the word out about your book takes time and deep thinking — along with some helpful tips. Sit down and create a calendar with all the social posts, ads you want to create, and even emails you want to send to your list.
Once you have your plan together, incorporate your launch team to help you execute it. At Self-Publishing School, we help people write, market and publish their first bestselling book. I was just having a mini panic attack because of the double spaces between sentences. Never thought of the find replace.
What a life saver! I got my book back from the editor and all she said needed corrections were the formatting. But, the tough changes are formatting for me. The double space after a period is my downfall. Thanks Chandler, sometimes the proofreading can be the hardest part. When I first saw your heading, I thought you might be talking about formatting for e-books.
Yay, k words; I better break out the real good coffee. Something that I see often in Wattpad books is that sentences will have exta spaces in them. If they're there to rock, and your vibe is not, you've got work to do. Once you've noticed it, reboot. Come back to presence, breathe, and ask yourself: What's the impact I want to have? How would I like to show up?
Name your negative impact and presence, take responsibility for it, and then ask for the support you need. In this case, the support I needed was simply to have everyone reboot, give it some grace, and table a discussion for process improvement with our vendors. There is a reason your presence is off. What can you learn from this event as a team?
What do you personally need to learn as a leader? If you find there's more to do to clean the situation up further, honor that sense and do it. This is essential; for yourself and for others. Allow for the "space and grace" to notice, reboot, and learn from it. You'll recover more quickly, learn faster, and become more resilient as individuals and as a team.