https://github.com/questdb/dasher-fe
An exercise for front-end skill assessment
https://github.com/questdb/dasher-fe
Last synced: 7 months ago
JSON representation
An exercise for front-end skill assessment
- Host: GitHub
- URL: https://github.com/questdb/dasher-fe
- Owner: questdb
- License: mit
- Created: 2024-05-01T15:54:27.000Z (over 1 year ago)
- Default Branch: main
- Last Pushed: 2025-02-20T17:42:21.000Z (11 months ago)
- Last Synced: 2025-06-06T22:11:16.530Z (7 months ago)
- Language: TypeScript
- Homepage: https://questdb.com
- Size: 153 KB
- Stars: 0
- Watchers: 6
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# QuestDB front-end work sample
Hey!
Thanks for your interest in joining the team.
The following is designed to take about 2-4 hours.
Or "one solid working block".
There is no deadline.
However, we do have lots of folks applying, so keep that in mind!
Time is of the essence.
## The task
This exercise is designed to mirror a realistic dev scenario.
There is a NextJS app with a base page, an API, and a view.
The view is located at `localhost:3000/audit`.
Your mission:
1. Get the app running
2. Update the Auditor UI to handle more rows
- Can you handle 1000 rows? 100k? 1.5B?
3. (Stretch goal) Generate stats using row data
- Hint: _QuestDB queries_
1000 rows is no problem, but after 100k things get dicey.
The DOM will explode, and it looks like our table won't cut it.
How can we improve this?
The API, view, and whatever else is yours to edit.
Direct real-time queries at the live [QuestDB demo instance](https://demo.questdb.io).
Be mindful of performance, efficiency, and failure when the queries returns a large data set!
Look for `@TODO`!
## Evaluation
We are evaluating:
1. How you handle the rows
2. How you constructed your "table"
3. Did you handle stats? How?
4. How you package the PR
There is also an **optional** [THOUGHTS.md](thoughts.md) page.
As you go, feel free to write any interesting thoughts.
If you got stuck (especially in the 1.5b case) you can indicate how you would have solved it with more time.
If you have any questions, please reach out to us!
## Submission
To submit:
1. **Clone the repo**
```sh
git clone https://github.com/questdb/dasher-fe.git
cd dasher-fe
```
2. **Create a new branch**
```sh
git checkout -b my-solution
```
3. **Implement your solution**
4. **Commit your changes**
```sh
git add .
git commit -m "My solution"
```
5. **Generate a patch file**
```sh
git format-patch main --stdout > my-solution.patch
```
- This creates a patch file with all changes made since the `main` branch.
- Alternatively, if you want to submit only your last commit:
```sh
git format-patch -1 HEAD --stdout > my-solution.patch
```
6. **Compress the patch file**
To avoid issues with odd characters, please compress the file from a command-line environment:
**Using `zip`:**
```sh
zip my-solution.zip my-solution.patch
```
**Using `tar`:**
```sh
tar -czvf my-solution.tar.gz my-solution.patch
```
8. **Submit your patch**
- Email us `my-solution.patch`!
### ⚠️ Important Notes
- Please **do not** push your solution to a public repository
- Ensure your patch file includes only necessary changes
- Compression ensures we do not have any weird issues applying it
- Avoid opening the patch file in a text editor, as this may alter the contents
Good luck! 🚀