Version Control is nobody's idea of an exciting, challenging part of our work. So, maybe that's why so many people don't do it properly. But it is a fundamental discipline. So, learn it and apply it well. That way, you'll have one thing less to worry about! Thank you for watching - please do subscribe to the channel and, to join my community, sign-up at onlinepmcourses.com/assets440251/the-onlinepmcourses-newsletter/
Hi Mike, with the version numbering system you talked about, each identifier (2.03.02) is separated by a period ("."). However, how do you implement this within a filename? I ask this because good practice for naming filenames are that 'snake_case', 'kebab-case', 'camelCase' or 'PascalCase' should be used in order to avoid spaces as a means of separating elements of a filename. Moreover, using periods in a filename can cause some trouble as periods are used to separate file extensions such as '.png', '.pdf', '.jpg', '.exe', and so on. Thanks!
Well, the way I do it is 2-03-02. This works fine on my Mac and I assume it will work on Windows and Linux. But, if not, just pick another separator that is an allowed character for filenames. My Mac doesn't mind spaces in filenames, but I agree that it is likely safer to use underscores or dashed to fill gaps. All this is why I wanted to talk in terms of principles, rather than rules. Apply the principles in a way that works with whatever systems, processes, and technology you have.
I slow my delivery because I know that half of my audience doesn't have English as a first language, and that some of the concepts, and therefore words, I use may not be familiar.
Version Control is nobody's idea of an exciting, challenging part of our work. So, maybe that's why so many people don't do it properly. But it is a fundamental discipline. So, learn it and apply it well. That way, you'll have one thing less to worry about!
Thank you for watching - please do subscribe to the channel and, to join my community, sign-up at onlinepmcourses.com/assets440251/the-onlinepmcourses-newsletter/
📄
Recommend a standalone software solution for version control. Tnks
@@sharafadeenmubarak2192 Unfortunately, I don't have enough knowledge to make a fair recommendation.
Do you have a preference for any software for .docx and .pdf version control?
No, I don't. I have used either manual numbering or high-end document management systems.
This is useful, thanks. What do you mean by new name in principle 1.
The file name needs to be different for every version - usually by including the full version number and/or the date in the file name.
Awesome video!!!! Clean and concise, thank you for this!
Thank you - you're welcome.
Hi Mike, with the version numbering system you talked about, each identifier (2.03.02) is separated by a period ("."). However, how do you implement this within a filename? I ask this because good practice for naming filenames are that 'snake_case', 'kebab-case', 'camelCase' or 'PascalCase' should be used in order to avoid spaces as a means of separating elements of a filename. Moreover, using periods in a filename can cause some trouble as periods are used to separate file extensions such as '.png', '.pdf', '.jpg', '.exe', and so on. Thanks!
Well, the way I do it is 2-03-02. This works fine on my Mac and I assume it will work on Windows and Linux. But, if not, just pick another separator that is an allowed character for filenames. My Mac doesn't mind spaces in filenames, but I agree that it is likely safer to use underscores or dashed to fill gaps.
All this is why I wanted to talk in terms of principles, rather than rules. Apply the principles in a way that works with whatever systems, processes, and technology you have.
Thanks Mike, this is helpfull keep doing such videos.
I certainly shall.
this guy is such a BOOMER lmao
I'm, on the cusp of Boomers and GenX - probably more GenX. But... so what?
why..
do you..
talk..
like... that?
I slow my delivery because I know that half of my audience doesn't have English as a first language, and that some of the concepts, and therefore words, I use may not be familiar.