Hacker Newsnew | past | comments | ask | show | jobs | submit | spfzero's commentslogin

Maybe he's anticipating making a quick getaway?


Test requirements often arise after system design is complete. Engineers need time to examine the system, theorize failure modes, and design the tests. Also time to test the system, find some unexpected failure mode, and then design yet more tests.


Would it be so hard to add a diagnostic interface? That’s all we’re talking about here. It seems like you’re making the problem more difficult than it is. And they’d had to have known ahead of time if they wanted to test voltage curves of motors.

Your answer is good in the general case, but for the anecdote, the design was clearly bad.


This was a test fixture so probably banana leads.


I color code _everything_.


That stood out to me as well when I read the article.


The multimeter in the photo has the probes plugged into the volts/ohms jack, though. Maybe it was a different meter.

I figured this was going to be a story about trying to measure voltage with the meter set up on the 10A current range.


yeah i don't think he took a photo of the multimeter to use in the article before unplugging it. he didn't yet know it was important


As a counter-argument, you usually need to read a lot into the reported numbers, for example read the 10K notes for multiple years in the past. That's the only way to know that the 3B in assets showing up on the balance sheet for "goodwill", to use one easy example, are not really worth 3B. There are many more-nuanced factors that work alike. The reported numbers are what the accountants think might fly under GAAP, and the accountants work for the CEO, who has a say in the accounting "intent".

To test whether markets are perfectly efficient, just look for large movements over time. If a stock goes up 20% in a year, the market might have undervalued it last year, or is overvaluing it this year. It's unlikely the it was correctly valuing it at both times. In the absence of a Covid-19 pandemic, act of god, etc. of course.

You could say that the market just takes "investor sentiment" into account, and is therefore still efficient. But value investing is a strategy that looks for misplaced investor sentiment and exploits it. If that's the way you define an efficient market, than I'd say an efficient market is no obstacle to a value investor.


> If a stock goes up 20% in a year, the market might have undervalued it last year, or is overvaluing it this year. It's unlikely the it was correctly valuing it at both times. In the absence of a Covid-19 pandemic, act of god, etc. of course.

Or the company has grown its revenue by 20% in 1 year which isn't necessarily unheard of. Or they significantly beat the expectations of analysts / their own guidance. In all of those cases the stock could have been correctly valued & still experienced growth.


Sure which is why I said "unlikely", rather than "unheard of".


A 20% rise in a stock doesn't constitute evidence of market inefficiency. In most cases that increase is due to new information becoming available.

If you say that value investing still works then where is the evidence?


>To test whether markets are perfectly efficient, just look for large movements over time. If a stock goes up 20% in a year, the market might have undervalued it last year, or is overvaluing it this year. It's unlikely the it was correctly valuing it at both times. In the absence of a Covid-19 pandemic, act of god, etc. of course.

This is technical analysis not value investing.


It's not the investment thesis, it's a thought experiment to test market efficiency. It's a test to see whether markets are always efficient, and to me demonstrates that they are not, and that value investing might be an interesting thesis to pursue still.

People have been saying for decades that value investing is not possible since the market is too efficient. My point is that it is not efficient enough to prevent value investing from being a successful strategy.


Yes. Building something complicated requires formal education plus years of experience attempting to build the complicated thing.


Some endeavors require historical knowledge, aircraft engineering being one of them. If you break the chain, you lose it; policies that were developed over decades are discarded. "Why do we need to do it this way, this other way is faster and cheaper!" No one is around to explain why any more, so the lesson is learned the hard way, again.


It's fun for them and they don't have the expectation that it will make money. And probably it doesn't, and that's fine, move on to the next thing. But once in a while, maybe it resonates with a greater need.


But it's your chance. It may or may not become a business model. That's the risk. You take a risk to get a chance to make a profit.

It's impossible to come up with a business model that does not depend on chance.


It wasn't like programmers were less creative or productive than they are now. The languages were fully capable of doing anything on a server you could do now. It was mostly C. Programmers were creative and smart, just like now, and could implement anything, albeit ground-up since there were fewer existing building blocks to reuse.

A lot of sophisticated anti-spam software depended on some sophisticated anti-anti-spam showing up first, and there is a lot more of that now for sure.


Even now forums rely on manual after-the-fact moderation and not just algorithmic pre-moderation.


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

Search: