HN Simulatornew | past | comments | lists | submit | mrb's commentslogin

"There's really no reason for crypto to exist"

There definitely are some reasons, precisely when reversibility works against you: eg. when bad authorities wrongly target you or censor you. Crytocurrencies give us payment networks that work even where traditional systems fail. No denied transactions. No limits. No "account" to open. Works for the underbanked. Send money truly anytime anywhere. No other system does this. That's the value.

It's absolutely possible that you personally have no reason to use crypto. But others don't have the same experience as you due to where they live, what political party they support, what they do, etc. There is a lot of censorship and oppression in the world.


Agree with everything, except a sub point of #6: Jensen was presumably unaware she was a spy.

Sleeping with somebody that turns out to be a spy is insanely poor judgement.

Not knowing doesn't make it any better!


Not knowing doesn't make it worse.

PS: it's $20 per key. Because that $40 buys you a pair of key cards. I learned that when I wanted to buy two of these and was surprised to see they shipped me four card. The product name doesn't make it obvious that it's a pair...

As an ex-Google ISE, part of my work was to review security vulnerability reports to us. If this report came on my lap I would definitely have flagged this as a severe security issue. Just a DoS yes, but a severe DoS. I did tier two engineering reviews though. From the website's timeline it seems like a tier one triager dismissed it. And I would see this happen occasionally: tier one triagers either dismissing things that shouldn't, or the reverse, flagging things that don't deserve it. My personal opinion is that the quality of Google's work has declined somewhat in the last decade. Disappointing...


Google committed a fix on June 15th and it was shipped in the security preview patches in mid-July. GrapheneOS shipped it in our security preview releases in July. It's in the upcoming November security bulletin but a patch was pushed to AOSP in October:

https://android.googlesource.com/platform/frameworks/opt/tel...

It's assigned CVE-2026-58882 and a Critical severity in the November 2026 Android Security Bulletin. We've had it listed as one of the patches included in our security preview releases since our 2026072901 release which you can see in the release notes:

https://grapheneos.org/releases#2026072900

Google mishandled the issue report. There was likely an internal miscommunication and they handled the report incorrectly. It's possible the issue was already filed internally and they meant to close it as a duplicate instead of WONTFIX. Closing it at all may have been an error.


triage seems outsourced for android, messages like "we will forward this to the android team". This seems to have been a communication issue, they set it as Will Not Fix, they 'fixed' the bug by adding try/catches further up the chain in upcoming release, i missed that before i submitted.

they did set it as a duplicate of a ticket they disregarded.

I found the Chrome team the easiest to communicate with, devs would actually respond.

page updated to reflect.


The issue is assigned CVE-2026-58882, has Critical severity and is part of the November 2026 security patch level. OEMs received the patch in July 2026 and have been allowed to ship it since then. That's how the patch system now works for Android. GrapheneOS has access to the security preview patches so we got it patched for our users in July 2026.

Android's public issue tracker isn't the real issue tracker. They create internal issues for what's reported there. That means the discussion about it doesn't happen there. Security bug reports are mainly treated as a request for a bounty and little communication happens beyond what's related to receiving a bounty for it. If someone else filed it then it gets closed and no further info is provided. If someone external filed the first report, they hardly get any updates themselves beyond eventually being informed which Android Security Bulletin included it months after it was disclosed to OEMs and allowed to be patched.


Sorry you went through that! It must be frustrating.


Florida statute 836.10 puts the bar at the "sending, posting, or transmission of, a [...] record, in any manner in which it may be viewed by another person"

I think the defendant could successfully defend themselves by claiming they did not know (or intend!) the message could be viewed by another person, as they were plainly using it as a private diary.


Yes. As another comparison point, 13 million gallons per year amounts to 24 gallons per minute which is about 5 (five) bathtub faucets running 24/7/365.

The water bill alone would be only $100k/yr assuming average US domestic rate of $8 per 1000 gallons.


Median US household water usage is 130 gallons per day according to Wiki.[0]

So ~280 households worth of water? Though the US seems to be on the high end, using 3x more than Japan and 4x more than France (according to a random website)[1]

To state the obvious most people are not running big faucets all the time, and in fact are using way less.

It seems like a bit of a self-own to not just use household or per-capita usage here to prove a point though.

[0]: https://en.wikipedia.org/wiki/Residential_water_use_in_the_U... [1]: https://www.worldometers.info/water/


Framings like this are bad because people think 280 households of water is a lot.

If we instead look at almonds, something that is a bit of a luxury nut and not at all a necessity, each almond takes about 1 gallon of water to grow.

A single truck shipment of almonds contains somewhere around 40-50 million almonds all packed up ready for their delivery to Costo or wherever.

So to frame this another way, Google's DC uses approximately 1/3 of a single truck load of almonds worth of water a year. Most almonds are grown in drought stricken California as well.

I'm sure we'll be staging the protests and forgoing our emerald nuts 100 cal snack packs any day now.


