How to identify efforts that make a big impact when building software products

Nov. 3, 2016

Spend time to watch the video:
How to Identify Efforts that Make a Big Impact When Building Software Products

https://www.youtube.com/watch?v=NZA6TkCP3yo

Topics in the talk:

1. Writing about engineering topic
2. Sit down and write 1000 words a day
3. Strategies in the book:

    Big impacts and values added  

    How it works -> Why it should work -> Ask questions about 70/80 hours/ week best strategies?

    Ask a few of questions:
    1. Decrease time to complete the task
    2. Can I come out agenda before the meeting -> avoid the meeting entirely
    3. Build a culture of the team -
    for example, address the performance as a feature, at the very beginning
    Process and tools
 
    Do something more than twice, think about automating it.

    Question: Push forward and iterate through vs doing too many things for a project
    Answer:
 
    2 high leverages: onboarding and new hire training
    2000 hours/ year for a full time, 40hrs/ week
    20 hours - one hour a day for a month - 1%
    How culture works?
    Justify the observation of first day, first a few days
    Small document, add on it - more tutorial, more documents, overtime, it builds up.

    Core structures - 10 on-boarding talks
    Best practice, quality standards

     Option #2: work on adjacent skills
     For example, front-end engineer, learn some project management skills

More videos:
1.     https://www.youtube.com/watch?v=BQVg-vxiKw8

2. "Make Better Software: The Training Series" Trailer
https://www.youtube.com/watch?v=Pj4PaXoURWc