This team has 89 public channels in total.
Topic: Signup Link: <[URL]>
Code of conduct: <[URL]>
Purpose: This channel is for team-wide communication and announcements. All team members are in this channel.
Topic: Non-work banter, water cooler conversation and developer group therapy. Friends of <@U0HCLMWGP> get in free.
Messages are lost to us. But Slack has them
Purpose: A place for non-work-related flimflam, faffing, hodge-podge or jibber-jabber you'd prefer to keep out of more focused work-related channels.
Topic: On-topic discussions & rubber-ducking on DDD-CQRS-ES. To join: <[URL]>
Purpose: General banter and generally on topic. Be nice :slightly_smiling_face:
Basic Concepts Found here: <[URL]>
Topic: I should know better than to try
*using hypotheticals by now.
*build my own store for prod
*making a good channel topic
*Name Your Event as The FQDN of the Class to ease serialization
* Share Your streams with strangers.
* use Kafka as store
Topic: <[URL]> is not for big-picture -event-storming, it used to be called RealTimeBoard BTW
Purpose: what it says
Topic: <[URL]> This isn't an official support channel, more of a user group / fans-of.
Purpose: For discussions related to [URL]
Topic: All IoC jokes must be abstract.Cynics welcome.Tuesday is `Microsoft.Extensions.DependencyInjection` day.
A) you need the return value right now
B) it's inside a try-catch
C) In a using block
D) At the top of the call stack
Thursday is F# day
Purpose: .NET related topics. Should be try to be on topic with this Slack team.
Topic: Topics regarding job and work opportunities only. Use threads to discuss specific job items. Discussions should be held in appropriate channel.
Purpose: We're hiring
Topic: Amsterdam, Feb 2020
Purpose: Domain Driven Design Europe <[URL]>
Topic: Background info: <[URL]>
Purpose: Subjects around "single-flow event storming" that Adam Dymitruk practices