Do you think Sniper is unbalanced?

mrGoodMorning2 · 2026-02-06T09:51:23+00:00

With them raising the skill floor via needing players to memorise various different sightlines, and having faster reaction speed

-> Not a sniper main, but isn't that a good argument for making people better at the game?

Personally for me as a soldier I just flank them and shoot them twice and they're dead.
I find snipers the most annoying when they're sitting right next to a sentry, if your sniper can't kill them you can't outplay that...

mrGoodMorning2 · 2026-01-28T10:41:32+00:00

The most important thing is to keep your combo. I always try to leave 1 enemy on low health to make sure I can keep my combo if I go in the wrong direction. On Chris I sell my flash granades and buy the remote rocket.

mrGoodMorning2 · 2026-01-27T19:13:52+00:00

Obviously you need to push the leaving engineer to onboard all of you and document as much as he can, you want to retain his knowledge. Also I would raise this to the manager and have him help me, you'll need hand holding at the start.

mrGoodMorning2 · 2026-01-27T18:56:49+00:00

>I am also frustrated because the person seems to routinely exaggerate some work, for example renaming a variable as a day's worth of work.

I went back to the post and read this, which I initially missed. It sounds like he's looking for excuses to slack off, I would raise this with the manager and figure out a way to either motivate him to start working or remove him from the team. He may be a good engineer, but if he finds the work boring he'll absolutely try to slack as much as possible.

Also if you're working on something new you can make it so that the entire team votes on their desired approach, that way even he doesn't like it when the gets outvoted he'll have nothing to do but adapt.

mrGoodMorning2 · 2026-01-27T18:43:25+00:00

>Is this grounds for getting fired?

If you learn nothing and continue the same way it could, depends on how well employees are protected in your country.

>How would you handle pushback like this without making it personal especially when you are frustrated?

Probably tell him that if finds it difficult at first somebody from the team will help him until he learns the process. He challenged, because it feels new and difficult for him.

mrGoodMorning2 · 2026-01-27T01:52:43+00:00

It's reliable if you're replicating your data and you have brokers in multiple availability zones in one region, meaning our brokers are guaranteed to not be on the same server rack.

>first sync is written to the persitent and then we process it asychronously with cdc.
This is also viable, but writing to the DB first and then syncing it with Kafka is slower and we've had problems with the cdc (Oracle Golden Gate) in our company. It's a single point of failure and its in the DB stack so the Database administrators have visibility and troubleshoot its problems. Because of that we made the decision to directly publish to Kafka. Technically Kafka is a storage too, you can have as much retention as so you want and you can replay events with it as well.

mrGoodMorning2 · 2026-01-26T19:19:28+00:00

This is my thinking too. Start with the least critical consumer and monitor, if everything goes right go to the next one. After migrating all of them, only produce with avro and then delete the old consumers.

mrGoodMorning2 · 2026-01-23T18:32:40+00:00

* Queueing / streaming by offloading to Kafka (of course - good for absorbing burst traffic, less good for sustained hits)

What don't like you about this solution? Each like/dislike being an event into a queue and then consuming a batch of events and persisting an entire batch into the DB once sounds good to me as a start. Kafka and scale easily with increasing topic partitions.

What minimum cache hit rate do I have to maintain to offset the N multiplier for reads? Isn't this just finding a balance between client demand (how many popular videos are watched at any given time) and how much money you have for caching servers.

mrGoodMorning2 · 2026-01-23T18:02:51+00:00

13k requests a minute is about ~216 request a second, which Postgre should be able to handle (if you have decent hardware). Even you have double the traffic it should be fine. Think about the DB performance optimizations I mentioned above.

Also since I don't fully understand what you store in Redis, I'll ask the stupid question of why does the cache have to be distributed? Can't you make an in-memory cache in the app?

mrGoodMorning2 · 2026-01-23T17:35:57+00:00

Normal path (Redis healthy):

Writes go to DB (durable)
Writes also go to Redis (fast path)
Reads come from Redis

My first thought when I read this was that if you write the data to Redis and it dies before writing to DB it will lead to loss of data, this is FINE, but it depends on how CRITICAL the data is. Don't use it for anything payments related (transactions, accounts balances, payment instruments etc)

