| Brighter & Darker | https://github.com/BrighterCommand |
| GitHub | https://github.com/iancooper |
| Brighter & Darker | https://github.com/BrighterCommand |
| GitHub | https://github.com/iancooper |
I've written up my own experience of the conference which everyone is talking about https://dev.to/thisisjofrank/my-experience-of-modern-frontends-conference-1cgg
๐ฆ๐: https://twitter.com/ThisIsJoFrank/status/1593605525446565892
If you're looking for blogging opportunities in the #fsharp / #dotnet area, there are still around 20 open spots for this year's #FsAdvent Calendar, let Sergey know in the comments inside the website:
https://sergeytihon.com/2022/10/28/f-advent-calendar-in-english-2022/
Was anyone realistically thinking about creating a #dotnet implementation of #mastadon ?
I sorta started on it, but wasn't going to continue if there's a #Microsoft led effort.
If there's no existing project, I'll try to gather some collaborators and continue.
Who's interested in trying to get a #dotnet7 version going?
Please boost to help me find people or a project! Thanks! 
Seen some posts talk about #moderation worries on the two large #Mastodon instances, .social and .online - scale seems to have outstripped moderation capability; other notable instances (such as .art) have now #silenced them to mitigate harmful content.
If you're on one of the two larger instances, you may want to think about moving/#migration to a smaller one. Doing so has benefits - it better distributes the network and eases the load on big servers.
Boosts for higher reach welcome!
4. The modeling, organisational and cultural parts are the hardest ones to tackle. None of these are simple and none of these can be done quickly by bringing in some high profile experts: YOU need to do the work and have the patience.
5. With (domain) modeling we need to find boundaries within which teams can make a high percentage of decisions without having to coordinate with others. Cross-team coordination will always slow you down, no matter what fancy tech you will use later on.