tychota

I'm a long time user of raw therapee, that i found both awesome and complex.

Awesome because if you set the right debayering algorithm and fine tune ondelette, you can get way better result than anything else, especially in rought situation.

Complex because if i don't practice often (like have a kid) i end up watching niche tutorial and reading the wiki for VNG4 vs AMAZE which is a bit frightning.

It make me want to test dark table or one of the clone

On top of the other answer, the people interviewing you might be HR people ressource with limited tech knowledge and this lack of nuance.

They are here recruit "AI ready engineer" or other vague, bullshitty slogan.

You often need to pass this first barrier to discuss with real futur colleagues. Thus you have to give them what they want to hear.

Which is hard on AI considering how polarised the subject is.

"en attendant Godot" is no longer a good joke! Nice work!

Why teach Paxos and not raft. I thought raft was easier to grasp, and is used a lot nowadays?.

I did follow the whole adventure online. I will buy this bokk for sure.

Thanks, Bob. You did a wonderful job.

I've mixed filling.

I'm sad, because:

- I started using Phabricator in 2012 and tried some contribution back then, when I was still learning. I learn PHP working on contribution.

- The product is really awesome and back then, the difference with GH and others was even more striking. Draft PRs years before GH, proper issue management with work board years before GH, a lot of automation (Herald) and an yet unmatched ability to customize the interface, and build extensions to the program. In peculiar, behind able to define custom lint and unit test and have them integrated to the UI is awesome. I've seen others good ideas come before its time, in peculiar with integrated CI/CD, being able to see links between everything (issues, diffs, wikis, ect)

- The codebase is awesome. I mean, they build a fully modular system from nothing, just raw PHP. In my sense, they build one of the best PHP framework along the product. The architecture is nice, and they had really great ideas (overheating queries https://secure.phabricator.com/T13133, EditEngine/ApplicationEditor: https://secure.phabricator.com/T9132). Bob, Chad, and Evan are awesome devs. They helped me improve and shaped me as a developers. They also created a fondation of craftmanship with stances like: "Don't create to much config, it is a sign of badly designed product" and so on

- I learned a lot about infra deploying phabricator.

- They was a lot of humor back then: https://secure.phabricator.com/T10000, https://secure.phabricator.com/T10054#151066, https://secure.phabricator.com/T6389

For all this, thanks Evan, and others. It was a nice adventure. I will really miss this...

... but for me that was expected, the contributions shrinked, the core team went from 3 to 1. External contribution was also more and more difficult and while I understand the reason (reviewing and maintaining is more expensive than doing all yourself), it build a model that only depend on the willingness of one man. Also lack of proper integration with Gitlab/Github (Nuance https://secure.phabricator.com/T12739), sticking to an old, pre React area JS framework called Javelin did make the end inevitable. I did see the contribution decrease overtime(see https://github.com/phacility/phabricator/graphs/contributors). In the last years, Phabricator was just a ghost to me, sadly...

I hopes that Evan is well, and the end of adventure is not to bitter.

I think too much depends on Phabricator for it too end like that, and I'm looking forward to @20after4 or others to fork. Maybe it will have a second breath.

Anyway, so long and thanks for the fish !