erur

Public teachers and other bureaucrats are probably some of the last roles to be replaced. If any objective competence or system efficiency in general was the goal, the system would look vastly different.

Efficiency seeking players will adopt this quickly but self-sustaining bureaucracy has avoided most modernization successfully over the past 30 years - so why not also AI.

You can go incredibly far with the type system.

If you wanna go down that rabbit hole, I'd suggest Typescript type challenges. Completely blew my mind when I came across it the first time.

When you start out with typescript you might think Omit<> and Partial<> are cool but holy hell, you can do so much more.

The flexibility=complexity aspect is such a big one.

Getting stuck with a limiting abstraction is something that's super easy to grasp as a developer. Devs constantly gotta tear down the walls of stuff they've built to fit in new things.

For less technical people however, the focus often shifts to the complexity only. It can be hard to relate to the worship of flexibility, if you haven't felt the pain of building tedious workarounds, squeezing logic into boxes that weren't made for it.

For what I'd call "stupid" compliance (GDPR,...), allowing for regional storage of data at rest is definitely important.

For any internal data where protecting it is a core interest of the company you'll also either need to prove your whole handling is trustworthy or you'll need to design a process that can do all the steps (preprocessing/vectorization/...) on customer controlled hardware.

If your solution can run in a customer owned environment without any external dependencies, that could save you a lot of auditing/certification.

Felt like that for some time but sorta started liking him. He got a pretty solid track record and besides the usual ups and downs there was no major scandal, no big oopsies, nothing truly awful in the last 20+ years.

Also besides loud marketing Salesforce has been honest with their CSR goals. With excessive bluewashing being the norm out there, that's gotta be worth something.

All the corporate BS aside I'm feeling like he kinda has an above-average talking-to-delivering ratio compared to the rest of the industry.

Could be a myriad of things, unfortunately. Have had my battery saver settings kill some background activity for example and adding Slack to the exception list fixed a lot of issues for me.

Maybe contacting the customer experience team could help. You can just use /feedback to open a ticket and they're pretty quick to respond.

First of all: This seems solely political and thus misplaced.

Secondly: Not arguing this isn't used for political gain by other authoritarians, but looking at the USSR, China, Cambodia... this feels like a healthy response to any notion of leftist ideology getting traction.

For Joe average, the expected value of working at a random startup is positive - compared to not working. It's just the employee's gamble to figure out whether the expected value is high enough and the risk ratio is aligned with their preference.

The expected return for an average MLM joiner is deep in the reds.

From an individual perspective that's a huge difference.

First of all - this sounds like a super high potential concept. The big hurdle I'd see that would keep companies from tampering around with the current version is that there's no info on data protection & security.

You won't get companies to share any internal info with a tool like that until that's out of the way - and even then it might require a lot of trust-building. Getting the certifications will be quite a chore though.

This isn't totally unique to software engineering (and broadly speaking knowledge, science and maybe even content in general) but I feel it's better placed here than anywhere else.

We're in a near global, near zero-marginal-cost environment.

If you build a broom that's mediocre, someone can still sweep with it and it's worth something. In this realm though, if you build a mediocre version of something that already exists in a better form, it's likely worth nothing.

That shouldn't keep anyone from enjoying building mediocre things - which might be the only path to get into a position to build great things. But it does make sense if your goal is to have an impact with the specific thing you're working on.

Kinda stating the obvious here but most of the mental overhead you feel with Slack Apps comes from a long list of Enterprise concerns that needed to be addressed.

If you just want to build a poc Slack won't keep you from creating an app manifest with all the permissions and be done with worrying about them. Also all those public APIs are designed to be fairly permanent. Can't compare it to IRC obviously but I wouldn't worry too much about stuff being deprecated all too quickly.

I work at Slack and frequently build automations for our customers so I'd love to hear about particular annoyances from the perspective of an old school IRC user.