Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
jaawn
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
15 ms
·
91.
▲
by
jaawn
11y ago
This generally rings true for me, it is almost required for developers to be continuously learning and honing skills as new patterns, technologies, and tools emerge. It is also generally helpful for developers to pursue side projects. Howe
92.
▲
by
jaawn
11y ago
And here is a link straight to the image (which is the only important content in this case): http://thumbnails-visually.netdna-ssl.com/the-only-10-slides...
93.
▲
by
jaawn
11y ago
FWIW, I thought The Interview was way better than I expected it to be. It is very, very silly, and it does not take itself seriously, but it wasn't particularly predictable either. Maybe you'd be pleasantly surprised?
94.
▲
by
jaawn
11y ago
I agree about your "real hype" statement. There is always the potential for a provider to build business value by nailing recommendation, especially when it comes to lesser known content. Most viewers have heard of big-budget
95.
▲
by
jaawn
11y ago
If that is the case, is that the fault of hiring and pay transparency, or the justice system?
96.
▲
by
jaawn
11y ago
Even political agendas and sensationalist trials need some leg to stand on to be successful. If you hire honestly and set pay honestly and fairly, with recorded justifications, it is unlikely that your company would suffer any negative rep
97.
▲
by
jaawn
11y ago
I think most managers would see that as an unreliable prediction to make, and not very valuable when making hiring decisions. When hiring someone, you are solving an immediate problem, and not often thinking of the future raises the person
98.
▲
by
jaawn
11y ago
If a manager and company have any justification for pay differences that are not due to protected classes, then they have nothing to fear. If they do pay people differently because of protected classes, they may run into trouble, but I thi
99.
▲
by
jaawn
11y ago
It is unfortunate that a large amount of the discussion is being distracted by the stringing-together-tweets thing. Yes, it was lame to do that, but isn't it more worthwhile to talk about the content? I think most of us probably work
100.
▲
by
jaawn
11y ago
This is a good point, especially regarding what would happen at a company immediately after going from opaque to transparent on salaries. However, the resolution is pretty simple. Employees can either accept the justification given by mana
101.
▲
by
jaawn
11y ago
Even if this is true, this doesn't magically make it not a gender issue. What if women are generally given less leverage by default in negotiations? What if implicit gender biases have a chilling effect on women's expectations w
102.
▲
by
jaawn
11y ago
Another factor to consider is that, at huge companies, not all management has a unified vision. It is entirely likely that the article source's manager and the next manager above him/her disliked the spreadsheet while the "o
103.
▲
by
jaawn
11y ago
As I've been trying to explain, the issue is with the secrecy and broken promise/contract because it puts one person's interests ahead of the other. If you disagree with that kind of relationship, that is fine...don't a
104.
▲
by
jaawn
11y ago
It is, quite simply, that they feel intense negative emotions and betrayal. It does not really need any more explanation than that. You can tell a distraught "victim" of cheating that they weren't technically harmed, but I
105.
▲
by
jaawn
11y ago
Its intent is to do something which harms. I don't think the infinitesimal collection of people who want their partners to "cheat" on them justify the flexibility you're implying. Basically, what you are saying, is t
106.
▲
by
jaawn
11y ago
I think we've learned over the years that perfection is an unrealistic goal when it comes to data security. We should still strive for better and better methods of securing data, but I think we should also try to change our expectatio
107.
▲
by
jaawn
11y ago
I would completely agree if the site were geared toward open relationships, but it is built on assisting people harm their partners in secrecy. It has nothing to do with the monogamy issue. Basically, there are a few truths we know about u
108.
▲
by
jaawn
11y ago
I don't think this argument really applies. It would be one thing if the site was devoted to assisting "open relationships," but it isn't. It is specifically a service to assist people in "cheating" on their
109.
▲
by
jaawn
11y ago
I hadn't considered this article's perspective before, but I think it is very compelling. A lot of commenters (and likely readers) are probably focusing heavily on the perceived impact of the "fraud" of reporting X amou
110.
▲
by
jaawn
11y ago
...and you also don't get thousands/millions of billboards put up for $500. This part of the comparison should probably be ignored as it is more to do with the intrinsic differences between the physical world and the digital &quo
111.
▲
by
jaawn
11y ago
I don't think this is necessarily true. Attractive, non-animated banner ads are my "favorite" type of online advertising to encounter. Standard AdSense text ads are ugly and add so much clutter to the page because of the ad
112.
▲
by
jaawn
11y ago
Most (all?) encryption functions are also hash functions, they're just special hash functions with the extra property of making it extremely difficult to discover the source. (edit: I realized after posting this, that this item is inc
113.
▲
by
jaawn
11y ago
Because, most of the time, performance doesn't matter enough to justify it. Custom solutions are only necessary if you know performance is critical to your application's purpose, and that you need to squeeze as much out as possib
114.
▲
by
jaawn
11y ago
https://news.ycombinator.com/item?id=5072224 (edit: this is an explanation of what "middle-brow dismissal" is)
115.
▲
by
jaawn
11y ago
In general, you may be right, but the security suggestions in this particular post are the same I hear from people "who have experience in security." Also, they often encourage readers to basically go out and find the thing every
116.
▲
by
jaawn
11y ago
or 3 - stop trusting the internal String implementation to be as efficient as possible, write a wrapper you can update with the best method for the current version, never look back :-)
117.
▲
by
jaawn
11y ago
I think you're alluding to a generic, implicit promise of reasonable performance. I definitely think this is a valid assumption to make, so you are right to point it out. Any API function needs to have reasonable performance, or else
118.
▲
by
jaawn
11y ago
I would usually choose option 2 or 3, but that is because usually small performance discrepancies are unimportant. If performance is paramount at the point in the code where the library is used, I would opt for (1) or a fourth option you
119.
▲
by
jaawn
11y ago
One method would be to have an informal heuristic you use when you're about to call a library: are the performance characteristics I need guaranteed by this library? If yes: proceed, if no: use a different solution or proceed with cau
120.
▲
by
jaawn
11y ago
I would say: definitely yes. I definitely think it is more common for a programmer to expect that if they make a substring, and never reference the original string again, only the substring would remain in memory after GC. It is more intu
More ›