gif about ochre without much context

every developer I know is at their peak

only great things can come out

a dark mode, but it doesn't show white images

Rethinking Pair Programming in the Age of AI Why "pairing with AI" is harmful to your team and what to do instead

🧠 Rethinking Pair Programming in the Age of AI

Why "pairing with AI" is harmful to your team and what to do instead

learnings.aleixmorgadas.dev/p/rethinking...

Let's have great documentation for your OCaml project. Markdown is not the excuse anymore

I wrote a blog post about odoc's Markdown backend sancho.dev/blog/ocaml-...

I absolutely want to try this!!!!!

Dream is currently the weakest link here, I'm considering other approaches such as simple_httpd or anmonteiro's stack directly

I'm super close to finishing a Next.js-like experience for OCaml on top of Dream: file-system routing, server components, typed routes, and a CLI that hides most of the dune machinery

with LSP, error overlay, hot reload, melange integration...

the only usecase I use is as a personal trainer that evaluates my activities and plans for next week

i randomly tell how I sleep and how much I eat from time to time

Haven't seen other useful ones tbh

DDoS'ing the human brain AI made us mass produce code at a scale we never could before. More code, more problems, same brain. Somehow I'm more productive and more exhausted at the same time.

Some thoughts about AI-assisted coding and how it affects my brain. I'm more productive and more exhausted at the same time.

marvinh.dev/blog/ddosing...

Very good post, thanks!

> My thinking context is occupied

same, and I think that's why I'm more exhausted as well

since I needed to generate unique classnames for each selector, which made "resolve &" to the right unique classname.

Happy to see more work on CSS in OCaml

Pretty interesting. In styled-ppx, since I support nesting of selectors and media queries, there's also the resolve media queries, join them, and unnest them.

Aside from "optimize" which I currently don't do any property/value optimization, selectors become a bit more complex...

omg is turbo, should be fast

waiting for turbo gti

its the new meta

It is the era of finishing the side-project of the side-project and go to the deepest rabbit hole possible

Your First Parser Build a config file parser from scratch, learning Parseff along the way

I wrote a guide on how to implement your first parser with parseff. Should be handy!

davesnx.github.io/parseff/gui...

is there anything you would want to learn/know about parseff?

parcho ahhahaha

renaming to parsexn?

the support today is on-demand input from a source. it does not do bounded-memory/incremental streaming, because backtracking requires retaining prior input.

maybe streaming is a stretch?

yeah, parsing functions need to be always inside... and you could nest parsers but that's often a really bad idea? I think it should work

but yeah, I set a register_printer that atleast the error is not terrible

DLS here is mainly for ergonomics and keeping current direct-style API shape

Kind of loses the purpose of the name tbh, but frankly, the comparison is:

46-75% faster without effects because each combinator call is now a direct function call + DLS.get nstead of Effect.perform + handler dispatch + continuation resume (~50-100ns)

exploring the idea of making parseff faster, autoresearch suggested to remove effects entirely from parseff and it makes fused operations equal, but primitive operations are much faster

yea, the shiny library doesn't appeal much these days

yep, that's me

publishing parseff v0.3.0

- Binary parsing (big and little endian)
- UTF-8 with uucp and new ocaml stdlib apis
- Parseff.locations () that give offset, column and line

there's ocaml thought

oh I want to know what you got . Once i learn about < object > syntax and i didn't expect it to be

Are you going to be in Miami between April 20/25th? Let’s meet at React Miami