Web developer playing with clouds, LAMP, Symfony, JavaScript. Currently working as a Salesforce developer as part of the Taylor & Hart team.
Kik Minev
01.

Hey there, I'm Kik Minev - web developer playing with clouds, LAMP, Symfony, JavaScript, Salesforce Apex. Currently working as a Salesforce developer as part of the Taylor & Hart team.

Why Salesforce? Pivoted to Salesforce when my colleagues needed a quick and efficient way to optimize business processes, sales and even manufacturing processes. That’s how I stepped into the Salesforce world, though most of my career has been focused on web with PHP. Strong love for the Symfony framework.

02.

My experience

Taylor & Hart - Salesforce and Symfony developer

Currently working as a Salesforce developer at Taylor & Hart where I help with accelerating buesiness processes in sales and manufacturing. I spend my day mostly writing Apex code and lightning components in Salesforce or PHP/Symfony for web features.

Oxxy - CTO

As part of Oxxy I was leading the team as a CTO. We started and shipped a drag and drop website builder that allows small business owners to launch a website without any coding skills. For my tasks I used the Symfony PHP framework, MongoDB, javascript for the web builder and AWS as an ifrastructure.

Webfactory - Web Developer

At Webfactory I spent my days mostly coding with PHP and Javascript. As part of a web agency I worked on various projects for different clients up until I started working on Protect Your Bubble. Really thankful to the colleagues that gave me the chance to work on this project and helped me develop my skills.

Webfactory / Protect Your Bubble - Team Lead

I became responsible for launching the US web site and lead a team of web developers to deliver and support the project. Duties were a bit different as I needed to work in Atlanta and lead the team overseas. Also, working with a Fortune 500 company has it's perks. Thank you all for the warm welcome in Atlanta!

Digitalus - Web Developer

Digitalus was a hosting company from The Netherlands(later aquired by another company). Here we worked with PHP and Javascript.

SiteGround

Epic times! Great start in the web industry.

03.

What I work with?

Back in the days I started coding websites from scratch using PHP and some custom frameworks. Throughout time I worked with ancient frameworks like CakePHP, Zend and others. Nowadays I mostly work with Symfony. Trying to keep an eye on the Javascript world as well.

PHP
Back in time I started with PHP from around version 4. Usually with Apache and MySQL. These days we run mostly nginx.
JavaScript
The beginings was vanilla and jQuery. Later I worked with Backbone and Angular. Now I try to keep in touch mostly with the React framework.
Symfony
I love how robost Symfony is. The initial steep learning curve is paying off with the projects. During the years I've worked with Symfony for SaaS products, CMS and eCommerce systems.
AWS
My experience with the cloud is in AWS where I mostly use EC2 and S3. I also have some experience with RDS for PostgreSQL. During the years I used EC2 to scale Symfony web projects and MongoDB cluster databases.
Git
Git is what I use for version control. Checkout my GitHub. I use Gitflow in my day to day work.
Docker
For personnal projects I will use Docker to maintain my developement environment. In some companies we also worked remotely, in the cloud. In other companies even with k9s on localhost. Depends on the company;)
Salesforce Apex
In Salesforce I usually work with Apex code to develop new features. It shares the Java syntax and object-oriented features, but it's limited by the Salesforce environment.
Ligning Components
Not very often I develop lighning components to extend the Salesforce functionality.
PhpStorm
Though I started with Notepad, moved to Notepad++, Vim, Eclipse, these days I work with PhpStorm and IntelliJ with Illuninated Cloud for Salesforce development.
↑ About me

Kik Minev

L A T E S T   P O S T S

Building a Twilio call center in Salesforce. Part 1: General overview, tools and architecture

Recently I was given the opportunity to build a call center for incoming and outgoing calls that works from inside Salesforce. The benefit of such a call center integrated into Salesforce is that the sales people will have the customer data immediately available with the incoming phone call or make an outgoing phone call directly from the customer record. I’m going to share a few words about the architecture and the problems I stumbled upon when building this. Just for the record, Salesforce provides plenty of ready made VoIP solutions that you can easily install and start using out of the box. Those solutions are not cheap, but still they are ready to use and require no development time. Still, if you want to  automate business processes and have custom actions into the callcenter it’s easier to rely on a custom solution.

To paint the picture I’m going to provide details about used technologies and general architecture:

1. The phone infrastructure is handled by Twilio – easy to learn and well documented. It allows you to build VoIP telephone systems programatically, using Node.JS. In short, if you want to handle phone calls via the browser you can develop custom made call center yourself. Furthermore it provides SMS infrastructure if you want to automate SMS notifications as well. The idea behind Twilio is that it provides an API which allows you to start/end phone calls and you can build on top of this API whatever comes into your mind related to a phone system.  So far it works great and it’s really stable.

2. Salesforce Callcenter – Salesforce service called “Callcenter” allows you to integrate telephony systems directly inside the Salesforce UI. With simple words, it gives you a set of tools that will allow you to build a phone UI and show it to your users in Salesforce. You can configure the callcenter to be accessible through a small window in each Opportunity record and consultants will be able to call prospective clients from the client information tab itself. This feature is available for all kind of records, not only the opportunity view.

3. Javascript – when developing the telephony system you will mostly work with Javascript inside the Salesforce environment. With it you will need to build the phone UI itself(phone keyboard, accepting incoming calls, making outgoing calls etc). Apart from building the dynamic UI you will also use it to communicate with the backend of Salesforce.

4. Apex Code – this will be the backend tool which you will use when developing in the Salesforce environment. It will be used to fetch data from the Salesforce database, make external and handling incoming API calls to Twilio. Apart from communicating with the external Twilio environment you will need it to send events to the javascript softphone that you will build in Salresforce.

4. Node.Js – you will need Node.Js to build your telephony system in the Twilio environment.

 

Part 2 will explain the problems I struggled upon when using the Salesforce Callcenter.

Part 3 will shed some light on how Twilio functions work and how they allow you to program voice communication channels.

 

Leave a Reply

Your email address will not be published. Required fields are marked *