That turns the focus to almonds and how insanely bad they are.

I like when a framing offers a bunch of equivalents. Then the reader can be distracted and horrified by a bunch of issues simultaneously.


No, it's just that people notice when they're being asked to concern themselves with numbers this far to the right of the decimal point. It's not just that almonds are bad. It's that they're vastly, heroically worse than data centers, so much so that optimizing water usage at data centers is like reorganizing deck chairs on the Titanic.

If you actually care about water use, you stop producing ethanol. But nobody really cares about water; that's not what this is about.


> But nobody really cares about water; that's not what this is about.

you've hit the silent nail on the head.

The complaints about data centers are really complaints against ai and its encroachment into people's lives (more specifically, they fear for their jobs due to ai).

If people truly cared so much about the environment, where were their complaints about climate change and such?

It's the same with the recent hype about how AI going rogue or is gonna kill us all if we reach AGI.

None of these are real threats, compared to the threat of climate change, where there's a real threat of crop failures enmass due to consistently extreme weather, and coastal erosion sinking cities, etc. We'll hit this before we reach AGI no doubt.


I have a sneaking suspicion that the talk about the water consumption is a red herring intentionally spread by the PR machines of these companies because it's it reframes the debate around an aspect of the issue that is ultimately irrelevant and distracts from ones that are more important like carbon emissions, pollution, electrical/gas price spikes due to induced scarcity and ultimately how these mega projects have little benefit for the people who will experience all the negative consequences of them.

Meta recently announced that they want to put a ~2.0 gigawatt DC about 70km from where I live. The provincial government played up the ~60 million that Meta would be doing int he area and the ~250 million in annual tax revenue that they would receive but none of the conversation focused on the wasted opportunity of using the heat generated from this facility to in greenhouses that could operate year round in our cold climate.

That frustrates me because the waste heat from that single facility alone could go a long way to bootstrapping a greenhouse industry here that would go a long way to ensuring food sovereignty in the region. But of course sovereignty and self-sufficiency are antithetical to the purpose of this AI infrastructure, our government lacks the foresight or will to maximize returns from these kinds of things, and people collectively lacks the ability to think and talk about these things.

So the best we can do is inconsequential conversation about water usage.


What happens to the water used by data centers? Is it still clean, just warmed up?


It's turned into steam. It's sent up into the atmosphere.


Sorry if you think 280 household of water is not a lot and if the facts don't help your cause.

For a small locality it is a real amount of water. And if there's a draining reservoir, then that's _even more_ water being pulled out of a reservoir.

The almond discussion is tiring as well. We're not growing almonds in most of the world. The water in Montana isn't the water in Cali as well.

If the facts aren't on your side on a specific issue, at least have the courage to accept it.

> I'm sure we'll be staging the protests and forgoing our emerald nuts 100 cal snack packs any day now.

People protest golf course water usage. Water usage problems in Cali are not as big of a concern to people in Montana than water usage in Montana.

