About Samir

This author has not yet filled in any details.
So far Samir has created 23 blog entries.
5 Apr 2018

URL Decode formula for Excel

2018-04-17T11:28:11-07:00April 5th, 2018|Microsoft Excel|Comments Off on URL Decode formula for Excel

Excel provides a EncodeURL() function to encode URLs, but surprisingly does not provide any function to decode a URL (e.g., DecodeURL or UnencodeURL).  Instead, you can use the following formula:

=SUBSTITUTE(SUBSTITUTE(SUBSTITUTE(SUBSTITUTE(SUBSTITUTE(SUBSTITUTE(SUBSTITUTE(SUBSTITUTE(SUBSTITUTE(SUBSTITUTE(SUBSTITUTE(CELL_CONTAINING_ENCODEDURL,"%3F","?"),"%20"," "),"%25", "%"),"%26","&"),"%3D","="),"%7B","{"),"%7D","}"),"%5B","["),"%5D","]"),"%3A",":"),"%22","""")

Replace CELL_CONTAINING_ENCODEDURL with cell address containing the encoded URL.

Please let me know if I’ve missed any codes and I’ll update the formula.

Thanks to Christi Olson for providing basis of the formula.  I completed it with some missing pieces.
28 Nov 2017

Why You Should Choose Photographers Who Will Provide RAW Images

2018-12-03T19:55:43-07:00November 28th, 2017|Photography|Comments Off on Why You Should Choose Photographers Who Will Provide RAW Images

I’m an advanced hobby photographer.  I take lots of photos of my family, but alas, am rarely in any myself.  Occasionally, I’d like to hire a professional photographer to take family photos.  But I don’t need them to edit the photos because I’m experienced at editing.  In fact, because photos are such valuable personal memories, I’ll spend more time and effort editing photos of my family than any pro photographer would find cost effective.  But to edit quality photos properly, you should start with original RAW images.  These are like having the negatives back in film days.

However, I’m baffled how many professional photographers refuse to provide the RAW images.  They usually simply reply to my request with, “This is not something I offer”, or “It’s not my policy.”  Back in film days, it was common to withhold negatives because it forced the client to come back to the photographer for more prints, off of which they made profit.

But with digital images, prints are not always the objective, and you can still print as many copies from a high res JPG file.  So why do some photographers refuse to provide RAW images?

Here’re some of the arguments I’ve heard:

“The final deliverable is my work of art.”

Ok, I get that.  Obviously, it’s less work and cheaper to not have to edit; but if you want to include edits, then do so, and include that in your price quote.  The client can still edit your edited JPG, which will most likely look worse (e.g., grainier) than editing the original.  Plus, the client is better equipped to pick meaningful photos — e.g., maybe the expression of child in one photo is meaningful to the client, but not to the photographer who throws it away in preference of a slightly better exposed alternative.

“I have to protect my brand.”

There are plenty of ways to still protect your brand without withholding RAW files.  For example, you could make it conditional that the photographer be credited only for the photos that s/he has edited.  Or perhaps require approval of an edited photo before using the photographer’s name.   These conditions can easily be explained and required in the commercial agreement.

Besides, again, the client can always edit a JPG file, which will probably look worse than editing a RAW file anyway.

“RAW images are bad.”

Most people do not want RAW images; they wouldn’t even know what to do with them.  Anyone who is asking for RAW images knows how to edit them and is experienced enough to know that exposure tests are taken, that sometimes someone’s eyes are closed, a stranger walks through the background.

And some clients may rather spend the time Photoshopping out a background stranger in order to keep the familiar child’s expression available only in that one image.  The client will be far more satisfied with that more meaningful image anyway.

“It’s like paying a painter for their canvas.”

I really don’t understand this argument.  When you purchase a painting, the canvas is included.  Perhaps they mean purchasing a print, and that’s really the difference.  Some photographers are just selling you (digital) “prints”.  But that doesn’t add up.  Buying a print of a painting costs a fraction of the original.  Thus, if a pro photographer is already charging $hundreds an hour just for prints, then that implies it would cost $thousands per hour to get their RAWs.  Are they really worth $millions per year?

Another analogy: When you hire a programmer to write a program for you, you almost invariably own the source code, which you can then modify, license, do with whatever you’d like.  Even programmers do not charge $thousands per hour.

“It’s not as impressive as giving them post processed photos.”

Fine.  Then provide both.  If your value is so great in post-processing, then it’ll be even more evident by providing the original and hard to reproduce.  I’ve shot literally with world-renown National Geographic cover photographers.  I find that the top photographers believe that the best images are captured well in the first place; they try to rely as little as possible on post-processing.

“The client may use the meta info to hire cheaper photographer.”

The argument is here is that the client might use the meta settings to learn the exposure and equipment settings the photographer used, and then hire a cheaper photographer to recreate the same photos.  First, this is impossible for any event shooting that can only happen once (e.g., weddings) and impractical for most family shoots, etc.  Who’s going to recreate a wedding or family get together?  Second, if the photos are so easily recreated from the same settings, then how much value is that photographer adding?  Good photography is much more than settings and equipment.

“Clients pay the photographer to pick out the best.”

Sure, some may, but I bet those aren’t the folks asking for RAW files.   The reality is that these photos will matter way more to client than the photographer, so the client is more likely to put greater time into selecting and editing photos, and is more likely to find a gem hidden in the rough (that the photographer might not appreciate – like a familiar child’s expression).  Why limit their choice and limit their editing with JPGs if that’s not what they want?

 

Perhaps the real reason is under the surface, and not stated.  For example, I suspect these photographers don’t want the client to see their “mistakes”.   But I suspect anyone who asks for RAW images is experienced enough to know everyone, even the best, take some shots that need straightening, cropping, or exposure correction.  In other words, asking for the RAW images is probably self-selection enough.

Besides, photographers, if the client really wants to edit your work, they will.  Withholding RAWs doesn’t really inhibit them much.  All it does is ensures they’ll have even worse results because they’re limited to editing JPGs.

Unfortunately, RAW pushback excuses come across as red herrings and look like the photographer wants to lock you into coming back to them for additional business.  It seems too photographer-centric.  E.g., What if the photographer goes out of business or my great-great-grandkids want to edit the images with advanced tools of the future?  Business has taught me that successful businesses focus on clients first.

If you don’t know what to do with RAW images or why you’d want them, don’t ask for them.  However, if you do, the good news is that you can find photographers that provide RAW images, but you may have to dig a little.  If you want the RAW original images and need no editing by the photographer, just ask for “Shoot & Burn,” and get agreement up front before the shoot.  I find that the really skilled photographers, who can capture images well in the camera with little need for post processing, have no problem providing RAW images.  These are the photographers you probably want to use anyway.  So maybe asking for RAW images works well for self-selection the other way too.

14 May 2017

6 Document Collaboration Methods…Compared

2018-04-17T11:22:54-07:00May 14th, 2017|Collaboration, Email, Knowledge Management|Comments Off on 6 Document Collaboration Methods…Compared

Do you collaborate on documents with co-workers? I.e., do you edit the same doc or file (I use “docs” and “files” interchangeably herein) with one or more people sometimes?

Duh, who doesn’t, right?

Unless your company has strict policies, you probably have some options on how you share documents. You could use browser-based apps like Google Docs or Microsoft OfficeOnline. Or you could email file attachments around.

(I can’t believe I’m still writing about email file attachments for doc collab; but alas, status quo is hard to change.)

Different users have different preferences and different needs. Some are power spreadsheet users. Some don’t need every word processing bell and whistle. Some are always online when they work. Some travel. Even each individual user may even have different needs at different times.

Unfortunately, though, there’s no perfect way to collaborate on docs (yet), so I attempt herein to qualitatively (as objectively as I can) compare the six main ways you can edit a doc and share it with others to review and/or edit. You may use one method primarily, or you may use different methods depending on your current situation. Hopefully, this will help ensure you know your options and the impact to you and others.

Doc Collab Methods

First, let’s look at the 6 primary doc collaboration methods. The typical scenarios include desktop productivity apps (e.g., word processing, spreadsheets, presentations via Google Docs or Microsoft Office) and cloud storage providers (e.g., Box, Dropbox, Google Drive, Microsoft Onedrive). But these concepts can apply more broadly to most apps and cloud storage.

Considerations

Next, let’s look at the main trade-offs when considering each collaboration method.

6 Collaborative Document Editing Methods

Bottom Line

Unfortunately, there’s no perfect solution for all people in all situations.

If you don’t need the advanced capabilities available in the desktop app, and you don’t need the ability to edit offline, using the Web App version is usually a great solution.  Keep in mind, however, the context of “you.”  For example, and individual may only use 20% of a mature application’s (e.g., MS Excel) capabilities, but if different individuals use different 20%s, then the organization may need to enable the choice of using the desktop application.

Email is clearly not optimal for document collaboration or co-editing.  However, it’s probably still the most common method.  This has to do with many factors including status quo (effort to change habits), flexible enough to cover every edge use case, possibly slightly easier for the individual at greater expense to the group (a topic for behavioral economics).

Selection of other methods that allow use of desktop app still requires consideration of the situation.  If it’s unlikely that lots of edits to the same doc will happen at the same time, and the overall storage requirements are not large, then automatic sync is easy and convenient.  However, in many organizations, the doc library can get too big to store on everyone’s PC (not to mention security concerns), so auto sync (without elaborate selective sync efforts) may be impractical.

I did not get into security here, as there are lots of variables.  For example, editing a doc from a public kiosk is always risky, and each editing method has its own risks.  Obviously, any time you’re storing a local copy of a file, there’s a possibility that someone else may get to it.  Even the auto upload options inevitably are saving at least a temporary local copy of the file; who knows if proper housecleaning is being done.  And even browser apps cache data locally, so beware of editing docs on insecure PCs.

The good news is there are better doc collaboration options than email.  The bad news is there’s no perfect solution.  It’s easy to stick with the status quo, but if they really thought about the costs to team productivity or of making bad decisions, more teams and companies would proactively move to non-email doc collaboration alternatives as quickly as possible.

10 Sep 2015

Collaboration – 3 Steps for selecting the right tools

2018-04-17T11:23:40-07:00September 10th, 2015|Collaboration|Comments Off on Collaboration – 3 Steps for selecting the right tools

I often get asked for recommendations for team collaboration tools.  The advice I give seems overly simplistic to me, but since I get enough compliments about it, I’ll share it here.

I could expound ad nausea on this topic, but I’ll attempt to be brief and offer 3 key steps in selecting a tool or tools:

There’s a plethora of options, most of which overlap (but few play well together), which unfortunately makes things more complicated.

3 Steps to Selecting Collaboration Tools

Objectives

First, determine what problem(s) you’re trying to solve.  Do you want to improve communications between engineering and marketing?  Perhaps you need a better way for new employees to find internal answers more quickly.  Or maybe you need better ways to communicate across geographies and time zones, but everyone’s email is overflowing.

Put Stakes in the Ground

Next, think of the givens that you can’t change.  For example, perhaps your company management uses PowerPoint religiously for presentations and finance folks use Excel.  If the engineers use Google docs, then you may have to think about whether you need to use both, or which constituents could more easily switch over.  The choice of desktop productivity tools could have a real impact on what collaboration tools you use.  And if knowledge management is a goal, consolidating formats and repositories will make it easier to build an knowledge repository.

Take Small Steps

Then, take small steps.  Don’t rush out and sign-up for a whole bunch of tools because you think you’ll need one in each category.  For example, if you solve doc collaboration, then you may find it better to use a shared spreadsheet for task management than a dedicated and unintegrated point solution.

Then, you can start to narrow down choices. They all have pros & cons, and everyone will have subjective preferences.

For example, at WaveMaker, we needed to solve geo and time zone spread of team and we use MS Office for most of our docs. Thus, we went with Yammer (as better tool than email) but it’s weak for doc collaboration, so we also use online SharePoint (because MS Office doc collab is key and Yammer is now owned by Microsoft, even though still poorly integrated). We use Salesforce.com for CRM, but found Chatter also lacking at doc collab, which was more important to us than CRM integration.

And when you move to a cloud storage solution, here’s a comparison of main methods for cloud doc collaboration.

10 Sep 2015

10 Reasons Why You Should Not Upgrade To Windows 10

2018-04-17T11:23:49-07:00September 10th, 2015|New Technology|Comments Off on 10 Reasons Why You Should Not Upgrade To Windows 10

After upgrading to Windows 10, I discovered a bunch of shortcomings…

10. OneDrive placeholders no longer supported.  What?  How do you now use that 1 TB cloud storage you planned on using as virtual storage for your MS Surface?

9. Search in Windows 10 Start is slower

8. Battery system tray icon no longer lets you switch power plans.  It’s now embedded several clicks in the UI.

7. All of a sudden, my monitor overscanning stopped working.

6. If you set OneDrive to not start upon Windows 10 startup, good luck figuring out how to start OneDrive manually (hint: look for OneDrive.exe in Programs)

5. Edge is Win 10’s new browser, but it doesn’t support all SharePoint capabilities like “Open with Explorer”, and guess what…you can’t install another IE version (clever IE download site confirms you already have the latest version)!

4. OneDrive folder selection won’t let you proceed unless it thinks you have enough free disk space, even though existing disk space is used by previously-synced OneDrive files.

3. Media Center is gone from Windows 10.  No longer available.

2. Mounted VHD in Windows 10 keeps randomly unmounting (worked for years with Win 7 – 8.1), and then OneDrive cannot complete synching if the mounted drive is not available long enough.

 

And the #1 reason why I should not have upgraded to Windows 10 is….

1. Where’s the benefit?  I see zero advantages over Windows 8.1, only regression.

 

The good news (if you upgraded) is that you do have 30 days to revert back to previous version of Windows (7-8.1).  Click on Start > Settings > Update & Security > Recovery > Go back to Windows xx.

9 Mar 2015

Docker Adoption in the Enterprise

2017-05-16T17:19:42-07:00March 9th, 2015|Continuous Delivery, DevOps, Docker, PaaS|Comments Off on Docker Adoption in the Enterprise

Docker is hot!

Docker was the #2 “best overall open source cloud project” according to a survey by The Linux Foundation and The New Stack in July 2014.  Google Trends sheds some light, though, on the relatively new entrance and rapid acceleration of Docker versus OpenStack and “Virtualization”.

Docker trends

Google Trends - March 5, 2015

So, why is Docker so hot?

Software used to have a major delivery drag – it had to be delivered on some physical medium like tape, disk or download and then installed. Since software could only be consumed so quickly, the impetus of independent software vendors (ISVs) to build and deliver new software was perhaps at an annual or semi-annual basis. SaaS has changed all of that. Now, there’s no reason why a bug cannot be fixed and delivered…instantly, or at least as “fast as possible.”

Web scale SaaS companies (a la Facebook, Netflix, and a big slew of smaller SaaS companies) have been striving to optimize their software release stream to do just that. These modern ISVs have given rise to “DevOps” teams that focus on this task of “Continuous Delivery”. This has given rise to scripting technologies like Puppet and Chef for automating release cycles.

The problem with these approaches is they are still prone to error. Creating a test environment via scripts is not 100% guaranteed to build an exact replica of the development environment, for example. So when QA finds a bug that is not reproducible in the development environment, valuable time is wasted determining if the bug is in the software or the environments.

Docker changes this paradigm. Instead of pulling your hair out to recreate “identical” environments, Docker gets much closer to actually just moving the actual environment around. This eliminates the errors due to release environment differences and the need to build and maintain lots of complex scripts.

Docker provides additional benefits to SaaS ISVs as well. Docker is very light weight, and fast, which makes it easy to scale, resource efficient, and for new cloud ISVs that may not be invested in technology like VMware, Docker providers many of the classic benefits of virtualization.

Enterprises need Docker too

Understandably, large scale SaaS ISVs lead the way in innovation, including Docker implementation. Enterprise developers learn from these best practices and are starting to adopt Docker. Enterprises, too, benefit from the speed and efficiency of continuous delivery (CD), especially those enterprises building customer-facing scaled SaaS applications. But there’s an even larger number of internal applications that perhaps don’t need the daily updates, but certainly need greater efficiency delivered by Docker on internal teams with limited resources.

What enterprise IT may not realize is that if they do not provide Docker for their developers, their developers have numerous external choices now for public hosted Docker services. In many cases, IT does not want their apps, workloads and data running on unsanctioned services, and the real problem is they probably won’t know it’s happening until well after the fact.

Forward thinking IT are providing Docker for their developers, and those furthest along are discovering additional benefits of Docker ranging from lower costs via greater resource utilization or reduced VMware licensing costs to workload portability for moving apps to/from public and private cloud infrastructures.

But it ain’t quite that simple

But what enterprise IT departments are also realizing is that Docker is not so simple to implement, especially given the unique needs of an enterprise. Docker is not an out of the box solution. To implement Docker, you must not only manage containers and orchestration, but ensure resource isolation and access control for security; streamline diverse stack support and upgrades; optimize data snapshotting, backups and recovery; implement monitoring at machine, instance, container and workload levels; and integrate with existing systems like LDAP or Active Directory.

SaaS ISVs need to scale a single application, on a single app stack, on a single infrastructure, and they have engineering resources dedicated to implementing Docker and all requisite components. Enterprises, on the other hand, have diverse workloads, varied app stacks, heterogeneous infrastructures, limited resources, and additional needs for security, control, visibility, governance and compliance, so implementing all of the Docker related technologies for these permutations can be daunting.

That’s were PaaS comes in. A Docker-optimized PaaS for enterprise should take care of implementing Docker and required components, while meeting additional needs like role based access control based on existing IDM with visibility and monitoring. A well designed PaaS will also leverage the unique advantages of Docker to deliver features like idle workload hibernation for further infrastructure cost savings.

Docker is young in the timeline of enterprise technology, but we’ve rarely seen one grow and rise so quickly. Enterprises will lag slightly behind SaaS ISVs in Docker adoption, but the smart IT organizations will not only provide Docker to their developers before they wander elsewhere, but will also discover the other powerful advantages of Docker unique to enterprises without spending an arm and a leg.

10 Sep 2014

Apple “iWatch”

2018-04-17T11:23:59-07:00September 10th, 2014|New Technology|Comments Off on Apple “iWatch”


It’s hard to know with what to be more impressed — the watch, the technology, the design, the demo video, even the product videography that went into the video is amazing.  Apple still has it after Jobs — albeit, clearly, this product has been in development for years.  What I find myself wondering, is how many things will this disrupt?  I cringe for watchmakers (which have taken a beating from smartphones already) and fitness specialty watches.   Will this cannibalize, a bit, even smart phone usage?  With payment, what will I do with my Coin, which I haven’t even received yet, let alone the phone payment options?  Although…you still need an iPhone to use this iWatch.  “Unfortunately”, I have an Android device, so I find myself wondering, who will/could develop a device even close this cool?  Samsung?  HTC?  Well, maybe some cobbled subset given enough time.  Until then, I live with my Ironman and Tissot trusted timepieces, (who uses those anymore?)   The “iWatch” looks pretty cool, but I did buy an Apple Newton back in the 90’s.  We’ll see.

10 Sep 2014

Webcast: Docker aPaaS for Enterprise Innovation: Are You Ready?

2018-04-17T11:24:07-07:00September 10th, 2014|DevOps, Docker|Comments Off on Webcast: Docker aPaaS for Enterprise Innovation: Are You Ready?

 

Docker aPaaS for Enterprise Innovation Here’s a link to the webcast I did on BrightTalk this morning.  Docker is hot. APIs are ubiquitous. aPaaS is finally gaining momentum. And Enterprises are facing increasing business challenges and complexity. How can these trends and technologies help? How does RAADD (Rapid API Application Development and Deployment) foster innovation and agility? How does Docker and Containerization really help optimize app workloads? Find out with Samir Ghosh, CEO of WaveMaker, as he gives you the end-to-end view of Docker aPaaS and talks about steps companies can take to effectively prepare for and leverage these trends and technologies.  I hope you’ll give it a high rating on BrightTalk if you like it.  Thanks!

 

Go to Top