Use Different SSH key For Specific Git Repo

Podcast Time!

This been haunting me for a long time.

To have a multiple account in the same git repo provider, say Bitbucket, you will encounter an issue where you cannot upload the same ssh key (id_rsa) to both account.

Bitbucket will reject it. And it is reasonable to do so.

All this while my solution was to generate new key (new_rsa) and use ssh config to specify that key.

The problem was it needs a modification in the origin url. Which means it needs quite a time to understand it (by noob like me) and even more time to setup with trial and error (again by noob like me).

There are an easy solution.

We can just specify in the git config which key file we want it to use for the current git repo we are in.

The command are as simple as:

git config core.sshCommand "ssh -i ~/.ssh/id_rsa_example -F /dev/null"

Tested in windows git-bash version 2.16.*

So, i suppose it will work for others too.

Cheers~

published at 30/04/2019 by Izwan Robotys

Podcast I Like For Myself

Podcast Time!

Its been a while that I've planned to have my own podcast for #notabisnes. Already have some design for it and already discussed with Bukhari Rami for it.

I do not know why it does not start yet. Blame the cosmic karma maybe.

Thus, here just some of the notes to make sure when I revisit this podcast idea again I have everything figured out and can start doing it immediately.

The podcast plan has parts that needed to be laid down first as its foundation. The parts are:

  1. Format
  2. Content
  3. Call to action
  4. Channel

Most of the format that we can see people choose for their podcast was interviews. This is good as interviews will bring external audience and new content to the podcast. This will grow audience based and also keep the content fresh.

So far, I like HBR Ideacast and Neil Patel Marketing Podcast format of interviews. Even if no interview, we can still make it works as long as the content is interesting and structured for bite-sized consumption.

Neil Patel podcast is around 7-9 minutes long. HBR is around 20 minutes long. That would be the range then.

Next is content. As the podcast is about #notabisnes, then the content will be about business too. Will revisit all my previous content to pick out the most engaged one and make it a basis.

Or maybe have a totally new set of content so that it is really fresh. But that will bear more risk as its lack of familiarity towards the current audience.

Or maybe the current audience crave for new fresh content by #notabisnes. I do not know much.

All in all, need to come out with a list of content, a total of 12 episodes with 9 to 15 minutes duration. 12 episode will be a good number for 1 season. The recording will be only in a day and release 12 episode altogether.

This to reflect the 'Netflix Binge Watching' culture. People may like to listen to all the podcast in one sitting to capture its value, and re-listening to it again in commutes as they already familiar the value.

Which bring the CTA: 1) Replay again next time! 2) Subscribe at notabisnes.net/center !

Notabisnes.net center will list down all available channel, its frequency, topic coverage and how to subscribe.

This will ensure we capture the customer database to be used later. The best part is we can track facebook user that visit the /center to retarget later when we have something to push in front of their face.

The channel was not the biggest concern, as it seems that podcast will be the same wherever channel/platform we choose. The main criterion for choosing channel then will be 1) Audience potential 2) ease of integration.

The first channel will be notabisnes.net/podcast ... that satisfy both criteria. Marketing will be done via subscription (RSS maybe?) and profile post.

Later will consider uploading the podcast to Spotify and iTunes and SoundCloud.

To summarize:

  1. Format: 9-15 minutes long, 12 episode
  2. Content: Business, Growth, Marketing
  3. CTA: 1) Replay again next time! 2) Subscribe at notabisnes.net/center
  4. Channel: notabisnes.net/podcast + Facebook post promotion

So much fun!

published at 10/07/2018 by Izwan Robotys

Web Design Elements

Less Coding More Thinking

In development of a website, front end has become very important as it is the first area where client can see what the developer are thinking. Unfortunately, it is also the most time-sucking area as graphic is much easier to be commented and discussed upon by non-designer, thus creating an unending loop of show design > customer ask for adjustment > show again > more adjustment > repeat till budget gone kaput.

If, by merlins beard the customer has progress beyond that, then comes the challenge of preparing the foundation of the front end code.

These foundation has move further from basic design features such as color, typography, all those subjective 'feeling' that client talk about into more concrete territory such as elements of the website in particular.

Such elements that has become my must-get-it-right-first-before-start-backend are:

  1. Header + Menu
  2. Footer + Menu
  3. Sidebar + Menu
  4. How do error notification shown?
  5. How do success notification shown?
  6. How and what icon sets will be using?
  7. Form inputs
  8. Standard grid: colum based
  9. Standard grid: line based

