> Instead looking at the problem and find the easiest solution to it offers great time to marked.
The easiest solution you can imagine. These are 90% of the time cute tricks that narrow down the scope of the solution so far it makes the surrounding code unmaintainable after a year.
I learned to call those people "Ricks" they are best used in walled of projects that are not expected to change. Not useable in cooperation.
> Which is not so difficult, because that busy person is in the same organisation as you
Hopefully. But not necessarily. This argument is spinning in circles.
In house projects can be abandoned just as oppen-source ones can.
For me that was Powermock for example.
Then your architect needs a fresh course in how to decide what open source project to use.
When its a critical spot you first check how it is maintained. Its that easy.
Have you seen the "Line goes up" summary by Dan Olson?
It puts the crypto sphere into context. From that many descisions and marketing practices start to make sense.
I wouldnt worry, the whole system up to this point has used "technobabble" as a means to confuse and impress outsiders. When reading up on it, there is no meaning to find besides "yep, its a linked list allright".
There is no baby. The technology does not solve technical problems that havent been solved better. The only thing bchains does is give ppl with a lot of money to become stakeholders, the possibility to comodify even more parts of the internet.
Thats the only upside of the technology, scam ppl for their money.
I feel the same, the dayli meetings are super important for fast iteration. Sayinf you dont need those is implying there is no outside input that yould improve your work. Wich is only true when your task is so sepperated from everyone that you could effectively get your own one man team.
The easiest solution you can imagine. These are 90% of the time cute tricks that narrow down the scope of the solution so far it makes the surrounding code unmaintainable after a year.
I learned to call those people "Ricks" they are best used in walled of projects that are not expected to change. Not useable in cooperation.