This is true, to a certain extent. But it doesn't mean that masters for vinyl always have more dynamics left intact.
More often than not these days, the same compressed master is used for the vinyl. To combat the groove-jumping problem, the overall level is simply dropped.
I use Gitit [1] as my personal wiki for notetaking. I've been pretty happy with it so far, as it uses the excellent Pandoc as the backend. I have not heard of Vimwiki until now - can you tell me your favourite features?
* links (to other wiki pages and content), move cursor over link and <Enter> will open wiki page, link in browser, image in image viewer, pdf in ... all from your console
* manages todo lists (including status indicator auto update for sublists: [.]->[o]->[O]->[X])
* headers (mostly useful when exporting to html)
* table creation and management
Overall a very lightweight and tightly integrated vim plugin, but gitit looks quite interesting, might give it a try.
The article brings to mind this wonderful short story by Ray Bradbury, "Pedestrian" [1]
"What are you doing out?"
"Walking," said Leonard Mead.
"Walking!"
"Just walking," he said simply, but his face felt cold.
"Walking, just walking, walking?"
"Yes, sir."
"Walking where? For what?"
"Walking for air. Walking to see."
> But in absence of this conflict, or the external meaning that is the cause of the (perceived) conflict, they wouldn't know what to do with their own existence
What nonsense.
> "Google" is nothing more than a tightly-bound collection of humans.
Yes, and collections of humans tend to exhibit emergent properties / behaviours which are not necessarily ideal in all respects.
Discussion of these properties / behaviours, and their desirability, is not a bad thing.
> They see the world in a black and white. "Us" and "them".
This is humorous to see in a post expounding a false dichotomy between the "two" types of people in the world.
I'm interested to know how you manage the risk inherent in project-based billing.
In my experience it is simply unworkable: the client will provide the vaguest of specifications and providing them with a set-in-stone price raises unrealistic expectations. The requirements are simply too fuzzy at the outset of a project to be able to price it accurately.
Of course the solution only becomes more concrete as the project progresses and requirements change and crystallize based on feedback. This is expected behaviour of course, but I've never been able to reconcile it with project-based billing.
Do you simply allow a certain buffer zone and take the good with the bad?
I'll just quote myself: "Personally, I figure out the worst-case scenario and price it for that."
Experience helps with the above. Obviously you can never know precisely how much effort something will take. Stuff comes up. Even if the work itself is stupid easy, it might take you 2 hours to find the exact line of code that needs to be changed and sometimes it takes 5 minutes. And you never know which is which. So charge for 2 hours.
> the client will provide the vaguest of specifications and providing them with a set-in-stone price raises unrealistic expectations.
Clearly define the parameters of the project. Clearly define what you will do. Don't do any more or any less than that.
If the client needs something extra done, and this happens, simply price that out separately.
> The requirements are simply too fuzzy at the outset of a project to be able to price it accurately.
I agree. Experience and clearly defined parameters and contract goes a long way in project based billing. If requirements are fuzzy then we developers need to help the client to make them clear by asking the right questions.
I'd agree with that, and also - an intense dislike of unnecessary repetition / work is definitely a good thing. I'm not sure using Vim causes that, but it definitely reinforces it.
For those that are interested, I would recommend "Practical Vim", and it includes many examples (including the above one) which really accelerate the learning process:
I would imagine that it would be much easier for Stripe to acquire local Stripe equivalents and rebrand, rather than trying to navigate the labyrinth of financial regulations in each location. Maybe that's the game plan for Pin?
From another Perth guy, more congrats to the Pin team (I actually discovered them when I had the same idea, googled it and found that it existed already - in my own town!)
More often than not these days, the same compressed master is used for the vinyl. To combat the groove-jumping problem, the overall level is simply dropped.