/explore
|
You are here 
|
www.philipotoole.com | ||
| | | | |
www.techelevator.com
|
|
| | | | | The relationship between math and programming and answering the question "How much math do I need to be good at this?" | |
| | | | |
www.chrisritchie.org
|
|
| | | | | Transcribing some Q+A from a career panel. | |
| | | | |
www.softdevtube.com
|
|
| | | | | Programming history is filled with bugs that turned out to be features and limitations that pushed developers to make even more interesting products. We'll journey through code that was so 'bad' it was actually good. Along the way we'll look at the important role failure plays in learning. Then we'll tame our inner perfectionists and | |
| | | | |
www.dewanahmed.com
|
|
| | | Who writes the developer documentation for your product? During the early days of my tech career, I worked on a database replication product at IBM. My immediate team had developers and testers but not a single technical writer. I can speak for myself when I say that I never bothered to know who keeps writing the lengthy and complex documentation for every release. Since then, many companies in tech (including companies like IBM) have taken a modern approach to documentation. This "modernization" started... | ||
