기본 콘텐츠로 건너뛰기

The reason why I selected Google Blogger

In SW Maestro, 3 mentors for our team are fixed, and we got our first official mentoring from mentor 배권한.
He gave us an assignment - make a personal blog and post an article about co-working tools. He insisted we run a blog for 4 reasons.
  1. We forget what we have studied someday
  2. We can realize something new when we think about it again
  3. Somebody like a headhunter may contact me through my blog
  4. To make my activities visible
So, I decided to make a post about pros and cons of famous blog services.

Criteria of Selection

I consider these factors.

Main Factors

  1. It should 'work' well.
  2. It should be easy to parse my posts from the blog.
  3. It should be easy to write code on my blog.
  4. It must take responsive design, so that it can be seen with mobile device.
  5. It must be easy to be exposed by Google search.
  6. It must provide reply function.

Sub Factors

  1. It is good if the design is fine.
  2. It is good if the markdown function is provided.

Comparison among Blog Services

I could find a GitHub repository that organized what kind of blog services famous developers of South Korea and the world use.

Popular Web Sites

  • naver.com, blog.me
    • 29 people use
    • Koreans only
  • tistory.com 
    • 75 people use
    • Koreans only
  • egloos.com 
    • 11 people use 
    • Koreans only
  • tumblr.com
    • 7 people use
    • Koreans only
  • brunch.co.kr 
    • 76 people use
    • Koreans only
  • medium.com 
    • 54 people use
    • 42 Koreans use
  • github.io 
    • 88 people use
    • 78 Koreans use
  • blogspot.kr, blogspot.com
    • 28 people use
    • Koreans only
    • Maybe there are more people because it is able to change the domain name

Pros and Cons

Naver

Pros
  • Many Koreans use...
Cons
  • It uses native search-exposure algorithm. So it is difficult to find Naver blogs from Google search.
  • It doesn't support Code Snippet or Gist.
  • It doesn't support custom design.
  • People who doesn't have Naver account are not allowed to leave a reply. (So foreigners will never leave feedback to me.)
네이버 블로그에 대한 이미지 검색결과

Tistory

Pros
  • It has comparatively high degree of freedom in design.
  • It supports visitor counting function.
  • It is still growing. (?)
Cons
  • Text editor is too inconvenient.
  • Each functionality is scattered.
tistory에 대한 이미지 검색결과

Tumblr

Pros
  • It supports markdown.
  • Text editor is convenient to use.
  • There is a mobile app.
  • Themes are aesthetic and customization works well. 
  • Users can leave reply with Disqus.
Cons
  • There is no category system.
  • A Windows program is needed to edit posts, and it takes too much resource.
tumblr에 대한 이미지 검색결과

Brunch

Pros
  • It is made by Kakao
  • Design theme is sentimental
  • And there are lots of advantage to use it but ...
Cons
  • It doesn't support Code Snippet or Gist.

Medium

Pros
  • It supports Code Snippet and Gist.
  • Text Editor is convenient.
Cons
  • Theme Customization is restrictively allowed.
  • Font is fixed with Serif, so that Korean font is fixed with myeong-zo(명조), and this font is so ugly.

Jekyll

Pros
  • It is possible to use Ruby. (But I don't use Ruby.)
  • It bases on GitHub Pages service.
  • It is possible to attach additional functionalities.
  • It has high degree of freedom in design.
  • It provides markdown.
Cons
  • I have to switch my GitHub account premium to make my articles private.
  • It's too free, so it's little bit bothersome to use.

Blogger (Google Blogspot)

Pros
  • It is made by Google. Need I mention more..?
  • It provides developer API.
    • I can extract json strings about my posts, pages, and comments from database with API.
    • We can see more about API from public Google supporting page.
  • We can edit posts with html.
    • So it is easy to apply syntax highlighting.
    • So design customization is maximum-free.
  • It provides markdown by adding a module.
  • It provides fucking-strong visitor statistics.
  • I can write a post blaming Korean government with an easy mind because the server is at the abroad.
Fake Cons
  • There is no category concept.
    • But, it is substituted by tag impeccably.
    • tag is better than category because tag can make M:N relationship with posts while category only can make 1:N relationship with posts.
  • There is no secret reply functionality.
    • But, it can make unsociable comment culture, so it is better without that functionality.
  • Most Koreans don't use Google blog and Google search engine.
    • But, most Korean developers do. :)
