In daily coding, I take a lot of programming notes. For me, these notes are just a way to avoid having to spend an hour or two researching and experimenting on a similar task the next time. For example, after the completion of writing the following articles, I encountered many similar tasks and returned to them for countless times, which saved me a lot of time:

  • Laravel 5.1 Artisan Command Line Combat
  • Composer loads third-party extension packages in a local path
  • Install the MongoDB server and PHP MongoDB Driver on Ubuntu 14.04

A common feature of this type of writing is that it is a concise record, without too much rhetoric, but a step-by-step guide to how to complete the task.

I have always felt that this kind of writing should not belong in the “blog” category. The content of a blog should be one’s own thoughts and thoughts, or the study of certain knowledge. However, such notes are relatively mechanical and unreadable, and are of little value to most readers who have not encountered the same task. Although I have written about this kind of article on my blog countless times, I always resist it in my heart. More often than not, I choose.md to log to my local file system. But here comes the question:

  • Graphic type of record is very inconvenient;
  • Inconvenient search, inconvenient retrieval;
  • The layout is not good, affecting the quality of access, especially the pictures in the article, the access experience is very poor;
  • Existing on the machine, remote access is more troublesome (can only use file backup), can not be like the web anytime and anywhere;
  • There was no feedback, and some of the recorded content was wrong, so it kept going wrong [facepalm];
  • Content loss is serious, because I tried all kinds of tools to record, over the years, these high value records to me scattered and lost;
  • .

That gave me the idea of creating a purely journaling product. Using the “wisdom of crowds” characteristic of the Internet, I also get good feedback on my records, and enthusiastic netizens even submit suggestions for amendments to my articles.

And not only can I take my own programming notes on it, I can also find other people’s high quality notes. Based on the “likes” and “user comments”, I can be sure that a certain note has been practiced by many people, and I can use his solution with confidence. If I find problems during the use, I can also discuss solutions with other authors who have performed similar tasks.

Tiicle mainly has the following functions:

  • Search function – quick location
  • Version control – Keep a record of every change made to an article
  • User submission – Allows users to submit articles directly [improved version]
  • User likes – help distinguish the quality of the content
  • Subscribe feature – Follow interested people and technical tabs
  • And of course, the most important, elegant Markdown editor (paste images, live preview, syntax highlighting, etc.)

If you share the same struggle with me, I invite you to try Tiicle:tiicle.com/. Your feedback and suggestions are always welcome.

The name Tiicle comes from a play on Tickle, meaning “to delight.”