> “The main downside is competing visions”

If this is the main downside to your “best of all” AND it’s the biggest challenge (for productivity) in a decentralized dev environment (#amiright ?) then we have solved nothing at all. 

How to push dev alignment WITHOUT compromising independence? 

 Well, you can't, by definition. If you want to work with someone you have to compromise. 

 No. Not “push devs into alignment” but “push efforts for dev alignment”. 

Alignment initiatives CAN have dedicated resources. Maybe they SHOULD? 

 That's what analysts are for.

Having a bunch of devs debate which of their preferred solutions is the one the others should use...  

 yeah, that's the neverending story

like my war with the rusticles and oop enjoyoors

analysts are good for blurring out these details and focusing on the ins and outs 

 And crafting a vision.
You need emotional distance from solutions to identify problems.

What is the problem you want to solve?
Now, forget that idea and go back another step.
What is the problem you want to solve?
No, it isn't.
Go back another step.
Go back ten more steps.
You're now at the top of a hill.
Turn around.
What do you see?

THAT is the problem you are trying to solve.
Now, solve THAT problem. 

 Nostrability has been a collaborative experience. There is good chance of alignment when the user experience is broken. 

Conversely, if things are not broken, then the task is much more akin to herding cats.

Perhaps there can be “best practices” from the perspective of one or a few devs/contributors to go along with the terse NIPS. These can add context, and more of a user focus, which could increase the chance of “dev alignment”. 

The conversation shifts to user experience from technical solution A vs B.

cc @jb55 

 So yea. Back to “initiatives” for dev alignment. 

- best practices dev wiki
- regular dev standup calls
- open channels for dev chat
- constant contact and outreach into the growing dev community

So who steps up to do or to fund these efforts? I’m down for the doing part…  

 I'm planning to keep up those dev standups 

 Let me know how I can help…. On any of the above.  

 Heard you making noise about this weeks ago, but never got wind of … did this just happen? 

 I did one last week, it was pretty last-minute. I'll do another one 3 weeks from now 

 How do you “advertise”? 

 I just post a note with a link. Some people reposted. I'll try to do it more in advance next time. 

 If you don’t have a hashtag … now you do. It matches your domain also. So … one reinforces the other. Let’s get devs aligned on both. 
#nostrtalk
nostrtalk.org 

 Three weeks from now we will BOTH be in Nashville? 🤔 

 That would be four weeks from now I believe 

 > “because it avoids creating yet another isolated patch of weeds”

Pitching in to existing projects actually brings MORE people into MORE and different and DEEPER weed patches BECAUSE each project has their “own way” to see the “problem” and to implement a “solution”. 

Code repos are ALL about implementation. There is ZERO room in a repo to back out and discuss the bigger problem BECAUSE it only ends up in YA issue, pr delegation, forked project, or abandoned #wontfix thread. 

ALSO, because these siloed “repo discussions” are all happening on GitHub, then there’s even less opportunity for the rest of Nostr to contribute to maybe keeping them alive and connecting dots for us developers who ARE “in the weeds”. 

@Laeserin may be onto something when she pitches bringing these repo convos into Nostr. This may help, but still … we need time and space for dev realignment. Nostr doesn’t have this. 
nostr:note1affw8xlq26aulc5u93293vhempxzgj3w44x7gxz2xl89ftsd7m6qyfx4hf