rossta

The article is about a _green reading_ technique called Aim Point rather than the putting stroke itself. In the title, "putting technique" might be interpreted as "putting stroke" and I would consider green reading and putting technique separate albeit very closely linked skills.

Aim Point is the brainchild of a software developer. It reminds me golf as a game is deserving of more attention on HN. Technology has changed the way the game is played and consumed significantly in recent years. Here are just a few examples:

- Most courses all over the world are mapped and available in a variety of GPS devices, including smart phones and watches allowing players to determine distances to the green (and intermediate obstacles) on every shot

- Sensors can be attached to clubs that, when paired with GPS, allow software to help the average player track with precision how far they hit each club

- Tracking shots over the years has yields millions of data points which now inform ideal course management strategy

- Launch monitors can measure the ball at impact to provide near instant readings and predictions of ball flight like distance, ball speed, club head speed, club path, angle of attack, spin rate

- "Shot tracing" technologies have emerged that provide video of a golf shot with an overlay of the ball flight (which I find make the game more enjoyable to watch)

- Design and production of clubs and golf balls themselves have undergone massive amounts of research and analysis—some manufacturers now claim AI driven design—to produce longer, straighter shots

At its core, golf is a physics problem. Player swings a device, imparts a force on an object, and observes the result. It lends itself very well to empirical analysis. And yet, despite this simplicity and all the technological weight thrown at the game, average players scores have failed to improve. There is still an art to the game that can’t be mastered with technology alone.

Beautiful game.

Bummer, I can’t reproduce. Could you share more details?

I have heard a few people mention issues but I haven’t been able to reproduce nor understand the scope of the issue. Any more details you can share? You’re getting HTML but JS or CSS assets aren’t loading, right? What status and headers do you see for static assets?

That’s fair. I acknowledge that terms like "horizontal" and "vertical" may be overloaded or even confusing, in this case, if it’s difficult to see the connection with the visuals. This is somewhat part of the risk in trying to explain a concept in a less-than precise way to introduce a new concept.

Thanks for the feedback. I was thinking along those lines but settled on a version that let you toggle between the two. I’ll keep this in mind for next time though.

There are probably a lot of fun variations to explore. Since this post seemed to resonate, I may be motivated to try some more experiments.

I don‘t speak for Noah’s family but can share from my experience.

I lost my wife suddenly and unexpectedly. The event was intensely traumatic for me and devastating for our extended family. One day, she and I were planning for the future. The next, I was left to raise our child by myself. In many ways, now several years later, I am still picking up the pieces.

In the days and weeks following her death, I did the work of making public announcements about her passing, funeral arrangements, collecting stories and photos to share with our son. I received many questions asking how she died.

While I appreciated the concern and believe it fair to be curious, I chose not to share details outside of our closest friends and family. The last thing I wanted to do was relive the experience. For me it was too painful.

Honestly, I could care less about the public perception. It has had no bearing on my grief and responsibility to our son and extended family. I have not spent one ounce of energy thinking about how my choice has affected others outside our closest friends and relatives—they are the only ones to whom I have ever felt any sense of obligation. I have no regrets about this.

As for Noah’s family, I respect their decision, whatever it may be, whether conscious or not. My heart goes out to them.

I remember meeting you at a DC Ruby conference after a talk you gave on middleware as a design concept. This was years ago, in the early days of Vagrant I think. Amazing to see how much you’ve accomplished since then. Congrats on your achievements and best of luck with your future hacking!

Similar goals, different philosophies and approaches.

A few differences: HTMX makes it possible to enhance any element with hypertext capabilities. I don’t believe it works with JavaScript disabled. Hotwire still relies on <a> and <form> to make HTTP requests as its focus is more geared towards progressive enhancement; the Hotwire portions of the app will still work with JS disabled.

I got my start in web development right around the time Ryan started RailsCasts, the early days of Rails. He inspired a generation of developers, me included, to learn the ins and outs of the framework and its ecosystem. His weekly posts were required viewing. I’d catch myself at work using his catch phrases: “Yay that works!”

I’d encourage anyone who hasn’t seen RailsCasts to check it out. Many software content creators follow in his footsteps. He set a standard for teaching through screencasts that still holds up today.

I’m looking forward to reading the rest of his series.

LOL this was my favorite comment