@lukerramsden The other nice thing running in CI is a clean env with everything defined in the codebase. Outside of that anything could be there giving a false positive on tests.
@thorstenball@gnapse@gynura0x The PR is where all the tooling and UI is.
Sure, that could instead be build around the commit but what are we gaining? It is also nice to have something finer grained. Changes need to be made? We can check them in a separate commit.
@nateberkopec Isn't this just slower CI? I want to test some local config interactions and now I need a full web server, database and running multiple layers of code.
@awesomekling Would be great to see a video on your AI workflow. I think your latest coding videos were in the tab completion era. Curious how you combine the latest models with in depth ladybird and c++ knowledge to get the best results.
@naval What does "weakly protected OSS model" even mean? I get to choose what I require approvals for. If someone gives a model access to everything and it rm -rf prod that is on them.
@dhh I am not sure where the quote comes from, but it seems mischaracterised compared to here: https://t.co/lq10UbcLS4
He is saying he doesn't think it is there for a small % of safety-critical, performance-critical code.
@awesomekling I think as a group programmers are going to be way more adaptive to this than other groups. While it was much less disruptive we already dealt with constant change before.
@JackEllis B is too dense and hard to parse, multi line ternary expressions with a bunch of nested functions. A is easier to read but too far in the other direction and over commented, but would be much easier to review.
@levelsio I think the more consistency it carries across generations the better. I don't find it that interesting for each clip to be completely different. The fal sitcom one is kind of carrying across but maybe the model is capable of more with the right promoting.