Diffity has a “tour” feature that can be directed to explain a local code change. Walks you through the important bits of the change with explanations.
I know nothing about the reasoning behind the original decision from Synology, nor the internal politics at play, but typically the customer support tail is not wagging the dog of the rest of the company. Might be bias/anecdata from the places I've worked, but product usually drives everything, and the support staff has to deal with the consequences.
Yes, but it's not support wagging the dog,
If they sell a NAS, the customer adds drives to it and already runs into issues requiring support, it creates cost which becomes part of a product problem.
In B2C that's a legal warranty-issue in many countries, because if the product didn't provide the advertised core-functionality the customer has the right for a full refund of the purchase price (within the EU for a period of 24 months!)
Below are the three alert levels for all hazards in Australia, including tsunami:
- Advice: An incident has started. There is no immediate danger. Stay up to date in case the situation changes.
- Watch and Act: There is a heightened level of threat. Conditions are changing and you need to start taking action now to protect you and your family.
- Emergency Warning: You may be in danger and need to take action immediately. Any delay now puts your life at risk.
The scale slides up and down, but can immediately be set to Emergency Warning if the situation demands it.
They can also be further defined with 'Calls to Action':
- 'Monitor conditions'
- 'Prepare now'
- 'Seek shelter immediately'
- 'Move to higher ground immediately'
Siren systems aren't widespread across the country, though systems are popping up in some flood-prone parts of Queensland. Sirens are typically activated when the 'Emergency Warning' alert level is reached.
You're watching out for something so that you can then warn people when it is happening. An example would be someone on fire watch. If they see a fire, they warn everyone. Emergency responders like fire departments have terms like Third Watch (hence the TV show) for the crew pulling the overnight shift.
So more than considering noun/verb, the subject is key. You're watching the storm for a tornado. You're not watching the tornado.
It’s clearly easy to get them reversed evidenced by the large number of people admitting it. I too had them reversed growing up, but took until I really got into learning weather in preparations for storm chasing way back before the internet. At least until I learned how expensive it is, and life had other plans for me.
Mocking someone for not understanding something you do is not a good look, and you should really try to be more empathetic. We all didn’t know something at one point.
I reversed them on purpose to make a point, so I don't feel mocked. My point was how easy it is to mix them up. Warnings and watches are, linguistically, very similar.
Additionally, his comment was a gentle correction, not mocking. I think his empathy is fine, not sure what language you're even calling him out for.
just saying it is easy to get them reversed just shows how GP is out of touch thinking it is strange that someone would get them reversed.
also, it's just not helpful to intentionally reverse them the way you did in such a declarative manner. Grok might use that as its basis for giving out the wrong information one day
I’ve also struggled with over-analyzing where stuff should go. I’ve restarted a new Obsidian vault based on PARA [1], and am experimenting with using LLMs (both Cursor and Claude Code) to help me decide where stuff should go. Been a big help so far.
I've started seeing a number of people talk about using Claude Code for searching, writing, and organising text documents. It is an interesting trend to me. I tried it out with my non-technical girlfriend and she really liked using it for helping with analysing interview transcripts. It seems like that agentic workflow is really effective outside of coding as well.
I just hope non-technical people that pick this up also pick up version control. Or, is there a better alternative to Claude Code that can accomplish a similar thing while being more friendly to non-technical people?
F1TV had some fun with it in their usual post-race programming: Joylon Palmer (F1TV announcer) did a deadpan "breakdown" of the Lego race during his segment, and Sam Collins analyzed the aerodynamics of the Lego cars in his.
The drivers all said it was the best driver's parade they've been in. I don't know how marketing like this works, and if it was worth it for Lego in the end, but what a masterstroke. Lots of fun organic mentions of Lego over the past week because of it.
This is what I don't get. We don't have masses of unemployed people waiting in the ranks to fill a large amount of new jobs, as unlikely an outcome as that even is. Which means any large uptick in people working in manufacturing would have to come from some other industry. So what jobs would we give up for it?
Yeah, we've used CAPTCHAs to great effect as gracefully-degraded service protection for unauthenticated form submissions. When we detect that a particular form is being spammed, we automatically flip on a feature flag for it to require CAPTCHAs to submit, and the flood immediately stops. Definitely saves our databases from being pummeled, and I haven't seen a scenario since we implemented it a few years ago where the CAPTCHA didn't help immediately.
Reminds me of the advice around the deadbolt on your house - it won't stop a determined attacker, but it will deter less-determined ones.
I agree, I love the Mazda approach to this in my CX-50. I'm not even sure if the display is touchscreen or not, because I always use the wheel-clicker thingie in the console to control it.
This was an intentional design choice from Mazda, of course, that goes hand-in-hand with their philosophy of giving such control to the driver that they "[feel] oneness with the car, as if it is an extension of their body." [1]
When searching around for a quote like that, I found a HN discussion from 2019 about the Mazda decision to eliminate touchscreens. [2]
Mazda only enabled the touch on the LCD when the car was stopped. It seems that with the Gen4 models (2019 onward) they just cost-reduced the sensing circuit out of the design and nobody has really complained. Taking that layer out also reduces the spidering issue when the OCA fill rewets.
The paper calls out a few things that they didn't cover:
> The CCC+TL model predicts the age of the Universe as 26.7 Gyr against the generally accepted value of 13.8 Gyr. This is of deep concern and needs the model validation against multiple observations, including BAOs, CMB, Big Bang nucleosynthesis (BBN), and globular cluster ages. Our focus here is on BAOs.
I am not in academia and therefore am not qualified to have strong opinions on any of this, but I do like the idea of papers not swinging for home runs all the time by explaining everything, and instead being happy with hitting a single by proposing something intriguing and asking for others to chime in.
https://github.com/nilbuild/diffity