ispivey
Joined 18 years ago
Joined 18 years ago
Obvious pieces to me appear to be (1) roles and auditability (2) end-user front-end (3) filesystem interface & associated ease of access for various services. But I'm not an expert!
Therefore, you should avoid using *-device-width, since the
page won’t respond when the desktop browser window is
resized.
GMail, Facebook, New York Times, and lots of other smart folks don't show their mobile-web versions if you make the browser viewport very small. Their sites have min-width ~980px when viewed on desktop.I imagine this is because (a) their mobile sites use different interactions that require different DOM and JS, not just different CSS styles, and/or (b) those different interactions might not be appropriate on desktop even if you shrink the viewport and/or (c) it's confusing for the site to work differently when you resize your window and/or (d) they don't want to send unused JS/DOM to devices that aren't going to use it.
Any thoughts, kinlan?
Perhaps people are interested in watching some awesome founders speak.
"Assessing the security of software via the question "can we find any security flaws in it?" is like assessing the structure of a bridge by asking the question "has it collapsed yet?" -- it is the most important question, to be certain, but it also profoundly misses the point. Engineers design bridges with built-in safety margins in order to guard against unforeseen circumstances (unexpectedly high winds, corrosion causing joints to weaken, a traffic accident severing support cables, et cetera); secure software should likewise be designed to tolerate failures within individual components. Using a MAC to make sure that an attacker cannot exploit a bug (or a side channel) in encryption code is an example of this approach: If everything works as designed, this adds nothing to the security of the system; but in the real world where components fail, it can mean the difference between being compromised or not. The concept of "security in depth" is not new to network administrators; but it's time for software engineers to start applying the same engineering principles within individual applications as well."
http://www.daemonology.net/blog/2009-06-24-encrypt-then-mac....
Douglas Hofstadter wrote a good piece of satire explaining why it's oppressive by s/man/white, etc: http://www.cs.virginia.edu/~evans/cs655/readings/purity.html
Contrary to what you say, "they" was used as the singular neuter pronoun for a long time, until a concentrated effort to force it out of use in the 1800s. Some examples from a previous thread: https://news.ycombinator.com/item?id=6824352. Some history here: https://en.wikipedia.org/wiki/Singular_they
Given it's possibly (likely) ostracizing and there's nothing categorically wrong about using "they" as a singular neuter pronoun, I think you're on the wrong side of this.
People should certainly stop fighting; the answer is to just roll with "they".
I grew up taking great pride in "correct" English usage, but I now think insisting on gendered pronouns causes harm without any tangible benefit.
...
You can't get a job that requires a Github OSS history. You're severely disadvantaged in job hunting when OSS contributions are a major metric.
If people tested your suitability for a job by pair programming with you, or looking at code samples, you'd look just as good as someone who contributes to OSS. But because OSS is an important metric, you're disadvantaged.
Does this make clear how it's discriminatory?
- Use Vagrant and some bootstrap scripts (or Docker) to make giving them a dev environment easy
- Get them to use a git GUI like SourceTree (free & good: http://www.sourcetreeapp.com/)
- Build a workflow around pull requests / review branches a la github/bitbucket/gerrit so you can have them submit changes but an engineer reviews/verifies before it's merged.
In general, empowering them to do this is an investment in the future and well worth it.
If the initial $400k bought 10% of the company, USV would need to buy 10% of each subsequent round to maintain their ownership, which would be ~$12.5M. That's ignoring varying definitions of pro rata rights, other dilution but probably a good lower bound.
If the initial $400k bought 20% (more likely for Tumblr in 2007), USV invested ~$25M to keep their ownership stake.
Fred seems like the kind of guy who always does his pro rata, so I'd imagine those numbers are closer to reality.
previously cloudflare, dropbox, bebop, simpler, tinyco, macquarie, ibm, mit