665 karma · joined December 15, 2011
Should she further the "achievement" of her child through cultural conformance and obsession with "achievement" and corresponding status, or is it her who needs to find her own voice, not defined by external validation. She laments how comfortable she is with her status accredited largely to Stanford, and is ambivalent to whether she wants her child to drink from the same source.
This is a "humblebrag" mix of a genuine and slightly insincere search for yet more validation. Children are a symptom and reflection of their parents' values. To acknowledge the limitations or shallowness of a life defined by a pursuit of "achievement" and validation for her child, she must become self-aware and acknowledge the same throughout her own life.
Efficiency is analogous to velocity, with gains analogous to distance. Highly efficient developers must still travel non-trivial distances to achieve performance gains, and therein lies the core of my epiphany, that performance is not efficiency, and highly efficient developers must spend non-trivial amounts of time to achieve performance gains that may in fact undermine development velocity, CPU efficiency per task, architectural efficiency (DRY), time efficiency (latency), etc...
One of the great personal epiphanies of my professional career was the discovery of data pre-computation FLOABW. More specifically, what I'm talking about is data denormalization.
I had always been aware of caching techniques, but beyond that, data normalization was so ingrained into my mindset, that storing any piece of data that could otherwise be derived from another seemed like heresy, something only an amateur or fool would do.
What really opened my eyes, was when I was forced to build a social network atop MongoDB (ouch), and I had to resolve the incompatibility of relational data, but with atomic write, with no join or transactional support. What I discovered, was that if care was taken to create a canonical representation of the data, a multitude of query-able denormalized derived tables could be utilized, and could in fact offer dramatically superior performance compared to its RDBMS equivalent. What was especially shocking, was how obvious this was in retrospect and how blinded I was by the assumption that perfect data consistency was a requirement for all software.
I now view most tasks with the consideration, "What would this look like if we ignored efficiency in favor of raw performance and might that be worth it?"
Serial example:
async function someAsync(list) {
let ret = [];
try {
for (let item of list) {
let res = await asyncFn(item)
ret.push(res)
}
} catch(e) { /* ignore */ }
return ret;
}
Parallel example: async function someAsync(list) {
let promises = [];
try {
for (let item of list) {
let promise = asyncFn(item)
promises.push(promise)
}
return await Promise.all(promises)
} catch(e) { /* ignore */ }
return [];
}1. Decentralization 2. Realtime 3. Spam protection 4. Contextual
1. Decentralization typically generates wide adoption, once it's able to overcome the barrier of entry to wide adoption. An excellent example of this would be JavaScript. It thrives largely because nobody owns it, and contributing to its success it's often used as a means to stave off the advantages of competing platforms.
2. Realtime meaning push, just because it's a modern technological expectation. Email frequently is realtime, except IMAP/POP.
3. GMail et.al have gotten pretty good here. Future solutions would need to be as good, ideally with some built-in mechanism for unsubscribe as well.
4. Contextual messaging would be the defining feature. It's a broad term that simply means some manner of object graph between messages that would natively support arbitrary organization of messages (flat, nesting, topic stream, overlapping (for edits), etc...).
> I see a lot of people take glee in punishing other people
The fact that prestige is more effective than force, doesn't mean that force isn't effective. Imagine someone who's completely undeserving of any prestige-based status, yet has the means to control a business. Prestige-based status is unavailable to them, so they will use force, and eventually, the only employees that stick around are those that accepts such uses of force. (Imagine a toxic work environment)
Silicon Valley on the other hand (or engineers) are in high demand, and thus have no need to endure use of force (abuse) because there are those that will employ them that are deserving of prestige.
Does anyone here actively use Swarm or any other Ambient Social Network? Why & what is your take? Like the various other Ambient Social Networking apps that came before it (Highlight, Sonar, Banjo), it would seem to suffer from a severe chicken and egg problem.
Long story short, it's not difficult to "sell" managers when the alternative is anarchy.
I think managers are toxic in an engineering organization, and a disincentive toward expertise; Rational intelligent engineers would be foolish not to abandon their expertise for a more rewarding (financially, politically, effort-wise) management track. That said, I consider it even more foolish to have nothing in their place. Managers serve a variety of roles that will be filled, implicitly or explicitly in any tribe/organization. Further, they resolve the matter of hierarchy and eliminate political position jockeying (while exacerbating other forms of politics).
If you pay attention, you'll see that modern software organizations are straining on the verge of breaking with current management styles. No viable alternative has reached mainstream (except maybe holocracy), but in the coming decade, one will.
In my company, we're replacing the classic management hierarchy with something closer to a federated republic where the various roles of management are broken into separate roles for separate individuals, with the goal of placing engineers on top with multiple peer-based support roles. Something close to this will be the software organizational hierarchy of the future.
[1] http://www.slate.com/blogs/business_insider/2014/04/25/googl...
Correspondingly, one of the vices(?) of socialism is the presumption of a single societal good. This of course makes sense when we have non-reproducible/limited resources like the environment or rights that could conflict like the use of force, but for all other resources like how we spend our lives, what we build, where we go, what we enjoy, freedom by definition means a subjective "good".
I always find it curious when postmodernism (skepticism of societal mores) presumes any form of objective truth.
Butter......... 4.89 cal/gal = 3,252 cal/lb / 665 gal/lb
Cheese......... 4.75 cal/gal = 1,808 cal/lb / 381 gal/lb
Milk........... 2.27 cal/gal = 276.7 cal/lb / 122 gal/lb
Chicken........ 1.92 cal/gal = 993.4 cal/lb / 518 gal/lb
Almonds........ 1.35 cal/gal = 2,608 cal/lb / 1,929 gal/lb
Almonds Milk*.. (See Almonds)
Ground Beef.... 0.81 cal/gal = 1,506 cal/lb / 1,847 gal/lb
Almond Milk
* Almond Milk is basically almonds + water, but the added water is eclipsed by the almond water.We see here, almonds aren't 10x more efficient, but closer to 2/3 more efficient, and of course cow milk is 2/3 more efficient than almond milk.
Further,
More than half the entire US water supply goes to livestock
Water going to livestock is a misrepresentation since not all of it goes to produce meat, but in fact goes to produce milk, butter or cheese. I will admit though that the numbers above look slightly suspect. How/why would butter be more efficient?Lastly, it completely (perhaps ignorantly again) misrepresents other meats with the following 2 easily disproven quotes:
Meat processing, especially chicken,
also uses large amounts of water
and... The more plant-based foods we eat versus
animal-based foods….the less water, energy,
and other natural resources we use
This is clearly false from the numbers above where chicken is actually 42% more efficient than almonds(!), which of course completely validates the anti-almond press and invalidates this entire blog post.[1] http://www.waterfootprint.org/?page=files/productgallery where beef is listed at "15415 litre/kg"
Perhaps you're right, and I merely remain wholly unconvinced, though I acquiesced in the OP that perhaps it will be necessary. Optimizability dictating language features to this extent is the tail wagging the dog. I think this would undermine the ecosystem by creating a subset that is neither Java nor JavaScript, neither safe nor dynamic; a lowest common denominator of sorts that may do more harm than good in the competition with native.
Some examples of strong mode changes we are aiming for are:
accessing missing properties throws, arrays cannot have holes,
all scoping errors are static, classes are immutable.
Specifically, "accessing missing properties throws" will undermine how developers use the language. Options objects require this as a feature. Immutable classes might also be an issue as language extensibility / monkey patching is another feature, enabling a whole swath of Aspect Oriented Programming solutions like New Relic's monitoring or the node.js async trycatch library.I do wonder though, in fighting for its life against native, whether JavaScript will need to adopt optimizing solutions like "strong mode" to strengthen where it's weak.
EDIT: It's really unfortunate that I'm getting down voted so severely (from +3 to -3 in <10m). HN increasingly discourages discussion and debate. I don't think there's any question that my comment adds to the conversation. At most, I could have added, "In my opinion..." to the beginning of my comment.
From Wikipedia[1]:
E = mc2 has frequently been invoked as an explanation for the origin of energy
in nuclear processes specifically, but such processes can be understood as
converting nuclear potential energy in a manner precisely analogous to the
way that chemical processes convert electrical potential energy.
I don't know, but it seems reasonable to me to conclude that when Einstein stated the following, he may have been referring to mass-energy-equivalence rather than nuclear potential energy, which in fact continues to hold true for the foreseeable future: There is not the slightest indication that [nuclear energy] will ever be
obtainable. It would mean that the atom would have to be shattered at will.
[1] http://en.wikipedia.org/wiki/Mass–energy_equivalencePrioritizing cofounders over spouses surrenders Silicon Valley's moral authority and undermines its cultural leadership.[1]
I've always found prioritizing cofounder over spouse a sad depressing commentary on priority of money over change by bad actors. Innumerable colleagues and VCs have quoted me unprompted, "You can divorce a wife, but you can't divorce a cofounder," leading me to doubt their integrity; It's only true if you prioritize your business over your vows.
It is far more difficult to succeed when prioritizing family, but such is the burden of leadership. Moral authority, a prerequisite of true leadership, derives from such commitments.
[1] Power derived when a leader embodies the values of their followers.
2. Yes, I agree on a VC's concern of risks on the viability of a market. (See First Mover Advantage myth) I'm focusing more on the way it's communicated rather than the content or the why.
3. Yes, I think you're right that a VC is masking weakness if he asks this, as opposed to, "How are you different from X?" Though, IMO it's still an assertion of dominance, similar to a veil of bravado.
The key insight though, is that dominant individuals tend to respond to assertions of dominance with their own return assertion of dominance. In other words, they don't like being dominated, and it's this reaction VCs are typically looking for as dominant behavior is likely perceived as a requisite character trait for entrepreneurial success. Programmers though tend to conversely be a prestige driven culture and respond negatively to dominance challenges like this.
If you're curious to know more, checkout the very interesting paper "Two Ways to the Top: Evidence That Dominance and Prestige Are Distinct Yet Viable Avenues to Social Rank and Influence"[1]
[1] http://www2.psych.ubc.ca/~henrich/pdfs/Cheng%20et%20al.%20(2...
[1] http://usgaming.msi.com/Product/2014/Notebook/GS60-Ghost/
Using a decarboxylase or AADC[0] inhibitor like EGCG[1] found in green tea extract limits peripheral serotonin metabolism, especially if you're supplementing with serotonin precursors like tryptophan or 5-HTP to avoid heart-valve issues.[2]
See Examine.com's note in the 5-HTP article[3] and the associated citation.[4] 800mg of EGCG 2 hours prior to supplementation demonstrated decarboxylase inhibition.
[0] http://en.wikipedia.org/wiki/Aromatic_L-amino_acid_decarboxy...
[1] http://www.amazon.com/gp/product/B000MYW2ZA/
[2] http://www.ncbi.nlm.nih.gov/pubmed/15781732
A stick figure running does not have an identifiable left or right side...