![]() ![]() (that is of course provided that you do have a repository/backup offsite and that you make sure that you backup your repositories often). ![]() You will not lose your code due to an alien invasion that targets your hard disk and makes it explode….You will be able to go back to a previous version.You will be able to tell what changed from version to version.Source Code Control and the path to happiness: It is almost as good as ice cream, cheese or chocolate. So why am I so passionate about Source Code Control? Well, it has saved me time, money and I just cannot imagine my professional live without it. ![]() If it is going to take him more than an hour of his time, it gets a repo created. He assures me that now he starts a repository no matter how small the project is. Anyway, after being mean for just a little bit I did help him to recover his project employing some XML magic. I don’t know about you, but I don’t want to lose 6 hours of my life. He did not want to tell me, but he finally did: “well, I was not using SCC, because it was a small project… “, I then asked him how long he had been working on this small project, the reply: more than 6 hours. I told him, well just go and update to the previous version you committed and you should be good. A couple of months ago he asked me to help him recover a LabVIEW project that was corrupt. Even my poor husband has started to use SCC. I no longer hear the “but I work by myself” argument. I am happy to report that the number has been steadily growing and now people approach me asking more about how to do it rather than why to do it. Over the years, I have asked how many LabVIEW developers were using Source Code Control at the beginning of several of my presentations. If you watch the video you will hear how a fellow at the front row laughed so hard that I knew I stroke a chord with that one. I have to thank Steve Watts for that last line: “Good programming practices have nothing to do with marital status”. Here is a video of the presentation starting at the moment I was talking about Source Code Control: Let’s start with a cartoon based on a real story that happened to me when working with a third party software provider: Today I want to focus on the last point from that presentation: “Every Developer Needs a Time Machine”. There were 5 tips in there, with some more focused on the UX (Usability Experience) and others focused on DX (Developer Experience). The title was “ How to Polish your software and development process to wow your end users “. I was interviewed by VIshots, I was asked to give the same presentation at NI Days in Paris and my friend Steve Watts gave his own version at NI Days in London the same year. I gave a presentation at NIWeek 2013 that turned out to be a lot more successful than I ever imagined. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |