use Slack for issues to be checked during the next 24h

Remember the receivers of the Slack channel BY DEFINITION are not required to respond to.

You MUST organise your topics into discussion Threads as much as possible – should you feel that you jump to another topic / theme use another thread and link to the previous thread.

Slack is extremely powerful tool for search old code snippets and could save US ALL a lot of time !!!

Use ONLY English as the communication language in the common channels – msgs in other languages in the common channels SHOULD and WILL BE deleted !!!

Agree on secrets encryption convention – do NOT copy paste passwords from the snippets in the Slack – moreover this is a violation of Customer agreements if done so …

If an issue & task takes longer than 15 min to do it – you MUST register a Trello task and accordingly later on report on the time spent in the hours xls.

Slack has pretty good clients for IPhone, Android, mac, Linux & Windows – your should be able to access it via browser ( use your google csitea profile !!! ) from the following url: https://app.slack.com/

When writing code use type ``` and space to use the code formatting – because this is the only way to ensure that the special characters you type will not be changed during the copy paste or the sending of the message.
Use the code formatting ( triple ``` starts a code block ) and a single ` closed by another way an inline code block) to share quickly code snippets

Huge Gotcha – for languages / configuration for which white space IS MEANINGFUL ( for example Python … ): Slack DOES TRIM whitespace … aka the stuff you do copy paste is not 100% the same , also pretty rarely it DOES change some non-white space characters too …

Here some additional CSITEA Slack specific best practices:

• if the reply is obvious , don’t reply …
• if you need to indicated that you got it and you are “on it” reply by thumb up , when having been passed the ball
• if you want somebody to do something on the Slack use the @his-slack-name/handle to ensure that the msg will pop up …
• if you want him/her to do something fast use WhatsApp, phone ( check above !!! )
• if some activities are repeating – and they have their own track in Trello / confluence .. don’t use the Slack to track the status … aka if the status is tracked explicitly in confluence – use confluence …
• if you are working on a project – use the project’s pro-<<proj-code>> channel
• fi channels are the only one in which the Finnish language is allowed …
• should you want any <<lang>> channel request this from the Slack Admin
• avoid uploading pictures … we are still not 100% sure that data load is 100% percent usage free …
• use code formatting whenever possible …
• use Slack for “code history” , but confluence / Obsidian for proper documentation … aka Slack is NOT the final documentation tool … but the quick search for the something probably worked tool …

Almost all of out channels are “technical” by default, which means that IF your role is constrained within Project Manager’s tasks & activities ONLY it would not benefit you much to read over 95% of all of the discussions in the channels. Thus you should read only posts in the common non-biz only channels , in which you are explicitly tagged by name.

So IF your tasks in the project also contain technical tasks and activities ( aka some kind of coding etc. ) you should tag explicitly by name those persons which do have t he PM role only.