1 1 00:00:00,000 --> 00:00:03,000 Here's something that happens to a lot 2 2 00:00:01,380 --> 00:00:05,100 of students and maybe it's happened to 3 3 00:00:03,000 --> 00:00:07,290 you. You decide you want to learn to code 4 4 00:00:05,100 --> 00:00:09,059 so you get a few tutorials and maybe you 5 5 00:00:07,290 --> 00:00:11,550 buy a course you start going through 6 6 00:00:09,059 --> 00:00:15,179 them and it's great but then you get to 7 7 00:00:11,550 --> 00:00:16,740 the end of the course and what next this 8 8 00:00:15,179 --> 00:00:18,270 is a very frequent question that I get 9 9 00:00:16,740 --> 00:00:20,189 from my students they've got the 10 10 00:00:18,270 --> 00:00:22,590 necessary skills to do software 11 11 00:00:20,189 --> 00:00:24,750 development but they're not sure on how 12 12 00:00:22,590 --> 00:00:27,510 to actually go about it so let's talk 13 13 00:00:24,750 --> 00:00:29,160 about that in this video hi guys I'm 14 14 00:00:27,510 --> 00:00:31,019 Jose and I've been teaching students how 15 15 00:00:29,160 --> 00:00:33,390 to code online for over seven years 16 16 00:00:31,019 --> 00:00:35,489 today I want to help you learn one of 17 17 00:00:33,390 --> 00:00:37,410 the most important skills when doing 18 18 00:00:35,489 --> 00:00:39,809 software development which is how to 19 19 00:00:37,410 --> 00:00:42,719 work on software projects either by 20 20 00:00:39,809 --> 00:00:45,899 yourself or with a team day in day out 21 21 00:00:42,719 --> 00:00:48,629 and how to make them and you successful 22 22 00:00:45,899 --> 00:00:50,370 this video is not about how to find work 23 23 00:00:48,629 --> 00:00:52,559 but more about how to handle your 24 24 00:00:50,370 --> 00:00:55,230 software projects so that working on 25 25 00:00:52,559 --> 00:00:57,329 them is easier ideas for projects are a 26 26 00:00:55,230 --> 00:00:59,670 dime a dozen like they say what's 27 27 00:00:57,329 --> 00:01:02,309 actually difficult is to make the stuff 28 28 00:00:59,670 --> 00:01:04,170 that you're making well I'm going to 29 29 00:01:02,309 --> 00:01:05,850 show you the industry standard process 30 30 00:01:04,170 --> 00:01:08,909 for developing software projects both 31 31 00:01:05,850 --> 00:01:11,670 large and small by yourself or with a 32 32 00:01:08,909 --> 00:01:13,590 team and for yourself or for a client no 33 33 00:01:11,670 --> 00:01:16,170 matter the size and complexity of a 34 34 00:01:13,590 --> 00:01:18,509 project the core of this process remains 35 35 00:01:16,170 --> 00:01:20,820 unchanged and there are five main steps 36 36 00:01:18,509 --> 00:01:23,250 to this process the first one is that 37 37 00:01:20,820 --> 00:01:26,100 you should become a user or at least 38 38 00:01:23,250 --> 00:01:28,229 have a user in your team the second one 39 39 00:01:26,100 --> 00:01:29,970 is that you need to populate the backlog 40 40 00:01:28,229 --> 00:01:31,770 or the actual work that you're going to 41 41 00:01:29,970 --> 00:01:34,110 do in the project and you're going to do 42 42 00:01:31,770 --> 00:01:36,240 this with the help of the user number 43 43 00:01:34,110 --> 00:01:39,090 three is the bread and butter of our 44 44 00:01:36,240 --> 00:01:42,390 craft which is actual design and coding 45 45 00:01:39,090 --> 00:01:44,220 for number four we've got a review we 46 46 00:01:42,390 --> 00:01:45,810 want to show the user what we've done 47 47 00:01:44,220 --> 00:01:47,520 and we want to go through all the 48 48 00:01:45,810 --> 00:01:50,220 software that we've developed and number 49 49 00:01:47,520 --> 00:01:50,880 five is to improve your process so that 50 50 00:01:50,220 --> 00:01:52,979 next time 51 51 00:01:50,880 --> 00:01:54,799 you can do things better let's talk 52 52 00:01:52,979 --> 00:01:57,540 about those five steps one at a time 53 53 00:01:54,799 --> 00:02:00,479 software projects have a bad rap for 54 54 00:01:57,540 --> 00:02:02,219 running over time and over budgets and I 55 55 00:02:00,479 --> 00:02:04,560 believe that happens because software 56 56 00:02:02,219 --> 00:02:06,630 projects change a lot over their 57 57 00:02:04,560 --> 00:02:08,069 lifetimes it's not uncommon that you get 58 58 00:02:06,630 --> 00:02:10,110 to the end of a project and you decide 59 59 00:02:08,069 --> 00:02:11,700 to add more stuff for example imagine 60 60 00:02:10,110 --> 00:02:13,530 you're developing an e-commerce website 61 61 00:02:11,700 --> 00:02:16,260 for a client 62 62 00:02:13,530 --> 00:02:18,750 you spend hours designing and planning 63 63 00:02:16,260 --> 00:02:21,390 and coding every feature that they ask 64 64 00:02:18,750 --> 00:02:23,190 of you initially then you get to the end 65 65 00:02:21,390 --> 00:02:25,830 and you show the project to the client 66 66 00:02:23,190 --> 00:02:28,560 and now comes the tricky part because 67 67 00:02:25,830 --> 00:02:31,140 they see what you can do or maybe even 68 68 00:02:28,560 --> 00:02:32,700 what can be done and they decide that 69 69 00:02:31,140 --> 00:02:34,980 you know maybe you should add a um a 70 70 00:02:32,700 --> 00:02:36,600 review system to this ecommerce store so 71 71 00:02:34,980 --> 00:02:39,030 that customers can leave reviews on 72 72 00:02:36,600 --> 00:02:41,640 items right how hard can that be when 73 73 00:02:39,030 --> 00:02:43,680 you'd already done everything else but 74 74 00:02:41,640 --> 00:02:45,989 the key thing is when you're planning 75 75 00:02:43,680 --> 00:02:47,820 and coding a software project you make 76 76 00:02:45,989 --> 00:02:50,850 decisions based on the information you 77 77 00:02:47,820 --> 00:02:52,920 have and having this review system after 78 78 00:02:50,850 --> 00:02:54,959 the fact could actually add weeks or 79 79 00:02:52,920 --> 00:02:57,570 even months of work to the project 80 80 00:02:54,959 --> 00:03:01,019 because you haven't planned the project 81 81 00:02:57,570 --> 00:03:03,450 for that and so if you had decided to 82 82 00:03:01,019 --> 00:03:05,310 add this review system initially then it 83 83 00:03:03,450 --> 00:03:07,290 may have been really easy to add it but 84 84 00:03:05,310 --> 00:03:09,900 if you add it at the end it can become 85 85 00:03:07,290 --> 00:03:12,600 really difficult to prevent this you 86 86 00:03:09,900 --> 00:03:14,310 have the client in your team looking at 87 87 00:03:12,600 --> 00:03:15,860 the progress you're making frequently 88 88 00:03:14,310 --> 00:03:18,360 and you should build your software 89 89 00:03:15,860 --> 00:03:20,190 incrementally so that they can always be 90 90 00:03:18,360 --> 00:03:21,959 using the project and giving you 91 91 00:03:20,190 --> 00:03:24,420 feedback on what to do next 92 92 00:03:21,959 --> 00:03:26,670 if you plan three or six months in 93 93 00:03:24,420 --> 00:03:29,880 advance you're building up a lot of risk 94 94 00:03:26,670 --> 00:03:33,000 that some or all of that plan may not be 95 95 00:03:29,880 --> 00:03:35,130 used or useful so how far in advance 96 96 00:03:33,000 --> 00:03:37,350 should you plan well the industry 97 97 00:03:35,130 --> 00:03:39,870 standards suggest that about two or 98 98 00:03:37,350 --> 00:03:42,269 three weeks in the industry we call this 99 99 00:03:39,870 --> 00:03:43,980 work period a sprint and let's take a 100 100 00:03:42,269 --> 00:03:46,590 look at what happens with this ecommerce 101 101 00:03:43,980 --> 00:03:49,709 project if you start it with the user in 102 102 00:03:46,590 --> 00:03:51,780 your team firstly you may have to fight 103 103 00:03:49,709 --> 00:03:54,120 with the user slightly don't let them 104 104 00:03:51,780 --> 00:03:57,000 just dump on you six months worth of 105 105 00:03:54,120 --> 00:04:00,150 work and then go away and not interact 106 106 00:03:57,000 --> 00:04:02,549 with you again you want to plan for one 107 107 00:04:00,150 --> 00:04:04,560 sprint worth of work with the user 108 108 00:04:02,549 --> 00:04:06,209 together in the same room if possible or 109 109 00:04:04,560 --> 00:04:08,370 in the same video conference given the 110 110 00:04:06,209 --> 00:04:10,530 current state of affairs that way you 111 111 00:04:08,370 --> 00:04:12,570 can really understand how the software 112 112 00:04:10,530 --> 00:04:14,519 is going to help them because what you 113 113 00:04:12,570 --> 00:04:17,010 want to achieve in one sprint is 114 114 00:04:14,519 --> 00:04:18,780 something that will be useful to the 115 115 00:04:17,010 --> 00:04:22,409 user that they can actually take away 116 116 00:04:18,780 --> 00:04:24,720 and start using this is called working 117 117 00:04:22,409 --> 00:04:26,849 software and every sprint should result 118 118 00:04:24,720 --> 00:04:27,540 in working software that you could give 119 119 00:04:26,849 --> 00:04:29,340 the user 120 120 00:04:27,540 --> 00:04:31,950 that way the user can play around with 121 121 00:04:29,340 --> 00:04:33,330 the software they can update the ideas 122 122 00:04:31,950 --> 00:04:34,860 in their head about how this software 123 123 00:04:33,330 --> 00:04:36,690 should be developed and they can 124 124 00:04:34,860 --> 00:04:39,240 potentially change their mind about what 125 125 00:04:36,690 --> 00:04:41,520 you want to do next this really is the 126 126 00:04:39,240 --> 00:04:44,250 key to breaking down large software 127 127 00:04:41,520 --> 00:04:47,040 projects making stuff that's useful in 128 128 00:04:44,250 --> 00:04:49,170 single sprints that can be two three 129 129 00:04:47,040 --> 00:04:51,900 four weeks but you got to make stuff 130 130 00:04:49,170 --> 00:04:53,730 that's useful in that time for the user 131 131 00:04:51,900 --> 00:04:56,790 once you've planned for your first 132 132 00:04:53,730 --> 00:04:58,590 sprint the user can add all other work 133 133 00:04:56,790 --> 00:05:01,200 that won't be completed in that time 134 134 00:04:58,590 --> 00:05:03,120 into the product backlog this is a 135 135 00:05:01,200 --> 00:05:05,940 ordered list of what the user thinks 136 136 00:05:03,120 --> 00:05:07,950 that you're going to tackle next the 137 137 00:05:05,940 --> 00:05:09,990 backlog is organic and the user can add 138 138 00:05:07,950 --> 00:05:11,610 or remove work from there as they change 139 139 00:05:09,990 --> 00:05:13,680 their mind as often as they want but 140 140 00:05:11,610 --> 00:05:15,480 what they shouldn't do is change the 141 141 00:05:13,680 --> 00:05:17,700 stuff you've already planned the stuff 142 142 00:05:15,480 --> 00:05:19,200 that you're working on in this sprint so 143 143 00:05:17,700 --> 00:05:21,540 I'd like to think of it in two ways 144 144 00:05:19,200 --> 00:05:23,130 you've got the stuff in your sprint that 145 145 00:05:21,540 --> 00:05:25,500 you have really discussed with the user 146 146 00:05:23,130 --> 00:05:28,200 you formalize and you've defined well 147 147 00:05:25,500 --> 00:05:30,120 and you've planned technically either by 148 148 00:05:28,200 --> 00:05:32,310 yourself or with your development team 149 149 00:05:30,120 --> 00:05:34,800 and then you've got the product backlog 150 150 00:05:32,310 --> 00:05:37,980 that is not very well defined and really 151 151 00:05:34,800 --> 00:05:40,200 it's more ideas for conversations that 152 152 00:05:37,980 --> 00:05:42,530 you want to have with the user later on 153 153 00:05:40,200 --> 00:05:45,060 when the time comes to implement that 154 154 00:05:42,530 --> 00:05:46,860 that way you're never spending too much 155 155 00:05:45,060 --> 00:05:48,630 time planning the stuff that you're not 156 156 00:05:46,860 --> 00:05:50,070 working on and when you get to the end 157 157 00:05:48,630 --> 00:05:51,840 of a sprint the user can review what 158 158 00:05:50,070 --> 00:05:53,490 you've done remember it should be 159 159 00:05:51,840 --> 00:05:55,320 working software and they can 160 160 00:05:53,490 --> 00:05:56,490 potentially change the product backlog 161 161 00:05:55,320 --> 00:05:59,250 and change the stuff that you want to 162 162 00:05:56,490 --> 00:06:01,350 work on before you plan it well coming 163 163 00:05:59,250 --> 00:06:03,750 to design and coding a lot of developers 164 164 00:06:01,350 --> 00:06:05,220 thing that you just design first you get 165 165 00:06:03,750 --> 00:06:07,170 it everything ready you make it pixel 166 166 00:06:05,220 --> 00:06:09,600 perfect and then you give it over to the 167 167 00:06:07,170 --> 00:06:11,340 coder and they code it and then that's 168 168 00:06:09,600 --> 00:06:12,870 it and but really that couldn't be 169 169 00:06:11,340 --> 00:06:15,450 further from the truth if you do that 170 170 00:06:12,870 --> 00:06:17,490 that's gonna cause some problems I would 171 171 00:06:15,450 --> 00:06:19,590 say designers and developers working 172 172 00:06:17,490 --> 00:06:22,590 together means that they can solve 173 173 00:06:19,590 --> 00:06:24,330 problems more easily by combining 174 174 00:06:22,590 --> 00:06:25,680 knowledge from both disciplines and also 175 175 00:06:24,330 --> 00:06:27,300 they can learn from each other by 176 176 00:06:25,680 --> 00:06:29,610 working as a pair with your designer and 177 177 00:06:27,300 --> 00:06:31,560 being involved in both the design and 178 178 00:06:29,610 --> 00:06:33,300 the coding processes you can do things 179 179 00:06:31,560 --> 00:06:35,910 like make compromises for example 180 180 00:06:33,300 --> 00:06:38,190 simplifying a design so it's much easier 181 181 00:06:35,910 --> 00:06:40,980 to code or the opposite you can make 182 182 00:06:38,190 --> 00:06:41,550 changes to previous code to allow for 183 183 00:06:40,980 --> 00:06:44,129 new acts 184 184 00:06:41,550 --> 00:06:45,930 is to be implemented let me give you an 185 185 00:06:44,129 --> 00:06:48,389 example of a previous company I worked 186 186 00:06:45,930 --> 00:06:51,509 at we wanted to add a telephone number 187 187 00:06:48,389 --> 00:06:53,009 field to a form and so the designer was 188 188 00:06:51,509 --> 00:06:54,659 working on this telephone number field 189 189 00:06:53,009 --> 00:06:55,919 and I was thinking about how we were 190 190 00:06:54,659 --> 00:06:58,289 gonna implement it you can probably 191 191 00:06:55,919 --> 00:07:00,240 already see that how could I think of 192 192 00:06:58,289 --> 00:07:01,379 how I'm gonna implement this if we 193 193 00:07:00,240 --> 00:07:04,530 didn't have a design yet but nonetheless 194 194 00:07:01,379 --> 00:07:06,300 I was I was giving it a thing and I was 195 195 00:07:04,530 --> 00:07:08,310 thinking well it's a phone number field 196 196 00:07:06,300 --> 00:07:09,870 we're gonna have to do some validation 197 197 00:07:08,310 --> 00:07:11,520 to make sure it's valid but we can get 198 198 00:07:09,870 --> 00:07:14,610 the users to just enter the phone number 199 199 00:07:11,520 --> 00:07:17,130 in a text field and maybe an HTML a 200 200 00:07:14,610 --> 00:07:19,620 number field or phone number field and 201 201 00:07:17,130 --> 00:07:20,190 we'll run some validation and that's 202 202 00:07:19,620 --> 00:07:21,419 about it 203 203 00:07:20,190 --> 00:07:24,210 and so I thought it was going to be 204 204 00:07:21,419 --> 00:07:26,370 pretty easy maybe a few days worth of 205 205 00:07:24,210 --> 00:07:28,139 work or something like that and but in 206 206 00:07:26,370 --> 00:07:30,539 the end what happened is in the design 207 207 00:07:28,139 --> 00:07:32,490 stage we decided that we wanted to add a 208 208 00:07:30,539 --> 00:07:34,590 drop-down to the phone number field 209 209 00:07:32,490 --> 00:07:37,440 where users would be able to select the 210 210 00:07:34,590 --> 00:07:39,719 country code and like +4 4 + 3 4 etc 211 211 00:07:37,440 --> 00:07:42,240 before entering their phone number and 212 212 00:07:39,719 --> 00:07:44,969 this added a whole new dimension of 213 213 00:07:42,240 --> 00:07:47,460 complexity to the validation as well as 214 214 00:07:44,969 --> 00:07:49,110 to the formatting of the phone number if 215 215 00:07:47,460 --> 00:07:51,030 I had been involved in the design 216 216 00:07:49,110 --> 00:07:53,009 process from the beginning and we had 217 217 00:07:51,030 --> 00:07:55,229 wanted this phone number to be released 218 218 00:07:53,009 --> 00:07:56,699 very quickly we might have decided that 219 219 00:07:55,229 --> 00:07:58,560 you know we can just make it a text 220 220 00:07:56,699 --> 00:08:01,139 field now release it quickly give it to 221 221 00:07:58,560 --> 00:08:03,180 the users and then add the drop-down 222 222 00:08:01,139 --> 00:08:05,490 feature to the product backlog to be 223 223 00:08:03,180 --> 00:08:07,099 implemented later on if we decided that 224 224 00:08:05,490 --> 00:08:09,300 that was something that was worth doing 225 225 00:08:07,099 --> 00:08:11,159 let's say we've got to the end of the 226 226 00:08:09,300 --> 00:08:14,789 Sprint we've done 2 or 3 weeks worth of 227 227 00:08:11,159 --> 00:08:17,190 work now the key is that that work must 228 228 00:08:14,789 --> 00:08:20,520 be working software you must have an 229 229 00:08:17,190 --> 00:08:22,800 increment of product that is working and 230 230 00:08:20,520 --> 00:08:24,060 the user can play with and so at this 231 231 00:08:22,800 --> 00:08:26,219 point you're gonna do some user testing 232 232 00:08:24,060 --> 00:08:27,960 and you're gonna do a review so the user 233 233 00:08:26,219 --> 00:08:30,270 is gonna get a chance to try out your 234 234 00:08:27,960 --> 00:08:31,590 product and change their mind regarding 235 235 00:08:30,270 --> 00:08:34,079 what to do next 236 236 00:08:31,590 --> 00:08:36,659 but not only is the user the one that 237 237 00:08:34,079 --> 00:08:39,479 benefits from doing this the team gets a 238 238 00:08:36,659 --> 00:08:41,339 massive morale boost if you have stuff 239 239 00:08:39,479 --> 00:08:43,500 to show off at this review you can see 240 240 00:08:41,339 --> 00:08:45,390 that stuff is getting completed features 241 241 00:08:43,500 --> 00:08:47,040 are getting done and you can see that 242 242 00:08:45,390 --> 00:08:49,800 larger features that maybe take longer 243 243 00:08:47,040 --> 00:08:51,420 than a sprint are slowly coming into 244 244 00:08:49,800 --> 00:08:54,660 fruition so this part is really 245 245 00:08:51,420 --> 00:08:56,490 important if you don't do review 246 246 00:08:54,660 --> 00:08:58,230 and you skipped too many of them what 247 247 00:08:56,490 --> 00:09:00,750 ends up happening is nobody in the team 248 248 00:08:58,230 --> 00:09:02,699 really knows what features are working 249 249 00:09:00,750 --> 00:09:05,310 or how features are working together how 250 250 00:09:02,699 --> 00:09:08,100 the end product looks and so doing 251 251 00:09:05,310 --> 00:09:10,259 reviews is great it's very important 252 252 00:09:08,100 --> 00:09:12,209 that everybody in the team uses the 253 253 00:09:10,259 --> 00:09:14,939 product frequently if possible and 254 254 00:09:12,209 --> 00:09:17,009 reviews are a great place to start doing 255 255 00:09:14,939 --> 00:09:19,980 that step 5 is the one that everybody 256 256 00:09:17,009 --> 00:09:23,250 misses and that is improve your process 257 257 00:09:19,980 --> 00:09:25,800 and this is critical you want to always 258 258 00:09:23,250 --> 00:09:28,620 have the opportunity to get together as 259 259 00:09:25,800 --> 00:09:30,180 a team without the user and look at 260 260 00:09:28,620 --> 00:09:31,829 what's gone well what hasn't gone so 261 261 00:09:30,180 --> 00:09:33,990 well what things you can change 262 262 00:09:31,829 --> 00:09:36,810 so that developing software becomes 263 263 00:09:33,990 --> 00:09:39,509 easier and this might be you've got some 264 264 00:09:36,810 --> 00:09:41,220 issues within the team maybe people are 265 265 00:09:39,509 --> 00:09:42,990 leaving or joining and you need to do 266 266 00:09:41,220 --> 00:09:44,879 some training maybe you want to 267 267 00:09:42,990 --> 00:09:46,529 introduce some new tools that are gonna 268 268 00:09:44,879 --> 00:09:48,750 help you and develop software more 269 269 00:09:46,529 --> 00:09:50,879 easily maybe you need to attend a course 270 270 00:09:48,750 --> 00:09:52,439 to learn about a new technology stuff 271 271 00:09:50,879 --> 00:09:54,779 like that those are all sorts of things 272 272 00:09:52,439 --> 00:09:57,060 that appear when you actually spend time 273 273 00:09:54,779 --> 00:09:59,220 together to talk about how to improve 274 274 00:09:57,060 --> 00:10:02,430 your process the most important thing is 275 275 00:09:59,220 --> 00:10:05,040 that everybody in this meeting needs to 276 276 00:10:02,430 --> 00:10:06,360 feel safe and to speak out their mind 277 277 00:10:05,040 --> 00:10:07,949 and they're not gonna get punished so 278 278 00:10:06,360 --> 00:10:10,170 there needs to be no blame and no fear 279 279 00:10:07,949 --> 00:10:12,240 in order for this type of meeting to be 280 280 00:10:10,170 --> 00:10:13,620 successful but it's very important all 281 281 00:10:12,240 --> 00:10:16,110 right that's really everything about me 282 282 00:10:13,620 --> 00:10:18,509 regarding how to plan and work on 283 283 00:10:16,110 --> 00:10:21,420 software projects the key point the most 284 284 00:10:18,509 --> 00:10:24,630 important one is to break stuff down in 285 285 00:10:21,420 --> 00:10:26,670 planning for one Sprint's worth of work 286 286 00:10:24,630 --> 00:10:29,610 two or three weeks normally so that you 287 287 00:10:26,670 --> 00:10:32,100 end up with useful working software at 288 288 00:10:29,610 --> 00:10:34,259 the end working software really should 289 289 00:10:32,100 --> 00:10:35,430 be the measure of progress and if you 290 290 00:10:34,259 --> 00:10:37,410 get to the end of a sprint with no 291 291 00:10:35,430 --> 00:10:40,079 working software that is a red flag that 292 292 00:10:37,410 --> 00:10:41,939 something is not going well somewhere 293 293 00:10:40,079 --> 00:10:43,470 when you're working in projects on this 294 294 00:10:41,939 --> 00:10:44,970 way where you're always producing 295 295 00:10:43,470 --> 00:10:47,579 working software every sprint and your 296 296 00:10:44,970 --> 00:10:49,980 user is always engaged with what's going 297 297 00:10:47,579 --> 00:10:52,649 on and software projects tend to never 298 298 00:10:49,980 --> 00:10:55,379 end what ends up happening is either the 299 299 00:10:52,649 --> 00:10:57,540 user or customer runs out of budget they 300 300 00:10:55,379 --> 00:10:59,129 run out of money maybe eventually they 301 301 00:10:57,540 --> 00:11:00,389 feel satisfied and they're like okay I 302 302 00:10:59,129 --> 00:11:02,850 think we can stop here because the 303 303 00:11:00,389 --> 00:11:06,420 software is useful this is what we 304 304 00:11:02,850 --> 00:11:08,040 wanted it's this seldom happens or maybe 305 305 00:11:06,420 --> 00:11:09,630 you end up moving it to something else 306 306 00:11:08,040 --> 00:11:11,730 if you're working in a larger company 307 307 00:11:09,630 --> 00:11:13,050 but this is common with software 308 308 00:11:11,730 --> 00:11:16,290 projects for them to never end you 309 309 00:11:13,050 --> 00:11:18,180 always add more stuff it's not uncommon 310 310 00:11:16,290 --> 00:11:20,550 that you get to the alleged end of a 311 311 00:11:18,180 --> 00:11:22,380 software project and lo and behold 100 312 312 00:11:20,550 --> 00:11:24,959 new ideas are coming your way for more 313 313 00:11:22,380 --> 00:11:26,940 stuff to add to a project if you'd like 314 314 00:11:24,959 --> 00:11:29,639 me to make a video on the tools and 315 315 00:11:26,940 --> 00:11:32,430 practices I use to work personally as a 316 316 00:11:29,639 --> 00:11:33,480 developer both solo and in a team let me 317 317 00:11:32,430 --> 00:11:35,250 know I was thinking of making something 318 318 00:11:33,480 --> 00:11:36,750 like this if we do make it it'll be 319 319 00:11:35,250 --> 00:11:38,130 linked down in the description below and 320 320 00:11:36,750 --> 00:11:40,380 also in one of those week cards that 321 321 00:11:38,130 --> 00:11:41,730 appear at the end of the video but other 322 322 00:11:40,380 --> 00:11:43,230 than that that's everything from me 323 323 00:11:41,730 --> 00:11:44,910 thank you so much for watching this 324 324 00:11:43,230 --> 00:11:47,899 video thanks for joining me and I see 325 325 00:11:44,910 --> 00:11:49,899 you in the next one