Skip to main content

A Twitter Usage Pattern

Twitter means different thing to different user. So the usage may vary. Some people use Twitter as a game to find as many followers as possible. I use Twitter mainly for feed aggregation. I read tweets more than I tweet myself. Thus, follower count is not my concern. I think follower count is distracting. Some even suggest that Twitter hide follower count.

I follow tech journalists like @TechCrunch, @rww, @slashdot, @alleyinsider, @techreview and @databazaar. I keep on looking for tech journalists with great sources to follow. Well, there are too many tech news that I can chew in a day so I just skim their headlines. Twitter's short text makes it easier to skim the headlines. Each tech line is accompanied with a link to the blog post where the full news is published. Because I am living in a different time zone I will read the news few hours late. I consider being late is an advantage to me because I can also read the comments.

I use the comments to check my own opinion on the subject. Controversial news will invite many comments where some of them are much longer than the actual news. Haters also leave comments. Sometimes I am amazed to the frequency of those hate commenters who keep on coming back to the blog although they had earlier threaten to abondon the blog.

In summary, here is my Twitter usage pattern. I skim through my Twitter's Home time line looking for tech news. Once a news catches my eye I will click on the link accompanied in the tweet. It will open in a different tab on my browser. I keep on openning up all selected news of the days while reading tweets. I will only read the news after I have done with Twitter. I read each news and follow with its comments. When I have something to say then I tweet. I will blog when a subject is harder to keep in a tweet.

Comments

Post a Comment

Popular posts from this blog

Setting Up PyScripter for Quantum GIS

PyScripter is a general purpose Python Integrated Development Environment (IDE). Quantum GIS (QGIS) is a desktop GIS application that can be extended with Python plugins. Both are open source softwares. We intend to use PyScripter as an IDE to build QGIS Python plugin. We are using PyScripter 2.4.1.0 and QGIS 1.6.0 in Windows. PyScripter does not come with Python. On the other hand, QGIS is built in with Python. Thus, we will setup up PyScripter to use the build in Python in QGIS. We assume both PyScripter and QGIS are already installed. Preparing PyScripter batch file We assume that QGIS is installed in C:\OSGeo4W\ folder and PyScripter is installed in C:\Program Files\PyScripter\ . 1. Copy qgis.bat in C:\OSGeo4W\ bin to pyscripter.bat 2. Edit pyscripter.bat to remove the last line that read something like this start "Quantum GIS" /B "%OSGEO4W_ROOT%"\apps\qgis\bin\qgis.exe %* and replace it with this in one line Start "PyScripter" /B "C:\Progr...
8 comments
Read more

Access Control

Access control is about controlling user flow within your application. Do not mistaken access control with security which is a bigger subject in itself. Access control begins by authenticating user and limit his or her activity in your application. An activity is something like creating, updating or deleting a content. There are always finite number of activities that can be done in a given application. Each user can be assigned to a set of activities that he or she is allowed to do. Access control is usually tied to session management. However, you do not need session management to have access control. When a user log in, a session is created so that the user is remembered for the subsequent access. Otherwise the user has to keep on providing his or her credential for each access. We can also keep a list of activities that the user is allowed to do in the session record. Some applications let the session alive indefinitely and some applications time out user after a duration of inacti...
Post a Comment
Read more

Separation of Front-end and Back-end Concerns

Separation of concerns is the cornerstone of MVC framework. Model, view and controller are three broad concerns of web-based software development. On its early days MVC was implemented on server side. The server renders views for clients. Nowadays, most clients render views themselves. Even the terminology of client-server has already morphed into front-end and back-end . The need for back-end to handle views is diminishing. View concerns have became increasingly complex with two big sub-concerns of aesthetic and dynamics. Front-end evolves into bigger MVC concerns of itself. While back-end evolves into larger modeling concerns. Now, front-end and back-end are two separate concerns. Front-end and back-end are handled by two different teams of software developers with different specialties. Back-end evolves into something like "dinner can be served even without plates, forks and spoons, without table and chairs, and without a dinning room." Front-end is serving the withouts....
Post a Comment
Read more