Wednesday, October 27, 2021 at 9:42:37 AM Pacific Daylight Time

Subject: Re: WebDevs Cookbook ini/a/ve

Date: Wednesday, October 27, 2021 at 9:05:03 AM Pacific Daylight Time
From: Lino Garcia Vallejo
To: Pablo Garcia, Shru/ Kapoor, Samira Allahverdiyeva, ScoP Mitchell, Chase Norton, Jus/n
Spears, Tahera Bodabhaiwala, Stan Carrico, Norm Ng, Mayank Arya
AHachments: image001.png

Good morning guys,

The WebDev Cookbook is now part of the skillXCHANGE ini/a/ve, launched globally just a few minutes ago.
It would be super awesome if you’re collaborate with your recipes:

hPps://bridge.paypalcorp.com/skillx/projects/76

Thank you

From: Lino Garcia Vallejo <lgarciavallejo@paypal.com>

Date: Tuesday, April 20, 2021 at 10:58 AM
To: Carlos Castro Felix <carlocastro@paypal.com>, Pablo Garcia Camou <pgarciacamou@paypal.com>,
Shru/ Kapoor <shrkapoor@paypal.com>, Samira Allahverdiyeva <sallahverdiyeva@paypal.com>, ScoP
Mitchell <sbmitchell@paypal.com>, Chase Norton <chasnorton@paypal.com>, Arseniy Kotov
<akotov@paypal.com>, Kruthi Venkatesh <kvenkatesh@paypal.com>, Jus/n Spears
<juspears@paypal.com>, Tahera Bodabhaiwala <tbodabhaiwala@paypal.com>, Stan Carrico
<scarrico@paypal.com>, Norm Ng <nong@paypal.com>, Mayank Arya <mayarya@paypal.com>
Subject: WebDevs Cookbook ini/a/ve

Hi everyone, my name is Lino Garcia and I’m currently part of the Consumer Financial Services WebDevs team.
with an eye toward developing an innovative community effort that fosters and promotes best practices, technical
improvements, consistency, and productivity I created the WebDev Cookbook repository. This cookbook is aimed to be a
collection of organized material into “recipes” conceptualized as simple practical problems along with a described solution
and a relatively short code sample. A recipe can be:
A programming task for frontend, or interaction with middleware/backend
Technique for CI
Pp-react components use case
Best practice and/or pattern applied
Infrastructure script
A testing strategy
And many others

The approach is about to go beyond the usual documentation, is focused on “living” code solutions (enriched with the right
enough documentation) that a user can just clone and play with them; currently the recipes are outcomes from our daily
work at CFS and philosophy of continuous learning and improvement.

A use case scenario for the cookbook might be: As a developer, you are assigned to work on a story that requires some
expertise in a certain topic or component. So, as a first option you look in the cookbook and perhaps someone else has
already made a contribution along the same lines as what you need; if so, this could hugely speed up your design and
development process. But it doesn’t end there: because you started working based on an existing recipe, you realize that it
can be improved, create a new recipe based on that and push it to the repo. And just like that, you would already be
contributing to the cookbook and the continuous improvement process.

All that said, my email is not just to share with you about the initiative but invite them to join it and together

Page 1 of 2
we can expand it across PayPal. I think there’s a lot of room for improvements, opportunities and
integrations, just like the one proposed by Shaun Warman about to link the cookbook with
https://go/webdocs .
Go through the README file for more details on how this initiative currently works and I really hope you find it useful (and
much better if you start contributing ).

Also, you can review the repo’s Wiki our contributions so far. It’s also worthy to let you know guys that we already are
making mini demos of each dev’s contribution in our biweekly WebDev Catch Up meetings, and we’re also working in
partnership with the Giving Platform Team.

What do you think guys? Do you want me to help to make broader adoption and impact across PayPal?

Thanks

Page 2 of 2