gv83

AI good or US health system trash?

given the "rebuild twitter" abundance of questions during the dreaded system design interview, it should have taken 2 weeks!

I’ve never seen a server with a rolling distro tbh

hey, maybe you have one of the use cases erl/el excels at; I'm not going to go against that - I also like the language and the runtime and everything.

my point is just that at some point and at a certain org size, the technical prowess of the platform is not the dominant term in the equation; social merits of your platform become it.

organizations also don't see the value of retraining everyone, risking bugs, customer and dev dissatisfactions, and a myriad other correlated problems; and as elixir orgs are not running laps around non elixir orgs (you know, executives do talk with other executives in other companies - and whatsapp is an once in a decade) and given that most of us build web cruds, internal LoB apps, other small automations, they can tolerate the eventual delays of having worser tools.

closing our eyes and thinking these things do not exist is ingenuous imho; I wish I was writing rust or el, I'm stuck in python trying to convince people using immutable dataclasses.

I still feel langs like el/erl and in general pleasant, powerful but niche things like clojure, are better placed as secret weapons for teams of highly skilled, motivated individuals with homogeneous culture about code. They are not industry standard and they should not be. Touting them as magical solutions just hurts them in the long run.

yes, Net Promoter Score

about the second part of your answer; my (probably very rare) opinion is that our job is not to "work in erlang" or "work in rust", is "solve problems/automate stuff". If I ask you to work in Foo instead of Erlang, it's the same job. I highly doubt that your job is slow because Go and fast because Rust, it's slow because process/idiots in other teams/idiots in your team/idiots as your "agile coach" etc.

I understand wanting to have a good career, but language is never the obstacle to a successful career. Also, this implicit bias that people who know exotic languages are better is completely false.

“Why not Elixir” is a more interesting question and I suggest you go ask it to engineering managers of polyglot organizations. They will usually bring you the super low nps from not-elixir-only devs and the resignation letters from elixir “talents” that are asked to do non elixir stuff.

I agree with your sentiment - I simply don't have a specific answer or I would be a very important person as I would have "solved" one of this century hardest problem.

I just believe that technology and innovation and creative destruction (in the schumpeterian sense) can (as they did) bring better resource usage which in turn drive better lifestyle for everyone.

I'm not sure where I would go from here; my brain is wired to my country problems (which is not usa, I hail from europe) which are completely 0 opportunities to actually get rich + complete domination of old money due to compound interest unstoppable force.

Heavily taxing inheritance in every form could be a start, but I'm not an expert in policy.

yeah, it was way better when you worked the fields for a duke who had dibs over your underage wife for the first night of marriage. and don't forget the round robin slave labour in the castle! and don't forget to set aside some grain for the taxes, who cares if this year has been bad and it all goes to the duke...

capitalism has its faults, but these platitudes about rotten systems really miss the mark.

the only thing this llm craze is helping is nvidia/openai/ms war chest, and fueling the illusion that every company can finally have their developers by taking any domain expert or barely knowledgeable person paired with an ai assistant. the mountains of trash produced by these things will end up costing a metric ton.

let's also measure the productivity of reviewers and people in general that, at a later point, have to wade through piles of ai generated crap.

last friday i had to review 2 trash PRs that were blatantly made with ai coding assistance. hundreds of code lines for something that, by reading the doc of the library, could have been made in 5 lines. and the fantastic comments like "returns the body" over a body() function.

the pot calling the kettle black

Bet the guys are also the ones most promoted. This is so screwed up.

Yes and no, sometimes you have to shed weight and kill some older use cases to start going back fast again. But yes, maybe for smaller projects.

This is also its downfall as my organization uses asyncpg and compatibility with it is still absent iirc :(

open governance and trying to get users make you uncomfortable while not merging prs, bus factor 1 and starting 300 projects with the same basic model ("do things - now with pydantic!") make you happy? fastapi has early mover moat and was great 3 years ago. but it's time to move on, there has been innovation. search for projects mentioning ovines (can't shill!)

btw, to complete the astroturfing, falcon is still the sanest python web library by a longshot (constructing a controller using init and wiring it manually? heresy, must use some bullcrap fake DI system), but it's completely ignored by almost everyone (and maybe dead-ish).