I've mostly worked in smaller companies (max 250 employees) and recently joined one of the larger corporations (not automotive related).

The main issue I notice is how bad the communication is and how little can be done & decided. Before deploying a new Jenkins pipeline I need to speak to two different teams. It's insane how much time is lost doing meetings and syncs.

> Before deploying a new Jenkins pipeline I need to speak to two different teams

It doesn't sound excessive that there would be two teams using a Jenkins pipeline that would need to be consulted.

Maybe deploying was a bad choice of wording, I'm talking about setting up a new pipeline, for my repository with an internal tool. I need to speak to two different teams to ensure my CI/CD jumps through all the necessary hoops.

Totally the same experience. And then everyone is expected to work on weekends because that deadline that was missed four times before definitely needs to be done by this weekend. At least until it gets missed for the fifth time.

Kurzarbeit is only available for a limited time and has the target to avoid layoffs resulting in much higher costs in unemployment payments.

It's 24 months at the moment, which is way too long. A buffer period for companies to allow for necessary adjustments should be one quarter, max two.

The alternative is, that if they don't manage to adjust, they let people go.

> scroll

Yet the navigation on mobile through swiping is non existant

existent, like in existence

What kind of strawman are you trying here?

The hardest challenge is not using your phone when sitting on the toilet

Old good air freshener label reading

Dr. Bronner's soap is good also.

DILUTE! DILUTE! OK!

If you never do, you’d hopefully be aware that it’s exceptional.

As an always-sitter, it’s always long enough.

Would you mind sharing good and bad examples of prompts? I always read comments like yours and miss examples.

There is no real definition of a senior engineer. Just looking at years served seems is wrong imho.

There's what "senior"-level developers say about themselves, and there's what's actually generally true about them. The two notions are, of course, not the same.

I worked for two years on a medical app. From my limited experience with audits it was more focused on everything being compliant with the ISO 9001 & ISO 13485. Actual tech audits never happend and stuff like Emailing scanned letters never occured. However this was in Hessen and not Berlin.

My point being I guess its ok-ish to not know what software libs are, the paper workflow is still horrible.

That has to be about a different Angela Merkel, the one I know had one priority: preserving status quo.

She also was for making Germany economically dependent on gas pipelines to Russia, even though she knew that she was funding Russia's war in Ukraine.

I am not inclined to give her a free pass on that.

Which recent German politician in power wasn't about preserving the status quo? The entire country and culture is all about the status quo.

I'm. It sure of the "recent" definition but Schroeder's tenure brought a lot of changes (which one can argue against, but it was not conservative).

> slow and steady presence

> preserving status quo

That sounds like the same thing to me?

> I’m confident it didn’t cheat and look at the EXIF data on the photograph, because if it had cheated it wouldn’t have guessed Cambria first.

Hm no way to be sure though, would be nice to do another run without Exif information

He did, by rerunning it on a screenshot of the image