Pablo D.

Soft skills conflict resolution, negotiation, guidance, culture, knowledge sharing I’ve been assisting teams both as tech lead and as software architect for some years. I'm good at solving technical issues, helping teams to find agreements, motivating them and guiding them into technical excellence. I like to promote culture and knowledge and enforce the team to investigate and dive into the areas they feel more motivated with. Design and architecture Backend Architecture, Frontend Architecture, Microservices, Web3 I have wide experience with distributed architecture and design patterns both for Backend and frontend web solutions. I’ve also worked with web3 solutions and have 2+ years experience designing blockchain and smart contract solutions and integrations. My main area of expertise is with microservices architectures. Programming languages C, C++, Go, Javascript, Python, C#, PHP, GoLang, C#, Kotlin I started with C ANSI 20 years ago and since then I have used dozens of languages, sublanguages and metalanguages. The point is to know the machine, how memory works and how your language interacts with that all. There is where complexity lies, the rest is just syntax. I adapt fast. Frontend Technologies Javascript, ES6, React, Redux, Flux, Angular, Vue I’m used to architectures like MVC or CBA and data flow paradigms like Flux or FBP. I'm proficient with frameworks like React or Vue and have worked and built many others. I have a deep understanding of frontend technologies, browser engines and interpreters and have experience designing and implementing complex architectures. Backend Technologies NodeJS, ExpressJS, gRPC, SOA, Microservices, Microliths, DDD, Domain Event, Mongo, SQL, Redis, ElasticSearch, Neo4j, SNS/SQS I’m confident with distributed service oriented architectures being SOA Microliths or microservices. I use DDD so I'm used to design, implement and work with domain events, use cases, aggregates and the whole pack. I have experience with databases, both relational and documental along other more ‘case specific’ like redis or ElasticSearch. I feel confortable with queue systems and message oriented design patterns, mostly with rabbitMQ and SQS/SNS.