It's going to be interesting to see how everything evolves.
It's going to be interesting to see how everything evolves.
Building a flashlight phone app? who cares, have fun.
Building something that collects personal data? it's reckless.
Collecting people's sensitive data? it's a recipe for disaster.
Building a flashlight phone app? who cares, have fun.
Building something that collects personal data? it's reckless.
Collecting people's sensitive data? it's a recipe for disaster.
Whether that is good or bad depends on the project.
If you build some internal tool or pet project that doesn't need to be "production quality". Go for it!
If you build a customer-facing app… that's problematic
Whether that is good or bad depends on the project.
If you build some internal tool or pet project that doesn't need to be "production quality". Go for it!
If you build a customer-facing app… that's problematic
One use-case you might want to cover: collaboration with coding agents. Where the result of the review is a prompt for changes to the agent with all the comments.
I already wanted something like this when working with Claude Code :)
One use-case you might want to cover: collaboration with coding agents. Where the result of the review is a prompt for changes to the agent with all the comments.
I already wanted something like this when working with Claude Code :)
* `jj checkpoint` which I use in Claude Code hooks to automatically `jj new` it starts/stops a task
* a couple of slash CC commands where I instruct CC to do a code review or draft a change description
I wonder if @steveklabnik.com has anything set-up with coding agents.
* `jj checkpoint` which I use in Claude Code hooks to automatically `jj new` it starts/stops a task
* a couple of slash CC commands where I instruct CC to do a code review or draft a change description
I wonder if @steveklabnik.com has anything set-up with coding agents.
$ jj clresolve [revset] # jj new revset (@- default) and ask CC to resolve the conflicts
& jj clstart <name> # create a jj workspace with that name, start a tmux session for it, run a script to prepare the session, switch to that tmux session
$ jj clstop <name> # teardown
$ jj clresolve [revset] # jj new revset (@- default) and ask CC to resolve the conflicts
& jj clstart <name> # create a jj workspace with that name, start a tmux session for it, run a script to prepare the session, switch to that tmux session
$ jj clstop <name> # teardown
$ jj sprs # (stack PRs) print PR urls the stack, any bookmark missing PR: opens browser with new PR form pre-filled
$ jj pro # (PR open) open the PR for the current bookmark in the browser
$ jj uprs # (update PRs) updates the base branches and adds/updates comment with the stack
$ jj sprs # (stack PRs) print PR urls the stack, any bookmark missing PR: opens browser with new PR form pre-filled
$ jj pro # (PR open) open the PR for the current bookmark in the browser
$ jj uprs # (update PRs) updates the base branches and adds/updates comment with the stack
Some of mine:
$ jj start # git fetch && new trunk
$ jj create <name> #
$ jj stack # jj log showing current stack of changes
$ jj ss # (submit stack) git push all bookmarks in the stack
$ jj sync # git fetch and rebase the current stack
$ jj tug # the usual
Some of mine:
$ jj start # git fetch && new trunk
$ jj create <name> #
$ jj stack # jj log showing current stack of changes
$ jj ss # (submit stack) git push all bookmarks in the stack
$ jj sync # git fetch and rebase the current stack
$ jj tug # the usual
However, it still seems extremely unethical.
However, it still seems extremely unethical.
One of the criteria was whether you can sub-contract your work. If you could not, you were more likely to be considered employed by a court.
One of the criteria was whether you can sub-contract your work. If you could not, you were more likely to be considered employed by a court.
youtu.be/Y7x0gvfFa0Q?...
youtu.be/Y7x0gvfFa0Q?...
> How it works:
> * We find the projects
> * You make a quick appearance: Just a couple of client calls to seal the deal, and maybe a quick standup now and then - that's it.
> * We do the work
> * You get paid: We split the profits 50/50
> How it works:
> * We find the projects
> * You make a quick appearance: Just a couple of client calls to seal the deal, and maybe a quick standup now and then - that's it.
> * We do the work
> * You get paid: We split the profits 50/50
We have already run into trouble where human-made lack of diversity in crops caused problems. Bananas are a good example: storymaps.arcgis.com/stories/38fd...
We should really worry what the unintended consequences could be for "genetic normalisation" to make everybody neurotypical.
We have already run into trouble where human-made lack of diversity in crops caused problems. Bananas are a good example: storymaps.arcgis.com/stories/38fd...
We should really worry what the unintended consequences could be for "genetic normalisation" to make everybody neurotypical.
Historically, most people that push humanity forwards have been neurodivergent, esp ASD, ADHD, and frequently both.
[1/2]
Historically, most people that push humanity forwards have been neurodivergent, esp ASD, ADHD, and frequently both.
[1/2]
Eso no lo veo nunca allí.
Y menos cuando la gente está haciendo cola antes de que abran para comerse un ramen con en verano 35º 🥵
Eso no lo veo nunca allí.
Y menos cuando la gente está haciendo cola antes de que abran para comerse un ramen con en verano 35º 🥵
There are people doing that...
There are people doing that...
Then we can rename agents to characters, multi agent systems are a party, and each task is a quest...
Then we can rename agents to characters, multi agent systems are a party, and each task is a quest...
And C++ never felt to me like a +1 increase over C 😅
Probably taking your joke too far: Should we call it "elicit engineering" instead?
And C++ never felt to me like a +1 increase over C 😅
Probably taking your joke too far: Should we call it "elicit engineering" instead?