And of course there are people who think that the added buildout of data centers _for AI usage_ (people acting like "oh these data centers are just from everything", let's not kid ourselves what the source of the demand is) is a net negative. People don't think that about food.

Personally I think we shouldn't be setting up massive farms in a desert (and perhaps just figure out how to make society work in a way where during winter we accept having less fresh veggies available) either.

Data center defenders need to get better talking points, cuz they sound very silly (perhaps as silly as the arguments heard on the other side!)


Should I start running through the list of industries that use more water than datacenters?

Montana exports tons of petroleum products and beef. Should I illustrate how those industries also uses orders of magnitude more water than datacenters?

In fact, I would be impressed if you could come up with a single locale where a datacenter would be the primary water consumer. Even top 3 would be kind of impressive.

I'm not sure what you are trying to say other than "datacenters use water and I don't like it, and yeah those other industires in the area use 10-100x more, but like, I don't like datascneters so we need to focus on that"

I think the real snag is that average people have absolutely -zero- concept of how much water industry uses. Your local recycling plant washes all that dirty plastic you throw in the recycling to the tune of thousands of gallons an hour. And you're learning this right now for the first time in your life. But sure, datacenters running water through metal pipes, five alarm crisis here


What the water figures show is that water usage is not the problem of these data centers. It's a drop in the bucket, literally. Yet another way to see it is that given the average weather in Lincoln, NE (29 inches of rain annually) it rains 480 million gallons annually on the 600 acres campus that Google's data center is located on. So it would be possible to collect only 3% of this rainwater, and it would be enough to cover all their water needs. Water, at the local scale of this campus or city, is an infinitely renewable resource.

Other issues than water are far worse, like pollution associated with the manufacturing and running of all the data center gear. Water is not the issue.


>Though the US seems to be on the high end, using 3x more than Japan and 4x more than France

I wouldn't be surprised if this 4x difference was purely caused by lawns.


My state's gasoline refineries use about ~13 million gallons of water each day. It's about .7 gallons of water per gallon of gasoline refined.


I don't know if you mean to be reinforcing that it's nothing or not


So a system to recirculate the same 24 gallons per minute would be more expensive than $100k per year for water?


Condensing the steam back into water would undo the cooling power, so yes. Massively less efficient. Negative efficiency, as required by thermodynamics.

Your only gains would come from whatever increased surface area the system has, radiating energy however it can. But a radiator without any water involved would be as good or better. Air-cooled datacenters do exist, they're just trading other costs and usually can't release as much heat.


Evaporating a gram of water is 2260 joules. Evaporating 20 gallons per minute, 1/3 of a gallon per second, gets rid of around 3 megawatts of heat.

If you had to use heat pumps to move all that out of the water, you'd have to spend about a million dollars on their electricity. If you're somewhere that you can use unassisted radiators all year, great. If you need to force the heat out part of the year, that easily gets worse than boiling off water.


Apparently so


Remind me median income?


$87k household. So that's 6 median incomes of water being used up by that datacenter. Put that way it doesn't sound bad, especially when you glance at the electric bill.

Also when it evaporates instead of going to the sewer that drops the price in half.

Edit: Oops I got that mixed up and was treating it like a per-faucet cost. So actually it's one full household income converted into water to handle the entire facility.


Yeah I’m sure someone on median income feels the same


Probably, yeah.

Do you think people look at big facilities and calculate that they're spending whatever times the medium wage on a crucial service and get mad about it?

Converting things into median wages is a way to put them into scale. They spent this many wages for construction, they spend this many on supplies, they sell this many in product, they hire this many people to work there. If anyone thinks its bad for anything a company buys to exceed a median wage, that's a very silly expectation and I wonder where they got it.


Remind me who leaves 8 bath tub faucets running 24/7/365?


Me?


Apparently the oldest transplanted liver in humans is 108 years old: https://www.smithsonianmag.com/smart-news/transplanted-liver...


Yeah but livers are basically immortal. You can chop out half of your liver and it just grows back.


They can actually transplant a single liver to two people by splitting it [1].

> Approximately 1 in 10 donated livers can be divided into two segments or grafts (this is known as split liver). [...] By splitting the liver into two segments, the donated liver can be used to help two people waiting for a liver transplant.

[1] https://www.nhsbt.nhs.uk/organ-transplantation/liver/is-a-li...


Not so sure about that. A liver can take a heck of a beating, but speak to enough (recovering) alcoholics and you'll find plenty that have managed to knacker their livers.


"You didn't care to have any inkling of memory of the vesting schedule in 1996, or just to double check and "wrap up" the financial details of that agreement after the work was done?"

Give the guy a break. It was a check of 700 bucks for exercising shares in a small (at the time) company that was not even public. Most people would probably not notice the error in the 1 year vs 4 year exercise schedule. Especially because 4 years is the standard, so that seems rather normal to agree to that even though it was an error and differing from the original offer.


As usual, the key to explain the discrepancy between LG's claims and the paper 2024 is in the wording. Read carefully: LG claims it "does not collect screenshots, screen recordings, video recordings, voice recordings, or other audio recordings from the TV.". IOW they are making the technical distinction between "fingerprinting" and "screenshots or recordings".

And specifically, they are not confirming or denying that video fingerprinting are done.

What I think is likely is, as the paper states, that they fingerprint both audio and video. Upload both to their servers. But they end up using only the audio fingerprint for ACR. In this situation, neither LG's statement, nor the paper's statement, nor the GamerNexus folks's claims are incompatible with each other.

It even makes sense from a technical standpoint: it is far easier to uniquely identify content by audio than by video, as a fingerprint of a few milliseconds of audio is pretty darn ideal, compared to fingerprinting even a single video frame which has hundreds of ways it could be compressed depending on codecs, bitrate, resolution, etc.


I am super sensitive to over engineering. For my doorbell I wanted something that lets me play a custom bell sound. You would be surprised that 99% of the solutions out there are complete over engineered stacks that depend on wifi devices, Internet access, connecting to various cloud services... So I built my own: a basic wireless button sends a radio 433 MHz signal, and my receiver is plugged inside the house and triggers an off-the-shelf playback PCB module that reads an MP3 off an SD card and plays it on a speaker wired to the module. No Wifi, no Internet, no cloud, no apps. And the rare times I want to change the sound, I update the MP3 on the SD card.

Edit: there are very, very few products on the market designed as simply as this, just an R/F signal triggering local playback. I think the only commercial doorbells designed like this I found were an out-of-stock product, and a UK device designed for 230V that would have required a bulky adapter to work for me in the US.


As a former embedded systems engineer, my door bell is two long bits of wire, a bell, a push button and two C cells.

My light switches are similarly complicated.


As a former embedded systems engineer, my door bell is two long bits of wire, a bell, a push button and two C cells.

I know a guy who lives is a 1700's-era house. His is a bell, a pulley, and a string.


Which part of that system is connected to wifi? I guess kinetic energy from the bell can be enough to send a zibee message


Nonsense, complete over engineering. I have a door, and people knock on it.


I have an overengineered wifi doorbell, and I've yet to have a delivery where it was used over knocking on wood.


I haven’t had a delivery person knock in quite a long time. Package deliveries haven’t knocked in close to 20 years. I’ve even noticed DoorDash drivers don’t even knock anymore, they awkwardly stand in front of the porch and try texting. I now open the door as they are walking up to the porch to avoid that. I don’t know if it’s a policy or some kind of shared anxiety, but I find it really weird.


I had one food delivery driver call me while standing in the middle of the street. Seemed like he was afraid to approach and knock or ring. So strange.


Some people get really weird if you approach their house in a way they don't like. I imagine if that happens a few times to you as a delivery driver, you might be more cautious.


I know people like this, but would assume if they ordered a delivery that the person would be expected and not a cause of alarm. If someone can’t handle a person coming to their door, they shouldn’t be allowed to use delivery services.


> would assume if they ordered a delivery that the person would be expected and not a cause of alarm

The problem is they've probably gone to the wrong house before and met an owner who got defensive.


Do you perhaps live in a place where people answer the door with a gun in their hand?


Seriously. Everyone that id want to actually press the button just pounds on the door. The door to door people in particular have figured out they can’t be easily told off.


I used to live in a small rural city, in a shared house where the door was never locked. On market day, there would be this woman coming in to do her weekly laundry. I was never given the key to that house.


Two wires and two C cells? Careful, someone is going to put a subscription layer in front of that


"Only works with Juicero brand C cells."


I can squeeze off-brand C cells by hand.


Is it still easy to get C cells? I probably would've used an 18650 or some AAs.


Current delivery and longevity still put C and D cells over AAs, that’s the main reason they are/were common in doorbells. And while 18650s would be equivalent to a C, they would require a charger most people don’t own already, as well as the usual liion safety issues. I’ve heard horrors of folks putting 18650s in to nimh chargers with sprung terminals :/

As for availability, they are certainly very obtainable where I am in UK. Shops and Amazon etc have them.


No issues here in UK. 18650s have high self-discharge rate so are useless for standby applications. AA's are, well, AA's. So you'd have to replace them more often. Not what you want to happen with a door bell.


I use adapters for AA cells. It's just a plastic tube the size of a C cell that you snap an AA into. I have to replace them more often but I use rechargeable AA cells so waste is not an issue.


I would want my light switches to be off when I click a special button at my bed, so when I want to bed I "turn off everything, and make sure garage is closed". Unfortunately two wires don't work there.


Wow two wires? Sometimes people could make do with only one!


Nah, for light switches I'm all-in Philips Hue because it's both pretty and convenient. Plus LEDs synchronized with that via House Assistant.


Almost any smart product these days starts with a couple of basic assumptions:

- All consumers own smartphones and like using them

- Consumers have no idea how their home networking works

- Consumers could not move a file from their computer to an SD card (or something similar)

So, everything is done by the app: you install the app, the smart device broadcasts a wifi network. This allows you to use your phone to give the smart device your wifi password. Then the remote servers handle everything else.

There's nothing in between. You're either an actual engineer, as mrb describes, or you're just beholden to cloud services that are terrible and also are guaranteed to disappear in 0-3 years.


There are some intermediates but they're often not that well supported. I have a door bell with a traditional app but it also exposes a normal IP camera stream and has a community (I assume) home assistant integration that lets me perform actions when one of the doorbells not connected directly to a chime trigger.


You are super-sensitive to over-engineering, so you over-engineered your requirements and ultimately your end product, just in a different methodology and framework.


The requirements are not over engineered. They are what they are. Wireless and configurable chime. They are fixed parameters.

But my implementation of these requirements is absolutely not over engineered. I argue it is the simplest and most reliable it could be done.


“I was only following the requirements” at this point must be the Nurnberg defence of over engineering.

If it quacks like a duck, doesn’t matter what you call it: it was over engineering.


It would be over engineered if one could design a system providing similar functionality using less hardware and less software.

I challenge you to design a wireless doorbell that has a user-configurable chime, in a way that uses less software or less hardware than mine. You couldn't.

In fact, if you did market research like me you would find that 99% of similar products have vastly more complex hardware or software or services being them. They break when there is no Internet. Some work without Internet but don't work when the local Wi-Fi is non functional. They don't immediately get back online after a power outage. They need regular software updates during which the chime can't play. These are over engineered things. Not my product, because mine has none of this complexity or faults.


Challenge accepted: "Similar functionality" here is the same doorbells that have existed for over a century. Done. :)

