Broken on mobile, cant scroll the results and the top is cut off.

This seems to be a common phenomenom with all those vibe coded apps. Bit weird since most traffic is mobile nowadays.

It is the same as adding dependencies or hosting on Azure/Aws, choosing a nosql db isn't it?

Well, except it's your entire codebase, yeah

Any tipps on finding interesting and valuable papers?

It depends on the theme. If we're picking something in a space the group already knows well, like databases, I'll look at "Best Papers" from recent VLDB/ICDE/SIGMOD conferences. If we're exploring a topic most people are unfamiliar with, we'll go with something more foundational instead. For example, we're starting an arc on datacenters (servers, racks, networking, load balancing, power, cooling, failures, etc.), and most attendees don't have deep background there, so I found a book on the topic that we're going to read through[1].

[1] https://link.springer.com/book/10.1007/978-3-031-01761-2

Not author, but in the past I was just going through papers on biggest conferences for the last year and checked what sounded interesting for my own education. But it was a bit of a chore. What I tried now is use gemini thinking research and asked it to do just that, go through main software/hardware conferences for last 3 years, find me papers on the topics of interest and give summary and links. The result is pretty good!

Thats my experience as well. Of course not ten paper a day but some learning is always encouraged.

One company had a +1 day. You worked 4 days, had 1 day for learning - everything relevant for the job was fine.

Investors want to see growth, chugging along is not the return they expect. It would be nice tho.

Sounds like a poisoned chalice.

As far as I recall, the founder and angels have put in almost as much money as VCs. Certainly an interesting funding story.

Its rare that devs are on standby, waiting for a pr to review. Usually they are working on their own pr, are in meetings, have focus time.

We talked a lot about the costs of context switches so its reasonable to finish your work before switching to the review.

Honestly I kind of envy the energy of these people.

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