After confirmed such elements then we move to the bigger picture which are:

  1. Layout 1: Home
  2. Layout 2: Dashboard after login
  3. Layout 3: List Page
  4. Layout 4: Login/register
  5. Layout 5: Object details page
  6. Layout 6: Object details form

What can be considered an Object? Simple: if such 'features' need to have a form, most likely it will involve a database. If it is, then most likely it is an Object. Thus, each object have form and each form need to show details. Hence: each object will got its detail page.

Only after all these was done can we move to more hig fidelity wireframe that will be shown to client once more, and get adjusted one more.

And the cycle repeats untill budget dried up.

:-)

published at 23/05/2018 by Izwan Robotys

MVP Most Important Lesson

The Reality Of MVP

... Is that it is not about creating something.

It is not about your product.

It is ultimately about your market. Or to be more specific: Market Feedback.

The result of an MVP is not a product, but a lesson.

Said lesson was derived from feedback.

Thus, make MVP to learn from feedback.

Not to fulfill your scope. Or features. Or 'This Sure Gonna Sells' idea.

MVP is nothing without feedback.

Feedback is nothing if you cannot learn from it.

published at 05/12/2017 by Izwan Robotys

Complete Guide Of Founding A Business

Startup Playbook By Sam Altman

Also known as: How To Startup.

Below are some of key ideas and strategy on how to build, manage and grow a startup towards an all conquering big corp with big revenue by Sam Altman.

He is the man of Y-Combinator Incubator with impressive line of successful startup. If an incubator has a Dropbox level startup is impressive enough, YC has a line of Dropbox level startup success.

Which means his writing and all is a gold!

If his writing about building a startup has been compiled and edited thoroughly like a guide book and put in one place accessible for all? It is a city of gold!

Said writing entitled Startup Playbook can be accessed here: http://playbook.samaltman.com/

And below are my personal snippets from said post:

  • Your goal as a startup is to make something users love. If you do that, then you have to figure out how to get a lot more users.
  • It’s much better to first make a product a small number of users love than a product that a large number of users like.
  • To have a successful startup, you need: a great idea (including a great market), a great team, a great product, and great execution.
  • 3 question to ask:
    1. What are you building?
    2. Why are you building it?
    3. Who desperately need that product?
  • The first two is about the idea. It needs to:
    1. Clear to the founder
    2. Founder can communicate it clearly
    3. Simply great
  • The desperate user is about market. In the best case, you yourself are the target user. In the second best case, you understand the target user extremely well.

    If a company already has users, we ask how many and how fast that number is growing. We try to figure out why it’s not growing faster, and we especially try to figure out if users really love the product. Usually this means they’re telling their friends to use the product without prompting from the company. We also ask if the company is generating revenue, and if not, why not.

    If the company doesn’t yet have users, we try to figure out the minimum thing to build first to test the hypothesis—i.e., if we work backwards from the perfect experience, we try to figure out what kernel to start with.

  • It’s important to let your idea evolve as you get feedback from users.
  • We also ask how the company will one day be a monopoly ... Instead, we’re looking for businesses that get more powerful with scale and that are difficult to copy.
  • Finally, we ask about the market. We ask how big it is today, how fast it’s growing, and why it’s going to be big in ten years.
  • We greatly prefer something new to something derivative. Most really big companies start with something fundamentally new (one acceptable definition of new is 10x better.)
  • What if you don’t have an idea but want to start a startup? Maybe you shouldn’t. (me goes: HAHAHA!)

    ...So it’s better not to try too actively to force yourself to come up with startup ideas. Instead, learn about a lot of different things. Practice noticing problems, things that seem inefficient, and major technological shifts. Work on projects you find interesting. Go out of your way to hang around smart, interesting people. At some point, ideas will emerge.

And thats only on Great Idea section of his playbook. There are 3 other bigger section namely Great Team, Great Product and Great Execution.

Please take time to at least go through once his Startup Playbook write up if there is even at least a peanut of ambition in you to build a startup that one day will rule the world.

At least, we will know what we really dealing with.

We will know what we do not know yet. And that is really powerful to us to make informed decision before we even start.

And thank you very Sir Sam Altman. That is really a huge help for us fledgling fellow aspiring founders of yet to born-and-die-repeatedly startup.

published at 04/10/2017 by Izwan Robotys