This is a demo repo for sharing ideas around communication
This is a gist example of my code
To have the ability to realise that you're not always right and that you might have a blindspot or a bias. To constantly look out to when you are wrong.
If you've done the research, gone through the problem, scientifically studied it, and you know that there's a specific solution but the majority of people don't believe it, you need to have the courage to fight for your reasoning.
Can you go into the mind of someone who is disagreeing with you and can see their viewpoint? With this you can come up with a compromise or direction where you both have a path forward.
Are you able to independantly come up with your own ideas or is somethign else making decisions for you? Can you self-reflect and come up with your own viewpoint?
Are you playing fairly or using tricks to deliberately misinform people to buy your viewpoint?
Do you have the ability to methodically go through why your solution is the best and go through and make sure that your solution will the implemented
Do you have the ability to have faith in scientific facts? To believe that reason will win?
Are you accepting compliments or criticisms in good faith?
Focusing on one skill/path isn't effective for your career. For job searching, a degree alone won't cut it. Having the qualification, a portfolio, and networking would be a triple threat.
- Sharing code that can be reproduced enchances conversation. Must run smoothly or else it can negate value. You can share code with gists / jupyter.
- Audio, video, and images to provide visual context
- Screensharing / casting to demonstrate and answer questions
- Produce once, reuse many
The most misunderstood aspects of teamwork is that talent is only one aspect of an effective team, and not the most important aspect. You also need:
- A clear, elevated goal
- Results driven structure, are people achieving goals and can you measure them?
- Competant team members
- Unified commitment
- Collaborative climate - if everyone is supportive and teamwork is rewarded then you'll have a collaborative climate. Management vs line worker or toxicity will ruin it.
- Standards of excellence - everyone agrees what 'good' IS, agree on thing that should be done and kept to
- External support and recognition
- Principled leadership - the leader has to have character and do things in a principled way
- Building a quarterly schedule that identifies what you might be building week-by-week. A technical plan of what you think will happen. Gets ideas flowing and makes you think about what you'll build
- Make a weekly demo to show progress and get things done. If you can't demo every week you're probably not going to meet your deadline
- Always be in a deployable state
- Automated testing, if it's not automated it's broken
- When breaking down tickets in a ticket system, think about things in a 4 hour to 3 day window
- Kanban lists of Todo / In Progress / Done, simple tracking for short term management
- Avoid hero driven development, who will swoop in at the end of the project to get things done
- Kaisen - make things better on a daily basis
Start with your list of Todos, maybe each is a ticket or an achieveable task in a project for a week.
Make a quaterly plan with 12 weeks and your key goals for the quarter. To aid in your kanban week-to-week.
Working overtime and nights and weekends is a failure in the system. Burn-out and quitting will follow.
Where work only gets done during a huge crisis. Solve why you're getting into the crisis rather than sticking to putting out fires all the time.
Highest Paid Person's Opinion. Where someone higher up comes in to change the plans. Their opinions need to come in the planning stages. There shouldn't be a daily or weekly randomisation. People shouldn't be pulled off certain parts randomly to work on other features.
It's easy to mimic what appears to be successful, but you can end up doing things that don't make sense. Too many meetings and charts instead of productivity. The lighter the process the better.
Don't just trust the person. People should be able to deliver incremental results. Hope is not a strategy.