I've had to contend with Conventional Commits both in the OSS world and at work as it proliferated from what seemed to me like robotic adoption by folks who were even loosely associated with the Angular ecosystem (remember that?).

I've always had a stance with KAC that folks trying to automate changelog creation (prior to LLM rise, mind you) were focusing on the wrong thing. I still think there's a fundamental difference in focus between what you write in a git commit and what you present in a changelog.

I know there are fundamental philosophical differences for folks who were used to HISTORY vs. NEWS vs. CHANGELOG but with the growing adoption of KAC-like CHANGELOG.md files and Release Notes (often not synonymous) I think we're thankfully past the weird era were maintainers dumped raw git log ranges between two tags and called that a changelog. I'm sure some still do it. But that's what Conventional Commits tries to replicate.

What's really odd to me is that this assumes (broadly) that every single commit in a repository is relevant to the eventual version release changelog (or release notes). Even if you assume some CC types get filtered and deprioritized from generated changelogs by some tools, it's still a huge miss on what communicating about a release typically means: these change likely matter to you as a package dependent or direct user, while others were omitted for good reason.

I'm trying to articulate that much more clearly in KAC 2.0 because there's a fundamental paradigm shift when a robot can now analyze recent work (yours or theirs) and craft changelog entries that appropriately shift the audience perspective from "git message for me/us in the future to understand this change" to "changelog entry for you/them to know what this group of changes means".

[0]: https://keepachangelog.com

[1]: https://github.com/olivierlacan/keep-a-changelog/pull/600 if anyone's curious and wants to get involved

From working on RubyGems.org a long time ago I vaguely remember that the metadata extracted from the gemspec is version-specific. So if you add a new native_extension boolean you'd have to artificially reprocess those previously published gemspecs to change the metadata for all past versions.

Being able to mutate metadata for past versions is dangerous enough that I'd be surprised it's allowed or even possible. So that might not even be something Aaron considered here for that reason. That said, it seems reasonable to me to suggest this improvement going forward to make unpacking the gem unnecessary to know whether it'll affect installation order.

https://www.france24.com/en/france/20251228-bardot-leaves-co...

Many outlets — including this CNN piece which is making the passive voice work real hard to make her awfulness about other’s perception of it — are slinging hagiographies as if death absolves all.

It's shocking to me how good Roborock mop-vacuums are for example, Eufy vacuums are nice as well. They still run into unavoidable issues, but they're: much quieter even at their highest setting; show you how they map out the space; allow you to easily customize routes or focus on specific rooms; do a shockingly good job at self-emptying; and best of all you don't have to rescue them from the exact same sliding door track every single time you run them.

Reading memories from the people Noah impacted in his life feels like a good way to understand the kind of person he was.

It's an underused treasure, however simplistic the UI may be.

See: https://www.nhc.noaa.gov/refresh/graphics_ep4+shtml/204534.s...

You can find individual static maps (sadly very low resolution) here as well for Hurricane Hilary: https://www.nhc.noaa.gov/graphics_ep4.shtml?start#contents

This kind of return on ultra flexible accounts is basically unheard of in most of Europe in recent memory as far as I know (born & lived in Europe as recently as 2019). What you describe are called Certificate of Deposit (CDs) in the U.S. and you can get 5.50% for those in August 2023 [1].

[1]: https://www.nerdwallet.com/best/banking/cd-rates

John Carmack is a very intelligent person who can teach you a lot about many extremely complex engineering-related matters.

Applying his advice on health and work-life balance without a full understanding of the many variables that skew his perspective and his own daily life is probably a bad idea.

Expertise is not automatically domain-transferable. Anyone claiming otherwise is suffering from hubris, or star-struck.

The only official Ruby documentation exists at https://docs.ruby-lang.org/en/ and is generated via the Ruby source code itself.

The excellent Colby Swandale has been working on a new open source alternative for Ruby documentation considering the design shortcomings of the default generated API documentation with https://rubyapi.org which I highly recommend.

If you're coming at Ruby from another language, the official Ruby site offers https://www.ruby-lang.org/en/documentation/ruby-from-other-l... and other documentation aside from API concerns here: https://www.ruby-lang.org/en/documentation/

Hope that helps.

The site presents evolutions of Ruby since version 2.0 in an editorialized and well-written categorized release journal called "Ruby Evolution": https://rubyreferences.github.io/rubychanges/evolution.html

There's also individual version releases annotated as well, for example for the recent Ruby 3.2: https://rubyreferences.github.io/rubychanges/3.2.html

Note that these are not copies of the NEWS.md typically released when minor and major versions of Ruby come out. Victor specifically spent time to write more descriptive notes of what each notable change occurred over time. It's an incredible resource and we're extremely lucky to have him in our community.