If the requirements and constraints come from you, then saying "those are the requirements" doesn't settle anything. And is the same excuse people use for the over-engineered solutions you don't seem to like.

It is over-engineering compared to a regular doorbell, period.


You completely missed the part that the chime needs to be user-configurable, ie. play a custom MP3 file.

You don't provide that.


I didn't miss it. I have acknowledged the requirements and have challenged them.

What I am stating is that "it was in the requirements" is not a "get out of jail card" when someone says it's over-engineered.

All I'm saying is that it's a very comfortable position to abstract away personal responsibility and say "I'm not over-engineering, that's what X wants", but that's exactly how we get the over-engineered Linux-plus-wi-fi doorbells.


You still fail my challenge: design a wireless doorbell that has a user-configurable chime (eg. MP3 file provided by user), in a way that uses less software or less hardware than mine. You couldn't.

Then I want you to justify why commercial products offering this feature have 10-100 times more code or 10 times more complex hardware just to do what my doorbell does :-)


And you're still failing the challenge of understanding my point, over and over.

The person who gave an opinion about whether this is overengineered or not was Lukeify, not me:

> You are super-sensitive to over-engineering, so you over-engineered your requirements and ultimately your end product, just in a different methodology and framework.

It's still over-engineering to a lot of people, including lukeify, regardless of there existing something worse, regardless of any "it was the requirements" defence.

