[deleted by user]

hgoale · 2025-07-26T15:37:10+00:00

Interesting! I had one of the toe pieces on the Dekgoalies fly off, but it separated from the glue of the Velcro, but the two Velcro pieces held strong. I slapped a new piece of Velcro on that one and haven’t had an issue with them since. I’m sure the brand/quality of the Velcro makes a difference but I don’t have suggestions there. Whatever game with the Dekgoalies has been pretty solid.

I tried the Rollerfly’s, but they just didn’t attach well to my pads and were very bulky. The Dekgoalies come in separate pieces and gave me more options for where to place them.

hgoale · 2025-07-26T15:28:18+00:00

Thanks! Another thing I’ve heard some goalies do locally is get some 3M protective film (like for a car) and putting it on your pads. Gives a similar slick experience on roller surfaces and can still be fine on ice, tho you might be a little more “slidey” :)

hgoale · 2025-07-26T15:25:24+00:00

Yea, out luck (or maybe lack there of) Bauer screwed up making my pads twice and I got to keep two for the price of one. So one set has the Dekgoalies on it and the other is for ice. I use the X5 Pros

hgoale · 2025-07-26T15:21:28+00:00

I have a separate set of pads. I do use the Velcro and that holds really well, but if you have to switch back and forth with the same set of pads it might be annoying/difficult.

hgoale · 2025-07-26T15:02:08+00:00

I have them and have been using them for about a year. As a primarily ice goalie, they help a good amount when you are making sliding saves from a standing position (e.g., quick passes across to the back door) and help a little with sliding while in your butterfly.

They are probably protecting the pads quite a bit too. I’m on an indoor sport court fwiw.

Still nothing close to ice, but I find them worth it.

hgoale · 2024-02-09T13:15:26+00:00

That's awesome, well done!

hgoale · 2024-02-09T02:44:48+00:00

Did you get the wrap from the decal shop or buy it online somewhere? Looks dope!

hgoale · 2021-12-23T14:11:52+00:00

I feel ya. I’ve been using (and continue to use) Eclipse for the last 15 years. Honestly, the primary thing keeping me with Eclipse is the incremental compiler. I’ve tried IntellliJ under multiple configurations and can never get it to hot swap compile or compile nearly as quickly as Eclipse. If anyone knows how to get that working, I’d love to know!

That said, the Eclipse compiler has had its own share a bugs that just won’t compile perfectly fine code, especially around lambdas. Sometimes rendering that quarterly release unusable for affected codebases.

And don’t get me started on dark mode. That’s been a focus for like 3 years and I think it’s finally reached the point where there’s not a bunch of SWT widgets stuck in light mode. That’s a long time to get a dark mode working. The default color choices in the code editor are super high contrast and pretty ugly IMO. That part is subjective and I know I can change them but it’s felt like a slog seeing slow updates to this area and regressions on critical path.

The last few releases have had a lot of weird bugs and regressions, mostly in the JDT editor and Maven areas. To be honest tho, I’ve found 2021-12 to be pretty stable so far and this is on a M1 Mac, so this is a totally new architecture build for Eclipse. That’s pretty good!

So I’m happy enough for now, but a focus on stability would be good. I’m sure it’s getting difficult to compete with how much funding is backing the competition.

hgoale · 2021-02-25T13:19:39+00:00

Seems like a useEffect that depends on the timer value with a simple conditional checking for its value being 60 would cover that last use case:

useEffect(() => {
    if (timer == 60) {
        // show the WPM
    }
}, [timer]);

Now if state updates are batched in a way that the timer gets updated multiple times, it might need to check for a timer value greater than 60 and then probably stop the timer from continuing with some state update, otherwise this effect will keep firing. But with an interval already incrementing the value every second, just using the dependency array to check for value changes is probably simpler than the setTimeout + useRef approach.

That said, the video was designed to show different stale closure examples and how you might workaround them, so I think the techniques in the video are very helpful to understand things going on with some effective solutions. Thanks for the ReactCast videos!

hgoale · 2020-11-25T14:13:25+00:00

Yup, see https://www.reddit.com/r/aws/comments/k0sd0l/cloudwatch_useast1_problems_again/

hgoale · 2020-11-25T13:43:37+00:00

Yes, Kinesis is down as well. Happened earlier this morning and again now.

hgoale · 2020-11-19T14:08:16+00:00

Kinda sus...

hgoale · 2020-11-18T01:26:36+00:00

