I find it very hard to believe that someone who has never done any CAD could design that with Fusion 360 in a day. I do lots of 3D design with Fusion and there is a serious learning curve. It's not something you can pick up in a day. She is doubtless much smarter than me, but that's not credible.
Google suspend email accounts that get lots of spam reports. It happens a couple of times a year for salespeople in my company who use Gmass (a bulk email sending tool).
I mention it only as a useful data point, and in the absence of anyone else on the thread mentioning that Google have robust email abuse monitoring.
Ask anyone with 30 years in the industry whether "agile", for all its problems, was a force for good or bad, and the answer will be an emphatic Good!
If nothing else, it gave us ammunition to argue against the impossibility of delivering a fixed thing in a fixed amount of time - which was the universal view from senior stakeholders of what competent software delivery looked like.
I am puzzled that the media is widely reporting that the issue was caused by solar radiation, and that the immediate fix is to revert to the previous version of software for the ELAC (Elevator Aileron Computer). The only explanation that seems to fit with the narrative is that the newer version of software has weaker memory integrity checks than the older version - which seems unlikely.
If you're in the vicinity of the road called London Wall (where the car park referenced in the article is) then it's only a short walk to London's Roman amphitheatre [1]. It doesn't seem to be very well known but is quite impressive. It's one of very many bits of Roman history entombed in basements of London buildings.
The Merrill Lynch Financial Centre also has a big chunk of Roman stuff in the basement - but there's no public access and no access to the walkway around the ruins even if you're an employee.
You don't need a removable wheel to sharpen a pizza cutter on a stone. That's actually pretty clear from the video showing the sharpening of the removed wheel - the fact they the wheel is not in the handle isn't material to the sharpening action.
Pizza cutters wear out by deformation of the hole in the middle of the wheel (in my experience). I have thought of hacking one to fit bearings, just for the joy of having something that is properly engineered.
The dominant themes in the thread relate to using existing WiFi infrastructure in real world environments. I thought it would be obvious that I was critiquing this line of thinking. Obviously not.
This is just a dedicated RF emitter combined with a dedicated receiver. The fact that is it uses WiFi hardware is probably just because that's the cheapest and most available hardware for the researcher to work with. There is no indication in the article that the WiFi can actually be used for transmitting real data at the same time; that a non-dedicated WiFi source can be used; that it works when there are many people between transmitter and receiver.
Therefore the ideas that this might apply to real-world situations and use existing WiFi infrastructure, are a stretch given the information that's been shared.
It basically doesn't seem like a big deal to demonstrate what has been demonstrated.
> You'd be surprised by how many amateur cyclists ride more than that each year.
You wouldn't.
As an 8k km/yr cyclist with a lot of cycling friends, I can tell you that 12.5k/yr is extremely high for an amateur. Sure, there are some, but a truly tiny proportion.
8k/year eats bikes, BTW. I used to wear out rims regularly before I switched to disks and chains/sprockets didn't even last a year (on a fixed gear bike).
Are you confusing "adventurer" and "explorer"? There are plenty of contemporary adventurers (motivated by ego, fame, personal achievement) but explorers? Not so much.
The idea that you can apply lower-quality engineering practices in some systems is totally wrong, I think. Good engineering practices will help you retain good developers, will allow you to maintain a sustainable development pace and will prevent you annoying your users so much that they stop using your system. I can't imagine any commercial project where this doesn't matter.
Isn't this just another representation of the fallacy that it's possible to deliver faster by cutting quality? That's the kind of thing I expect to hear from ignorant stakeholders who know nothing about developing software, not on HN.
Our team has thorough, high quality, automated tests. In the past 5 years we have never released such a badly broken system that emergency remedial work was required. We still don't release on Fridays. It's just common sense, risk management and (most importantly) respect for the developers home and family time.
I am a runner. I had proper flu this year for the first time. I have never been that ill ever before. I could not even get upstairs to bed one night when I was at my worst.
Fantastic app. My wife and I are gradually becoming able to recognise more and more birds by their call. This is great because the human ear is better than the app at rejecting environmental noise - so we can spot birds by their call even close to a noisy road when the app cannot.
The app, at least on my Pixel 6, struggles with very high frequency calls - e.g. long-tailed tits.
The preliminary report seems to suggest that the yacht's construction was at fault.
I don't understand the following:
"The study indicated that if the wind was blowing directly onto Bayesian’s beam and the yacht was in the
‘motoring’ condition, a gusting wind speed in excess of 63.4kts would likely result in the vessel capsizing"
...but it didn't capsize - it sank (due to water coming down the main stairs, reading between the lines of the report).
The angle of vanishing stability, in the configuration in which it sank, was estimated as 70 degrees - and the videos I saw seemed to show it blown further over than that.
Anyway, the report makes an interesting read (as do all the MAIB incident reports - they are addictive reading if you're interested in boats).
I built something like this. I am amused that mine too was built for my wife and also was one of the few techie things I've ever done that received unqualified spousal approval.
Mine shows weather and tide times at my wife's rowing club. It has the form-factor of a large fridge magnet. This led to the need to be battery powered and therefore very frugal with power - so a RPi wasn't feasible. It uses an ESP32. The data itself is collated by an AWS lambda.