notes.chiubaca.com | Fleeting Notes

20・12・24

so much ai stuff from cloudflare

https://blog.cloudflare.com/model-context-protocol/

23・11・24

Cursor teaching me how to re-write my big-two game with xstate which is awesome. Its not so scary when applied to a real life context. the API sort of reminds of vue.js options API

  export const createBigTwoGameMachine = createMachine(
  {
    id: "bigTwoGame",
    initial: "WAITING_FOR_PLAYERS",
    types: {
      // Types for context, states, actions etc all go here
    },
    context: {
      players: [],
      currentPlayerIndex: 0,
      roundMode: null,
      cardPile: [],
      consecutivePasses: 0,
      winner: undefined,
    },
    states: {
      // Define all possible state here and also what those state can transition          to. we can also place guards and other things in thes states too. e.g
      WAITING_FOR_PLAYERS: {
        on: {
          JOIN_GAME: {
            actions: ["addPlayer"],
          },
          START_GAME: {
            target: "GAME_STARTING",
            guard: "hasEnoughPlayers",
          },
        },
      }
    },
  },
  {
    guards: {
      // small functions to guard against impossible states
      hasEnoughPlayers: ({ context }) => context.players.length >= 2,
    },
    actions: {
      // actions like dispatchers, the actual buisness logic to update the state          context. this where mutations live.
      addPlayer: ({
        context,
        event,
      }: {
        context: GameContext;
        event: GameEvent;
      }) => {
        context.players.push({
          id: event.playerId,
          name: event.playerName,
          hand: [],
        });
      },
    },
  }
);

…and it has also taught me the slightly new setup version of the this API too.

export const createBigTwoGameMachine = setup({
  types: {
    context: {} as GameContext,
    events: {} as GameEvent,
  },
  actions: {
    dealCards: ({ context }) => {
      // Implementation here
    },
    playCards: ({ context, event }) => {
      // Implementation here
    },
    setRoundMode: ({ context, event }) => {
      // Implementation here
    },
  },
  guards: {
    hasMaxPlayers: ({ context }) => context.players.length !== 4,
  },
}).createMachine({
  id: "bigTwoGame",
  initial: "WAITING_FOR_PLAYERS",
  context: {
    players: [],
    currentPlayerIndex: 0,
    roundMode: null,
    cardPile: [],
    consecutivePasses: 0,
    winner: undefined,
  },
  states: {
    WAITING_FOR_PLAYERS: {
      on: {
        JOIN_GAME: {
          actions: ["addPlayer"],
          guard: "hasMaxPlayers",
        },
        START_GAME: {
          target: "GAME_STARTING",
        },
      },
    },S
  },
});

15・11・24

# dev-journal

immer for updating deeply nested objecting in an immutable way is a game-changer pair with react and state-setting.

04・11・24

# pocketbase

Good guide to self-host pocketbase . Was almost too easy… Whats the catch?

03・11・24

# bluesky

Did you hear? tech twitter is on bluesky now https://bsky.app/profile/patak.dev/post/3l7pyknij2z2y

02・11・24

# pocketbase

pocketbase on fly.io for free

31・10・24

# typescript

import types into a definition file is not intutive! https://stackoverflow.com/a/51114250

27・10・24

# realtime

Exploring realtime options to build big-two

Leaning towards convex due to familiarity, but pocketbase for simplicity and portabability looks very compelling.

19・10・24

# dev-journal

encrypt data with base 64 encoded urls https://64.surf/

07・10・24

# dev-journal

React one is a new framework to keep an eye on. Tight integration with https://onestack.dev/docs/data , replicache could make this very interesting for local-first and real-time applications. Maybe a good contender for my big-two game.

06・10・24

# neovim

10 days of trying to code with nvim and still finding it a bit clunky. Some commands feel good like gd and ci{ (and other ci variant) . Just not fully using navigating a file with just hjkl, mouse scroll still feels superior and smoother? Will keep at it for rest of this month.

25・09・24

# neovim

started learning neovim

https://vimforreactdevs.com/ , good starter uses kick start
https://www.youtube.com/watch?v=V070Zmvx9AM - specifc for web dev not just React, recomends lazy vim which overall feels better to me
- https://www.lazyvim.org/

18・09・24

# 3d

Free alternative to https://crocotile3d.com/ , https://jeiel.itch.io/sprytile
https://www.youtube.com/watch?v=-GWvYamwKRI S

11・09・24

# 3d

make 3d models but also using 2s tile maps for that retro look! https://crocotile3d.com/

06・09・24

# gamedev

sprite sheets with ChatGPT https://x.com/i/bookmarks?post_id=1712674661706977360 https://www.youtube.com/watch?v=dR8JMsYtq9w&t=81s

21・08・24

# godot

Learnt about the Event Bus pattern a.k.a global signals.

Instead of letting child nodes handle their own signals, we centralise them at the highest point in a Godot game state,[ an autoloaded singleton. This creates a singleton (class) available to all nodes at runtime. If we set up signals in this class, we can invoke this signal in any node simply by referring to it any other node e.g. GlobalSignal.hit.emit(). This also means that any other node can subscribe to the events of this Global signal like its broadcasting from the highest level. This pattern has been useful when constructing a HUD for a game. When my enemies die I need to emit how many points that were to show it on the UI, the HUD.

    GLobalSignal
      signal: points
   /           \ 
  /            HUD 
 /              - GlobalSignal.points.connect(update_score)
Enemy
- GLobalSignal.emit.points()