[thelittleone]

I’m always a little wary about these claims. For example I worked at a Fortune 500 before and I created a setup on an app like Slack using my corporate email account.

There is a big difference between “used by company Y” and “used by tiny team X inside company Y” (probably without IT approval).

[flukus]

Agreed, just saying x is used at y is meaningless, especially when that company is a multi headed hydra like google or MS. I see it so often with languages these days but I'm pretty sure you could find a team in a huge company like MS programming in TCL all day.

You can prove anything with case studies.

[sebazzz]

True, my team happens to be slack but the company actually employs Teams as a chat solution.

[client4]

I'm sorry for your loss. Teams is truly a horrible experience. "It's like SharePoint for chat" said no happy person ever.

[tapland]

We're getting teams which I'm a bit excited for since it is going to be a company wide replacement for Lync/Skype for business and no developer here has ever used Slack, IRC or anything like this.

[OJFord]

Sorry to end your excitement, but it's basically identical to Skype for Business.

As I understand it MS has been covering the two (in both features and design) so that at some point one or other will be deprecated, but that in practice all that means is a name change for those users.

[tapland]

Not really.

Group chats in Skype don't happen, messages are stowed away in outlook under past conversation history and everything you send on Skype for business is a new conversation @tagging the recipient (singular in almost all cases). And everything to be brought up with multiple people thus ends up being an email chain after the Skype convo.

[black_puppydog]

gosh I hope they pay you well...

[tapland]

It's COBOL, but my first software development job. It's a good pay for a novice-dev in Sweden ($44k/yr and our currency has dropped by 1/3 compared to the USD).

I like the language and environments, and it's fine that almost all developers are close to retirement, they are great libraries of knowledge after having worked in the system for 20+ years.

It's mostly the legacy ways of working around here that are an annoyance, communication by email and having to wait for order- and project numbers before starting any development, instead of being allowed to develop improvements that can just be implemented when/if they get the ok.

The wait time does allow me to create some automated tests of which we had absolutely none, that other young developers here also benefit from.

I'm gaining knowledge and the system seems to be getting replaced in not that long, at which point my fiancée wants to move back home to the states, but health insurance woes has kept me from looking into that.

[namdnay]

Hahaha we migrated from Sametime, so it's honestly not too bad