Cons
  • There is no trackback concept.
  • There is no file upload functionality. I have to make a cloud share link to upload.
관련 이미지

Conclusion

Google Blogger satisfies every aspect that I consider while others have at least one trivial flaw.
Therefore, I decided to use Google Blogger for my blog service.
From now on, my blog is started.
Welcome, everyone!

댓글

댓글 쓰기

이 블로그의 인기 게시물

Kotlin + NDK, OpenCV

원래 이 블로그는 영어로만 작성하려고 했었으나, 코틀린 프로젝트에서 OpenCV를 사용하는 방법에 대해 정리한 한글 블로그가 거의 없어서 이 참에 블로그 방문자 유입도 좀 늘릴 겸하여 이번 포스트는 한글로 작성하려고 한다. 절대 영어로 쓰기 귀찮아서 한글로 쓰는 게 아니다. 내가 좀 쫄보여서 그런지는 몰라도 간단한 테스트도 iterative하게 진행하는 게 마음이 편하다. 그래서 1. Kotlin 2. Java + NDK(C++) 3. Kotlin + NDK(C++) 4. Java + NDK(C++) + JNI + OpenCV 5. Kotlin + NDK(C++) + JNI + OpenCV 순으로 프로젝트를 생성하여 한 단계씩 통과시켜가며 넘어갈 생각이다. 그런데 결론부터 말하자면, OpenCV에서 Kotlin을 지원하지 않는 것으로 보인다. OpenCV의 라이브러리 폴더(OpenCV-android-sdk\sdk\native\libs\mips64)를 열어보면 libopencv_java3.so 파일은 찾을 수 있지만 libopencv_kotlin 비슷한 이름을 가진 파일은 없다. Kotlin에서 C++을 돌려봤다는 사실 정도에 만족하고 넘어가도록 하자… ㅠㅠ 환경 다음의 환경에서 진행한다. * Android Studio 2.3 * OpenCV 3.3.0 Kotlin Project 생성 먼저 안드로이드 스튜디오에서 간단한 hello world 자바코드를 생성하여 코틀린코드로 변환해보자. 그냥 처음부터 코틀린으로 만들면 되지 왜 굳이 자바코드를 변환하고 앉아있느냐 할 수도 있는데 안드로이드 스튜디오 2.3에서는 그런 기능을 제공하지 않는다. ㅠㅠ 3.0부터는 아예 코틀린이 안드로이드 스튜디오에 빌트인으로 제공되면서 처음부터 코틀린 프로젝트를 만들 수 있게 된다 카더라. 프로젝트 생성 그냥 자바 기반 안드로이드 프로젝트를 만들면 된다. 어플리케이션명을 적당히 정해주자. Company Domain은 소속된 회사이

Running Anaconda Python on Jupyter Notebook with Docker in Windows

I think there is no IDE more suitable for studying machine learning or deep learning with Python than Jupyter Notebook. However, it is so difficult to construct a Jupyter environment without crushing with the existing Python environment. So, I decided to make an only-for-deep-learning environment in the Ubuntu Docker container to avoid all annoyance. I will assume that you already installed Docker. Environment Ubuntu 17.04 LTS Anaconda 5.0.0 (containing Python 3.6) Creating Docker Container First of all, we are going to create a Docker container. The world is going better day after day! You can get a Docker image containing Anaconda that someone created and simultaneously make a container with the image you just downloaded just with this one-line command. docker run - it --name jupyter -p 8000:8000 --volume /c/Users/jinai/Dropbox/HaveToLearnToRun/CSE/3_1_MachineLearning/jupyter_workspace:/root/jupyter_workspace continuumio/anaconda3 /bin/bash It’s quite complex. So let m

Cooperation Tools That Support Scrum Development Process

We have to cooperate for our project, and we need to decide which tool to use. One of our mentors recommended 3 cooperation tools which support scrum board function, and suggested we learn about that tools, put into shape, and share them one another. So, to follow his order, I write this post. Scrum - Agile Software Development Process First of all, we should know what the hell the SCRUM is. I referred here  and wiki . In agile software development process, there are 3 elements that consist of it - roles, artifacts, workflow. Roles Product Owner They ponder on what they make. Scrum Master They ponder on how they make. Scrum Team They just make T_T Artifacts Product Backlog It contains general requirements. (I don't sure it is right explanation for product backlog.) User Stories It contains detail requirements. Estimates It contains the order of priority of all requirements(user stories). Workflow Iteration & Incremental Developme