Refund Policy for Payoneer

Payoneer has recently started asking for a Refund Policy if you want to continue receiving money from clients using their platform. Here’s the refund policy I follow:

  • The entire amount will be refunded if I can’t manage schedules after accepting a project.
  • I accept payment by milestones, there will be no refund for milestones completed (as agreed by the client).
  • If I can not finish the project within deadline, the client can ask for refund of the current milestone and they can end the contract

Top 500 StackOverflow contributors from Bangladesh

Update: The result returned from the StackExchange is slightly outdated. So it might not display the latest reputation or other profile changes and thus slightly affecting the ranking.

Update: Because the large list was affecting the site performance, I have moved it to Github Gist.

This post uses the StackExchange Data Explorer to query the StackOverflow users and grab their data. The Python script to query and parse the data is attached below the ranking. So let’s wait no further and meet the top 500 people on SO from Bangladesh:


Managing Golang Workspace: My ZSH Configuration

One of the first thing beginners wonder in the Go userland is how to organize a project. Go expects to have a global workspace. A go workspace contains 3 directories: “src”, “pkg” and “bin”. The src directory contains the source codes for all your projects and their dependencies. When you try to import a package, go compiler will try to locate it under this “src” directory. The “pkg” directory is used to build cross OS packages out of your source code. Yes, you can build single compiled binaries for other platforms directly from your current OS. That is one of the awesome features of Golang. Finally, the “bin” directory holds all the executable binaries. When you’re building a command line app or trying to install one from 3rd parties using the “go install” command, the binary is placed in here. I have the central Go Workspace in ~/Projects/golang.

Go expects the path of the go workspace as the $GOPATH environment variable. So I added this to my ZSH profile:

My $GOPATH is set to ~/Projects/golang:

Now that we have a workspace, how do we lay out individual projects? We can choose any structure we like. As long as Go can find required packages in the workspace’s src directory tree, it will be okay. However, since we all love to push our codes to some code hosting service, we will try to match our project structure with our VCS url structure. How? Well, first, we know that Go has a fantastic tool – “go get” – it can download source codes from an array of VCS and install them for us. How does it work? When I type: “go get”, it understands that it’s a git project. It would create the reflecting directory structure inside the “src” directory of the workspace so that we can import the project as “import” in our local projects. So it’s better if we keep our own projects in a similar pattern whether we publish them or not in the future.

I created a directory named “” under “src” and then created “masnun” under that. Now my projects would reside in: ~/Projects/golang/src/ directory. My newly created project path would be something like: ~/Projects/golang/src/ I can now treat ~/Projects/golang/src/ directory as my personal workspace. So, I added these to my .zshrc for convenience:

After I have this mirrored up, I can actually do:

Then I added a handy alias to emulate Python’s virtualenvwrapper’s “workon” command:

So I can now just do:

I also added the ~/Projects/golang/bin (aka $GOPATH/bin) to my system path so that I can use the commands installed from “go install” or “go get”.

How do you organize your Go projects? What tools/techniques do you use in day to day Golang hacking?

Copying (duplicating) MongoDB Documents (Rows)

The use case is simple – I have one row (I mean document). I need to make multiple copies of it. Say, I am building a blog app and I need to quickly generate a few posts on the database. Scripting is one way to do it, but if I need to do this only once, automation is a waste of time.

Thanks to mongodb’s shell and JS-like APIs. This is actually simple.

Connect to mongodb:

Select the database:

Find an entry on the “posts” collection:

Now let’s change the “_id”:

X is now a whole new object/document (since we changed the “_id”). We can alter other fields as well. Let’s store it:

You just copied one document into a new document. Cool?

The command line mongo client has readline and history support. So you can actually use the up arrow to repeat the commands quite easily.

Vim Madness

I use the top notch IDEs for development but that is not geeky enough. So, ignoring my previous failed attempts, I am going to give the text editor one more try. Apparently, this blog post would be more like self documentation, mostly notes and hints to self. If anyone else also gets benefited, that’d be an added bonus.

Quick Shortcuts

  • Vundle Bundle Installation: “:BundleInstall”
  • New Tab: “:tabnew
  • Navigate Tabs: “:tabn” for next, “:tabp” for prev. “gt” in normal mode
  • Switch Windows: “Ctrl + w, Ctrl+w”
  • Splitting Windows: “:split “, “vsplit” for vertical splits
  • NerdTree – Open in new tab: “t”

Let there be ~/.vimrc

OK, here’s my ~/.vimrc, the initial version is messy, not organized at all, everything I came across, I stuffed in here. I shall update and clean the vimrc over time.

Go: Creating new types based on built-in types

Ever needed a custom string type to add your own methods or tweak certain behavior? In languages like Ruby or Javascript, you can directly modify built in types. In other languages, we usually create custom objects to wrap around a default type and then extend that object with necessary methods or attributes.

