41–45 of 45 posts
It is frustrating how widely applicable this book is. Universities across the country are struggling to adequately prepare students for software engineering jobs. It is also frustrating that this book from 2012 is still applicable in 2018. I'm not sure what the solution is or what would drive change here.
- The very bottom of the 2012 PDF page [1] mentions the related doc generation project, MarkBind [2]
- The MarkBind site mentions two software engineering courses whose materials were written using it.
- One of these is TE3201 [3], which links to the current version of the book [4].
[1] http://www.comp.nus.edu.sg/~seer/book/2e/
[2] https://markbind.github.io/markbind/
No section for "Embedded" development? I think its missing a big part of the current picture ..
We're always the first to be forgotten.
I've recently been reading Elecia White's Making Embedded Systems which is the closest thing to this book I can think of.
Earlier quoted context omitted.
We were introduced to version control in our first year. The only problem was that till we started managing large code bases, most people found it very difficult to understand why we used Git in the first place.
Yes! Git is not merely version control but a specialized sort of version control. I've run into the opposite problem, when I've tried to use Git for projects that weren't source code. Without thinking about it, just by reflex, I'd create a project directory for a new project: Web pages that were almost entirely English text, or a Photoshop project, or an e-book project...and init my git to track it and set up my serv…
edit: And you can undo when you find you need something again you deleted, which happens once in a while too.
Earlier quoted context omitted.
We're always the first to be forgotten.
If anyone has a book similar to this for embedded - I'd love to know. I've recently been reading Elecia White's Making Embedded Systems which is the closest thing to this book I can think of.