Skip to main content

Good Bye Adobe

The title says it all. Today was my last working day at Adobe and I've decided to pursue my career elsewhere. I've spent more than three and half years at Adobe, working as a part of the ColdFusion Engineering team. Over the last few years I've learnt a lot from the team, from the ColdFusion community and from many others at Adobe. I've developed interests in HTML5, JavaScript and other related technologies and frameworks and I've decided to pursue my interests.

I really like the developments that have been happening in HTML5 space and also in the JavaScript world. There are tonnes of frameworks built and client-side development is becoming more and more complicated. If you've been a regular reader of my blog, you would've noticed that I've been learning and experimenting with JavaScript frameworks. I want to explore the opportunities in this space and build services using these technologies.

Back when I joined the team in 2009, I heard of ColdFusion for the first time, when I was being interviewed at Adobe. I was grateful to Adobe for offering me a place in their immensely talented team. The team members were very welcoming and are always fun to be around with. I've enjoyed my time being with them in doing various technical and fun activities at work place. I'm sure I've interacted with each and everyone of them at some point or the other.

A few notes on ColdFusion:

ColdFusion is a kick ass platform and provides great set of services right out of box. When I started to learn ColdFusion I felt that I should have learnt it when I was in college, but unfortunately it was not included in the curriculum. It has come a long way and one should definitely explore what it has to offer today.

Every once in a while I do come across people (especially on the #ColdFusion twitter feed) who blabber about ColdFusion. These are mere nuisances, ColdFusion still continues to innovate and I can see people adopting it. Many complain that ColdFusion is not being marketed well and Adobe treats it as its step child. I disagree. Some of the team members are present in almost all ColdFusion conferences, the ColdFusion blog - is a great resource. And of course, there are e-seminars conducted every once in a while. There are some valid concerns and the team knows about it and I'm sure they are being worked upon.

Going forward: 

My next employer is as awesome as me :) I'll take a break for a few days and join this prospective employer sometime soon. I wish the ColdFusion team a very good luck with the next version of ColdFusion and I hope that they build something great.


  1. Hi Sagar: I know we've locked horns a bit in the past, but I've always thought you were one of the "good 'uns" on the CF team, and really seemed to know your stuff. So it's a shame - for us - that you're moving. However it's exciting stuff for you, so best of luck.

    One thing though... your mention of marketing. If Adobe think that marketing CF is best done by preaching to the converted - which is basically what you described - they I think everyone who has complained about Adobe's lack of direction and focus with ColdFusion marketing is basically right. You don't need to market it to us: we're already on board. You need to market it to everyone else. And I *don't* see a lot of that. Anyway: this wasn't your problem before, and sure isn't now, so leave that with the CF marketeers to mull over.

    Best of luck in your future, and thanks for all the work you put in to ColdFusion over the years. And thanks for putting up with me on the P/R programmes ;-)




  2. Good luck at your new employer! Thanks for all you did for ColdFusion.

  3. I'm really sorry to see you go, and thank you for all of your hard work with ColdFusion over the years. Best of luck in whatever you choose to do!

  4. Thanks for all your smart work for the ColdFusion and thanks for presenting at Chennai CFUG meetings as well.

    We are all going to miss you for sure and many congratulations on your New Job.

  5. Thanks Adam, I really appreciate your contribution in PR programmes. I'm sure the team will try to address some of the concerns around marketing ColdFusion.

  6. Thanks Akbar, I'm going to miss all that stuff.

  7. Hi Sagar, I agree with Adam. It has always been a pleasure to chat with you and get to the nitty gritty of the bug.

    All the best for your new role.

  8. Sagar, good luck with your next venture! And thanks for helping to make ColdFusion what it is.

  9. Hi Sagar, wish you all the best on your new journey, and thank you so much for all you've done to ColdFusion!

  10. Sagar, thanks for working on the product I know and love! I wish you the best in your future endeavors.

  11. Couple of days late seeing this. Best of luck for the future Sagar. It was awesome meeting you at SotR last year. The CF team have definitely lost a fantastic engineer.

  12. Thanks Andy, it was nice meeting you and many others at SOTR.


Post a Comment

Popular posts from this blog

De-obfuscating javascript code in Chrome Developer Tools

I had blogged about JavaScript debugging with Chrome Developer Tools  some time back, wherein I have explained how these developer tools can help in debugging javascript code. Today Google Chrome 12 was released and my Chrome browser was updated to this version. As with every release, there have been some improvements made on performance, usability etc,. One feature that stood out for me is the ability to De-obfuscate the javascript code. What is Minification? Minification is the process of removing unnecessary characters such as white spaces, comments, new lines from the source code. These otherwise would be added to make the code more readable. Minifying the source code helps in reducing the file size and thereby reducing the time taken to download the file. This is the reason why most of the popular javascript libraries such as jQuery are minified. A minified jQuery file is of 31 KB in size where as an uncompressed one is about 229 KB. Unfortunately, debugging minified javascript f

Adding beforeRender and afterRender functions to a Backbone View

I was working on a Backbone application that updated the DOM when a response was received from the server. In a Backbone View, the initialize method would perform some operations and then call the render method to update the view. This worked fine, however there was scenario where in I wanted to perform some tasks before and after rendering the view. This can be considered as firing an event before and after the function had completed its execution. I found a very simple way to do this with Underscore's wrap method.

On GraphQL and building an application using React Apollo

When I visualize building an application, I would think of using React and Redux on the front-end which talks to a set of RESTful services built with Node and Hapi (or Express). However, over a period of time, I've realized that this approach does not scale well when you add new features to the front-end. For example, consider a page that displays user information along with courses that a user has enrolled in. At a later point, you decide to add a section that displays popular book titles that one can view and purchase. If every entity is considered as a microservice then to get data from three different microservices would require three http  requests to be sent by the front-end app. The performance of the app would degrade with the increase in the number of http requests. I read about GraphQL and knew that it is an ideal way of building an app and I need not look forward to anything else. The GraphQL layer can be viewed as a facade which sits on top of your RESTful services o