This changed sometime in the early 20th century.
The source was some parenting/manners/etiquette book from 190x.
704 karma · joined February 26, 2008
This changed sometime in the early 20th century.
The source was some parenting/manners/etiquette book from 190x.
No type system support... but no catch block, either.
* Sample data for test suites. I have single files of such larger than 21MB in my current project's git repo, and I've seen much bigger. * Audio resources. * Large PDF documentation items.
No modifiers, no nonsense.
I love Vimperator.
What one application considers metadata is another application's data.
From the apparently trivial (file sizes, line numbers) to the domain specific (date of joining social network; file server cluster that hosts this image), each tool doing the work has a very different viewpoint.
The motivation for abandoning the distinction is this fluidity, not that there is no distinction.
(Sidenote: I like the Clojure definition of metadata:
"It is used to convey information to the compiler about types, but can also be used by application developers for many purposes, annotating data sources, policy etc.
"An important thing to understand about metadata is that it is not considered to be part of the value of an object. As such, metadata does not impact equality (or hash codes). Two objects that differ only in metadata are equal.")
Threads are crap as a programming model.
Something like Clojure's parallel-friendly constructs has the potential to make an Azul box shine, whilst avoiding programmer error.
The first is perhaps the most obvious: Mercedes, slicked back hair, always on the phone. They work by having a kind of primal desire to win: they never stop, they keep calling, they play hard, they give 100%. It's distasteful, but if I had to get 100M in sales, these are the people I'd try to attract. I've heard them called "lions". You need these if you're trying to win big contracts against competitors, because they can go from no foot in the door to a contract by sheer persistence.
The second is I think (hope?) more common in tech. Smart, fairly technically inclined, and long-term thinkers. They don't come off as slimy, but they do somehow remember your name. These people keep clients by learning requirements, keeping track of them, keeping relationships warm, and keeping the tech/product people loosely coupled with the customers. You need these if you're a tools company, because you live by long-term customers.
The third is more subtle, and I've only met one. This is the technically minded, completely non-conniving leader. By apparently completely honest, clear technical dialog with customers they build trust and confidence, which are the root of sales. It just happens that it's genuine. This works really well, but you sure can't fake it.
(I'm a Brit who's had a little too much social liberalism today. Sorry.)
E.g.,
* "this is how I work"
* "fool! You should be doing TDD/AOP/Agile/XP/NIH/WTF/BBQ!"
* "actually, that's not possible for reasons X, Y, Z."
The problem is that the respondent always assumes that the writer of the original post is in the same environment, subject to the same conditions. There's a name for this fallacy, but I don't remember it.
A similar problem is when posters assume that their situation is the typical one: I see this all the time as people post stories like "how to do X", omitting the crucial phrase "... in Ruby", or "in the web development world", or "on Windows". Knocking them down with "I think you'll find telecoms is a little different" seems to be a habit of mine.
Every browser that handles HTML 4 supports a kind of "tag soup". You must take explicit action to shift them into a strict mode; consequently, it does not take longer to "parse a broken schema" -- handling an HTML document without the final closing tags should be no slower than a complete document, because no validation is taking place.
There was a majority physical component -- actually using the mouse was much, much more painful -- but there was also a psychological component. I suspect that this was anticipatory tension or somesuch, similar to a flinch response.
To do anything interesting means reducing or delaying your paper output (which your supervisor will not appreciate), and to get the results published requires you to write so as to persuade people with no vested interest in publishing novel output to agree with you... but without being able to have a dialogue.
I recall one amusing paper review by three reviewers which was essentially
1. "the treatment of X is great, but I'd like to see more Y", 2. "too much Y, not enough X", 3. "both X and Y are fine, but I'd have been really interested in seeing Z instead", where Z was entirely unrelated.
How on earth could an author anticipate the preferences of those authors and get three recommendations? Well, picking a non-controversial subject would be a good start.
Multiply this anecdote up to the size of the academic and industrial systems, and it's no wonder that so many people decide that academia is not for them. These people tend to be lumped in with the people "not cut out for it", but I think a significant percentage simply realize that academia has a different value system, and don't want to participate. Some of those people go on to do interesting or revolutionary things in corporate research, or even in mainstream industry.
Would the world be better if they were in universities instead? Probably not... but we'd have our interesting scientists back.
http://repo.or.cz/w/MacVim.git?a=tags
and their Google Code updates list:
http://code.google.com/p/macvim/updates/list
MacVim has seen a huge number of changes in the 2+ years that TextMate has been under development: not least Leopard support, Vim 7.2 integration, and a ton of interface and speed improvements. They're on Snapshot 45 right now...
What's that joke about my brain being a L2 cache of Wikipedia? :)