1,038 karma · joined May 14, 2010
One time the biker got pissed at me, when he had a red and was making a turn in the wrong direction at night. He and the biker in front of him didn't slow down at all. I narrowly missed the first biker and paused when the next guy hooked me with his handlebar.
I managed to get over it relatively quickly, with several realizations.
The hurt I felt, wasn't that love was lost, but that I no longer had a place for all the love I had. This leads to the understanding that love cannot be lost, it's a resource inside us all, and we just have to find other means to redirect it.
To think of love, from the perspective of a single entity, leads to the kind of thinking of it being worthless. But the shared love that we think of romantically is coming from a multitude of entities, it isn't lost but as a resource redistributed elsewhere.
In death love is truly lost on one side, but is also somewhat immortalized on the other. This solidification of love, is similar to the concept of heartbreak, we don't want to share that love, but the easiest way to free ourselves of the pain is to love.
Love is something you create and give. It can't really be lost, because every day is another day to create or find something to love. You have to separate the concept of love from the entities and relationships.
I still love her, always will, but I had to say goodbye to the friendship because trying to hold onto her was doing exactly what you said. It was killing me, trying to hold on to the relationship, as she started moving on with another. I realized that they deserved a chance, she was chosing to move on with her life and love. That hurt, but what hurt the most was that I couldn't share my love with her any more without possibly alienating him and the love he gave.
I realized those things about love coming from inside and being okay with moving on and focusing on things and others. Accepting that love and care sometimes require sacrifices of ourselves for the good of others.
This might be a good candidate for having the link updated.
I would contest that it has no relation, I could be wrong since I have no knowledge. That said I always saw it as a relation to the cards themselves and the magnetic-strip on the back of the card.
Though it might also mean that scores will be more variable for new submissions, and that may have an impact on front-page/2nd-page variability and bounciness, which doesn't seem like it would be friendly to casual users.
The HN algorithm has temporal-gravity to help pull down old content that wasn't hugely popular. Due to that algorithm if the content doesn't take off in the first hour, it likely won't take off.
Those 2 points point to a far simpler solution. Just show most of the items from the last hour on the new page. So instead of 30 items, you show 100 items on the new page, which should accommodate most of the recent posts without requiring any clicks.
(minimaxir's point is also very valid.)
https://www.ftc.gov/tips-advice/business-center/guidance/ftc...
Maybe growing up there, but I actually prefer the solitude. The interesting thing about those few small houses is that you end up getting to know the people in your area and around you pretty well. Nearly everyone. So I wouldn't make the assumption that "it must suck".
I could make the same assumption about any over populated area, like the Bay Area, because it's nearly impossible to really know your community and traffic is horrible. Ugh, it must suck to be an engineer working on some startup and living there.
If they wanted to bring $100B back, they would pay up to $35B (the use repatriation fee - minus the foreign taxes). So they really only managed to bring back ~$65B, that was created largely overseas, just for moving an asset across international borders. That is a sensible thing, to just toss away the valuation of Uber, to bring money into the US?
Legally fine, but it is not sensible.
It can be an annoying feature, though there are other things that can be annoying about actually reflowing the text as well, as a lot of the mobile layouts are already cramped, and as such zooming could cause other issues.
It's a situation where you're given several really bad options, and you need to pick one you feel is most optimal. Locking the viewport to a specific zoom-level to prevent the side-to-side swiping is an accessibility issue, but makes the layout simpler.
Most missing chars seem to be capitalized. A few specifics: F, H, B, P, X
Part of the issue was that Z comes right before that and was filled with one-sided words like 'dazed'(5/5 left-handed strokes) and 'sized'(4/5 LHS's).
And then you qet to Q and you're now forcing yourself to go in the opposite direction with a fatigued hand.
Pixel-art is great, when it is crisp. Most of his examples are crisp and well animated, until you get to his. The characters are oddly proportioned, but I can deal with that, and at least they were pretty crisp, but the interface around them was horrible.
Jason Calacanis went after their horrible tactics 5 years ago[0], and was very vocal about it. This is the first I've heard of them in 3-4 years, so I just assumed they had closed up shop.
Only one link among many. [0]: http://www.bizjournals.com/seattle/blog/techflash/2010/11/ja...
It was an inevitability, that the site would shrink, and that FB would either decide it couldn't continue to fund a small community or the handful of employees would decide to depart.
Currently, there are only 3 members of the team working at FB, and I have a feeling a few of them have decided to move on which has precipitated the closure.
I'm currently working on a system, but it requires user input, in order to bypass the limitations of the API.
When I was about 8-9, I found the mechanism, and ended up dismantling the system. I then wedged a little Wolverine action-figure's foot into the space to keep his foot down on the switch and ran the system without the cover, because it looked pretty badass to have the discs spin out in the open.
[In retrospect: All of this was probably a horribly unsafe thing to do, considering what would happen if the disc cracked or broke while spinning.]
The PoW system adjusts the difficulty based on the current distributed hash-rate, so an individual(or pool) is operating in a percent range of the total hash-rate.
To analogize the two, properly, you'd have to set the PoW system to the highest difficulty, and keep it there for every individual password you want to check.
Also the scrypt currencies have a fixed memory bound, AFAIK. While use in password cases, "could be" modified in the middle, doubling the required time-bound.
Having watched Jiro Dreams Of Sushi, his task is to provide excellence in food, in service, and overall experience. And at the root he needs to understand each component of the food and the service intimately, so that he can put them together in a way that is both pleasurable and fitting to the customer. He uses what he knows and the resources he has to create the best dishes he can.
For a programmer, the core of our trade is algorithms, and their combinations. You may not need to know them at the smallest details, or even that they are called algorithms, but to accomplish anything you will use them. Combining larger programs together in a specific way to perform something novel is an algorithm, though we may not call it that.
Next, data structures, understanding how to store information in a way that your algorithms can use and alter. This underlying knowledge is key to creating larger things from many small things.
Next, simplicity, combining logic and code together to accomplish the goals alone is not enough. While it may be simple to combine large things together, the question should exist of whether it could be done more simply. Simplicity can be hard to accomplish, but is easy to appreciate. Simplicity means avoiding cleverness, if possible, as it can make the program hard to be changed or maintained. Simplicity is elegant refinement, which leads to doing small things very well.
Those three things, in my mind, are the only pure things necessary to being a programmer. Algorithms, data structures, and simplicity.
The reasons none of the other things apply in my mind to the overly-general title of just programmer is that they are not required by every programmer.
Text Editor - Cannot pen and paper be used just as well in the task of constructing a program as a text edit?
Programming Language - Maybe I could have leniency here, you do need language to describe yourself, but not necessarily a programming language.
Databases - This is much higher-level than a regular data-structure, and as such isn't a necessity. Applies more to specific fields.
Algorithms - Yes, even if not known by name.
Math - This isn't a requirement, though it is a nicety. Some get by without knowing much more than the very basics of Arithmetic and maybe a little basic Algebra. It applies more to specific fields.
Debugging & Testing - These aren't necessary, but they help ensure quality or finding issues.
Documentation/Comments - If the code is simple enough, it should describe itself. That isn't to say documentation and comments aren't important, but they aren't necessities either. You should describe as much in comments and documentation as necessary, to provide clarity and usable instruction, and is a great skill to have.
I hope I've explained things clearly enough. Knowing one's craft is understanding the fundamentals, and that comes much further ahead of the tools one uses, within reason. In my opinion the single best thing for describing the craft of programming is the Unix Philosophy[1].
> "More specifically, since children have little formal or actual wealth ownership, we focus on wealth ownership by adults, defined to be individuals aged 20 or above."
[1](page 5): https://publications.credit-suisse.com/tasks/render/file/?fi...
[1]: http://www.the-numbers.com/movie/Transformers-Age-of-Extinct...
You don't have to do that, my password has capitals, but after I found out the shift the alphas to only one case I stopped typing the caps.
The commit does exactly what it says, adding one extra hyphen to go below the 's' at the end of the preceding line.
That's not exactly true. Since more people can upvote than downvote, the threshold for downvote privileges is > 325 karma. So downvoting is reserved for those that frequently interact with the service in a positive manner. Downvoting could have had almost zero impact done to it due to the small set of people with that privilege.
As quantity increased, and newer less frequent users stopped upvoting, because there was no way to discern one's value in that interaction. Downvotes could have held at a similar frequency, because of it's smaller group. The decrease in upvoting could be accountable for a large portion.
Also, I rarely used a mobile device for interacting with HN, until 2-3 months ago, because the interactions are quite crappy (one of the reasons they mentioned for opening the API up.)
Edit: It's actually interesting, that the upvote/downvote ability wasn't considered impactful, since you mentioned it further down in the article.