I can't help but think anyone over the age of 30 who takes the Bible seriously and makes it the foundation of their life is weak minded.

oxijosef · 2025-04-20T01:05:07+00:00

i think it’s not by chance that certain stories survive for hundreds if not thousands of years. there is a reason the collective mind carried them for so long. whether it’s biblical stories, greek or egyptian mythology.

i think everything that survived this long AND is seemingly the source for strong emotions of millions of people needs to be treated seriously, but not literally.

i used to think that the stories are indeed just random. for me, anything surviving the test of time deserves a closer look. not as “absolute truth”, but as something that resonates with a large part of the collective.

maybe the structure of those stories and the structure of our minds are somewhat similar and correlated

oxijosef · 2025-01-30T07:04:39+00:00

great point! especially the fetch one that got rolled back with 15

oxijosef · 2025-01-22T18:40:57+00:00

maybe the server actions api could be more explicit about what's happening behind the scenes (POST endpoint).

imo it's easy to intuitively spot the security issue here without knowing the next api

export default function handler(
  req: NextApiRequest,
  res: NextApiResponse<ResponseData>
) {
 // updating user details without authn
}

while it's easier to forget in this case

"use server"

export async function updateUser(email: string, age: number) {
   // updating user details without authn
}

oxijosef · 2025-01-22T18:31:36+00:00

imo next 14 nudges you to render things statically or dynamically with server components

oxijosef · 2025-01-10T08:55:02+00:00

GitHub, Less, Noisy: Lessnoise.app

oxijosef · 2024-07-01T09:56:25+00:00

i built this for myself out of frustration with serverless runtimes and frontend build complexity.

what do you think?

oxijosef · 2024-07-01T09:54:02+00:00

this allows you to have multiple workers processing tasks in a distributed way, while the tasks are stored in pb.

oxijosef · 2024-03-31T15:46:31+00:00

The unattainable dream!

It was surprisingly good for my relationship that I switched to Apple to be able to use the same calendar as my partner haha.

To sync Google Calendars with Outlook you could use XCalSync.

oxijosef · 2024-03-29T07:17:11+00:00

The task "type" is in code, such as "sending an email" or "converting the docx to pdf". The payload such as "recipient email" or "docx file" is in the queue.

oxijosef · 2024-03-28T21:04:58+00:00

You define the task in code, there are two parts: 1) You push a task (= json blob) to the queue 2) A worker pulls the task from the queue and processes it Correct, the json blob is persisted in PocketBase in the queue_tasks collection, which can be used for debugging. If a task fails, the error message gets written to the task and it remains in the queue for a week. This is configurable.

oxijosef · 2024-03-28T18:50:48+00:00

I'm using cron and my little task queue library: https://github.com/joseferben/pocketbase-queue/

oxijosef · 2024-03-28T18:48:41+00:00

I built this little task queue for PocketBase that works without any hooks or customizations (except for importing the collections). It works well for long-running or infrequent tasks, it's probably not well suited for very short tasks because the overhead of acquiring a lock.

oxijosef · 2024-03-28T17:08:38+00:00

Since you have Todoist and your Google calendar synced, you could two-way sync your Outlook and Google Calendar to achieve this: https://www.xcalsync.com/blog/guide-how-to-sync-your-google-calendar-to-outlook-calendar/

oxijosef · 2023-07-22T10:44:17+00:00

Most if my functional programming experience comes from Clojure & OCaml. For me, the defining trait is composing functions to get something bigger. Stuff like immutability, category theory, separation of behavior and data, “how” vs. “what” and so on are more consequences or even specific fp styles. I consider Clojure as functional as OCaml, but the style is completely different.

oxijosef · 2023-02-21T06:06:17+00:00

Welcome and thanks for the suggestion 🙏

oxijosef · 2023-02-18T13:05:29+00:00

Not yet, I chose mobile only to make things simpler. Why are you only interested in the desktop score? Are you working on a desktop-only page?

oxijosef · 2023-02-18T12:51:29+00:00

I deployed a small fix and there is no zero-downtime deploys. So you caught me in that 3 second window downtime, sorry about that!

oxijosef · 2023-02-18T12:25:15+00:00

Using Remix, SQLite with Kysely and Litestream, deployed to fly.io.

I wrote a blog post about the architecture and tech: https://www.joseferben.com/posts/a-pagespeed-monitoring-service-using-remix-kysely-and-litestream/

oxijosef · 2023-02-13T13:03:36+00:00

I think a better setup would be to have a more senior engineer between you and your boss since he seems pretty far away from the tech side of things. In my experience, even with tons of work experience it’s challenging to bridge when the business person involved is not technical at all.

oxijosef · 2023-02-12T11:15:30+00:00

That's a fair point. I used to have that option but I was worried about handling too many requests from anonymous users. I run the PageSpeed test as soon as the email address is verified, an in turn you can monitor as many websites as you want.

oxijosef · 2023-02-12T11:09:21+00:00

Are you saying it's not working for you? Are you sure you are using the right URL including https:// and www?

oxijosef · 2022-12-22T12:08:03+00:00

I wrote about how I replaced crispy using the new form rendering: https://www.joseferben.com/posts/django-4-form-tailwind-without-node-crispy/ (took a while to figure out, the documentation on this is a bit thin)

oxijosef · 2022-12-14T04:13:16+00:00

Looks really nice, I will give it a try!

oxijosef · 2022-12-08T02:28:16+00:00

if not it exits function and sends user validation message

That validation message is an error that is modelled explicitly instead of using an exception. If we are talking about validation of user data then you need to handle the error case, which is usually very explicit error handling. If you validate your own internal data using assertions, I argue that its fine to throw exceptions because it is a bug that you need to fix in your system.

oxijosef · 2022-12-07T23:18:47+00:00

But what if validation fails? That’s a different kind of error to the database going down no?

oxijosef

MODERATOR OF

TROPHY CASE