Discussed at length:
6,352 karma · joined July 9, 2011
The problem then becomes one of identifying the crucial part of the challenge. If framed that way, your comment doesn't really help.
Here's a discussion of the main idea:
https://news.ycombinator.com/item?id=13883954
Here are other submission of the same story, and the inventor's rebuttal of some of the criticisms:
https://news.ycombinator.com/item?id=14163971 (Inventor's defence)
https://news.ycombinator.com/item?id=13901392 (submitted video now unavailable)
https://news.ycombinator.com/item?id=13890437
https://news.ycombinator.com/item?id=13885124 (Repeat of 13890437)
Can you be more specific about why you think this is "a flood?"
I find the display crowded, but there's a lot there. I wonder if you could provide a "novice" mode that has a lot less detail, but gives significant "bang for buck". Then people can learn how to read the basics, and see that there is more information if they choose to self-identify as "experienced". It might help prevent the "Wall of Stuff" response.
The information appears to be useful, and the fields and abbreviations have pop-ups to name them, even if they don't have complete explanations about their meanings and implications.
In short, I like it, and if I want a tool like this I'd use it. I'm not sure I'd remember where it is if at same random point in the future I wanted the facilities it offers.
That's a problem I've never seen a solution to.
350 comments
They aren't. You made this assertion:
... if someone can't comprehend a
paper diagram they can't comprehend
this either.
I think what you've said is reasonable, although it doesn't really address the poster's questions.
You need to decide what you want to accomplish. If things can be changed, would you want this job anyway? If you do want this job (assuming it can be saved/fixed) then what is it that needs to be changed?
Your point 6 nails it - as I see it you need to go to the CEO and say that while your title is "manager", your "team" is actually going to and taking direction from the CEO. As a result, you say, you are unable to do the job.
Now you need to make the decision as to what you want, or you can simply leave it up to them. Choose:
* Say that you require the authority as well as the responsibilities, so your team must only take direction from you, except in exceptional circumstances which must then be confirmed by you;
* Say that since you are not given the authority of a manager then you require that you return to being a member of the team;
* Give them the choice between the above two options, and that whatever is agreed must include written confirmation of the separation of duties.
But you must decide what it is you want to achieve. Yes, it would be a PITA to relocate again, but as it stands you will be miserable, in danger of being "let go" regardless, and have no control. If you do take control of your own destiny, at least you will have some control!
You have the title of manager. That doesn't just mean that you tell your team what to do, it also means that you must manage your relationship with your manager - the CEO. Perhaps even start by saying that you are keen to make a success of your position, you need their assistance and guidance, and that to do your job properly you must be given the authority. To phrase it like that means they demonstrate power by giving you the control you need.
FWIW. As I say, random advice from a random stranger on the internet.
The origin of the word bug as
it pertains to engineering goes
all the way back to 1947 when
Dr. Grace Hopper discovered a
moth stuck in one of the relays
of the Mark II computer.
Reflect C across the X axis, and that's point 2A.
So you're not missing anything, the article is misleading at best.
In short, to take the sum of two points A and B, draw a line through them both to find a third point on the curve, reflect that point across the X-axis, and the result (which will also be on the curve) is A+B.
If A and B coincide then use the tangent at A.
The point at (vertical) infinity plays the role of the zero.
Really?
> I can't see where that was written
^^^^
> Only that malicious users may read
> past the end.
Reducing complexity
Improvement is not that much effective?
Actually, we are optimizing the wrong way!
Really ;)! When optimizing code, you have
to, in order:
reduce complexity;
tune your compiler;
optimize your code.
So, how can we reduce complexity (Currently
O(n) for both algorithms)? Simply by storing
the string length somewhere! The complexity
is then O(1)
But it's all there, and either you've read it and I don't know what you mean, or you haven't read it, and I've provided the pointer for you.
But you're right, and it does put the entire article in question. I'm tempted to use this as an interview question:
There's a bug in this code - can you find it? Talk to me about why this is a bad thing to do? How can we fix it? What's the most important thing to be thinking about?
I was also interested to read the follow-up linked to from the bottom of the article, but that's a 404.
> As you can see, it can be totally transparent for the user. You just have to take care ...
It's that word just that bothers me.
"Programming is simple, you just have to write the code."
"Bug-free programming is easy, you just have to avoid putting bugs in."
Yes, this code "just" requires some care.
There are a number of other submissions of this story, but the titles vary wildly and I haven't been able to find any other significant discussion.