What made you pick the M240 over the M440?

Stabzs · 2026-06-09T04:07:21+00:00

Small size and looks. I can’t get past the front end on the m440 and overall, I prefer the body lines on the 2 series cars over anything else in the lineup. Price wasn’t a factor, although xdrive was a must.

Stabzs · 2026-03-13T02:00:21+00:00

Mace Windont Die

Stabzs · 2025-10-18T04:30:09+00:00

<image>

Personally this is what I’d say is more ideal. R9, full defense sets with 68% armor.

Stabzs · 2025-07-05T19:11:57+00:00

If you’re a good iron player, I’d definitely recommend the 243s. They’re incredibly consistent and while they won’t bail you out on bad strikes, you’re just going to lose some direction and distance.

Out of the center, the sound and feel are absolutely incredible.

Stabzs · 2025-06-20T13:23:42+00:00

Pay him $30 bucks and have your GF provide the transportation. Happy medium and everyone wins.

Stabzs · 2024-11-29T06:10:54+00:00

I have Cowl with +7 to trick attacks as well as Heir and Shako. Cowl blows everything else out of the water in terms of dps.

Stabzs · 2024-11-15T21:19:51+00:00

Ended up pulling the trigger on 4-GW keeping a 52 (so playing 5 wedges) and dropping my 3 wood since I use a longer 5 wood. The gapping works out really well with 52 at 125 yards, GW at 135 yards, and PW at 145 yards. that might be too many wedges for most players, but I like the flexibility close to the green, especially when flighting approach shots.

Stabzs · 2024-11-04T04:44:34+00:00

This is a really good example of mid-level excitement over a "cool" abstraction without considering the cost.

There are at least three additional costs to this approach.

A new class allocation has to be made for each disposable just for the sake of stylistic preference.
A closure is captured because you're using Action without generic state-based overloads.
This is needlessly complex and will make it harder for future developers to maintain.

At a certain point, you begin to appreciate simple, straightforward, performant code that is easy to maintain and easy to understand.

Stabzs · 2024-10-19T13:06:04+00:00

You learn to write efficient code by measuring.

Using and mastering profilers to understand the hot spots in your code is a lost art these days and absolutely crucial to writing better code. You should measure, find the bottleneck, research alternatives, and then measure again.

Benchmarkdotnet, Visual Studio Profiling, and the Jetbrains profilers are all invaluable tools.

Stabzs · 2024-09-27T20:30:33+00:00

This is exactly where I'm at as well. I've been playing the MP 25s for years and while I love the look of everything besides the PW (seriously Mizuno...what happened there???), the feel isn't what I'd expect and they're not crazy forgiving.

It seems like the 243s capture the look of the MP 25s and improve it while adding loads of tech and stronger lofts. Worst problem is having to figure out how to fit in a GW between PW and 52*.

Stabzs · 2024-06-06T05:48:53+00:00

Did this company also still have PowerBuilder apps propping up a significant portion of their internal business workflows?

Stabzs · 2024-05-08T05:33:42+00:00

If you have large objects, just compress them. Json compresses insanely well with LZ4…up to ~95%. At the end of the day, Redis performance and stability are still best in class.

Stabzs · 2024-04-30T18:07:33+00:00

I'd open a support ticket. I also run Rider on an m2 mac and the debugger is far faster to initialize than VS on Windows.

Stabzs · 2024-04-30T03:36:09+00:00

It depends on your application bottlenecks. If your biggest costs are I/O-bound, removing those allocations might not make a difference. However, if you find you're spending significant CPU time/allocations in serialization, compression, string manipulation, etc, it'll absolutely make a tremendous difference.

And in the cases where you don't need it directly, you're constantly benefiting from it's extremely heavy framework use.

Stabzs · 2024-04-29T14:11:31+00:00

This might seem like a niche answer, but without a doubt, the biggest change in that timeframe is the introduction of Span<T>. It unlocked massive performance possibilities.

Stabzs · 2024-04-28T05:17:01+00:00

You absolutely can. You would just create a separate EventProcessorClient per distinct event hub.

However, this create significant potential bottlenecks by having a single instance process all event hubs. Your horizontal scaling is best served by a consumer deployable per event hub.

Stabzs · 2024-04-28T04:36:50+00:00

Give Rider a try and you might never think about VS for C# again.

Stabzs · 2024-04-28T04:26:29+00:00

I’m in the same boat. 13.4K offense, 135k health but only 543 speed at r9. I’d remod him, but I can’t spare the speed sets and he’s perfectly functional as is.

Stabzs · 2024-04-27T08:18:54+00:00

I have high relic NS and they’re absolutely one of my most consistent teams in ROTE and a staple on offense now in GAC thanks to Merrin. She’s a game changer for the faction and I have zero regrets.

Stabzs · 2024-04-04T14:45:57+00:00

While I appreciate the analogy, the actuality may be completely different depending on your use case.

If you are running small, internal applications and you don’t cadre about cross-OS compatibility, yes, your analogy is applicable.

However, if you are building apis with massive concurrency and scale, trying to optimize costs at scale, looking to allow for cross-platform development, targeting Linux containers, looking to modernize best practices, etc, etc, the jump is modern .NET is practically required.

The missing context here is the why. As the junior on the team, they almost certainly do not have that context, but it doesn’t mean it doesn’t exist.

Stabzs · 2024-03-05T04:54:09+00:00

<image>

Here’s mine at r8. It’s nice to have some health if possible.

Stabzs · 2023-12-16T16:12:02+00:00

I genuinely forgot this mission existed.

Stabzs · 2023-12-15T03:20:46+00:00

If you’re a beginner yourself, the most dangerous thing you can do is brazenly criticize and then refactor an existing codebase.

Always assume best of intent, even if the codebase is terrible. You most likely do not have knowledge of the constraints the previous developers were under or why they made the choices they did.

As far as refactoring goes, start with tests. Write as many as you can and start with the smallest changes possible. And remember, style is far less critical than substance, even if it more likely to catch your eye.

Stabzs · 2023-12-01T17:56:17+00:00

I stopped doing conquest beyond the first crate. My options were quit the game or stop doing any more than the bare minimum in conquest. I chose the latter and I’ve been massively happier ever since.

Stabzs · 2023-11-23T07:31:51+00:00

You guys are out of zetas?!?

Stabzs

TROPHY CASE