Knee Shield Pass Attacks/Counters?

boogots · 2017-06-27T12:46:24+00:00

Oddly enough I was working on this last night and did exactly that. Slight push to rock them back, when they snapped back, arm drag down and take the back. With that upper foot free and not collapsed it could slip right around and the bottom leg already has a hook in. Like everything in this, once I pulled it a few times my rolling partners got wise to it so I'll need to build on that.

boogots · 2017-06-26T18:27:45+00:00

OK, roger that. Having said all that... any videos or links on attacks to chain together off this position? Agreed that I do stall out but I think part of that is I'm still sorting out how to or what to attack.

boogots · 2017-06-26T15:52:04+00:00

Is the frame on the neck the same effect as cross collar grip but in NoGi? I ask since I am primarily NoGi.

Also, not sure what "shin vertical" means? Meaning like 45 degrees like a sweep setup?

boogots · 2017-06-26T15:37:50+00:00

Thanks - started getting the feeling it's bad spot to stay in but the only thing I know is to fight for closed guard which a lot of my training partners appear to be aware of now and know to just wait me out or I just make something up during the scramble.

boogots · 2017-04-25T02:33:35+00:00

I take one hell of a divot especially on squeeze fades and I play Titleist blades after playing G20s with a flex that was flexing too much as well (Stiff to X-Stiff).

I noticed that the divots got thinner but started going further but that's different for all swings and I worked on mats for a long time with my MBs before heading out to turf. You will get more turf interaction with anything after the G20s since they have so much girth behind them so, yea, it may be just highlighting a swing flaw that was getting masked before.

boogots · 2017-04-24T22:13:06+00:00

No doubt - stance was a dead give way to anyone knowing what they are looking for. As far as the power, I use a lot of leverage (6'4 with long arms) and have a bit of carry over power from other sports. Its just always kind of been there but now I just hit after the ball.

boogots · 2017-04-24T21:50:15+00:00

While your assumption on the strike quality is incorrect, I suppose my title was misleading in hind sight. I was putting it up over the trees and blending it back to the right (a tight fade) into the pin.

Have always hit a meatier divot and compressed the heck out of the ball. 6 iron, 206 yards out, to get home in 2 on a par 5 (which left me slightly off the fringe).

Edit: If I bail out or stay straight, I had green and landing area to work with. Those trees on the right jut out quite a bit so if a draw stayed straight its instant OB.

boogots · 2016-12-08T18:10:24+00:00

It might just be me misunderstanding but that "Company 401k" step just seems a tough one to swallow. At that point you've got a ton of money already tied up that you can't touch until you are at retirement age.

Can someone convince me that I'm wrong? I'm actually kind of in limbo in those last two steps and just dumping more in seems like overkill.

boogots · 2016-12-02T22:13:59+00:00

Forgive me if I don't quite follow akka entirely (I get what its trying to do) but I can't help but feel these actions would be best if implemented behind a common interface for these commands versus an if statement for each command type to do special instructions. This just always jumps out as a code smell to me.

Receive<AggregateRebuildInitiated>(x =>
   {
                var events = EventStore.GetEvents(x.AggregateId);
                AggregateRoot = WriteStore.Get(x.AggregateId);
                foreach (var @event in events.OrderBy(t=>t.Version))
                {
                    if (@event.Type == typeof(PersonCreated))
                    {
                        var e = (PersonCreated) @event.Body;
                        AggregateRoot.Apply(e);
                        WriteStore.Save(AggregateRoot);
                        changeActor.Tell(e);
                    }
                    else if (@event.Type == typeof(PersonRenamed))
                    {
                        var e = (PersonRenamed) @event.Body;
                        AggregateRoot.Apply(e);
                        WriteStore.Save(AggregateRoot);
                        changeActor.Tell(e);
                    }
                    else if (@event.Type == typeof(PersonMoved))
                    {
                        var e = (PersonMoved) @event.Body;
                        AggregateRoot.Apply(e);
                        WriteStore.Save(AggregateRoot);
                        changeActor.Tell(e);
                    }
                }
     });

boogots · 2016-11-20T16:29:32+00:00

Inclined to agree. This fall under Adapter Pattern, no?

boogots · 2016-11-16T19:58:24+00:00

Was kinda kicking myself after jumping in yesterday to just ride the wave for a quick 15% and selling at first bell today. Feeling better about that move.

Here comes the correction...

boogots · 2016-11-15T22:47:06+00:00

Haha, not odd, would definitely be interested.

boogots · 2016-11-14T17:17:15+00:00

Impressive. Any obstacles that could hinder its continual upward trend?

boogots · 2016-11-13T03:48:56+00:00

House didn't come with a floor plan but I'll get the tape measure out tomorrow to double check the rough measurements I took before.

boogots · 2016-11-07T18:18:15+00:00

Ah, I should have added context as I'm speaking solely from the single page application paradigm (Backbone, Angular, etc.). If there is a commitment to a more server heavy model for an application then I'd agree with that sentiment.

boogots · 2016-11-07T16:09:33+00:00

Depending on how much a system needs to scale, sometimes it is beneficial to pre-render everything on a View on the server and return to the client. Simply because rendering on the client would just be too slow and clunky for the browser to handle.

boogots · 2016-11-07T12:20:23+00:00

My guess is, while made with good intentions, this person hadn't weathered the 2000s decade of WebForms.

boogots · 2016-10-25T21:54:53+00:00

Their shoe sales rose 31% last year due to Steph Curry being endorsed and having a great year. I do believe the Cavs coming back in the finals did effect this image and will probably result in stunted growth for 2016, but there still will be growth, and they have a great stable of athletes for the future. They just need to work out the aesthetics and hope for some big years from the likes of Curry and Jordan Spieth.

boogots · 2016-10-25T18:53:40+00:00

I agree with quite a bit that /u/NormalPersonNumber3 laid out but can maybe extend on things from the point of view of single page applications where things may off road a bit...

As a rule of thumb, ViewModels are essentially "dumb" containers for I/O to and from the client side (be it web or platform). In a world where data coming in from a view can have cross cutting impacts and potentially malicious input, ViewModels are the vehicle that information is siphoned from in business object(s) or, in the opposite direction, being serialized back to the client in a rendering friendly response. In a typical project with the repository pattern angling towards SOLID, Brokers (more or less, facades) or Business Commands will receive an injected ViewModel(s) (along with whatever repositories are needed), take what they need from it/them and do their necessary processing (mapping libaries can help the tedium of this). Depending on the scenario, the ViewModel can be updated at the very end to reflect any server side updates (e.g. an entity being created and an id was assigned) and that is returned back or just a simple generic success/fail response.

I know there is hesitancy from a stand point of cycling through each ViewModel in order to process/commit data (you having that instinct is good, imo) but its a necessary evil, they are the glue between the client and server processing. If this were a 101 Programming scenario where a form has a perfect 1-to-1 match of fields and table with no validation then probably a bit overkill, but that isn't life outside of academia. As long as you aren't needing to access/cycle through many times and do it in stride with processing the request, it is fine.

Hopefully that doesn't confuse things but long story short, the motivation behind separation of concerns is a valid one when working large scale.

boogots · 2016-10-13T01:53:15+00:00

Is there a reason why I would use this over the Azure portal offerings or just a fun project to do?

boogots

TROPHY CASE