There's even a changelog for this meta-changelog, which makes my little Keep a Changelog heart sing, so you can see evolutions of this site over time as well: https://rubyreferences.github.io/rubychanges/

HVAC installers are not merely system assembly specialists, they're system design specialists as well in nearly all cases. Or at the very least they outsource HVAC system design to experts who are familiar with required air flow, static pressure, air changes, condensation formation and evacuation, and yes of course whether the system is appropriate for cold climates (cold climate heat pumps are notably different from temperate or hot climate ones: coils are larger to capture more heat from the air outside temperatures are very low); they have different refrigerant systems; and way more insulation to prevent the cold affecting operation; some even incorporate resistive heating elements... or a gas furnace in cases where their efficiency would drop below an acceptable threshold.

One of the biggest and most important part of an HVAC system design is sizing for climate and dwelling. It should be extremely suspicious to any installer that their design system efficiency would be so much higher than the real world system performs.

I'd be shocked if professional HVAC installers couldn't spit out several reasons why the system might be performing so poorly just by reading this blog post. Notably the absurd assertion that the installers were professionals despite wildly overpromising and underdelivering. Some contractors acting professionally doesn't make them professionals.

As others point out in this thread, implementing a system that meets the stated design goals roughly on target is what a professional does. I've seen some absurd lambasting of PV solar installs as an example of empty promises. Again, those are tell-tale signs of deficiencies, not an indictment of the underlying technology.

Which is the most irresponsible part of this senator's post. Given your post and prominence, the least you could do before publishing something like this is check your basic assumptions: that the installer did a fine job.

1. https://pathofthepanther.com

2. http://floridawildlifecorridor.org

I believe the documentary should be released on Disney+ in late April but it already premiere in some theaters in Florida.

These folks are doing incredible undervalued work to protect endangered species in the Southeast US. They're also trying to prevent Florida from building multiple new toll roads cutting through pristine inland areas of the state which would devastate already struggling ecosystems due to the rising waters in the Everglades.

Ask them when they realized that their work was extensible to any radio frequency client (cell, Bluetooth) and used for targetting missile strikes. I can guarantee you know at least a few people in the industry who did.

Just because we can doesn't mean we should. This story reeks of DoD funded research which somehow gets whitewashed as "cool new tech thing!" on tech blogs when it should really be sending chills down your collective spines.

This capability may be fringe and nation-state controlled for a few years, then it will inevitably fall into the hands of large and well-funded criminal organizations, abusive spouses, and of course overfunded trigger happy SWAT teams — who will still manage to get their court order addresses wrong and kill innocent people and pets over a no-knock warrant.

All this triggers in me is the irrespressible urge to get technologists to finally get it through their thick skulls that what we do does kill people exactly like doctors. We've just refuse to take responsibility for it when any other industry would have seriously discussed ethics board and licensure at this point. No matter how complicated such an effort would be.

  - no touch screens
  - no embedded screen below the dash, instead screen is at instrument cluster height
  - in center column, where your hand natural can rest, a palm-sized wheel:
    - tactile feedback on rotation
    - multi-directional shifts (cardinal & diagonal)
    - pushing/clicking wheel is selection/confirmation
    - finger tips buttons surround wheel with shortcuts: 
      - navigation (either CarPlay/Android Auto nav app or GPS)
      - music (either radio or CarPlay/Android Auto currently playing music app)
      - favorites (can be radio, satellite, etc.) 
      - home (one click -> CarPlay Home, double click CarPlay Dashboard with map & media)
      - back

I've seen myriad folks passing judgement on these systems because they've lived with touch screens in cars for a very long time. I was lucky to skip that entire generation going from a minimal LCD digital screen straight to a Mazda with this system. It took a few weeks to feel comfortable, but not once did I ever feel as insecure as I have in a vehicle with an touch screen located below the instrument cluster line.

I think we've numbed ourselves to the routine distraction of touch screens which (generally) bypass most people's ability to mentally map physical buttons to specific actions. It's obvious as has been mentioned in this thread that touch screens are a massive cost saving (initially at least) and vehicle production timeline trick.

The huge missing story for touch screens is user experience and safety. The Mazda input system does take some time to learn, and it does divide my attention when I use it, but it has trained me to be more sparse with my interactions with the multimedia system and to rely far more on voice input control whenever I absolutely need to input data into the system (music selection, route finding, text response, etc.)

This isn't even getting into the surprisingly well-designed software and hardware intermingling that Mazda has accomplished between the instrument cluster (which features one central LCD gauge that mimicks the two real physical gauges that surround it) and the multimedia operating system navigation.

Here's some references for folks who find it interesting and are interested hardware/software design for safety in vehicles:

  - https://www.wardsauto.com/interiors/why-mazda-blindfolding-its-engineers-and-designers
  - https://www.mazda.com/en/innovation/technology/philosophy/human-centric/