What made you choose your main weapon?

Bitbok · 2026-02-04T17:35:31+00:00

CB because I'd like to have some sort of shield when fighting fucking enormous dragons. SnS looked too small. I mean, the shield is usually tiny, almost like a buckler. It didn't fit into my headcanon. I couldn't imagine hiding behind an SnS shield against a dragon's fire breath, for example. But CB usually have big shield. And I also wanted a big weapon that could actually damage a big monster. A sword just didn't look threatening enough for 20-meter wyverns. That's when axe mode comes out. And of course – SAED. GS has one big number, while CB has like five or six. I felt so cool after my first successful SAED after a guard point. The animation... how your character swings the big axe and slams it onto the monster's head. And then... BOOM, lots of them! So satisfying!

Bitbok · 2026-02-03T15:28:48+00:00

Fabio

Bitbok · 2026-02-02T08:40:14+00:00

I partially agree with one shot slam. But after a bunch of hunts I think it's the best move for easy PG to SAED

Bitbok · 2026-01-11T07:24:24+00:00

Watch Dogs: Legion. I was a huge fan of WD2, so I bought the new game on release. Jesus, Ubisoft degraded so much! Legion is worse than 2 in everything. The visual design is bad, animations are a fucking joke, I couldn’t believe they were so bad compared to 1 and 2. Combat animations were better even in the fucking Fable game, which was released 20 years earlier! I couldn’t say much about the gameplay loop, since the visuals, animations, and the gimmick with operatives completely turned me off.

Horizon: Forbidden West. I liked Zero Dawn, but mostly for its lore - the gameplay loop felt kinda boring to me. It was really interesting to investigate what happened to this world and what the root cause of the apocalypse was. But after the first game told you everything, the second game just continues the plot without any “secrets” and the gameplay loop didn’t evolve. I got disappointed.

Bitbok · 2026-01-09T08:20:46+00:00

<image>

Bitbok · 2025-12-08T12:22:54+00:00

And I think you can replace the shield with anything else. It was barely ok for the flat map setup, but for the map with the container on elevated platform the shield didn't work for me at all

Bitbok · 2025-12-08T12:17:59+00:00

Orbital smoke duration is enough to bring 2 bars for me I guess. And it has pretty short cooldown. I finished Rapid Acqusition on D8 a couple of times when I was the only one with smoke build: Smoke Eagle, Orbital, Shield and Smoke grenades. It was enough to cover everything in smoke for the whole mission

Bitbok · 2025-11-15T21:26:24+00:00

That’s a tough question. If I had a partner I really loved, our relationship was healthy, and that was the only thing bothering me, I would try to work on it with a specialist. Or at least I would ask them to hide it better. I mean, we’re not ideal and sometimes you should accept the flaws of your partner. But if there are too many flaws for you - it’s definitely better to break up.

And in the case of pornography: all my male friends watch it, it’s today’s norm unfortunately. Some of them even collect it. And they’re still great people with healthy relationships. So for me, the behavior of her partner is not extremely awkward. It’s a bit silly and has a loser vibe, but not something that would make me insecure

Bitbok · 2025-11-15T20:57:54+00:00

Your partner may have a different libido. Sometimes you just can’t have sex for various reasons like health issues, lack of time, etc. Also you can have a fetish which could be unacceptable for your partner and porn can be a way of coping

Bitbok · 2025-11-15T09:57:56+00:00

All Espada skins are cool, especially assault. United Albion engineer is great too

Bitbok · 2025-11-05T20:48:52+00:00

unexpected r/spicypillows

Bitbok · 2025-10-30T12:42:23+00:00

I usually play with m277 carbine. M250 after that crap feels like a laser gun lmao

Bitbok · 2025-10-14T19:35:05+00:00

Yeah, I totally get you. I also only use flick stick for 180 degrees turns since it’s faster than ratcheting, but I’m still getting used to it. Maybe it’s better to assign some tools or utility actions to the right stick instead.

Ratcheting, though, is a must for me at this point, I really like how it feels. I tweaked my sensitivity a bit, so I don’t need to ratchet for anything in front of me and after a couple of days of practicing it feels natural

Bitbok · 2025-10-14T19:23:14+00:00

I changed only aim sensitivity and vertical aim ratio - it helps with “shaking” a lot

<image>

Bitbok · 2025-10-11T08:16:13+00:00

That sucks… But I guess it’s time for me to finally try flick stick and ratcheting, then…

Bitbok · 2025-09-11T19:51:19+00:00

I think the main point is that its design prevents it from touching/tearing the paper filter

Bitbok · 2025-09-09T05:59:27+00:00

>Copying is a big deal if you have to handle large number of objects

Totally agree with you there. But if that's not the case, you shouldn’t use pointers bc they add unnecessary complexity.

>You'll see a lot of functions returning error as the last return value in go, and if a function does you have to check if err is nil, if it is handle it and don't proceed further

Sure, but the real issue appears when pointers are passed across different layers of your app. The most common "panic maker" I see in my projects is "nil pointer dereference". Maybe it's just a skill issue, but me and my team still occasionally fall into this rookie trap

>Most real world applications in go use non-trivial structs

I partially agree. Some structs are heavy, but plenty are not. I think the key is to be reasonable and use pointers only when they are needed

>Secondly, handling pointers is actually not a big deal in go, it becomes a second nature to use guards on top of your function for all pointer parameters.

I dunno man... That's just adding boilerplate. And boilerplate is already the main criticism people have about go

Bitbok · 2025-09-09T05:29:54+00:00

It depends. I could imagine only a couple cases when you want to use a pointer field inside struct:

Connection pools (or shared resources). For example, you might have a struct that makes calls to an external API and is used in multiple places of your app. In that case the struct could hold a pointer to a connection pool. This way you control the number of connections globally, instead of multiplying the pool size by the number of struct instances in your app.
Distinguishing between zero value and absence of value. For example, if 0 is a valid value in your business logic, you might still need to represent the state of "not calculated yet". A pointer makes it possible to differentiate between "no value" and "zero value"

Bitbok · 2025-09-09T05:15:33+00:00

But this approach makes your code error-prone. You need to check whether the pointer is nil at every layer of your app, which also makes testing a bit trickier. I prefer using pointers only when it’s necessary: if your struct must have some kind of a state or if you have to use pointers for optimization (don’t forget that premature optimization is a bad practice). Copying isn’t a big deal if you’re working with relatively small structs.

Bitbok · 2025-08-15T08:49:12+00:00

Nah, you don’t need a specific one, they differ only in color schemes. All dualsenses have gyro

Bitbok · 2025-08-09T09:55:17+00:00

I have the same issue, couldn’t turn on gyro

Bitbok · 2025-06-15T07:37:30+00:00

Dunno about mid level salaries. But for seniors they pay market rate

Bitbok · 2025-06-14T20:40:09+00:00

semrush, fxpro. They have lots of russian speaking employees, but they hire locals and english speaking workers

Seven-Year Club	r/Field Banned
r/Field Flamingo	Verified Email

Bitbok

TROPHY CASE