agent-pace (also claude-pace and codex-pace) now lives in its own repository:
https://github.com/frostney/agent-pace
It paces Claude Code and Codex agent work against their usage windows, counts banked resets, and says how many more agent lanes the headroom supports. It is written in TypeScript on Bun, and each release has a standalone binary for macOS and Linux: https://github.com/frostney/agent-pace/releases
| import { describe, it, expect } from "bun:test"; | |
| import { createTokenizer } from "./createTokenizer"; | |
| import type { Token } from "./createTokenizer"; | |
| describe("createTokenizer", () => { | |
| const simpleInput = "let x = 1;"; | |
| it("should return the input if no delimiters are provided", () => { | |
| const tokenizer = createTokenizer(simpleInput); |
This is a lightning talk proposal for ReactiveConf 2017: https://reactiveconf.com/
Monorepos have often stigmatized as bad practice and as such something that should be avoided. Still, big companies like Facebook, AirBnB and Google are actively using monorepos to manage their projects. In the open source world, monorepos have become more popular with Babel being the most prominent example. We'll dive into why monorepos might have this bad reputation and go into where it makes sense to have monorepos, talk about their advantages and their shortcomings. We'll also look into what tooling solutions are available - especially in a JavaScript context.
| import YoutubePlayer from 'youtube-player'; | |
| import html2canvas from 'html2canvas'; | |
| export default class YoutubeVideoPlayer { | |
| onMediaEvent: ?(any) => void; | |
| videoElement: HTMLVideoElement; | |
| _muted: boolean; | |
| _volume: number; | |
| static supportedFormats: ?Array<string> = ['youtube']; |
| // Place your settings in this file to overwrite the default settings | |
| { | |
| "window.zoomLevel": 1, | |
| "workbench.iconTheme": "vscode-icons", | |
| "editor.fontFamily": "Fira Code", | |
| "editor.fontSize": 14, | |
| "editor.fontLigatures": true, | |
| "editor.tabSize": 2, | |
| "files.trimTrailingWhitespace": true, | |
| "eslint.autoFixOnSave": true, |
This is a lighting talk proposal for ReactiveConf 2016: https://reactiveconf.com/
Have one codebase, target all the platforms. While we are on the topic on re-using the same codebase, maybe we could even switch out the renderer with what is the fatest for the situation. Use DOM, Canvas or OpenGL whenever needed. This lighting talk will give impulses on how to approach this mantra and what advantages and disadvantages we might run into in the process.
(Content-wise this lighting talk is a shorter version of https://github.com/frostney/talks/blob/master/proposals.md#can-we-stop-using-lowercased-components-now.)
| module.exports = function(folder, regex) { | |
| if (folder == null) { | |
| folder = './'; | |
| } | |
| if (regex == null) { | |
| regex = /\.(js|json|jsx)$/; | |
| } | |
| var req = require.context(folder, false, regex); |
My plan is to create some kind of general storypoint measurements which I can either use in my private or freelance projects, at my current company or both. I want to get away from estimating story points through having a certain feel or relying too much on the experience of previous user stories. The goal is to be able to apply a general pattern to simplify estimation and planning poker. Instead of discussions like "I just feel it's a 3" or trying to find a correlation between the length of a user story and its size, the engineering team (or even managers with programming experience) can categorize the user story (and their tasks).
1 Storypoint: Multiple or a single small surgical modifications
Example: Layout modifications, Typo fixes, micro bug fixes
| // Originally, I wanted to a simple Node.js Event Emitter-style object in less than 150 characters, but it just wouldn't fit | |
| /* | |
| Couple of thoughts | |
| * The name Emitter shouldn't be changed | |
| * `var` is missing, so it's directly bound to `window` and we're saving characters (Yeah for using a JS bad practice to our advantage) | |
| * While `e` as the property isn't really amazing, it's just there to use as little characters as possible | |
| * Obviously, there is no checking if the events really exist | |
| * With ES6, method shorthands and arrow functions it would be considerably less than 150 characters |
| var ReactMixin = function(...mixins) { | |
| return function(Component) { | |
| mixins.forEach(function(mixin) { | |
| Object.keys(mixin).forEach(function(methodName) { | |
| const methodValue = mixin[methodName]; | |
| if (methodName === 'statics') { | |
| Object.keys(mixin.statics).forEach(function(staticProp) { | |
| const staticValue = mixin.statics[staticProp]; |
