|visits||member for||2 years, 6 months|
|seen||Apr 1 at 10:59|
- PostGraduate Student at the University of Athens
- Student homepage: http://cgi.di.uoa.gr/~grad1217/
- AI/Game Developer and Unity3D enthusiast
- Co-Developer of iThink, an AI (classical planning) library for Unity3D:
- FOSS-UoA Community member/admin at: http://foss.uoa.gr/
- Member of http://www.pirateparty.gr
- Twitter: https://twitter.com/#!/basanas
|bio||website||cgi.di.uoa.gr/~grad1217||visits||member for||2 years, 6 months|
|location||Athens, Greece||seen||Apr 1 at 10:59|
How do you balance between “do it right” and “do it ASAP” in your daily work?
@ErikReppen: Only problem with this approach is when biz (or the analysts) are aware of the issue but they usually disregard it due to budget and priorities, OR when your typical project is always underestimated in order to keep biz happy. In that case, any additional contingency time (15-20%) is used in order to cover last-minute requirements, contingencies (you usually cannot predict all component interactions, especially when you don't know the system well enough) etc. Then, the only thing you can do, imo, is to simply get better and learn the system in order to be able to catch up.
Is there a single book that covers the breadth of computer science fundamentals?
You're probably interested in something like "Computer Science: A Modern Introduction" by Goldschlager & Lister. Another one would be "Schaum's Outline of Introduction to Computer Science". But, as @dasblinkenlight suggested, you should focus on specific parts of CS and read that "bible" accordingly. For example, if you're interested in Algorithms, you'd probably have to read Knuth's tomes on the subject, or a book by Sedwick, or "Introduction to Algorithms" by Cormen, Leiserson, Rivest, Stein.