Software Engineering 101

Failures

Hello, I am Alex

Self-taught

FullStack Engineer

 

Web Frontend Expert

 

I help programmers become better

Failures

Do not be afraid

2 steps

Step #1

Learn first how to cope with failures yourself

  • How do you feel about it?

  • How do you learn from it?

  • How do you fix the consequences?

Step #2

Learn from other people failures 

  • Networking!

  • Conferences, Meetups, Chat rooms

  • Case Studies

  • Share Failures!

Failure is the source of experience

Experience is the source of intuition

Success is a side effect

Survivorship Bias

You cannot escape it

Failures and Edge Cases 

are essential to our craft

Be responsible!

Respond to failures

Safety Nets / Plan B

Design for Failure

vs

Happy Path

Thanks!

@mr_mig_by

http://fse.guru

Take Aways

  1. How To Be a STAR Engineer

  2. 4 Steps To Be An Effective Engineer

  3. Spaced Repetitions

  4. Learn How To Learn

  5. Survivorship Bias

  6. Opportunistic Refactoring

  7. Working Effectively With Legacy Code

  8. Give it 5 minutes

  9. Facts and Figures on IT Projects

  10. Badass: Making Users Awesome

SE101: Failures

By Alexey Migutsky

SE101: Failures

  • 2,250

More from Alexey Migutsky