Threema is great, I’m using it privately a lot. Several German authorities have set up and published variants of Element X, using the Matrix protocol in the backend.

The only thing that really got me going was small applications I had some interest in. Writing games I will not play never kept my interest up for long. So I’ve been building mini tools I used for teaching numerics classes in meteorology (Python, Julia, Fortran, C) or code I would be using for some tinkering with microcontrollers or similar (Python, C++) when using new languages. For me personally, some iconic projects were a CO2 sensor with an attached display, or very simple internal gravity wave ray tracers. But that’s likely not what you’d be interested in. So without trying to suggest specific applications for you (many good examples in the responses :-) I’d advise to do something you’ll have fun with. Get yourself a small project that generates added value for you specifically (and fun is great added value in my eyes).

To be honest, I simply wouldn’t feel comfortable storing this data on the third party servers hosted on hyper scaler infrastructure. That probably works for most but I’m not keen on a Telekom / AWS combination there. The regulation itself is a totally different discussion. There’s arguments both in favor and against and I don’t really wanna judge that here. I’ll say though, that IMHO the OS level is totally the wrong place to do it. Just gives large non-European companies a powerful bonus datapoint.

Where are the photos of the document processed though? And if not on the phone itself, is the server backend open source as well? Can I self-host it? And is the data which is used to generate certificates deleted immediately or stored in the backend? I have questions.

That’s a much reduced statement. Construction noise is indeed a massive disturbance, which is why there’s a lot of efforts on mitigation it. Once the plant is running, however, it has been observed to work as an artificial reef increasing the local populations. To increase the effect there’s some work on adding boulders in between the monopiles. Another reason is that power boats are (depends on country) often forbidden to enter which actually reduces the noise disturbance within the area. There’s also effects on some species (lower trophic levels) due to the local reduction in wind speed in the wake which modifies the amount of mixing in the surface. That is, however, an active field of research. Long story short: fields of wind power plants are depending on the current life stage a disturbance but have in some sites been observed to be the opposite once operating. A conclusion to only build them on land could hardly be drawn at this time.

I’m glad to hear that lack of time/resources for code reviews are more common. Also for clarification: I was the author and requested reviews by my colleagues. In reverse, I did not receive requests to review PRs so far. Tbh. I would really like such a review culture as it is already standard in scientific publishing and it would have avoided some obvious bugs we did encounter in the past. Having that said, as I did not receive any review at all and I would appreciate low(er) quality reviews better than none.

It was more a question of finding the time within the daily business of doing science. I suppose it is also a culture issue, the priority to do a review is usually low. In other words, there was de facto never a review.

From a scientific modeler perspective: Always trying to do 5 (or 4), but I’m having difficulties getting a culture of reviewing each other’s codes going. Many times I was asked to “just merge” months after submitting a PR. In the context of operational or large community codes, 5 is usually strictly enforced. Weather services don’t appreciate broken code.