Tim Fischbach

@tfischbach.bsky.social

Software developer. Building @pageflow.io / https://www.pageflow.io/

TIL you can use registered custom properties in CSS to force computing a property value at a certain level in your DOM instead of just applying text based substitution. This can useful when working with nested containers and wanting to reference an outer container in via container query units.

Screenshot of two nested divs with container-type: inline-size. The inner container has 60% width and contains two boxes: One with width 50cqw relative to the inner container and one wider one with width 50cqw relative to the outer container. 
:root {
  --size: 50cqw;
}

.outer-container {
  container-type: inline-size;
}

@property --px-size {
  syntax: '<length>';
  inherits: true;
  initial-value: 0px;
}

.inner-container {
  /* Turn cqw into computed pixel value */
  --px-size: var(--size);
  
  container-type: inline-size;
  width: 60%;
}

.box.with-size {
  width: var(--size);
}

.box.with-px-size {
  width: var(--px-size);
}

Experimenting with a custom jj-pin script to make history cleanup in #jj-vcs feel safer. I often find myself tweaking a stack of changes moving things around without wanting to change the overall diff. Especially when there are conflicts to resolve, I want to be sure not to mess up.

~/my-repo[my-feature q]$ jj-pin
📌 pinned my-feature (7a738bec1452)
~/my-repo[my-feature q 📌]$ # Rearrange/clean up changes
~/my-repo[my-feature q 📌]$ echo "Accidental change" > foo                                                                                                          ~/my-repo[my-feature q 📌✗]$ jj-pin-diff 
Modified regular file foo:
        1: Accidental change
~/my-repo[my-feature q 📌✗]$ jj-unpin # when done

There's an interesting dynamic, where coding agents not only reduce the activation energy required to follow certain best practices (automated tests, small commits, limited scope etc.), but sort of turn them into prerequisites to have a chance of making the process work at all.

Moreover, it seems to me that there is a third option beyond the “don’t look at the code” vibe coding approach and “big design up front” spec-driven development. That third option is an agent-based workflow, which I’d characterize by:

Simon Willison@simonwillison.net · 11mo ago

Vibe coding is irresponsibly building software through dice rolls, not caring what code is produced What about when engineers at the top of their game use AI tools responsibly to accelerate their work? I propose "vibe engineering"! simonwillison.net/2025/Oct/7/v...

A blog post I'd like to write if I had the time (or a maintained blog for that matter): "The Role of Automatic Testing in Agentic Coding" or maybe "Techniques for Test-led Brownfield Development with Coding Agents"...

We’re trying a rather radical new approach at Piccalilli by doing real world projects — for real clients — in the open. This gives us a context to provide genuine high quality, real world education for free at the point of entry.

We need your support to do free projects for good causes and publish free high quality education

We’re trying a rather radical new approach at Piccalilli by doing real world projects — for real clients — in the open. This gives us a context to provide genuine high quality, real world education...

piccalil.li

Here's what rendering React Server Components is gonna look like in Parcel. Just point it at your server entry point, use any server framework/router/libraries you want, and render your components. Coming soon! 👀

$ parcel server.tsx

// server.tsx
import express from 'express';
import {renderRequest} from '@parcel/rsc/node';
import {Page} from './Page';

let app = express();
app.get('/', async (req, res) => {
  await renderRequest(req, res, <Page />);
});

app.listen(3000);


// Page.tsx
"use server-entry";
export function Page() {
  return (
    <html>
      <body>
        <h1>Hello React Server Components!</h1>
      </body>
    </html>
  );
}

Last school day before the holidays. Shall we play a game? In the replies, list ONE benefit of Test-Driven Development that nobody's listed yet. I'll go first. Continuously working (shippable) software. Your turn :-)

Also, I want to make more use of the fact that a core part of the Rails application I'm working on day-to-day is open source at github.com/codevise/pag.... Ten years of development on a real-world app should give me something to talk about.

GitHub - codevise/pageflow: Multimedia story telling for the web.

Multimedia story telling for the web. Contribute to codevise/pageflow development by creating an account on GitHub.

github.com

Tim Fischbach@tfischbach.bsky.social · 2y ago

#RealCodeFriday When building query objects or methods that perform more intricate queries, I often find myself wanting to preload different data based on where the query is used. Here's one approach that has been working well for me:

Screenshot of https://github.com/codevise/pageflow/blob/4eccad2cd111d187fbd601f53545fa478b2fdb2d/app/models/pageflow/draft_entry.rb#L17-L23

Choose 20 Ruby gems that you've used time and time again, or have inspired you in some way. One gem per day for 20 days, in no particular order. No explanations, no reviews, just README links. (1/20) github.com/thoughtbot/f... 💙💎 #20DayGemChallenge #RubyOnRails #distilled.rb

GitHub - thoughtbot/factory_bot: A library for setting up Ruby objects as test data.

A library for setting up Ruby objects as test data. - thoughtbot/factory_bot

github.com

What feeds are y'all using? Especially (web) dev related but curious in general, trying to be more active and involved here 🤓

What's the best way to discover content related to a specific topic on here? For example, I'd like to find more posts related to the Ruby programming language, but as a search term it mainly brings up drawn characters named Ruby.