Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login

The article shows that there is at least one engineer who looked at the code and found issues.


sort by: page size:

A junior engineer who read the documentation, but didn't quite understand parts of it. And also got parts mixed up with documentation for something else.

That's different. That engineer is just mistaken, but at least is acknowledging that a problem exists, that's a good starting point.

Sounds like an engineer knee deep in diagnosing the issue.

This is a great example of a "10x engineer". Someone less experienced would take 10x or 100x the time to investigate and resolve this problem.

Also, the engineers are often well aware when something is wrong or dubious.

But there's a difference between knowing that and having the power to do something about it.


The engineer who includes the binary is responsible for understanding the ramifications

Wouldn't be surprised if some overworked engineer made a mistake.

That's not engineering. What they did is identical to developers copying code from SO and running it to see if it works.

That's not engineering. What they did is identical to developers copying code from SO and running it to see if it works.

What kind of engineering code you dealing with? Just curious.

This could only be the case if the engineer doing the development was the same person as the engineer doing the QA.

Like he said, an engineering problem.

It’s a hard problem that engineers- if they really are good engineers- should question the utility and consequences of solving.

Thank God some of them are.


Lots of Engineer Spelling in this article...

A lone "senior" engineer could, maybe, but definitely not someone who hasn't worked in the problem space

Since the article sucked, I'll give the 2 best engineering advice I've received from 2 different senior engineers:

>Remember when you'd go to eat at a restaurant, and the kids menu has that game where 'What's the difference between these two pictures?' That is Reverse Engineering. You have a part that works, a part that doesn't work. What is different?

>"You just kind of figure it out". Not sure how to start/solve a problem. Figure it out. This means researching, doing math, proving, and testing. And as I've done this more and more, math is really really useful to prove things.


It's rarely the engineer deciding this.

Ah, interesting. Originally, it would answer that question correctly. Then it got concern trolled in a major media outlet and some engineers were assigned to "patch it" (ie make it lie). Then that lie got highlighted some places (including here on HN), so I assume since then some more engineers got assigned to unpatch the patch.

I'll take that as supporting my point about the folly of wasting engineering time chasing moving goalposts. :-)


But it included this one engineer
next

Legal | privacy