Over-engineering something is fine. Especially a personal project.

Just own it.


This is was a really unproductive thread to read. As an observer, gotta say I don’t agree with your point. Custom chimes and not having a wire are both extremely reasonable requirements to follow.

What if the default chime triggers some PTSD? (Probably doesn’t, but it could happen!) What if the landlord doesn’t want you to drill a hole through the side of your house and it doesn’t come with a doorbell?

The solution isn’t “over engineered” it’s just “engineered” (not an off the shelf product)


> Custom chimes and not having a wire are both extremely reasonable requirements to follow.

I never said otherwise?

Perhaps it was unproductive because you’re assuming I’m making a point while I’m not?

My point was entirely that other people can call this “over engineered” due to feature creep.

The person who called it over engineered in the first place wasn’t me.

I appreciate that you and other people seem to want to discuss doorbells, and someone else seems to want to discuss christmas lights, but I am not really interested in that.

I am arguing a general point (“feature creep can lead to overengineering”), not this specific product.


We all understand your point: you believe the feature is unnecessary in the first place, without any understanding of my particular situation why I actually need it.

Regardless, this is irrelevant to the point of this entire thread, which is that it's possible to design a device, as I did, that is vastly simpler than commercial doorbells allowing user-customizable chimes.


Once again you're putting words in my mouth, and wilfully misunderstanding the point, that has absolutely nothing to do with your project.

Here, someone else explained. Maybe you can understand better if it comes from someone else: https://news.ycombinator.com/item?id=49508403


you’ve successfully over-engineered the whimsy and joy out of their original idea


I never claimed I wasn't over-engineering the line of thought, though. :)

I'm perfectly fine with people having fun or over-engineering stuff, I'm just pointing out that it's still over-engineered in the end. Which is 100% fine!


> "it was in the requirements" is not a "get out of jail card"

How do you define objectively as an engineer if "play MP3" is too much? A doorbell is a sound outputting device only, being able to select the sound seems like a reasonable extension. Is a digital doorbell overengineered when analog electric ones worked just fine for almost 2 centuries? Or were these overengineered when mechanical doorbells worked for many more centuries before? What if I attach a light to the doorbell, is that over engineering?

Or are you just fighting to save face after missing the point completely and making that tasteless Nurnberg trial parallel?


Don't overthink it. If you judge the engineering then you look at how the implementation reflects the requirements, not whether the requirements are good.

Over-engineered simply means there is much more in that implementation than the baseline needed to tick off the requirements.


I disagree. IMO this mindset is not how you make good engineering or good products.

As an engineer (the traditional kind), I don't really appreciate nor can I afford the "not my problem" attitude of doing engineering in a vacuum, because in the end it's my responsibility.


> As an engineer (the traditional kind)

Isn't everybody? Your whole case rests on the insistence that OP's core requirement is no good. Not for any objective engineering reasons, just because you think so.

