Just put it here as a reminder.
https://www.reddit.com/r/cpp/comments/8o8q1e/how_should_one_write_a_fullscale_program_in_c/
quote:
Most of us just make it up as we go along dude.
Its a continuous process. The fundamental issue is the technical debt as you go along. Never be afraid to refactor and push back against manager types who hate allocating time for "refactor". The growth is always organic but you have to maintain a balance between navel gazing and actually executing the idea. Tools of the trade are source control, a decent build system, Google and an evolving thought process which is atleast 2 steps ahead of the code you are writing. Don't get lost in cutting edge C++ features; Good software engineering has nothing to do with the latest compiler tricks or reading through C++ standard proposals.
[note] Nevertheless, it's still important to catch up, why? Because there are design ideas inside these proposals as well. And if we have something better, feedback to the community.
https://www.reddit.com/r/cpp/comments/8o8q1e/how_should_one_write_a_fullscale_program_in_c/
quote:
Most of us just make it up as we go along dude.
Its a continuous process. The fundamental issue is the technical debt as you go along. Never be afraid to refactor and push back against manager types who hate allocating time for "refactor". The growth is always organic but you have to maintain a balance between navel gazing and actually executing the idea. Tools of the trade are source control, a decent build system, Google and an evolving thought process which is atleast 2 steps ahead of the code you are writing. Don't get lost in cutting edge C++ features; Good software engineering has nothing to do with the latest compiler tricks or reading through C++ standard proposals.
[note] Nevertheless, it's still important to catch up, why? Because there are design ideas inside these proposals as well. And if we have something better, feedback to the community.
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.