Xavier

@xavier@sunny.garden
235 Followers
297 Following
1.6K Posts

Artist & programmer based in Brussels. Queer, genderqueer, vegan, BLM, free Palestine, anticapitalist, etc.

I talk about programming languages, sometimes I share my art and ongoing projects, and retoot funny things :>

Feel free to say hi 😌

Websitehttps://lambein.xyz
Pronounsthey/them/he/him
Pronomsil/lui + masc.
Since yesterday I've been working on a little game with friends for #LD57 #ldjam We're making a sort of platformer where you control the depth of focus in the camera, and this affects what can be collided with.
Made some roti for lunch, to eat with leftover curry. Was my first time, but it turned out pretty well :>

It's been a bit over a month now since I started a new routine of exercise. I've always struggled to be consistent, so I'm quite happy with myself. I hope it lasts 😅

This is the routine I'm following: https://www.hybridcalisthenics.com/programs

I also made a tiny web app to track my reps and time them, using Webstrates.

Hybrid Programs — Hybrid Calisthenics

Hybrid Calisthenics

I just released a new track :> It's called "Rains Will Rise", it's sort of emo-rock. You can check it out here:

https://xavierlambein.bandcamp.com/track/rains-will-rise

#music

Rains Will Rise, by Xavier Lambein

track by Xavier Lambein

Xavier Lambein

Made myself a little app to track workouts on my phone and laptop, using local-first #Webstrates. It's the biggest projet I made with it so far. Was fun the do!

Also for some reason the screen recorder didn't capture the metronome, but it did record the speech synthesis 🤔

today's little overdrive loop

Looking for thoughts from people who know more about writing apps with databases than me (so probably a lot of people).

If you're viewing a list of items, and you want to split the code for individual items into its own function `viewItem`, you have two choices. Either `viewItem` accepts an ID for the item to show, and then the function gets the item's fields from the database based on the ID. Or `viewItem` accepts a list of fields, and those are queried by the caller function `viewList`. I've written these two options in the embedded image. (I'm using SQL and React as examples, but it's not about those technologies specifically)

The problem with the first option is that it's making an extra query for each item, which is pretty expensive. The nice thing is that there's less coupling: if you change what you want to render (e.g., add or remove a field), there's only one place to change. So, to me this feels like the best option, if only it were more efficient.

I'd love to have my lunch and eat it---that the fields I query in `viewItem` would somehow affect the query in the parent. Does anyone have ideas about this?

how things have changed since April 1997

https://web.archive.org/web/19970411224438/http://x.com/

Welcome to WWW.X.COM!

My #DecemberAdventure is that I'm once again making a new GUI framework 🙄

I spent the past few days studying the API and implementation of several frameworks I like, stealing their ideas and attempting to improve the things I disliked. Today I've finally started writing some code, and so far things are falling into place fairly smoothly 😊

I don't even know what to make of this one 😐