@BerserkAsIfUWereMad @ChesswurmOTB
Idea: Since, it seems that this team is about CSS, JS coding in lichess (and other languages), developer emphasis, I would like to start another sibling team (as in the Inbox virtual thread experiment: sibling team with different acting leader, and focus, but very closely related, logically so).
This one would be:
Learning CSS, JS coding in lichess (and other languages)
I would make a closed sticky one-post-thread linking to it, here. And reciprocal there, There I would use material from here, as basis of discussion.
This would allow all the topics that have been approached without conclusion or without a working code as product to be the object of discussion or threads there.
Among those: all the more thematic questions that can't be packaged yet as projects, but which are definitely building blocks or steps needed to identify what to learn in priority, for those of us who have time to get lost in open questions.
code as an object of science, would be my aesthetics, or bias, or angle of learning. (pulling on one thread to see the whole thing, if not then another thread, going back and forth maybe). Experimental. Hands-on for the old or lazy people.
I am asking you about your permission to use your creations or posts as material of discussion or dissection, if i think it appropriate for my topics. You would not have to be members but could be, you could use the stuff there, here as well, with links to thread or even posts, finding ways not to double the work, though.
Any objection? or preference. Do you think it would be good. can i use this team names and proposed mechanics? Amendment suggestions welcome.
I would clean up open ended stuff that i have backed up from here, and what is left here in the intro and general thread. Might even put the thread about notes on team management over there (any preference for that particular idea)?
Idea: Since, it seems that this team is about CSS, JS coding in lichess (and other languages), developer emphasis, I would like to start another sibling team (as in the Inbox virtual thread experiment: sibling team with different acting leader, and focus, but very closely related, logically so).
This one would be:
Learning CSS, JS coding in lichess (and other languages)
I would make a closed sticky one-post-thread linking to it, here. And reciprocal there, There I would use material from here, as basis of discussion.
This would allow all the topics that have been approached without conclusion or without a working code as product to be the object of discussion or threads there.
Among those: all the more thematic questions that can't be packaged yet as projects, but which are definitely building blocks or steps needed to identify what to learn in priority, for those of us who have time to get lost in open questions.
code as an object of science, would be my aesthetics, or bias, or angle of learning. (pulling on one thread to see the whole thing, if not then another thread, going back and forth maybe). Experimental. Hands-on for the old or lazy people.
I am asking you about your permission to use your creations or posts as material of discussion or dissection, if i think it appropriate for my topics. You would not have to be members but could be, you could use the stuff there, here as well, with links to thread or even posts, finding ways not to double the work, though.
Any objection? or preference. Do you think it would be good. can i use this team names and proposed mechanics? Amendment suggestions welcome.
I would clean up open ended stuff that i have backed up from here, and what is left here in the intro and general thread. Might even put the thread about notes on team management over there (any preference for that particular idea)?
