alamsterdam

jenkins running on an old Dell under a desk from someone who left the company 18 months ago looks more reliable these days haha

nope, 6 hours, nothing. I guess they are also load shedding

wasn't that years ago? or was that Skype? hahaha

911 has one! :)

A few friendly suggestions:

- Building a floor and then the room/office is a bit annoying…. Should auto build the floor (like Sim Tower)

- Stairs are difficult to build, it should be possible to build a vertical column, seems you always have to build horizontally?

- It should be possible to have multiple elevator cars in 1 shaft. Of course this is not possible in real life, but we are looking at a 2D shape of a 3D building. Either that or reduce the demand on the elevators

- In real life, Stairs and Elevators generally share a fire space away from residential, that should be encouraged

I played it earlier. Quite enjoyed it (GitHub issues)... Reminded me of my childhood.

Gameplay was a bit wonky, some issues. I saw the OP was posting here looking for comments, I wanted to give some feedback.

Not sure why it was flagged?

Mon and Dad (MS) are (generally) pretty solid with uptime.

What is happening at GH?

Rate of change trying to keep up with new challengers? Over-reliance on AI? Engineers trying to debug slop?

It's been hours :(

I have sympathy for the on-call team trying to resolve it, most of us have been there done that.

But seems something is systematically going wrong at GH

Campaign pushing for end to developers ending video games by withdrawing online support

Agree with the above, we built and run a ticketing platform, the actual transaction of purchasing the ticket at the final step in the funnel is not the bottleneck.

The shopping process and queuing process puts considerably more load on our systems than the final purchase transaction, which ultimately is constrained by the size of the venue, which we can control by managing the queue throughput.

Even with a queue system in place, you inevitably end up with the thundering heard problem when ticket sales open, as a large majority of users will refresh their browsers regardless of instructions to the contrary

Yes, I was wondering what is to stop you replaying the same PoW multiple times. All I can find is:

To prevent the vulnerability of “replay attacks,” where a client resubmits the same solution multiple times, the server should implement measures that invalidate previously solved challenges.

The server should maintain a registry of solved challenges and reject any submissions that attempt to reuse a challenge that has already been successfully solved.

This doesn't seem very scaleable? Or am I missing something?

For me (where our BE consists of maybe 100 endpoints) we’ve found the sweet spot to be Google AppEngine. Incredibly simple to deploy, we don’t really need to manage infrastructure or networking (although you can if you want), decent performance, plays well with other GCP services, great logging and observability, etc

We’ve tried deploying services on K8s, Lambda/Cloud Run, but in the end, the complexity just didn’t make sense.

I’m sure we could get better performance running our own Compute/EC2 instances, but then we need to manage that.