This advice works only if 5 prerequisites are met:
- the coder is fluent in programming. Beginners will not know how to architecture things, and need to fiddle way more. It's impossible for them to create a doc that will make sense from the top of their head.
- The coder understands the problem well, and it has a known solution. Many problems are better understood when trying to solve them, by exploring its space while programming. It's impossible to start documenting something you don't know very well. It's espacially true if you have to come up with a novel solution.
- The problem is well defined. Unlikely. Clients don't define their problem well, and it's half our job to extract the information from their brain. However, while it is sometimes possible to get that on paper, and formalize it, most of the time, programming an incorrect PoC and iterating on it is a better interface to communicate with the client: they have a visual result to discuss. Writting a doc that you trash down every day would be a waste.
- The coder understands the field well. I'm currently working with a Bank, and I don't know the field. Many algo I must implement are in the head of my clients, and the quickest road to understanding them is to peer code them. They attempted to make a formal doc first of course. After 6 months, they still don't agree on how to do some things. One week of coding with me forced them to confront reality, and take concrete decisions.
- The coder has the big picture. Starting with a doc assumes you know what your API should look like. I would recommand that you do know, if you don't, you are probably in trouble. But it's a fact of life that sometimes you can't figure it out, and starting from something incomplete and coding it will make the big picture clearer.
That's a lot of pre-conditions.
My experience is that most teams starting with the doc (or tests) don't ship, or end up shipping only once they start fiddling. Those who do are excellent teams, the best ones, and I love working with them. But they are a rare bread. We are usually an average team, not ticking all pre-conditions, and not composed of only very skilled or experienced professionals. We fiddle a lot.
And unless you have a great team leader, taking such an ordinarity team and making it write the doc first will result in a terrible doc that doesn't match the solution to the problem, that you will rework again and again, while nothing is getting in the hand of the client for concrete feedback.
I favor a middle ground: start with paper, but don't pretend you are going to have a full spec.
Voss teaches classes, as well; they are useful well outside the bounds of hostage negotiation, in almost any context where soft interpersonal communication is a determining factor.
My introduction to Mr. Voss was through an immersive training event, where the participants got a small taste of his world/skillset. Watching him work was illuminating, to say the least. Mostly, the value I've retained from that experience has been applicable in business contexts, and, ironically, during the home-buying process. It changed how I looked at interpersonal conflicts, and has been very handy in figuring out a path which essentially leaves all parties feeling like they got what they needed to get out of the deal.
I just listened to an interesting podcast interview with the author of this book [1].
He discusses what the GP said above: there's a team of say, 7 people listening, and each person has a specific job, depending on the situation: listening for positive things they say, negative things, tone, timing, background noise. Pretty interesting interview.
- Transactions are more expensive in BTC for small amounts, and more expensive in Visa for big amounts.
- However this is only true if you use on chain transactions for BTC. BTC transactions using lightning are always cheaper than Visa no matter the amount.
- Lightning nodes do not yet form a network big enough to cover 100% of the transactions, and most transactions are small, so the idea that VISA transactions are cheaper for most people is, for all intents and purposes, mostly true at the moment.
Lightning, though, is quite an interesting system. Half of the solution it offers is technical, but half of it will be the social construction of the network of channels. I doubt most people will open one consciously, but I assume wallet providers will make that automatic.
Eventually, this means somebody needing the decentralized aspect of BTC will be able to open a channel and profit, while somebody who wants convenience will use a centralized wallet and be happy.
I suspect most people will want the turn key solution and that the system will centralize a bit.
But again, I see your point: our financial system is already very efficient, BTC will have to be way better than it current is before it can compete with it for day to day use.
I'll keep an eye on lightning though. It makes any transaction, no matter the size, instant, and cost a tenth of a cent. It has potential.
And no matter how well it does, investors will expect growth. So what further sliminess does Diablo Immortals 2 do to get growth? This behavior is unsustainable.
Theorising that high carbon steel can form by mistake in some scenarios is no where even remotely close to the information management necessary to spontaneously create a tesla.
And even a Tesla is no where remotely close to the organic cell. The smallest known functional, and most importantly, stable biological unit.
That's the interesting part of RNA. You don't need a reader!
RNA can act like an enzyme. They can fold and form strange shapes and have some "sticky" parts, so they can replace the activity of enzymes. Enzymes made of proteins are more efficient, so now most(all?) enzymes are made of proteins. But in the initial form of life perhaps enzymes were just a short RNA strip.
RNA can be copied. They can be in a single strain, and they can collect the parts [1] and make an inverse copy, and then separate. DNA is better with a lot of helper enzymes is much better, but in the initial form of life perhaps RNA is good enough.
None of these steps need a reader, so perhaps they can form an initial and very inefficient life(almost-life) form.
> None of these steps need a reader, so perhaps they can form an initial and very inefficient life(almost-life) form.
May I ask, have you ever considered if any of these systems that you're researching or investigating are the product of deliberate engineering rather than random chance?
You have the same issue with smokers and cancer, obese people and heart attack, drunk/tired/hurried drivers and accidents, drug users and depression, sugar consummers and diabetes, extreme sport hobbyists and traumas, etc.
At some point, half of the population fall under some risk factor that they could avoid, but instead, make society pay for it.
That's the game of universal healthcare.
As a vaccinated French citizen, I'm ok with it. The pros beat the cons.
In the specific case of smokers, it doesn't actually increase health costs. Smokers die younger and often have a relatively short illness before they die. Compare this to someone who lives 95 and requires care in a care-home it's "cheap". You also save on things like pension costs because you don't pay them to dead folk, and income from taxes.
I'm not entirely sure about the numbers on things like obesity, drug use, etc. off-hand.
I agree with you as a matter of principle, so not that it really matters, but people sometimes say "smokers should pay the cost they inflict on society themselves!" and turns out they're not actually inflicting the huge costs people imagine they do.
Interesting point: how can you say "The pros beat the cons"? So far, and more important from the history (one scandal per WHO pandemic declaration, same plot before and ongoing) we have see only evidence of the very contrary: 2021 total mortality was far higher than 2020 one, 2020 with covid, without "vaccines", 2021 with "vaccines".
What evidence you know of the contrary? The À la une of some journal stating that or something more solid?
Long story short: try to compare USA health costs (the highest in the western world) with the lowest mean quality with classic EU PUBLIC and UNIVERSAL health systems the cheapest and the best in mean quality. Than try to draw where the costs came from and more important: from witch pocked money depart to end up in witch other pockets.
You have only shown arguments to revise implementations of universal healthcare - not any reasonable stance to regulate behaviour (which by the way, is not a novel topic - see seatbelts etc. - and not a trivial one with easy answers).
If you start putting more rule, you get healthcare, but not universal.
That's what the universal stands for.
It's for everybody, no matter the person.
If you are not ok with that, they you don't want universal healthcare, you want something else.
I personnally love universal healthcare, and I'm happy to pay for it. I don't want to have to play a game of chess to live my life in the most likely way to be reimbursed by the system.
- the coder is fluent in programming. Beginners will not know how to architecture things, and need to fiddle way more. It's impossible for them to create a doc that will make sense from the top of their head.
- The coder understands the problem well, and it has a known solution. Many problems are better understood when trying to solve them, by exploring its space while programming. It's impossible to start documenting something you don't know very well. It's espacially true if you have to come up with a novel solution.
- The problem is well defined. Unlikely. Clients don't define their problem well, and it's half our job to extract the information from their brain. However, while it is sometimes possible to get that on paper, and formalize it, most of the time, programming an incorrect PoC and iterating on it is a better interface to communicate with the client: they have a visual result to discuss. Writting a doc that you trash down every day would be a waste.
- The coder understands the field well. I'm currently working with a Bank, and I don't know the field. Many algo I must implement are in the head of my clients, and the quickest road to understanding them is to peer code them. They attempted to make a formal doc first of course. After 6 months, they still don't agree on how to do some things. One week of coding with me forced them to confront reality, and take concrete decisions.
- The coder has the big picture. Starting with a doc assumes you know what your API should look like. I would recommand that you do know, if you don't, you are probably in trouble. But it's a fact of life that sometimes you can't figure it out, and starting from something incomplete and coding it will make the big picture clearer.
That's a lot of pre-conditions.
My experience is that most teams starting with the doc (or tests) don't ship, or end up shipping only once they start fiddling. Those who do are excellent teams, the best ones, and I love working with them. But they are a rare bread. We are usually an average team, not ticking all pre-conditions, and not composed of only very skilled or experienced professionals. We fiddle a lot.
And unless you have a great team leader, taking such an ordinarity team and making it write the doc first will result in a terrible doc that doesn't match the solution to the problem, that you will rework again and again, while nothing is getting in the hand of the client for concrete feedback.
I favor a middle ground: start with paper, but don't pretend you are going to have a full spec.