Modern testing for modern stacks

Breaking things into smaller chunks of code worked well with some Tasks for me. I have never been able to implement it fully for all tasks. The idea is that when you get the momentum rolling with a few quick wins, you will be better poised to tackle the hard thing next. We need to use our cognitive resource well as its limited. However, I feel some days you have it more and it also goes by your interest areas. Reviewing things after it is done is also one more thing which I need to work on.

The best solutions for getting started on anything big is to break it up into the small. And, do it quickly. Take a few minutes to think through that big thing. What are its component parts? What will be the real effort required? Write it down. Then start working on the easiest of those component parts first.As an example,when I do regression testing, what I did was,I have written down the components to be tested,and where should I give priority.so what happened is almost I found where the bugs occurred and I did it quickly. The first thing to do after we look at the application or if we are going to start the work is make sure we understand what the end product is supposed to look like. Always create a timeline for completing our tasks. Complete the task early enough to have some time left for a final review.

Its a nice video, like the way she has given examples & related things. I can relate the experience to my current job & previous jobs in a different way. In Qxf2, we have a culture of breaking down our week into small tasks which have a healthy time-box, focus is more on the learning by trying out several times than delivering the perfect solution or completing within a particular time. In my previous companies, though the tasks were broken down, they all had a critical time-line to be completed within which at times was very hard & quality was compromised. As she quotes the example, sometimes we might jump from A task to C task subjective to our skillset. I agree that we should follow what she says about moving onto other tasks than just staying at one & piling up all.

It's a very nice video, explained very well about cognitive resource, deliberate practice with good examples. This video reminds me few techniques, which I learned during my post-graduation. Work Breakdown Structure (WBS), Critical Path Methods (CPM) and Project Evaluation and Review Technique (PERT) are very helpful in managing and estimating time and cost of work/project. This video also reminds me following quote: "Start by doing what is necessary; then do what is possible; and suddenly, you are doing the impossible." Many times while learning new things/languages, during exam time study, I achieved good output by breaking it into pieces. After breaking the work or task, it will be clear for us from where to start and where to end. A structured flow of work is very important to produce effective work.

My interpretation of this video: That cognitive resource is like a water bottle, you drain your resource working your brain, breaking down large tasks into smaller tasks helps, how to broke down tasks too was mentioned, and you can gain expertise in something- chicken sexing. How I can relate to it: I had this trouble when I used come to the office. I would burn my resource and when I get to the office I could do really little work, I have experienced breaking down smaller tasks when I learned Python, I had little knowledge about python class initially, revisited it after I came to know about Borg pattern,Javascript is another example,finally understand why we have hello world program and certain books ask you to try out programs before you start learning the programming language.