May 03, 2023
On Wednesday, 3 May 2023 at 23:17:28 UTC, MissPiggy wrote:
> On Wednesday, 3 May 2023 at 11:13:34 UTC, Mike Parker wrote:
>>
>> Our enthusiasm is high, and we're ready to get going. I think you'll like where we're headed.
>
> IVY may increase the probability of a particular outcome, but it cannot predict a particular outcome.
>
OK?
> You simply cannot ever know the position and velocity of every atom in the universe.

Luckily some very clever physicists have worked out that this task is a fools errand and instead one *can* model the interesting large scale dynamics of the system extremely well (until you can't, but still).

>> You're going to hear more about IVY as time goes by, and eventually,
>> we're going to start employing it more broadly in the community.
>
> Whether you can in fact 'deploy' IVY into the 'broader community'... well..that remains to be seen.
>
> It's more likely, I think, that D's 'future' will be increasingly determined by the priorities of a select group of corporations, rather than any psychological/behavioural science.

Ignoring that this statement doesn't make any sense (IVY is but a tool):

Let's not bother then eh — I'm sure Mike, who is the main liaison between these groups, hasn't put any thought into this.
May 04, 2023
On Wednesday, 3 May 2023 at 23:42:37 UTC, max haughton wrote:
> On Wednesday, 3 May 2023 at 23:17:28 UTC, MissPiggy wrote:
>> On Wednesday, 3 May 2023 at 11:13:34 UTC, Mike Parker wrote:
>>>
>>> Our enthusiasm is high, and we're ready to get going. I think you'll like where we're headed.
>>
>> IVY may increase the probability of a particular outcome, but it cannot predict a particular outcome.
>>
> OK?
>> You simply cannot ever know the position and velocity of every atom in the universe.
>
> Luckily some very clever physicists have worked out that this task is a fools errand and instead one *can* model the interesting large scale dynamics of the system extremely well (until you can't, but still).
>
>>> You're going to hear more about IVY as time goes by, and eventually,
>>> we're going to start employing it more broadly in the community.
>>
>> Whether you can in fact 'deploy' IVY into the 'broader community'... well..that remains to be seen.
>>
>> It's more likely, I think, that D's 'future' will be increasingly determined by the priorities of a select group of corporations, rather than any psychological/behavioural science.
>
> Ignoring that this statement doesn't make any sense (IVY is but a tool):
>
> Let's not bother then eh — I'm sure Mike, who is the main liaison between these groups, hasn't put any thought into this.

I don't believe my post required this kind of response. Check your motivations please.

First, I was simply stating the obvious.. that there are always things that are not under your control. You can predict possibilities of an outcome only (where such variables are in play). This is not the same as saying you shouldn't try, which was your criticism against something I never said.

Second, I was simply stating the obvious (e.g who attends these regular meetings? Increasingly, its business oriented, isn't it? That is not a criticism. Other languages have also been driven by business priorities, and have succeeded very well. Whether this is true for D, remains to be seen.

When I go on a road trip, even when I know where I want to get to, doesn't mean I'm going to get there. It also doesn't mean I'm not going to go on a road trip.

May 04, 2023
On Wednesday, 3 May 2023 at 23:24:53 UTC, Walter Bright wrote:
> This initiative has my full support.

While I have ceased using D because of my concerns about the project's future (I discussed my reasons in a previous message that don't need to be repeated), I have continued to check this forum occasionally, hoping to see the slope turn positive. Mike's message and your response are both the kind of thing I was hoping for.

While there is no guarantee that the effort Mike describes will have the desired outcome, the mere fact that the effort has been made and endorsed by you is a significant positive step.

I'm sure I needn't tell you that technical work and project management require related but different talents. I did both professionally for a very long time and I certainly was not equally good at both. You can probably guess which one was the laggard. But I have seen it done well, having worked for some really great managers.

One who deserves mention is the late Frank Heart. The ARPANet (and thus the Internet) would not have existed without Frank's unique ability to herd the brilliant cats at BBN 50+ years ago. He's in the Internet Hall of Fame, deservedly. See https://en.wikipedia.org/wiki/Frank_Heart. Some of the great people in the history of computer science are in the picture on that page, including Bob Kahn, who, with Vint Cerf, won the Turing Award. Both played absolutely key roles in the development of the Internet.

I really hope that this is the start of something good for this project. A lot of value has been built here, but the project has obviously foundered in an organizational way. Project management is difficult, so the trouble is not surprising or unique. The key is recognizing that the problems are happening and taking steps that have a reasonable probability of improving the situation.

I will watch how this unfolds with great interest.

/Don Allen
May 04, 2023

On Wednesday, 3 May 2023 at 11:13:34 UTC, Mike Parker wrote:

>

...
Our enthusiasm is high, and we're ready to get going. I think you'll like where we're headed.

Interesting.
Good luck with the endeavor!

Ivan Kazmenko.

May 05, 2023

On Wednesday, 3 May 2023 at 11:13:34 UTC, Mike Parker wrote:

>

That’s a lot of words but little actual sense. What makes you think that this IVY™ program is the silver bullet that D desperately needs? And not just yet another load of crap invented by some “consulting” firm as a relatively honest way of taking money from businesses? Because it’s sounds like one.

May 05, 2023

On Friday, 5 May 2023 at 11:26:26 UTC, Ogi wrote:

>

On Wednesday, 3 May 2023 at 11:13:34 UTC, Mike Parker wrote:

>

That’s a lot of words but little actual sense. What makes you think that this IVY™ program is the silver bullet that D desperately needs? And not just yet another load of crap invented by some “consulting” firm as a relatively honest way of taking money from businesses? Because it’s sounds like one.

Because we went through the program and can see how it's going to benefit us. It's not automatically going to make things better. We have to do the work. But the point is, now we know how to do the work, whereas before we were just throwing things at the wall to see what stuck.

People around here frequently complain about bad management. Through the IVY program we, all of us non-managers, learned an approach to management that makes sense to us. It's going to change the way we do things, and we're all confident the change will be for the better.

Ucora's workflow is built around IVY as well. Saeed shared with us some of the ways they use it so that we could better see how we can employ it. He's also made himself available to help us as we go along. They're serious about it, and so are we.

You'll hear more about it before and during DConf. After, I expect it will become part of the common lexicon in the D community.

May 05, 2023

On Wednesday, 3 May 2023 at 11:13:34 UTC, Mike Parker wrote:

>

I'm not exaggerating when I say that this is going to be the most significant change in the D community in the 20 years I've been a part of it. I expect we're going to encounter bumps along the way, but that's okay. We now have a clear vision and purpose, and that makes all the difference.

This sounds very exciting -- more than any details (which I'm sure we'll learn over time), I'm struck by the enthusiasm and confidence for the future of how D will be supported.

I really look forward to learning more as things progress. Many thanks to Ucora for their investment of time, insight, and resources.

May 06, 2023

On Wednesday, 3 May 2023 at 11:13:34 UTC, Mike Parker wrote:

>

Ucora’s long-term vision is to change the way the world works. As part of their mission, they provide organizations with the tools they need to transform the way they work. IVY, their organizational development program, is a simple but innovative approach to workflow. Ucora has been using D for several years. They're invested in D's success, and so they want the DLF to be successful. Paul offered to put the DLF team through the IVY program at no charge. We accepted, and every Friday for the past 14 weeks we've been having sessions with Saeed Sabeti, Ucora's Director of Organizational Development. May 5th will be our 15th and final session.

Hi Mike,

Thanks for the update. This is very interesting!

-ikel

May 07, 2023

On Wednesday, 3 May 2023 at 11:13:34 UTC, Mike Parker wrote:

>

IVY, their organizational development program

Your solution to hearing luas dev saying "I dont manage anything" and whatever feedback from your survey, is you got corporate training and now you gun-ho about management?

Was I in an extreme minority here?

https://monkyyyscience.substack.com/i/93037044/stop-pretending-d-is-a-corporate-language

> >

Stop pretending D is a corporate language

> >

You have a community of meta-programming-crazed iconoclasts

> >

Either you believe this small community has great 1000x programmers or you don't and we are doomed anyway

> >

If Adr says "I want to make a color lib", don't stand in his way give him the namespace std.community.color that can be written to his style guide, to his standards, on his github, and when a new version of the compiler ships a script will grab a snapshot

Please redesign and relaunch std.experimental to have a completely hands-off, anarchic structure. I'm confused how you came to the conclusion that complaints about management mean there should be more management instead of a fundamentally different approach.

> >

Don't herd cats, just clean out the litter boxes.

May 09, 2023

On Sunday, 7 May 2023 at 02:15:02 UTC, monkyyy wrote:

>

On Wednesday, 3 May 2023 at 11:13:34 UTC, Mike Parker wrote:

>

IVY, their organizational development program

Your solution to hearing luas dev saying "I dont manage anything" and whatever feedback from your survey, is you got corporate training and now you gun-ho about management?

Was I in an extreme minority here?

https://monkyyyscience.substack.com/i/93037044/stop-pretending-d-is-a-corporate-language

> >

Stop pretending D is a corporate language

> >

You have a community of meta-programming-crazed iconoclasts

> >

Either you believe this small community has great 1000x programmers or you don't and we are doomed anyway

> >

If Adr says "I want to make a color lib", don't stand in his way give him the namespace std.community.color that can be written to his style guide, to his standards, on his github, and when a new version of the compiler ships a script will grab a snapshot

Please redesign and relaunch std.experimental to have a completely hands-off, anarchic structure. I'm confused how you came to the conclusion that complaints about management mean there should be more management instead of a fundamentally different approach.

> >

Don't herd cats, just clean out the litter boxes.

To be honest, this has always been my take as well.

I don't want to be critical here, because I have no idea what IVY is and what is supposed to come of this, but I have seen people for years saying that D has a management problem, and this has always seemed wrong to me. D has an effort and agreement problem, but that's not something you can manage in a community of volunteers. Management implies an ability to focus effort. Broadly, D doesn't have users who want to improve D, D has users who want to improve doing X with D.

Now D management can say "we want to reach style X" or "we are working on improvement Y"; they can do this by setting review standards and only merging PRs that go in the direction they want the project to do. But they cannot decide what work gets done - only accept or reject.

Isn't the point of the DIP process primarily to be able to forecast whether a feature will be accepted or rejected? So managing the work requires an inherently reactive approach.

This is why I never understood why people were saying D "needed better management". What work got done has always been, in this language, a matter of some person saying "I could do this cool thing" and going and doing it. This can be mismanaged, sure, and there's room for improvement, granted, but better management can still not make improvements appear where currently there are none.

(Honestly, maybe 80% of the time when I've seen "D needs better management", it has been code for "D management didn't like my proposal.")