Learning C/C++ Programming

Author
Discussion

TheExcession

11,669 posts

251 months

Tuesday 8th September 2015
quotequote all
MarkRSi said:
Would the various books mentioned in this thread be good for .NET developers as well?

Not done much C/C++ at work but would be good to be prepared.

Only just started doing test-driven development/unit tests etc. wished I'd started doing them sooner.
A1

I think you might find Writing Solid Code interesting, primarily the book was written about memory management, and also giving thought to user interfaces.

Is it relevant today? Yes 100% - is it useful as a text - very probably not! smile

As for TDD - can some one actually describe to me what TDD actually means in a working role role writing code?








GreigM

6,728 posts

250 months

Tuesday 8th September 2015
quotequote all
TheExcession said:
As for TDD - can some one actually describe to me what TDD actually means in a working role role writing code?
It means you are working for a very large, well funded but ultimated hugely unproductive development team - probably in the financial industry. You will end up writing 20 times the amount of code you actually need to write in order to get the task done, 95% of your coding is abstract test cases. To print a variable to system out will take you 7 days to code and it will have to pass 4 "gateway" meetings with 2 project managers.

You will feel your life disturbingly mirrors a dilbert comic.

You will find the talented coders in your team (the ones who can actually cut masses of clean code with next to zero errors first time out) leave the team in droves to become contractors to a rival financial institution at 140 times their permanent rate. Two months later they will retire to bring up the kids in a daddy-day-care situation.

You will find your project cancelled after 2 years and £14M investment as the business user got fed up waiting and got their mate Dave who does daddy-day-care to put together and excel spreadsheet which does the job.

TheExcession

11,669 posts

251 months

Wednesday 9th September 2015
quotequote all
GreigM said:
TheExcession said:
As for TDD - can some one actually describe to me what TDD actually means in a working role role writing code?
It means you are working for a very large, well funded but ultimated hugely unproductive development team - probably in the financial industry. You will end up writing 20 times the amount of code you actually need to write in order to get the task done, 95% of your coding is abstract test cases. To print a variable to system out will take you 7 days to code and it will have to pass 4 "gateway" meetings with 2 project managers.

You will feel your life disturbingly mirrors a dilbert comic.

You will find the talented coders in your team (the ones who can actually cut masses of clean code with next to zero errors first time out) leave the team in droves to become contractors to a rival financial institution at 140 times their permanent rate. Two months later they will retire to bring up the kids in a daddy-day-care situation.

You will find your project cancelled after 2 years and £14M investment as the business user got fed up waiting and got their mate Dave who does daddy-day-care to put together and excel spreadsheet which does the job.
That's a bit worrying - but the OP just wanted a bit of help in wanting to learn how to be a good programmer.

I've given up programming - look at the the guy's that are coding games these days.

Tetris vs Elite, look at all the latest games - I'll be honest and say all I can do is advise on how to move data.





otolith

56,167 posts

205 months

Wednesday 9th September 2015
quotequote all
hehe

TheExcession

11,669 posts

251 months

Wednesday 9th September 2015
quotequote all
otolith said:
hehe
Could you just explain that?

otolith

56,167 posts

205 months

Wednesday 9th September 2015
quotequote all
GreigM's description of software development methodologies gone wrong.

TheExcession

11,669 posts

251 months

Wednesday 9th September 2015
quotequote all
GreigM said:
It means you are working for a very large, well funded but ultimated hugely unproductive development team - probably in the financial industry. You will end up writing 20 times the amount of code you actually need to write in order to get the task done, 95% of your coding is abstract test cases. To print a variable to system out will take you 7 days to code and it will have to pass 4 "gateway" meetings with 2 project managers.

You will feel your life disturbingly mirrors a dilbert comic.

You will find the talented coders in your team (the ones who can actually cut masses of clean code with next to zero errors first time out) leave the team in droves to become contractors to a rival financial institution at 140 times their permanent rate. Two months later they will retire to bring up the kids in a daddy-day-care situation.

You will find your project cancelled after 2 years and £14M investment as the business user got fed up waiting and got their mate Dave who does daddy-day-care to put together and excel spreadsheet which does the job.
Years and years back I had an argument with a new (then) programmer - he slated open source code. His stance was at least Microsoft provided a decent API you could work with.

About that time I was learning Linux.

To be honest at the time I didn't really know the difference, but now know I'd take Linux everyday for a LAMP environment.


AND AS FOR OUR POOR OP ASKING FOR A BIT OF HELP - is there a change that we can all just agree that if he wants/needs to code he needs to buy the dead tree version of the K&R ANSI version of the book that taught so many of us how to think in 'C'.