laurels-marts

Refreshing that the author doesn’t try to conceal his character or thoughts.

The contents of his character and thoughts are quite objectionable though.

No one cares enough of zig to do it, people will just continue moving to Rust and similar.

You seem to think you know other people’s best interests better than they do.

Damn this is exciting. I love that gpt models are much faster, efficient and cheaper than Claude models. They are so fast even on high/xhigh that I don’t find myself using the parallel agent setup anymore much since its cognitively less demanding to just follow along what the model is doing and most tasks it will complete in <5-<10mins anyway.

I love that Codex is open source and issues like these can surface/be addressed publicly.

Wait what. I never used CC but use Codex CLI with 5.5 daily and authenticating has never been an issue. I even rolled skills that instruct it how to retrieve test user credentials for auth purposes.

Today using the devtools I asked it to reverse engineer the login auth flow of another app in our company and it created a nice browser-like headless script (with cookie jars etc) that emulates the entire Auth0 flow with all the internal API calls, redirect loops etc so that given username/password I end up with a valid JWT without having to open an actual browser instance and go through the login steps manually. Zero hesitation or questions asked.

I think this is in-line with OpenAI's philosophy. They see Codex agents as just tools for developer to use. They don’t try to imbibe them with “feelings”, “constitution” or “morality” the way Anthropic does.

And much faster!

My company gave me cursor license after I had already been using Codex CLI for months and VS Code for a decade.

I had absolutely no interest in their VS Code fork. The Agent Window was okay but buggy (eg wouldn’t load branches on Ubuntu via WSL2).

Overall used it a couple of times but still use Codex CLI as my main driver. Might try CC in the future esp. if they unban Fable.

i have shell scripts that create/tear down worktrees. the shell script finds unique unused ports across all existing worktrees and assigns in local .env upon worktree creation. when the worktree gets merged and is torn down the ports get released. secrets that are not worktree-specific i don't keep in local .env i inject via shell.

honestly creating these local scripts for automating the dev work was trivial and they combine well with all other cli tooling. thats why i havent tried any of the GUI apps yet. im not sure they're able to compete with my custom local setup that works exactly the way i want.

Are you complaining that government is not corrupt enough?

Wait so when u navigate to a different page/tab the url wouldn’t update?

You have been authoring HTML by hand for decades. Not every SWE is a FE dev.

For me it never updates and shutdown. It always just updates and restarts.

What I’ve heard often is that the customer might want to build a dashboard using AI on the fly.

Like imagine you have a site and there’s blank canvas. It has access to some data in the background. The user might be like “build a dashboard showing YoY performance of X and break down the shipments in a table by Y and Z”. Then the agent builds it and persists it such that when they log out and log back in they can see their custom dashboard they assembled themselves.

I’m basically doing lvl 3. There’s not a single port in my local worktree’s .env that’s not guaranteed to be unique across all worktrees. Skills for agent to start their own managed dev server, launch their own isolated instance of chrome etc. literally end-to-end code and debug the entire app. I do have to say though you have to know the app inside out and have to have a pretty well groomed backlog in order to run them all in parallel and actually benefit from it.

I’m a bit confused by this.

I migrated my Remix 2 app to react router 7 and I think it’s great.

Sure I have to pull in Express for server, Typescript for types, Vite for bundling etc but it’s not a lot of overhead. React Router mostly solves what I expect a modern framework to solve (also love v8 middlewares)… so what is Remix 3 adding? Are they really proposing that they will create a better bundler than Vite, a better UI renderer than React, a better types system than TypeScript? And for what? Such that you can say that you can build a “modern” app without any other deps other than Remix itself in your project?

Unless I misunderstand something but why not just roll a couple of helper shell scripts that create a new git worktree for you, copy over a local .env file (or any other config file) and populate it with ports/variables that are unique across all worktrees (to avoid collisions if you're on localhost, but you could also do this with Docker) and a helper script for tearing down a worktree after you've merged the changes back into main. I'm even supplying unique chrome debug ports and unique temp user data dirs for isolated automated testing in chrome via chrome devtools mcp. Like, I'm not sure why an external library/tool is needed for this.

Yes and the official docs even mention that if you’re on Windows you should run Codex CLI via WSL. Meaning, it’s specifically designed for unix systems.

Government cutting internet access to 90m ppl while killing protesters in the streets and “growing up without internet” is not even remotely comparable lmao.

You’re not alone. I absolutely love going to office every day but also love the flexibility to occasionally wfh if needed. I just feel like when I enter the office and put on my “unreachable” focus mode on I’m in the zone and very productive. At home there’s endless distractions (my cats make sure to check in with me every time get too focused). Also I do like interacting with colleagues. I think I started liking going to office even more once I broke up with my gf that was living with me for 4 years. Something about working the entire day from my apartment completely alone is… not appealing to my social side of the brain.

Sports. I do 2h of strength training every Mon/Wed/Fri. You work with barbell, not machines. Requires all your mental and physical focus. That pretty much will soak up any “free” after-work time you have on those days. Then on Tue/Thu you can do social activities. Any time spent not working/sport/social activities I spend “whatever” which means watching a show, reading a book or doom scrolling - but it won’t a lot of time left for it. And honestly at that point you probably have a pretty well balanced life that “doom scrolling” is not an issue.

refused to interview Harris

Why spread misinformation?

iPhone XS Max here. I'm tempted this year.

I have been taking 300mg of Magnesium Bisglycinate 30 mins before sleep for the past 5 months or so. I have anxiety which can lead to insomnia. It has been a great help.

Is there a meaningful difference?

What sort of mating strategy are you optimizing for?

It could be that you have an anxiety disorder, obsessive personality disorder or OCD. Or perhaps not, but the obvious red flag is trouble sleeping. If you’re typically a good sleeper but find yourself sleepless when in one of your spirals it's a good indicator that you need to take a step back, take a deep breath and reset your mental state because its not the refactoring thats not letting you sleep its all the stuff that you have built up in your head.

Also complete rewrites in general are overwhelming and tend to turn out not the way you imagined anyway. Small incremental improvements and isolated refactors over a sustained period of time yield the best results.

So you have duckdb running on the server (e.g. node.js) and duckdb-wasm running on the client? Or are you hitting S3 directly with duckdb-wasm?

Only ever give node answers in ESM format.

I also add to always use async/await instead of the .then() spaghetti code that it uses by default.

D3 is from jQuery era so there are a lot of methods for manually manipulating the DOM like d3.select() and then selection.attr() etc. but those patterns tend to lead to components that are lengthy, hard to read and hard to maintain. Arguably a better approach is to group each D3 module based on whether it "modifies DOM" or "doesn't modify DOM". Then use React/Svelte to declaratively render the DOM and only use the D3 modules from the latter group for their math utilities.