Leon Carlo Valencia - CEO & Co-Founder, ReaLearn

CEO & Co-Founder @ReaLearn

AICEdTechElectronics EngineerAWSC++JavaScriptPythonSystem ArchitectFounderDevOpsBackend DeveloperITStartup Founder

I've always learned technologies quickly throughout more than 2 decades of experience. It’s because I focus on first principles instead of any individual method. With this approach, I built many products ranging from developing API's using AWS AppSync to writing firmware in C. For the past 7 years, I've been providing technical advisory and leadership where the ability to grok technology became useful in making an impact. Five (5) of those have been with AWS, consulting for hundreds of startups in the Philippines. In the past 2 years though, a vast majority of the technical leadership has been directed towards AI. Now, I'm using all that experience to build ReaLearn, which aims to make learning fast and effective for everyone.

ClinkIT SolutionsLead Architect

Oct. 2018 - Sep. 2019NCR - National Capital Region, Philippines⁍ I architected Trampoline to be serverless, multi-tenant and fully event-driven. The resulting system was fast, elastic, and resilient. It's also loosely coupled which means fewer bugs and faster development. In fact, 1 front-end and 3 back-end engineers built the core of the platform and an iOS application on top within a month. ⁍ I researched and applied a lot of technologies quickly to achieve Trampoline's architecture. Though I'm also new to said technologies, I still mentored my colleagues about them. ⁍ I developed 60% of Trampoline's back end by the end of my stay. There were two factors to this level of contribution. First was writing code that's easy to reason about and hence faster to produce. Second was having fewer bugs which means more time developing features. Both were the effect of leveraging on serverless technologies. ‣ Roles: → lead technical architect → senior back-end engineer • Project Types: → cloud application → software as a service (SaaS) platform → API back end • Architecture: → serverless architecture → multi-tenant architecture → event-driven architecture (EDA) • Cloud Providers: → Amazon Web Services (AWS) • Designs: → system design → algorithm design → NoSQL database design → GraphQL API design • Processes: → git workflow → software deployment • Software Elements: → NoSQL → database as a service (DBaaS) → function as a service (FaaS) → GraphQL → cloud storage → identity & access management (IAM) → infrastructure as code (IaC) → application logging → high-level scheduler → publish/subscribe (pub/sub) messaging → push notification • Languages: → Typescript → Node.js • Frameworks: → Serverless Framework • Databases: → Amazon DynamoDB • Cloud Services: → AWS Lambda → AWS AppSync → Amazon S3 → Amazon Cognito → AWS Identity & Access Management (IAM) → Amazon Simple Notification Service (SNS) → Amazon CloudWatch → AWS CloudFormation • Tools: → Node Package Manager (npm) • Version Control: → Git

Feedback from Leon Carlo’s ex-colleagues