1,924 karma · joined April 27, 2015
- moon-dev-tools https://antoinemopa.github.io/moon-dev-tools/
- claydash https://claydash.com/
Github: @antoineMoPa
My favorite output so far is that I asked it what life was and in a random stroke of genius, it answered plainly: "It is.".
It's able to answer simple questions where the answer is in the question with up to 75% accuracy. Example success: 'The car was red. Q: What was red? ' |> 'the car' - Example failure: 'The stars twinkled at night. Q: What twinkled at night? ' |> 'the night'.
So nothing crazy, but I'm learning and having fun. My current corpus is ~17mb of stories, generated encyclopedia content, json examples, etc. JSON content is new from this weekend and the model is pretty bad at it so far, but I'm curious to see if I can get it somewhere interesting in the next few weeks.
> Developers are not Idiots
I'm often distracted and AIs are idiots, so a stricter language can keep both me and AIs from doing extra dumb stuff.
I don't really care about the governance model as a user seeing this landing page for the first time, so I wonder why it's so prominent, vs telling me what the actual product is.
EDIT: yep - https://gsgen3d.github.io/
https://github.com/antoineMoPa/tfjs-text-experiment/blob/mai...
I feel like sync communication is necessary for groomings & design review.
> design was taken forward (approved by the team) just to be heavily criticised during implementation
Pretty strange that it was approved by the team and then criticized. Is this a recurring thing or just a one-off issue people did not spot early enough? If it's frequent, the team should either do a better job of discussing before implementation or understand that they have to unite behind the decision once a design is approved.
I would love to read more about that! Do you have a blog post or other insight?
On the other hand, that does not feel so nice as a contribution environment, it creates a software design bottleneck on one person, increasing shipping time and creating a dangerous bus factor. It's not a really scalable way do software design. Overall that attitude is pretty detrimental to community as he basically complains about all previous contributors.
Maybe I'd suggest him to:
- Work on his attitude, respect other contributors & stop calling them names.
- Spend less time developing and more time educating other people who work on the project.
- Come up with a set of design principles that the rest of the project can follow.
But yeah that's open source, he's free to fork a project. Probably his project will be successful anyway despite the negativity.
Do we have info about the implementation somewhere?