@sascha @dach Friendica unterstützt C2S.

@BandanaBug I currently code a new section in Friendica, especially for groups. This should improve the handling, I think.

@CyberEgg es gibt ein grundsätzliches Problem: kalte Luft kann nicht so viel Feuchtigkeit aufnehmen wie warme Luft. Dementsprechend wird es zwangsläufig zu Kondensation kommen. Und die kann problematisch werden. Ich kann mir das Video zur Zeit nicht ansehen, da ich unterwegs bin. Mich würde interessieren, wie die Lösung dagegen aussieht.

@CyberEgg mir wurde gesagt, dass das System in der Firma etwa 3-4 °C schafft. D.h. wenn tagsüber 32°C sind, schafft das System die Absenkung auf etwa 28°C. Das ist gut, aber nicht so gut wie eine Klimaanlage.

@sascha Wir haben das im Büro. Die Teile schaffen leider nur eine Absenkung um ein paar Grad. Klimaanlagen sind in der Regel leistungsfähiger.

@TehPers That sounds like a very bad situation!

@Petter1 I'm a lead developer. And often I hear from my architect when I missed stuff in some PR that I just checked.

I worked in a lot of different software companies over the last 35 years. And this company has by far the highest standards. It's sometimes really annoying when you maybe coded 8 hours for a use case, just to spend 10-12 additional hours just for the test cases and maybe some 1-2 additional hours because the QA or the PO found something that needs to be changed. But in the end we can be proud of what we coded.

@Limerance Well, on Friday I spent around 1.5 hours just reviewing a single PR. And I'm not done. I will have to continue my work on it on Monday. Reviewing in our company means understanding the connected use case, then having a look if the coding does what the use case defined. Also we look if the coding is done according to our internal style guide. Since our review is normally done by at least two people, (at most of our apps two people have to accept the PR until it can be merged) one person will see what the other missed. And we often talk about what the other missed, so that we learn.

Concerning angry customers: Our apps are used by several ten thousand users. And although our group doesn't have direct customer contact, we get the bug reports and have to fix them anyway or we have to support the teams who directly work with the customers.

And I just realize that I'm in a very lucky situation. In our company each use case is tested thoroughly by the responsible QA and PO. And for each use case we write half a dozen (or more) test functions that check the functionality. Normally coding the tests takes more time then coding the use case itself.

Our company is very AI driven, but on the same hand we hear in the regular town halls about the customer satisfaction. And the goal there is to increase it steadily. Our customers are companies, so maybe there's the difference.

Who creates these AI-generated PRs? Colleagues in your company or some third party people in an open source project? I guess when this would happen to me, and the PRs were created by colleagues, then I would escalate this to my line manager. And I guess that she would understand why this is a problem and why it had to stop.

@TehPers @Limerance why hadn't you time to review it? Every minute in review pays off because it saves you from hours of debugging and handling with angry customers.

@Petter1 @remington at our company every PR needs to be reviewed by at least one lead developer. And the PRs of the lead developers have to be reviewed by architects. And we encourage the other developers to perform reviews as well. Our company encourages the usage of Copilot. But none of our reviewers would pass code that they don't understand.

@caos @connaisseur Das hat bei Friendica schon immer funktioniert, da das Interface sehr unterschiedlich zu vielen anderen AP-Diensten ist.