About Me


I'm a Venezuelan interested in all things technology has to offer.

I'm a Salesforce certified Technical Architect and a TOGAF 9 certified enterprise architect.

With a degree of Computer Science engineering, this has been my career progression:
  • I started as a web developer, eCommerce mainly.
  • Then I progressed to developing bespoke CRM solutions with a stint in project management.
  • I then moved to Spain, working on Siebel as a developer
  • I changed my aim to Salesforce and have never looked back: from developer, Senior Developer, Technical Architect, Senior Technical Architect and now Head of Architecture!
Currently, I specialise in Salesforce.com and everything related to it, but I have a wider interest in all things computer science, especially on Cloud Technologies, DevOps and systems integration.

I'll be writing about all of this and probably some more! Oh, and all views are my own.

On the personal side, I'm a family man and the thing I love most in the world is spending time with my beautiful wife Katherine and daughter Valentina, not forgetting my dog Pichis!

I love travelling and eating (also reading, sports, TV and film!), so who knows, might be posting some things on that as well.

You can find me on twitter @ivanesalmeida

Comments

  1. Katherine2 August 2018 at 07:27

    We love you!!

    ReplyDelete
  2. Gaurav6 August 2018 at 21:24

    Read through all the posts so far! Great work and I hope you can keep up the pace in the weeks & months to come!

    ReplyDelete
  3. Unknown11 September 2018 at 03:31

    Good to find your thoughts and valuable knowledge laid in this blog Ivan. Thanks for sharing that with us all.

    ReplyDelete

Post a Comment

Popular posts from this blog

Salesforce and DevOps Part 1 - My views

Image
To get my blog up and running, I thought I'd start with a series regarding my current preferred topic: Salesforce and DevOps. Let's start with a couple of conversation topics (bear with me if you know them already, comment if you don't agree, feel free!): What is DevOps : you can find good definitions for DevOps all over the place ( this one , for example), so I'm not adding anything new here. The important part for me is that people know that it is a culture shift , it's a way of working, and it's not just the tech and tools involved! Who uses DevOps : well, everyone in a technology company should! It includes (as the word implies) Dev and Operations, but it's a bit broader than that, as it also includes testing, collaboration, monitoring, and so on. There is DevOps for everyone! Why use DevOps : the benefits are many! Faster time to market new features through automation Higher quality of deployments, as less defects move all the way to produ
Read more

Architecture principles for Salesforce implementations

Image
As an architect (Salesforce and Enterprise), one of my favourite things in the world are architecture principles. Principles define the foundation for the way your teams must work and the rules you want to have set in stone (they can't be broken without extensive and clear justification). They are mandatory, but they shouldn't be adversary, they need to be an agreement, a consensus that allows everyone involved to understand how things need to be done, and more importantly, why they need to be done. They have to believe it for the whole thing to work! I googled the definition of principle and this is what came out: "a fundamental truth or proposition that serves as the foundation for a system of belief or behaviour or for a chain of reasoning." I like that very much. I want to focus on the way principles serve as a foundation for a system of belief, behaviour or for a chain of reasoning. They are what you need to build upon, when creating teams of people, n
Read more

Salesforce and DevOps Part 3 - Development Lifecycle

Image
Now that you (hopefully) read my rants on my views and the tools involved in DevOps for Salesforce, I'm going to show how a common development lifecycle works in Salesforce today. I'm going to leave this slightly agnostic to the tools, focusing more on the steps for development and releases that in my view are needed for a common Salesforce implementation. This includes DX use, I'm going to mention it here and there, but won't go into detail in this post, as it will have a dedicated one next in the series. This post covers just a single org lifecycle, as you can extrapolate to as many orgs you need by applying a flow for each. This assumes that the orgs are completely independent and that there's a valid use case for that. For some good info on determining if your company or client needs one or multiple orgs, check this article , it can probably be a bit outdated on some details, but it's a very good starting point. Let's get to it, then. First of al
Read more