completions VS ideas3

I am building _exactly_ the same thing for Playwright over at https://ray.run/. I think this is the future of writing tests no doubt. Planning to launch next week.

Note: Use page.goto('/') and have "baseURL": "http://ray.run" set in the playwright.config.ts file for concise code.

Your website https://ray.run/ does have that nostalgic early 2000s vibe, which is cool! Regarding the search functionality, you might want to explore open-source alternatives to Algolia.

Projects like Elasticsearch, Solr, or even using Google Custom Search can provide search capabilities without the cost. They might require a bit more setup and maintenance, but they can be budget-friendly options for a free community.

In case you need help or assistance with your project, feel free to contact us! https://www.ratherlabs.com

* Most of the pages I use are rendered at the request time, rather than build time

For context, this is the website https://ray.run/

Ensuring in-article hover definitions for terms on the https://ray.run/ blog.

I have added a zone to Cloud DNS (GCP) for https://ray.run/

I updated completions library to allow statically typed responses:

import { type Browser, chromium, test as base } from '@playwright/test'; import getPort from 'get-port'; import { playAudit } from 'playwright-lighthouse'; export const test = base.extend<{}, { browser: Browser; port: number }>({ browser: [ async ({ port }, use) => { const browser = await chromium.launch({ args: [`--remote-debugging-port=${port}`], }); await use(browser); await browser.close(); }, { scope: 'worker' }, ], port: [ // eslint-disable-next-line no-empty-pattern async ({}, use) => { // Assign a unique port for each playwright worker to support parallel tests const port = await getPort(); await use(port); }, { scope: 'worker' }, ], }); test.describe('Accessibility Testing with Lighthouse', () => { test('should pass the Lighthouse accessibility audit', async ({ page, port, }) => { await page.goto('https://ray.run/'); await playAudit({ page, port, thresholds: { accessibility: 100, }, }); }); });

import { test } from '@playwright/test' test.beforeEach(async ({ page }) => { await page.goto('https://ray.run/login') await page.fill('#username', 'admin') await page.fill('#password', 'password123') await page.click('#login-button') expect(await page.url()).toContain('/dashboard') }) test('should display user profile', async ({ page }) => { await page.click('#profile-button') expect(await page.textContent('body')).toContain('Admin User') }) // Other tests...

I wrote some notes about this of what I want in my "life engine":

https://github.com/samsquire/ideas#5-life-engine

I never got into the quantified self but I did want a portal (such as similar to the Yahoo! and Excite.com days) in the early 2000s. of personal details that I can take actions on.

Then a few years later I wrote about "life situational awareness apps"

I want my phone and desktop computer system try to have widgets for "accommodation", "travel", "food".

https://github.com/samsquire/ideas3#59-life-indicators---sit...

I did write a question generator feed dashboard written in Electron that let you snap in data collectors that would let you save records of stock purchases and facts about yourself such as your salary. The idea is that you could get advice based on what you answer.

https://github.com/samsquire/living-documents

https://github.com/samsquire/living-documents-library (the app repository)

Unfortunately it's probably not buildable and I forgot to take screenshots or videos.

My blogging/journalling setup is simple.

I just use GitHub. I just rely on the default repository view on GitHub.com

I create a README.md and add markdown headings to the bottom or to the top (bottom if its a journal, top if it's a blog) and then when I get to 100-800 I create a new repository and repeat.

https://github.com/samsquire/ideas (2013)

https://github.com/samsquire/ideas4

https://github.com/samsquire/ideas3

https://github.com/samsquire/ideas2

Thanks for posting this Ask HN question.

I journal ideas and thoughts about computers and software. I am interested in software architecture, parallelism, async, coroutines, database internals, programming language implementation, software design and the web.

https://github.com/samsquire/ideas (2013)

https://github.com/samsquire/ideas2

https://github.com/samsquire/ideas3

https://github.com/samsquire/ideas4 <-- this is recent but needs editing

https://github.com/samsquire/ideas5 <-- this is what I'm working on now

https://github.com/samsquire/startups

https://github.com/samsquire/blog <-- thoughts I want to write about, but incomplete

I use README.md on GitHub and create a heading at the bottom for each entry. I use Typora on Windows or the GitHub web interface to edit.

I journal computer ideas and the ideas from database engineering are yet to percolate everywhere, especially to the desktop environment. Why is every company building frontends and backends when the CRUD problem could be solved properly once and for all and reused everywhere? We did the same for communication and kernels with Linux, Windows and BSD, and BSD sockets which is shared by practically everybody. Your React frontend is legacy and shall be rewritten in 5 years. But BSD sockets or the Linux kernel doesn't get rewritten everyday.

Rather than writing hand rolled code for querying data structures and manipulating them as Linux does, we can define queries that retrieve data structures in in the shape we're looking for.

To put this simply, this is extremely high level, and the idea that data layout, data structure and algorithm can be unaggregated for cache locality and performance and developer experience. We can form materialized views on top of other materialized views and calculate the most efficient retrieval and storage format based on the structure of the data.

I suspect a materialized view, as in the data structures of the Linux kernel is more efficient than materializing a join at runtime.

One of my ideas is "ideas4 9. Query for data structure", https://github.com/samsquire/ideas4#9-query-for-data-structu... which is the idea we should be capable of querying to retrieve data structure in the shape we want. The shape of the data lends itself to solving certain kinds of problems.

An ideas3 is "Query database" https://github.com/samsquire/ideas3#17-query-database, we persist queries as we persist data and use them to optimise query format.

I also had the idea # 10. in ideas4 to persist data access patterns directly and optimise that. https://github.com/samsquire/ideas4#10-access-pattern-serial...

I am more likely to journal and blog if the friction to creating a post is as simple as opening a document and writing. The important part of journalling or note software is that you actually create notes. I did use Hetzner to run a Wordpress blog but it had an overhead of server expenses and keeping Wordpress up-to-date.

I don't want my data trapped in a proprietary system where it is difficult to export, so I use plaintext. I looked into Publii [1] but I prefer my current plaintext setup. Today I journal software ideas, computer ideas, startup ideas and community ideas on GitHub in the open, as README.md files. My journal is all public on GitHub at the following links. There are over 550+ journal entries, I am sure you shall enjoy them.

https://github.com/samsquire/ideas

https://github.com/samsquire/ideas2

https://github.com/samsquire/ideas3

https://github.com/samsquire/ideas4

https://github.com/samsquire/startups

https://getpublii.com/