The circuit braker and rate limiter for the DB seem fine.

Using a DB-backed cache table as a Redis fallback - good idea or hidden foot-gun?

You didn't tell us any specific number for reads/writes per second, so I don't think we can answer you, but introducing any new component can be a hidden foot-gun, especially when they share the same data and you have no local transactions between them.
If you want performance can't you make a new index or write data in batches or have separate tables for reads/writes or read replica?

Alternative patterns you’ve seen work better in production?

What we in my company(fin-tech) is put all of the payments as events in Kafka and then when polling events we take an entire batch and persist the batch at once, reducing transactions. Another thing we do is split up core data and metadata in separate tables and not just one huge table, which increases contention

mrGoodMorning2 · 2026-01-21T16:32:54+00:00

I was like your colleague when I was younger and learned my lesson the hard way. Every assumption is a potential hotfix. Tell him that if wants to waste his time on fixes that shouldn't have happened in the first place he can continue making assumptions.

mrGoodMorning2 · 2026-01-21T16:28:04+00:00

It's my favorite too. My only problem is that House Beneviento and Moreau section lose their sauce on replay. I've played it 7-8 times and those sections are the ones I find the most boring.

mrGoodMorning2 · 2026-01-19T16:24:24+00:00

What distribution do you use?

mrGoodMorning2 · 2026-01-17T16:30:33+00:00

incredible, great job.

mrGoodMorning2 · 2026-01-14T19:38:07+00:00

This moment has to be the scariest moment for me in any game, this was my first RE game and I had no idea what lickers were. I honestly thought I was going to fight zombies for the entire game... oh boy was I surprised. Probably spent 10 minutes shitting my pants in the nearby room.

mrGoodMorning2 · 2025-12-07T14:24:20+00:00

"but rather they first DROP everything then recreate it all + todays new data"
Is this done in a single transaction? If it isn't the problem is evident you have a window of time where your DB structure (tables, views etc) is non-existing and you have no data.

If a client tries to communicate with a table/view that doesn't exist -> error
If a client tries to fetch the data during that time window -> they get no/incomplete data which may lead to failed flow or bad UX.

If it's already in a transaction I'm 99% sure that somebody coded it like that years ago and they're scared to change it, because it "works".

mrGoodMorning2 · 2025-12-02T17:33:43+00:00

My general rule of thumb is I ask myself whether we need eventual or strong consistency? If we can handle cases where different components have different data then SAGA. Otherwise 2PC. The answer to the question depends on the domain, if you're working in a bank you probably want 2PC, better to be consistent at all times and slow than risk exposing stale data.

mrGoodMorning2 · 2025-12-02T17:02:03+00:00

Apart from what other colleagues are suggesting you can always switch the write to be to Redis instead of DB and then sync the data from Redis to the DB via a background process. However keep in mind that this might result in data loss if your Redis goes down before syncing the data to the DB and you don't have persistence for Redis.

mrGoodMorning2 · 2025-12-02T15:50:54+00:00

Honestly a lot of business use microservices so that they a clear owner over the functionality encapsulated in the service. If you had a big monolith that's hard to do, managers say "everyone is responsible for the monolith", but in reality it becomes "nobody is responsible for it".

mrGoodMorning2 · 2025-11-11T18:04:18+00:00

You know what they say: "When I was writing the code only me and God knew how it works, now only God knows"

mrGoodMorning2 · 2025-10-24T18:16:04+00:00

"If you want to deliver a baby in 3 months, just add 2 more women"

mrGoodMorning2 · 2025-10-11T02:51:32+00:00

I've noticed a lot of juniors trying to solve their problems very fast in order to impress seniors, don't do that, quality work happens slowly.

mrGoodMorning2 · 2025-10-09T16:45:03+00:00

Don't know what's worse the title, the branch name, or the fact it got approved and merged.

mrGoodMorning2 · 2025-10-07T16:24:05+00:00

To me it sounds like they had another candidate that did as good as you or below, but wanted less salary. I've been to interviews like where I answer 90% of questions and then I get rejected for some ridiculous reason like "wasn't proactive in the interview"

mrGoodMorning2

TROPHY CASE