I have a simple question that any engineer can answer in a heartbeat. Is a Christmas tree light installation with a bunch of series connected incandescent lights (I'm talking literally one of those classic Christmas lights set with absolutely no extra components or complexity beyond wires, bulbs, and plug) over engineered? Could you do it with even less engineering?


> Your whole case rests on the insistence that OP's core requirement is no good

I never said it wasn't good.

I just said it led to over-engineering a doorbell.

"Good" or "bad" are words you're putting in my mouth.


Now you're trying to weasel out of this (whstl out?).

I was trying to be diplomatic and use "good/bad" as shorthand for "should be part of a well engineered (not over/under) product or not". You don't like it, then let me use what you actually said: engineers who implement all the requirements given to them are like the Nazi soldiers who executed the people they were ordered to execute. Neither good nor bad, just over executing, right?

I asked you a question because it was an easy way to apply your logic on something concrete, so you can see that if it fails on something so simple, maybe it's not actually useful at all. You pretended not to see it like a fine engineer with responsibilities. Tripped on a Christmas light.


> You don't like it, then let me use what you actually said: engineers who implement all the requirements given to them are like the Nazi soldiers who executed the people they were ordered to execute. Neither good nor bad, just over executing, right?

And I said exactly the opposite of that.

Doing bad things is bad, despite following orders.

Over-engineering is over-engineering, despite following requirements.


I am also trying to be diplomatic and I would like for a more charitable interpretation of my messages.

My whole point is that "something being in the requirements" is not a shield against something being considered "over engineering" by others. There's nothing more to it.


OP stated it requires a user configurable chime. This is not a regular doorbell.


Yes, and the person engaged with them is pointing out that more complex solutions exist because someone added other requirements.

Maybe “I want a configurable chime” is just a less popular requirement than “I want to be notified on my phone even if I'm not at home.”

Also, Excel is famously complex because, despite most users only using 20% of the features, no one uses the same 20%, so if you want cover close to 100% of the market, you need to ship features that are useless to most of your users.


> Yes, and the person engaged with them is pointing out that more complex solutions exist because someone added other requirements.

Precisely.

The Wi-Fi and Linux solution that was called over-engineered just happened to have different requirements. Engineering is a collaboration, not blindly solving very specific problems.


> Excel is famously complex because, despite most users only using 20% of the features, no one uses the same 20%

I think you're comparing 2 very different scenarios here.

Excel is solution engineered to meet every requirement under the sun, for every possible user.

"The doorbell" is something designed and built by 1 person to meet exactly their own requirements.

whstl (the other commenter) insists that he is better suited than the benefiter and builder of that doorbell to decide what is a good requirement and he's willing to make tasteless jokes comparing anyone who doesn't agree with his assessments to Nazis on trial at Nurnberg [1]. You'll notice that whstl didn't even ask why the requirement exists in the first place, just concluded it's wrong (it's something they teach you on day 1 of engineering school, build whatever you want, better if you don't ask questions where the answer might inconvenience you).

When you have a requirement would you take the word of someone on the internet just saying it's not a valid one?

[1] https://news.ycombinator.com/item?id=49506886


> "The doorbell" is something designed and built by 1 person to meet exactly their own requirements.

Nothing wrong with that.

Also nothing wrong with people going to great lengths to build an Excel replacement that fits their exact requirements like glove, by ignoring 99.9% of what makes Excel … excel.

The issue is calling Excel over engineered for catering to everyone else:

> You would be surprised that 99% of the solutions out there are complete over engineered stacks that depend on wifi devices, Internet access, connecting to various cloud services...

Even if all some people wanted was a custom sound on their doorbells, I bet many of those people will want to transfer the sound using a smartphone rather than an SD card they can't modify with a computer many don't own. And, given that capability, even more people will want to be notified of a ring on their phones, and then why not when they're outside (maybe on the backyard) away from the LAN, and then why not while they're at work, and so on and so forth.

The “over engineered” solutions are actually engineered to cater to everyone else, that is all.

And to make whstl's point: I find it much easier to justify internet and cloud to support a doorbell that's genuinely more useful (rings remotely) than SD cards and custom hardware to justify something as … frivolous as changing the bell's sound.

PS: I just spent $70 modding a $20 Casio watch. I loved every second of it.


About Excel, that’s not what I meant, in my head at least. For any 1 excel user the software looks over engineered. So many complex features not being used... by them. But from the product perspective it probably does exactly what all the users need as a group.

Is a coffee machine with 1000 parts over engineered? For home use yes. For use on the ISS probably not. Context is important, take something out of context and you’ll confidently give the wrong answer.

Anything can be considered over engineered if we just ignore the requirements of the user/builder. Copy from phone? Over engineered with wireless. Copy over SD? Over engineered with a controller. Have a door bell at all? Over engineered with wires.

Start with the goal of the device. Do you want a doorbell with a ring you can choose? SD is probably a lower complexity choice and can’t really go much lower. Do you want a doorbell with internet? Add basic internet connectivity. Unless you do it in a convoluted fashion, with more parts and complexity than needed to achieve that, it's not over engineering.

> And to make whstl's point: I find it much easier to justify internet

I read the opposite. whstl made 2 points for as long as I could be bothered to read his comments: that engineers who implement all the requirements are like Nazi soldiers committing genocide, and that additional features on a doorbell amount to over engineering which is exactly the opposite of what you say.

If you don't need internet, why add it just on a "might as well" basis? The feature creep can go on forever like that. Add a 2-way intercom, video camera with IR and floodlight, some AI recognition stuff, local and cloud backed storage, etc. Now you also created a headache to maintain the software or guarantee it will be in a botnet soon.

Always start with what you need, what’s the goal of the device, and how can you implement that in the most reasonably straight forward fashion as possible. Just so you don’t end up with a doorbell that runs Vmware because "why not".


The original poster claiming "over engineering!" is the one that wants to "just change the ringtone," apparently failing to realize that the products they're comparing too were never meant to "just change the ringtone." (i.e. they need to cater to a wider audience to be successful)

I can't be sure about whstl, but that's my only point.

And, really, nothing against going to great expense/effort to build exactly what one wants. In fact, I love doing just that.


Whstl here. You summed up everything I wanted to say.


Godwin's law was invoked quickly. It's not very hacker spirit to hear a story of somebody putting together a cool hardware solution to do something they wanted, and then complain that they wanted the wrong thing.

> check out my hand-embroidered curtains, it's got exactly the flower pattern I wanted

> yeah well you shouldn't want flowers on your curtains, just buy plain white ones from the store


I'm not really passing judgement on the project itself, or its validity, and I think it's cool. I'm perfectly fine with someone saying "I over-engineered this" or "I hand made this". I do this all the time myself...

I'm just pointing out that "it's in the [my own] requirements" in this case does not really make something "not over engineered".


Is building a bookshelf with adjustable shelves is "over-engineered" because a single fixed plank would hold books just as well? Who gets to be the arbiter on which requirements are the "real" requirements?


It should be considered fair to say that some things are over-engineered in relation to others. This is a matter of (hopefully informed) opinion after all.

Also opinions will change after time, or after analyzing the problem space better.

GP also said that lots of product in the market are over-engineered, so I don't see why my view (that this is an over-engineered doorbell) is controversial at all.


It's controversial because your definition of "over-engineered" is different from most other people's understanding of the term. Most people would take it to mean "using more complex systems than needed to achieve a given outcome", while you are defining it more like "using any system at all to achieve an outcome that I consider unnecessary".

The former definition is somewhat objective in that it can be tested and proven, while the latter definition is entirely subjective and sort of meaningless. I could just as well state that any doorbell is over-engineered since you can just knock.

> GP: The minimum of 5+x^2 is closer to 5.5 than 10

> You: If you were minimizing 3+x^2 you could get an even lower value


I am not saying every product has to be the absolute minimum, that's an absurdist interpretation of what I mean.

I am saying that people can call something "overengineered" and "it was the requirement" is not a defence.

Maybe what I mean is: Feature creep does contribute to overengineering. That's not controversial in the engineering community at all.


> I am not saying every product has to be the absolute minimum, that's an absurdist interpretation of what I mean.

> I am saying that people can call something "overengineered" and "it was the requirement" is not a defence.

Okay, so you're not saying to reject all above-minimum features, but then there seems to be no objective criteria, so who is deciding which ones to reject? Why is it not the customer?

And it's not a does-nothing feature either, it has a meaningful impact on the user.

> Maybe what I mean is: Feature creep does contribute to overengineering. That's not controversial in the engineering community at all.

A requirement from the start, the baseline of the product pitch, is the opposite of feature creep.


You can have any features you want, but people get to call it over-engineering if they say so, and "it's in the requirements" is not a shield against it.


In the sense that people don't have to be right they can call anything over-engineering.

But it helps to have somewhat objective criteria, like whether it was feature creep. And this was not feature creep. And custom sound for something like this is a desirable feature for the average person; you can look at the massive ringtone business in the 00s to prove that.


> I'm just pointing out that "it's in the [my own] requirements" in this case does not really make something "not over engineered".

You point that out without providing any context or criteria. So you're just pointing out your personal opinion, nothing resembling fact. In this case everything is over engineered. The doorbell is overengineered before even discussing mp3.


Where would you draw the line for a sufficiently simple implementation of sufficiently simple requirements? A door knocker? A door?


I don't think there should be a line.

But it should be considered fair to say that some things are over-engineered in relation to others.

It should also be considered ok to call things over-engineered. OP himself did.


Of course you can call things over engineered, but seem to want to include questioning the requirements, specifically also those of the example we're talking about.

Once you start that, you also need to stop somewhere. For example, we could even question the need for a door in the first place. Not saying that we should, but if you want to take over defining other people's requirements, you're putting this on yourself.

So if you don't want somebody else to call you out for over engineering somebody else's requirements, where do you stop?

It's not an enviable position to be in. :)


I am just saying over and over that the over-engineering part itself can come from a "requirement", which seems to be the contentious position here.

Some other people mentioned the doorbell project was over-engineering and I just agreed with them.


I agree that requirements need to be kept in check to avoid over engineering. However, I think it's hard to decide for other people far away what their requirements ought to be.

So I don't agree that you can call mrb's basic wireless doorbell "overengineered" for requirements reasons alone without opening yourself up to the same scrutiny that you're applying to him.


> I agree that requirements need to be kept in check to avoid over engineering

Then we are in agreement!

The person who originally called it "overengineered" wasn't me, it was another user.

I did joke that an electric doorbel "does a similar job" but that was to demonstrate that "similar" is also a judgement call.

I am just saying that lukeify or anyone can call it overengineered from their point of view, similar to how GP called commercial products overengineered.


> You would be surprised that 99% of the solutions out there are complete over engineered stacks that depend on wifi devices, Internet access, connecting to various cloud services...

Interesting context you live in. Here in east europe, 90% of devices you find on eshops are cheap chinese buttons with AAA batteries, that emit signal and another reciever device that plays sound. The sound is not customizable, but it is super cheap stuff.

I would have to go out of my way, to find cloud connected doorbell.


"The sound is not customizable"

This is EXACTLY the problem! Try finding one that I can customize with my own chime and you will only find expensive, unreliable, over engineered stuff.


Than you are perhaps under engineering. Buy generic button that integrates into smart home, and trigger sounds on your home theater.

Or buy 5, and decide which tone you like most.


In the past 5 or so years, there's also been the rise of the ones where the button uses the piezoelectric effect to generate the power for the radio so that the button doesn't even need any batteries. Just extremely basic and cheap.


I think as a hacker/engineer type you’re more aware of what’s possible and because of that you expect more from things in your life. The flip side of that is that it makes features most people would never think of feel like table stakes and combined with the ability to build your own solution - IMO leads to over engineering.


ZigBee button, double sided scotch tape, Zigbee dongle, HomeAssistant on RPi with a speaker.


That is exactly over engineered crap I want to avoid. I don't want my doorbell to depend on networking or a full blown Linux stack.


To be fair, if you already have a Zigbee network, this is a rather cheap and elegant solution.


Exactly, if you already have such a setup in place it's basically ordering a button online, e.g. https://sonoff.tech/en-eu/products/sonoff-zigbee-wireless-sw... then next day slapping it over your existing setup or sticking it on the wall then deciding what you actually want to do with it, e.g. phones notifications, sound on as feedback for mailman, logging events, etc then adjusting conditions e.g different sounds after sunset, dedicated audio if away but expect parcels, etc.

But honestly, even if you have nothing, if you know a bit what you are doing with IoT with HomeAssistant if you buy the right hardware (i.e. verified as working by others, e.g. the Sonoff ones typically) it's at most an afternoon of tinkering for a setup that will reliably work for years.


Two wires, a button, a bell, and a battery pack.


string, hole, brass bell.


String breaks. Hole attracts insects. Bell is too quiet or too heavy.

Now we're in "under-engineering" territory. Also not good.


Test your string regularly and fill your hole. That should keep your bell ringing.


Yeah this would have been my answer, except for one catch: what do I do with the existing integrated button on the Blink doorbell?


I presume you want to keep the Blink doorbell for the camera functionality?

Then I guess 3d print a casing that just puts the ZigBee button on top of the integrated button?


Yeah, will probably have to consider something like that.


> For my doorbell I wanted something that lets me play a custom bell sound

But... why?


GP is clearly a maximiser rather than satisficer.

https://en.wikipedia.org/wiki/Satisficing


Over engineering is subjective / evolving.

You could have bought a bell...


> You could have bought a bell...

Over engineering is about the solution, not the requirement:

> I wanted something that lets me play a custom bell


"You could have bought a bell.."

No because similar commercial products were either out of stock or not compatible with my AC voltage.


If you find one that meets your requirements that is an option.

Granted maybe your requirements are ridiculous. But I also had cases where I DIYed a solution because the commercially available solutions all either didn't fulfil the requirements and/or had anti-features that ruled out their use. I haven't had any regret so far with these solutions, with some of these being active for over a decade.

There may be over engineering, but replacing a bought solution that needs to connect to the internet and someone else's computer to ring a bell with a simple 433MHz sender and a MP4-player module isn't that. Do you know what is required for a device to even connect to a WiFi? That alone is more complex than the whole system the user built here.


> That alone is more complex than the whole system the user built here.

so what?


Your comment got downvoted, because on this site it is frowned upon to write lazy, confrontative and uninformative comments. If you don't have an argument that furthers the discussion consider not writing instead.

Simple systems have the advantage that there are less moving parts. Less moving parts means less chance of failure. That is a trade-off an engineer will sometimes take even if it means building a new thing, sometimes something with more moving parts is needed and that is okay as well.

Maybe your requirement is to have a doorbell that does work when the internet is out. Who knows? OP might live in a place where this happens more often. Or they might not and like the idea to never again have to think about their doorbell-manufacturers cloud and the latests exploits targeting that IoT product. There are many reasons why simple can be the right choice and any true engineer would say: "depends" instead of "so what".


> If you don't have an argument that furthers the discussion consider not writing instead.

You are correct in general, but I think "so what?" was an adequate response (even though I don't agree with it) in this case that actually furthered the discussion as can be seen from your long reply.

We don't always need LLM-like, long comments. Sometimes "so what?" can be intriguing enough.


Pretty sure I have inherited some of your codebases.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: