olivierlacan

le mois dernierdiscuss

Keep a Changelog[0] maintainer here, weirdly seeing this while deep into work on way overdue 2.0 "release"[1], which should be out very soon.

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

olivierlacan

il y a 6 moisdiscuss

Had the same thought reading this but I suspect what's in the gemspec could accidentally differ from what's in the RubyGems.org metadata, although that should probably not be possible.

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.

olivierlacan

il y a 7 moisdiscuss

Notorious islamophobe, homophobe, transphobe, xenophobe, and loyal supporter of French far-right parties is what most French people know her for.

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.

olivierlacan

il y a 7 moisdiscuss

If you've used any non-iRobot vacuum alternatives in the last 5 years and ever owned a Roomba in the past there should be nothing surprising about this headline.

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.

olivierlacan

il y a 3 ansdiscuss

You may be working with people who, at the beginning of their careers, worked on exciting and challenging projects as junior engineers for U.S. defense contractors to either detect the precise location of specific Wi-Fi clients.

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.

olivierlacan

il y a 4 ansdiscuss

This is precisely why I'm so infuriated so many people (me included until recently) aren't aware of the excellent alternative manufacturers like Mazda are offering in their cars, their Command Controller:

  - 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

Here's a good video showing how it functions: https://www.youtube.com/watch?v=Q8ORngbdKI4

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/

PS: not a Mazda shareholder or rep, just a happy owner, take that bias as you wish

olivierlacan

il y a 4 ansdiscuss

You don't "have to disagree". You're presenting a very different context than the one the author presents, a decidedly non-European working environment.

The one you relate has far more balanced relationships between employers and employees. In that one, there are stronger guarantees against reprisals, but I'd wager those guarantees are not foolproof either. It's very easy to poison someone's reputation in a community without them finding out for a very long time.

Everything can be disagreed with if you switch the context to an alternate universe. Your example was useful and probably astounding to a lot of North American workers, so I appreciate you sharing it.

olivierlacan

il y a 5 ansdiscuss

The boulder-sized caveat for all this admittedly really neat stuff being:

> PlanetScale's Non-Blocking Schema Changes' workflow doesn't support FOREIGN KEYs in users' databases.

> PlanetScale determined that the production safety that Non-Blocking Schema Changes provide are worth this technical tradeoff. Learn more.

https://docs.planetscale.com/concepts/nonblocking-schema-cha...

comments