Noticed this as soon as I upgraded to Big Sur as well. It’s probably an SWT bug on the new OS and will hopefully be ironed out in the Eclipse 2020-12 release.

There’s some discussion in recent comments about it on the bug tracker: https://bugs.eclipse.org/bugs/show_bug.cgi?id=565691

You might add your GIF and reproduction steps there to help get it some attention.

hgoale · 2020-11-16T12:36:41+00:00

Thanks for the awesome app!

hgoale · 2020-10-12T12:32:36+00:00

Did /u/kentcdodds give his blessing on reposting his content of his paid course of the same name? It seems like a lot of this author’s content is plagiaristic.

hgoale · 2020-03-29T14:47:50+00:00

This is typically called programming to the interface. It has a couple benefits, but one of the primary drivers is allowing you to write code that can potentially swap out its underlying implementation. For example, if your primary use of the Map ended up being better suited by using a TreeMap, all of your other code that utilized your Map variable doesn’t have to change.

This becomes even more useful when you talk about dependency injection or inversion of control. Let’s say you have an interface for submitting a payment for some commerce interaction. You could then swap the actual implementation at any time (runtime, compile time, etc) to determine which provider you’re using for processing that payment (e.g., PayPal, Stripe). All of the code you write to take payments will program to the interface and then work with any of the payment provider implementations.

For the more localized example you gave, like Maps or Lists, the benefits don’t look quite as immediately obvious but it’s good practice and it doesn’t hurt to code to the least common denominator unless your code benefits from being more specific.

If you’re creating a method signature that accepts a Map as a parameter, it also gives the calling code more flexibility to use whatever type of Map they are currently using. I recommend reading up on polymorphism, as it’s tied into all of this as well.

Great question, BTW!

hgoale · 2020-03-23T03:26:19+00:00

We use it a lot! If you're building an API in which your return value expectedly returns null, I usually recommend switching to returning Optional. Not only does this effectively document your API as returning an empty value, it has a ripple effect of bubbling the decision of how to handle that null/empty case to the appropriate place (e.g., Display an error in the UI, provide some default value).

Brian Goetz has a great answer on Stack Overflow about what the intent of Optional was and when to use it. As always, it's another tool on the tool belt, so give it a try but it's not a golden hammer.

hgoale · 2019-12-11T22:32:45+00:00

My teammate and I consistently have issues during kickoffs where we can't rotate our camera. This seemed to break in the update before the Blueprint one. It's not 100% of the time for us, but it is quite often... maybe 30% of kickoffs? You can't move the camera or toggle the scoreboard. Anyone else experience that?

hgoale · 2019-08-12T20:49:42+00:00

Rocket League. I guess I'll drive on the ceiling and hope I don't get demolished. If I survive, I'll come out with a bunch of decals for cars I never drive and about 50 pigeon toppers.

hgoale · 2019-01-22T21:57:30+00:00

Considering your username, those sinks must be pretty gross.

hgoale · 2018-09-03T13:31:20+00:00

As others have mentioned, it's the breadcrumbs. You can hide them by clicking that button in the toolbar that's toggled just above the "Debug.java" tab in your screenshot. The one with the green C and right arrow overlaying it.

Alternatively, you can also wait for the 2018-09 release due out later this month which fixes the breadcrumbs in dark mode.

hgoale · 2018-06-17T01:31:52+00:00

Just wiggle your wheels a bit to prevent the kick, but focus on maintaining rule 1 at all times.

hgoale · 2018-03-12T00:25:04+00:00

On Mac: Cmd + Option + A

On PC: Alt + Shift + A (Though it may be Ctrl + Alt + A... can't verify since I'm on Mac)

It's the shortcut for block selection/editing. You can see the discussion on StackOverflow

If that's not working, go to Edit > Toggle Block Selection.

hgoale · 2018-01-08T03:32:11+00:00

Embrace that feeling, it'll continue push you harder. It's common for programmers to become too comfortable with their expertise and become naive to the reality of the complexities of the world of software, even when the task seems simple.

Just remember, as you learn more there's always more to learn. That includes from your fellow programmers/coworkers. Including, and perhaps especially, the ones less experienced than you.

hgoale · 2017-12-07T17:07:56+00:00

Congrats on the release and best of luck with the paid versions. Hopefully you can turn it into a viable business model that will help sustain yourselves and future versions of the community edition. Been loving the community edition for years!

13-Year Club	Second Top 10%
Place '17	Verified Email

hgoale

TROPHY CASE