Boldingd
I'm a Ph.D. student at GSU studying Computer Science. I spent two years working as a Software Engineer -- actually a Research Scientists by title, but functionally a software engineer.
I'm new to wiki-ing also.
Useful links:
- https://en.wikibooks.org/wiki/Subject:Computing
- https://meta.wikimedia.org/wiki/Help:Edit_summary (less than it could be)
- https://en.wikibooks.org/wiki/Help:Starting_a_new_page_or_book
- https://en.wikibooks.org/wiki/Using_Wikibooks/Starting_A_New_Wikibook (good to pry apart)
- https://en.wikibooks.org/w/index.php?title=A_Little_C_Primer (good to pry apart)
- http://en.wikipedia.org/wiki/Foreach_loop (code-formatting example)
- http://en.wikipedia.org/wiki/Python_(programming_language)
Also
GUI Programming edit
In my capacity as a Ph.D. student, I sometimes teach courses. Last fall (2013) I was teaching a course on Windowed Systems Programming; suffice to say I didn't like our existing textbook. As students need a reference, I had the clever idea of just making a wikibook to track what we do in class. There are already a number of "Learn GUI Programming with X" guides, for any language X. I'd like to tackle something a little more general, aiming at modern practices that span specific toolkits.
That's a little tricky though, because I basically discovered that the overlap between modern toolkits isn't perfect, and to do anything useful you have to get down in the weeds - and different toolkits have different copses of weeds at different places. I may finish this wikibook or I may come back and do one for a specific toolkit.
Subjects:
- Basic concepts of event-driven programming
- Overview of toolkits
- Common Widgets
- Common Layouts
- Basic Design Principles
- Long-Running Jobs