I don’t know what exactly you mean by “general attitude”, but you are certainly being lazy to a fault here because I have been very open with everything I do for years contributing to Grin. To answer your question, I’ve merely posted links to my work that you could have found yourself, but you haven’t even invested your time in doing so and want others to do it for you. I am more than happy to offer my apologies if I am misconstruing laziness with you having some attitude against me or my work. Maybe you’re just too busy and that’s fair, but if so, I invite you to try to be more honest by saying something like “I haven’t followed much of what you do.”.
OK @ardocrat you finally brought points that can be addresses, thank you. I am happy you did. Let’s begin.
And I’m not saying otherwise, but I’ve always had the same approach, and as I explained above, it has always worked so far. One could probably argue that this Q wasn’t my best.
I will tell you this: my “mistake” was to estimate on the unknown without taking into account that I was doing something totally new to me.
I started experimenting with Nostr with skepticism after integrating Tor Bridges into Grin++ only to realize that Nostr could actually be a solution for Tor. Using Bridges helps but doesn’t solve the problem completely, Nostr could do it. For a PoC I needed to change some responses, and adapt the code. That aside the instability of using overloaded relays that stops working, I had to deploy my own relay in order to use it with the release, the lack of portability of Nostr’s Python libraries, and the differences between relays implementations, not all of them responds the same way. Take into consideration that I am working with two separate repositories here. That’s pretty much the non-technical summary of my last Q.
Now, my take based on my experience writing software is this: There is no need for the commits tree to reflect all of that. Commits should, for the most part, reflect value; me, as a developer, I should be able to move to any commit and get something that works. I should be able to roll back to any commit and deploy it just like I could deploy the master branch.
I have seen many times developers make any small change in the source code just to say “look, I’m doing something!”, especially under pressure from project managers. But others may have their own reasons which I do not want to refute. I won’t tell anyone how to do their work.
I know there are people who see commits as you are more or less putting it here. It’s nothing new to me, but I disagree.
So now you might ask yourself the valid question: how do you show progress? Well, as I have been doing all this time. I publish how it’s going, ask for feedback, and generally give me time to do an alpha release. I then gather more information, correct the problems found, refactor the code I consider faulty, commit it and publish it. Only this time it has not been possible so far for the reasons I have already explained several times.
I’ve linked the releases of all the progress in Grin++ and its current status that you can go click and use it right now, and your answer is: “the world deserves to see real work at Grin” and shows a list of the commits! Madre mia! The irony here! Amazing!
Yes, but I won’t. Repeat with me: committing for the sake of committing is useless. Don’t tell me how to do my work, don’t waste your time.
With all due respect, and I mean it… with all due respect I strongly disagree with that approach. I have talked about it quite a bit in the past and how this is/was affecting Grin.
Look, building a good product is not like going from A to B in a straight line. It never is. The path to a good product is more like a spiral, you code, you release, you test, you fix, you release and repeat:
You shouldn’t go into the dark to write code and think you’re building the perfect product without getting feedback from your users somehow. Technology is advancing so fast that if you do, you will end up launching a product that most likely won’t even hold your initial assumptions and will be old by the time it hits the market. There is plenty of documentation on the subject, enough to change anyone’s mind.
That said, I have no right to go into Keybase to build conflicts just because I don’t agree with the approach taken by the people working on the Rust implementation. That would be disrespectful and immature of me. All I have to do is to be ready to help in any way I am needed, as I have done so far.
For years I have been presenting my work publicly asking for opinions/feedback/comments here, always. I have taken the ones I consider valid, and discarded the others. The most recent example is from my last post, I can honestly say that most of my assumptions were wrong. I am not afraid to say it. I have been changing much of the code because I accepted the observations as good and valid.
I embrace criticism, criticism of my coding style, for example, has helped me a lot of times.
I have been able to interact here with people with whom I disagree most of the time but many other times I have found valid points that I have taken without problem.
Asking about the status of Grin++ while openly accepting not being qualified to review it? Now there are people who can’t even write code telling me how to do my job? Questioning me without even reading my posts and/or reading my updates during past meetings? People admitting they can’t review my code but wanting to judge my effort and time? At this point I don’t think it’s “just criticism”. It’s more like a witch hunt.
I care so much about Grin users that I my entire approach is focus on them since day one. Now I want to release something that will allow us to gather enough feedback to initially evaluate how Nostr + Grin could work successfully. I have repeatedly expressed that after this next release my focus will be on things that are not exactly visually perceptible to regular users, and will be for a long time to come. The more value I can deliver to users in this next release, the better.
Do your thing, I don’t care. I do mine.
You can also have stats from https://grinnode.live/stats if you like too:
Some people here can say what they want about my “attitude”. They can criticise my approach, but it would be crazy to say that I don’t care about Grin users.