I'd have a language reference book, and a platform reference book.
If we are using a lightweight management process, like Scrum, I'd have a book on that too.
I may also have a variety of specific technology books (e.g., OpenGL, Vulkan, Metal, CUDA).
I also tend to have a bunch of "best practices" books for the language being used. Like Effective C++, Modern C++ Design, C++ Coding Standards, et cetera.
My "library" of must have books are: Code Complete, Writing Solid Code, Debugging the Development Process, Design Patterns, AntiPatterns, Clean Code.
One of my colleagues I highly respect strongly recommended these books to me as ones I should add to my library: Influencer, Getting More, Measuring and Managing Performance in Organizations, The Power of Habit, Drive, Test-Driven Development, Growing Object-Oriented Software, Refactoring.
And although all those books may be available in electronic form, I prefer actual books.
Experienced ASP.NET developer passionate about learning Software Engineering, being an effective team member, and carving out my own little niche in the world.
I enjoy working with jQuery, Angul...
Sorry, I haven't needed to work with SQL since the late 1990s. At that time, I just used the Microsoft book that came with MS-SQL.
That particular project had a full-time dedicated database architect who constructed all the ERDs, models, schemas, and stored procedure APIs. And he co-ordinated with the database administrators so everything would scale to the needs of the project.
He was awesome. I wish I knew what tools he used, because the output was very nice. But because of that, all the gory details were already ironed-out and given to us developers on a silver platter.
At some point after I left the project (and the DBA had also moved on), the project moved from MS-SQL to IBM DB2. I've always wondered how well that transitioned.
In general, I think the publisher Addison-Wesley produces top-notch books. Rarely do they ever print a stinker. My next favorite publisher is O'Reilly, but sometimes they have mediocre or stinkers so you need to be a little more careful.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'd have a language reference book, and a platform reference book.
If we are using a lightweight management process, like Scrum, I'd have a book on that too.
I may also have a variety of specific technology books (e.g., OpenGL, Vulkan, Metal, CUDA).
I also tend to have a bunch of "best practices" books for the language being used. Like Effective C++, Modern C++ Design, C++ Coding Standards, et cetera.
My "library" of must have books are: Code Complete, Writing Solid Code, Debugging the Development Process, Design Patterns, AntiPatterns, Clean Code.
One of my colleagues I highly respect strongly recommended these books to me as ones I should add to my library: Influencer, Getting More, Measuring and Managing Performance in Organizations, The Power of Habit, Drive, Test-Driven Development, Growing Object-Oriented Software, Refactoring.
And although all those books may be available in electronic form, I prefer actual books.
Anything you recommend for SQL/SQL Server/Database Design?
Sorry, I haven't needed to work with SQL since the late 1990s. At that time, I just used the Microsoft book that came with MS-SQL.
That particular project had a full-time dedicated database architect who constructed all the ERDs, models, schemas, and stored procedure APIs. And he co-ordinated with the database administrators so everything would scale to the needs of the project.
He was awesome. I wish I knew what tools he used, because the output was very nice. But because of that, all the gory details were already ironed-out and given to us developers on a silver platter.
At some point after I left the project (and the DBA had also moved on), the project moved from MS-SQL to IBM DB2. I've always wondered how well that transitioned.
In general, I think the publisher Addison-Wesley produces top-notch books. Rarely do they ever print a stinker. My next favorite publisher is O'Reilly, but sometimes they have mediocre or stinkers so you need to be a little more careful.