A sample example in Python would look like:

In Go, we would define a new type based on an existing type. Then define methods on the newly defined type. It allows us to easily create new types based on existing types and then customize to suit our needs. The same example in Go would look like:

Simple, isn’t it?

Goroutines: Threading made easy!

This post is dedicated to the awesome concept of “Goroutines” in Go. A “Goroutine” (Go Routine?) is a lightweight thread implementation that executes asynchronously with the main process. To define a goroutine, we use the “go” keyword before a function call. Instead of a regular blocking call, the function is then executed asynchronously.

Let’s jump into a quick demonstration. We shall write a program that creates multiple threads, each thread sleeping for a random period of time. For us, the mere mortals, we shall politely ask the threads to print some information so that we can tell when they go to sleep and when they wake up!

The blocking call (from the main process) always executes first. The Scanln() call waits for user input thus allowing the async functions to print their information on the terminal. If we don’t wait, the main process will finish execution and the program will quit. Since the other functions are async, we shall never see their outputs. So we wait and wait for their messages! 🙂

Sample output?

It’s simple, right? In some languages, you have to subclass a built in class and then define specific methods to direct the behavior/actions. In Go, you just define a function and prepend “go” before making the function call. Good thing, you can use anonymous functions and invoke them immediately as well.

For communication between these goroutines, we can use “Channels”. Hope to write another blog post on using channels soon.

The “Go” Programming Language: A First Look [Part-1]

It’s been a while I am looking at Go. The language is nice, feels like a mixture of Python and C with huge performance gains and some innovative language features. In this post, I would try to quickly focus on the basics of “Go”. I hope I shall write more on the language in the coming days.


Installation is really platform specific. I would happily forward you to for installation instructions on your OS.

If you happen to have the same OS as mine, that is OSX, I highly recommend installing Go using Homebrew. It’s just a matter of one line –

Once it’s installed, you can display useful information with this command –

If you are on Windows, Linux or any other OS, please follow a suitable instruction set from the documentation.

Running Go Programs

How does a first program look on Go? Let’s see –

A Go file must define a function named main if you want to run it. We can define a function in go using “func” keyword.

Running it –

You can directly run a Go file by using the “go run” command. This comes in handy for debugging, if you want to build a compiled binary, use “go build”.

Variables, Constants and Printing

First, how do we define variables in Go? It’s simple –

In Go, we can import packages using the “import” keyword. The package “fmt” has a nice function named “Println” which is more or less Go equivalent to System.out.println() in Java. Let’s see a code sample –

If you are initializing a variable, you can optionally skip the variable data type. Go can infer that from the initialization.

There is a shorthand format for declaring and initializing a value quickly –

It will create a var type string and assign the value “masnun” at the same time.

To create a constant, we just replace “var” with “const”. Example:


In Go, we use “for” for all types of looping. Check out –

While Loop:

Generic For Loop:

We can do common “foreach” loops combining “for” with “range”. We shall see them in the next section.

Arrays, Slices and Maps


If you are any programmer at all, I probably don’t need to tell you about arrays. Defining arrays in Go is easy.

The syntax is –

We can reference the indexes just like in any other language. We can even declare and initialize an array on the same line. Take a look at the example:


Slices are like arrays but not fixed size. However, the type must remain the same. I mean you can’t add a string type to an integer slice.

We use the make() function to create a slice. In fact, in Go, make() can create a lot of stuff for me. We shall soon find out. For now, let’s see how we can use a Slice.


Maps are what we call “Hashes”, “Dictionaries” or “Associative Arrays” in misc other languages. Maps are in reality key value pairs. We use make() to create maps of certain types. Example follows –

Iteration with Range

“range” allows us to iterate over a number of data structures. range gives us the key and value in each iteration. It works quite like the “enumerate” function in some languages (eg. Python). Let’s see how we can iterate over common data structures:

That’s all for Part – 1. In my next blog post, I shall try to cover “If/Else” with “Structs, Functions & Methods”.

Beautiful Themes for Sublime Text 3

I have been using ST3 for a while now on test drive and I have checked out some of the themes currently available for Sublime Text 3. All of these themes are available via Package Control. I am also going to link the screenshots to their respective github repo in case you don’t want to use Package Control for some (weird) reasons.

Soda Theme

Soda is probably the most popular theme for Sublime Text

Flatland Theme

Cobalt 2

Nexus Theme

Reminds me of Google Nexus.

Nexus Theme

Pseudo OSX theme

Mac / OS X users are going to love this one

Reeder Theme

Here’s another nice one

Phoenix Theme

And it’s cool


Which one did I miss?

So you know there’s a cool theme for ST3 that is not yet on this list? Please let me know in the comments, I shall add it.