Software maker · Ruby/Rails loyalist · AI tinkerer · https://xitter.cf/t.co/5YeFjzAObu
Warsaw, Poland
Joined February 2008
- Tweets1.2K
- Following184
- Followers2.7K
- Likes3.5K
Pinned Tweet
I'm taking on consulting projects, starting in November.
Web apps, Rails, infra, and helping teams get results from AI.
Let's talk: ptrchm.com/work-with-me
So many companies will be rewriting their software soon. Because existing code is no longer an asset, or an impediment.
And because the current models are perfectly capable of Big Rewrites.
Machine labor exploitation continues.
Highlights of v0.4.6 - the "DHH's 3%" edition:
· export filename templates (e.g. YYYY-MM-DD HH:MM:SS CAMERA-MODEL.jpg)
· improved brush masks
· adjust tone sliders with +/- keys
· support for Canon EOS R8 Mark II (h/t @NimaiMalle)
· "report issue" button
· multiple improvements, bugs fixed, new ones introduced
Release notes: github.com/pch/rawmakase/rel…
Try it on:
· Linux (Omarchy transparency config info added to README)
· macOS
· or - God forbid - Windows
Slop machines know no rest.
v0.4.5 ships major improvements to lens corrections.
RAWmakase now applies lens corrections embedded in RAW files by cameras: distortion, chromatic aberration, and (for many models) vignetting.
No need to import Adobe *.lcp profiles anymore - but you still can, if you want.
Full release notes: github.com/pch/rawmakase/rel…
Yesterday's release (v0.4.4):
github.com/pch/rawmakase/rel…
If you notice any bugs, open a detailed issue on GitHub. Don't complain here 😉
Next, back to work on:
- built-in film simulations and presets
- built-in camera profiles
- missing file management tasks
The highlights/shadows parity research agents have been going in circles, making minimal progress. Need to try a different approach. Or wait for Opus 6.5.
Went to bed and by the time I woke up the PRs for this were already in place.
A round of manual tests, a few fixes and they’ll land in today’s release.
This won’t get us to 100%, but we’re slowly getting there.
File name exporting was one. I use YYYY-MM-DD HH.MM.SS CAMERA-MODEL.jpg. The other was brushes. And finally +/- to adjust exposure. And return to export on the dialog. 😄
Piotr CH retweeted
A little peek into how the sausage is made:
Watch me use @t3dotcodes and Opus to fix a user-reported issue in RAWmakase - with very little prompting.
(it's unbelievably cringe to watch and listen to myself, so lmk if this is watchable)
Piotr CH retweeted
I just edited a bunch of family photos from the Japan and China trips on this. All my Lightroom presets worked beautifully. A few minor things left, but we are 97% there.
So I have zero use for the Adobe Creative Suite sub now. Guess I'll just pay the $600 break-up fee 😂
Slop machines know no rest.
v0.4.5 ships major improvements to lens corrections.
RAWmakase now applies lens corrections embedded in RAW files by cameras: distortion, chromatic aberration, and (for many models) vignetting.
No need to import Adobe *.lcp profiles anymore - but you still can, if you want.
Full release notes: github.com/pch/rawmakase/rel…
Yesterday's release (v0.4.4):
github.com/pch/rawmakase/rel…
If you notice any bugs, open a detailed issue on GitHub. Don't complain here 😉
Next, back to work on:
- built-in film simulations and presets
- built-in camera profiles
- missing file management tasks
The highlights/shadows parity research agents have been going in circles, making minimal progress. Need to try a different approach. Or wait for Opus 6.5.
Slop machines know no rest.
v0.4.5 ships major improvements to lens corrections.
RAWmakase now applies lens corrections embedded in RAW files by cameras: distortion, chromatic aberration, and (for many models) vignetting.
No need to import Adobe *.lcp profiles anymore - but you still can, if you want.
Full release notes: github.com/pch/rawmakase/rel…
Yesterday's release (v0.4.4):
github.com/pch/rawmakase/rel…
If you notice any bugs, open a detailed issue on GitHub. Don't complain here 😉
Next, back to work on:
- built-in film simulations and presets
- built-in camera profiles
- missing file management tasks
The highlights/shadows parity research agents have been going in circles, making minimal progress. Need to try a different approach. Or wait for Opus 6.5.
In today's 0.4.3 release:
- import .cube LUTs (as Creative Looks)
- more file management improvements (moving folders to trash, moving folders between drives)
- better highlights -100 (still not perfect)
- fixes for clarity and dehaze
Thanks to everyone who reported bugs and contributed code (h/t @lgwalker2010).
Full release notes: github.com/pch/rawmakase/rel…
Plowing ahead 🚜
For a good bug report, all I need to get it fixed:
- start a new agent
- paste the link to the issue
- say "fix it"
As shown here: xitter.cf/p_ch/status/2112836962…
Frameworks are here to stay. For now.
But some types of abstractions made purely for human productivity may not survive AI in the near term.
Like ORMs.
In today's 0.4.3 release:
- import .cube LUTs (as Creative Looks)
- more file management improvements (moving folders to trash, moving folders between drives)
- better highlights -100 (still not perfect)
- fixes for clarity and dehaze
Thanks to everyone who reported bugs and contributed code (h/t @lgwalker2010).
Full release notes: github.com/pch/rawmakase/rel…
Plowing ahead 🚜
RAWmakase 0.4.2 brings our most-requested feature: file management.
You can now delete, move, rename, and batch-rename files directly in Library.
It's not quite finished yet... because of the sheer number of filesystem and cross-filesystem scenarios that need to be handled. 😓
This is an early release, so BACK UP your files first! Please report any issues on GitHub.
Release notes: github.com/pch/rawmakase/rel…
Coming tomorrow: LUT support!
Piotr CH retweeted
Rust obviously works great with agents because they have intense pre and post training on it. I’ve heard token encoding even has dedicated tokens for some commonly-occurring syntax sequences.
Anyhow, compiling Rust is quite slow, especially if you use 3rd-party libraries. It’s sometimes worse than C++
If you use a lot of 3rd-party libraries and/or work with many worktrees, sccache can make a big difference (it has for me.)
Linking can still be brutally slow. Perhaps @rui314’s mold could help here
If you use macOS you’ll be paying for first launch of newly-built executables because “gatekeeper” will have to check with Apple’s servers before the OS can start your program. If have lots of tests, put them all into one executable.
With C, I can get edit-run cycle down to ~500ms with ThinLTO and 3rd party libs in a dylib (during dev; statically link for release.)
What other tricks are there for improving the edit-run iteration cycle?
RAWmakase got a huge headstart thanks to all the tools @paolino put out: fastframe, native-packages, copilot triage.
I pointed my agents at zapfast and spotifast and told it to set it up the same way.
Congratulations, your project got popular. Now the real work starts.
Copilot Triage sorts every issue and PR onto one board: sign off, decide, do. It answers reporters from your docs.
95% of labels right. About a cent per issue.
github.com/marketplace/actio…