abtv / tech-radar Goto Github PK

If a tweet was classified as job it should be highlighted

Add link to time field.

Reuse table-view

Move .css -> .scss and add sass plugin support for realtime reload

Try to search something, then click to any topic and then click back in your browser.

A lot of ? signs. Either fix the problem or delete such tweets.

Put resulted gif into README.md file

While this is still a pet project, I would like to make it working as a "real" site. Right now, we use search for tweets in memory. In general we can find only daily tweets. It would be nice to provide search for weekly or even monthly tweets under 1 Gb of RAM.

Regarding in-memory search: I still think that it's the best way for this app:

1. no external service dependencies like ElasticSearch or Solr (simple deployment)
2. predictable hardware requirements (search in memory is fast and at the same time consumes predictable amount of memory if we limit amount of tweets in memory)
3. it's fun to implement your own search (which is usually not appropriate in "real" projects)

It's mostly changing tweet count settings and testing it in small instance.

Use max-tweets-count and threshold (if we exceed threshold we will run garbage collector to delete old tweets). It should work on per-topic basis.

User can't know what screen is opened except he opens menu

Right now some topic diagrams have too many ticks and it's unreadable. Reducing number of ticks should improve readability.

We need more memory (RAM) to provide better (more) search results. As it's open source project, I have to minimize costs. The solution is simple - find a cheaper and still reliable hosting provider, then deploy new instance and test it.

react.inc.js:19287 Warning: flattenChildren(...): Encountered two children with the same key, .$1107263. Child keys must be unique; when two children share a key, only the first child will be used.

Technology switch should contain combo box with tech names. When user selects a tech name he will see appropriate chart. By default we show job trends. By default we show 40 items.

Only for topics page to reduce number of pages

It's better to have a list of stop words in a file (like settings)

Reload tweets and trends in memory every n hours (settings value)

Some simple proximity metric. If 2 tweets are similar just increment counter field. Tweets with big counters should have a special mark in status field.

2 reasons:

1. reduce traffic size on mobiles
2. sometimes tabs are shown in 2 rows, it takes more space than necessary
   Try send twice less texts