"Stay Hungry, Stay Relevant"

Tips to be a sought-after Developer

Pesto.tech

"Taking opportunities to places where talent exists"

Why you should care?

"Work like someone is working 24 hours a day to take it all away from you."

- Mark Cuban

Time

A developer's most important asset

82.3 years

30,039.5 days

720,948 hours

43,256,880 minutes

2,595,412,800 seconds

30% done with life

30% you sleep

Tips to give yourself more time

Keyboard Shortcuts

• Estimated 2 seconds of productivity lost per minute when switching between a keyboard and mouse

• [2 wasted seconds / min] * [480 min / workday] * [240 workdays / year] = 64 wasted hours / year!
• 8 work days per year
• 3.3% loss of working productivity

Automation

• Time savings depend on the task and the complexity of the automation script

• A good rule of thumb: if you end up doing something repetitive 3 times, you should write a script for the 4th time.

Use Zapier to automate Workflows

Use Equipments

• The right machine
• Use Monitors
• External Keyboard
  • Average typing speed: 40 words per minute

  • Professional speed: 100 words per minute

Save up to 21 days per year.

Resources: bit.ly/pesto-equipments

Tips to give your team more time

Document Everything

• If some problem took you a long time to figure out, it will likely take the next person a long time to figure out.
• It takes you 4 hours to set up your development environment
• After finishing, it takes 15 minutes to add documentation to the readme making set up take only 15 minutes
• 3.75 hours saved per person
• 5 person team = 18.75 hours saved for a total cost of 15 min

Tools: Notion.so, Dropbox paper

Resource: Gitlab Handbook

Easy Handoffs

In the medical industry, sloppy handoffs lead to patient deaths.

• 64% of handoff errors are due to communication

Show Don't Tell

• Using videos and images to give your teammates more context can save everyone a ton of time. This is especially important in remote teams.

• Add before an after screenshots on UI pull-requests
• Add videos when replicating a bug

Tools: Loom, Dropbox, MonoSnap

Tool: Monosnap

Overcommunication: Make it easy

Emails

• Inbox 0
• Use Labels
• Set Expectations Straight 

Due to high workload, I am currently checking and responding to e-mail twice daily at 12:00pm and 4:00pm. 

Vs

"Due to high workload, I am currently checking and responding to e-mail twice daily at 12:00pm ET [or your time zone] and 4:00pm ET.

If it's urgent, please schedule a quick 15 min Zoom call at 9pm ET at this Calendly Link."

Save time for community

How many countless hours have these saved you?

git, linux, react, mongo, postgres, c, etc

Always Give back: Mentor Junior Developers, Work on Open source projects.

https://bit.ly/pesto-curriculum

Tools that make you superhuman

• RescueTime
• Notion.so
• useloom.com
• slack/workplace/basecamp
• Mixmax
• 1Password
• Zapier
• Marker.io
• Pocket
• MonoSnap
• Wunderlist

How to learn?

"Read 500 pages every day. That’s how knowledge works. It builds up, like compound interest. All of you can do it, but I guarantee not many of you will do it." — Warren Buffett

• You can go wide or you can go deep.
• Don't chase the next shiny thing. 
• Follow the relevant people.
• If you’re just off to becoming a professional developer, focus on the stuff that won’t change first.

Pro tips to be one of the best?

• Programming Deliberately vs Programming by Coincidence
• Read all of the docs, sometimes the source code
• Never commit code you can't explain
• Search your mind deliberately → Google → Github Issues → Post to stack overflow → Ask a co-worker
• Debugging Deliberately
• Don't fix it! Reproduce It!

Happy

Humble

Honest

Hungry

Facebook: aayushjaiswal07

Twitter: aayushjaiswal07

Medium: aayushjaiswal07

Instagram: aayushjaiswal07

ayush@pesto.tech

Feel free to get in touch :)