So you've asked yourself again.
Who's it for.
And you've answered your own question and it's the people you're working with the ones you're sitting
next to.
Or maybe they're in a group chat.
And now in today's day and age it saddens me how many communication channels there are because most
of them encourage communicating too often.
Now one thing you'll probably pick up is that unless it's an emergency now is often never the best time.
So let's break this down projects you work on will have arbitrarily long timelines with many milestones
plans and steps.
And keep in mind the longer the time scale the worse humans are at dealing with them.
Break it down days and weeks are much easier units of time to understand what are you working on this
week.
Write it down.
Share it with the team.
This not only consolidates your thinking it gives your team an opportunity to ask questions and offer
advice.
You'll find that short term progress often disappoints but long term progress surprises.
So if you're working on a six month project you can break this down like starting from zero months.
It might be hard to realize what's happening right at the end.
So you break it down.
You've got a four week month.
You break one month into four weeks and then you break one week into five days.
I don't know about you but when I try to think of something that's six months ahead I have a lot of
trouble.
But when I break it down to go what can I do today.
That's going to add up to this week.
And what can I do in this month that's going to add up to this first month here and then go.
Same for the next one.
Same to the third one.
And then by the time I get to this end of six months I realize Wow I've actually come a long way and
it's all from breaking it down into days and weeks now.
The first part of this is what did you work on today.
Now of course this is just one technique that you might want to try.
But you could set a reminder for the end of each day and have it ask you what did you work on today.
Your response doesn't have to be too long but it should be written down.
You could use the following template.
What I worked on today so one to three points on what you did.
Maybe you could do what's working what's not working what could be improved and what I'm working on
next.
What's your next course of action based on the above and why what's holding you back.
Remember that conversation want to have with your project manager or team lead or something like that.
They want to be at a remove roadblocks for you so you can get back to doing the work your best at to
coding projects relate.
All of these back to the overall project goal that six month project pretty hard to understand in one
go but day by day week by week sending these updates through to your team.
This is really going to help out.
So what you want to do is take note of the overlaps which questions arise.
If a question gets asked more than three times it should be documented somewhere for others to reference
and you'll see that some of the communication points for the people you're sitting with cross over with
your project manager just like we've discussed before.
Now of course I trust you're smart enough to figure out when the things that you're communicating with
your teammates also need to be communicated with your project managers and seniors.
It's gonna be hard to put in any of these communication techniques with people on your team if you don't
actually have a job or aren't on a team yet.
So in the next video we'll look at what to do before you have a job.