Silberengel on Nostr: There are three main solutions to this efficiency problem: 1) form intra-project ...
There are three main solutions to this efficiency problem:
1) form intra-project teams (group of people working in a tightly coordinated fashion on one system)
2) form inter-project teams (group of people working in a loosely-coordinated fashion on multiple systems)
3) some combination of both 1 and 2
The key here is COORDINATION. Identify the stakeholders, discuss and plan with them, straighten out the specs and the interop, promote and test each other's implementations, make joint announcements, discuss problems, etc.
That's the sort of work @elsat has been doing and I'm trying to do, and I think there needs to be more focus on this. The NIPs repo is now too large in size and scope, to have everyone just hanging out in every discussion. We have to actually put effort in, to selecting where to hang out, now.
All the people working on relays: form a team
All the people working on books: form a team
All the people working on teleconferencing: form a team.
All the people working on AI: form a team.
All the people working on blogging: form a team.
And so on.
Nostr has almost enough #devs and enough beta-testers, but way too few project managers and alpha testers.
The left side of the development cycle is just "dude sitting alone, hacking wildly on his keyboard, with no plan". Which brings results barely better than cheap AI.
Published at
2025-02-05 11:30:56Event JSON
{
"id": "3cda35f4954e81d2e19597ae7f574f6dfd14548c0f88b218eeb895981288e00c",
"pubkey": "fd208ee8c8f283780a9552896e4823cc9dc6bfd442063889577106940fd927c1",
"created_at": 1738755056,
"kind": 1,
"tags": [
[
"e",
"0cc88d906f7f3543a4113b9f157c16a98bc7db1115035ff35a85557fe470d2b5",
"",
"mention"
],
[
"p",
"fd208ee8c8f283780a9552896e4823cc9dc6bfd442063889577106940fd927c1",
"",
"mention"
],
[
"q",
"0cc88d906f7f3543a4113b9f157c16a98bc7db1115035ff35a85557fe470d2b5"
]
],
"content": "There are three main solutions to this efficiency problem:\n\n1) form intra-project teams (group of people working in a tightly coordinated fashion on one system)\n2) form inter-project teams (group of people working in a loosely-coordinated fashion on multiple systems)\n3) some combination of both 1 and 2\n\nThe key here is COORDINATION. Identify the stakeholders, discuss and plan with them, straighten out the specs and the interop, promote and test each other's implementations, make joint announcements, discuss problems, etc.\n\nThat's the sort of work @elsat has been doing and I'm trying to do, and I think there needs to be more focus on this. The NIPs repo is now too large in size and scope, to have everyone just hanging out in every discussion. We have to actually put effort in, to selecting where to hang out, now. \n\nAll the people working on relays: form a team\nAll the people working on books: form a team\nAll the people working on teleconferencing: form a team.\nAll the people working on AI: form a team.\nAll the people working on blogging: form a team.\n\nAnd so on.\n\nnostr:nevent1qqsqejydjphh7d2r5sgnh8c40st2nz78mvg32q6l7ddg24tlu3cd9dgpz3mhxw309akx7cmpd35x7um58g6rsd3e9upzplfq3m5v3u5r0q9f255fdeyz8nyac6lagssx8zy4wugxjs8ajf7pqvzqqqqqqyw9j36q",
"sig": "89b2622077600d82d06a02a23f84329b45aabea9dd7332dd414f8a8feefd6834a216287f2decd4f449529cbaa242c61d289ac47262364228ec5e5513527ceb83"
}
