@BoomerCPC@elonmusk The pay isn’t anywhere near commensurate to the training, skill, or responsibility involved. Entry level ATCs should be making >100k and quickly promote to >$200k. Their union should be fighting tooth and nail for compensation levels that can attract and retain more talent.
Hey folks - I'm gonna talk about lessons learned while scaling @elmlang applications at https://t.co/AUnI6K1GOj today at 16h30 BRT / 19h30 UTC on the Elm Online Meetup.
@lambdapriest is also giving talk that I'm sure will be great!
Come! :)
https://t.co/6BLoJySiW4
@sabine_s_@tereza_sokol I got pretty proficient with intermediate-to-advanced Haskell and migrated several services from Node/GraphQL to Haskell/Servant at a previous gig. I still prefer Elm. They are the easiest code bases to work in and maintain, ever.
@editingemily Knees behind the toes is safety myth. There nothing dangerous about your knees traveling past your toes. In fact, you have to push you knees past your toes to do a full depth squat and in order to fully engage your quads.
@DeetsOnPolitics @laurenlee Care to explain why? I see so many people deriding him for all kind of stuff that turns out to be obviously false when I go verify primary sources.
@ryanflorence Idk, it’s been stupid easy with Elm for a decade. Never worked in a React code base that didn’t quickly devolve into a wad of tech debt. React 19 doesn’t appear to offer anything that will prevent that from continuing.
@0xglitchbyte@Aron_Adler@elmlang Literally every @elmlang app is built using fundamentally the same program architecture, so no matter what Elm code base you find yourself in, you have your bearings from the get go and can be pretty productive immediately.
How history of Software Engineering repeats itself over and over again:
1. You just started as an SE.
2. You write code.
3. You discover patterns.
4. If you have an opportunity, you share how you write the code with others on meet-ups and conferences.
5. People think it’s a best practice and follow it.
6. The more people follow it, the more common it becomes.
7. You use the approach you recommended in anger.
8. You discover its limitations and pitfalls.
9. Heck, it might even be an antipattern!
10. After so many years, you’re too burnt out from engineering.
11. You know how to code but you don’t give talks anymore. You just do your work slowly on a stable job.
12. You watch a YouTube video with a person advocating for the same approach you liked decades ago.
13. You’re too exhausted to care.