elbear

They withdrew in WW1 after the revolution.

> No one claims that good type systems prevent buggy software.

That's exactly what languages with advanced type systems claim. To be more precise, they claim to eliminate entire classes of bugs. So they reduce bugs, they don't eliminate them completely.

Likely because some people don't like to hear about positive experiences with LLMs.

I forgot about fromJust. On the other hand, fromJust is shunned by practically everybody writing Haskell. `unwrap` doesn't have the same status. I also understand why. Rust wanted to be more appealing, not too restrictive while Haskell doesn't care about attracting developers.

I never said Rust makes guarantees that code is panic-free. I said that Rust provides more safety guarantees than C. The Result type is one of them because you have to handle the error case explicitly. If you don't use unwrap.

Also, when I say safety guarantees, I'm not talking about safe rust. I'm talking about Rust features that prevent bugs, like the borrow checker, types like Result and many others.

I forgot about that one. Oops. So, ignore the part about Haskell and keep the rest.

The point is Rust provides more safety guarantees than C. But unwrap is an escape hatch, one that can blow up in your face. If they had taken the Haskell route and not provide unwrap at all, this wouldn't have happened.

I think the title or the author of the posting tends to draw a certain crowd.

For example, I recognised the name because the author also has a famous guide on network programming. Thanks to his reputation, I was curious what he has to say about learning CS.

My university uses Teams and the browser version is missing some features. For example, I can't see the files uploaded by the professor. That tab won't load.

Tiddlywiki

I wanted to say the same: parents don't treat all children the same. For example, I have the feeling that the first child is the "practice" child. The parents learn from the mistakes made with them and don't repeat them with the children that follow. I don't know if there's any research to back this up and yes, I am a first born.

How do you know we're not seeing technological unemployment? There have been quite a few layoffs, some of them attributed directly or indirectly to "AI".

Second, there are far fewer junior jobs in software development, again attributed to the advance of AI.

> As long as central bank is doing at least a halfway competent job, overall unemployment will stay low and stable. Ideally, you have people quit for a new job instead of getting fired, but in the grand scheme of things it doesn't make too much of a difference, as long as in aggregate they find new jobs.

Two big ifs: the central bank is competent and enough and people find new jobs.

Don't get me wrong: I am for progress and technological innovation. That's why we're working, to make our lives easier. But progress needs to be balanced, so that the changes it brings are properly absorbed by society.

How do you reconcile that with people getting fired because they're replaced with technology?

To what goal?

Yanis Varoufakis?

Just curious, are C, Go and Rust and the only viabile languages for an implementation?

See also What I Wish I Knew When Learning Haskell: https://sdiehl.github.io/wiwinwlh/

It's more up to date.

It sounds like some people.

If they work themselves to death, do they still receive more value than they give?

Yes, but people don't always make voluntary trades. Like staying in a job they hate, because they believe they will find it difficult/impossible to find a better option.

There are people who trade at a deficit just because they believe that's the only viable option. They see commerce as a zero-sum game.

Location: Bacău, Romania

Remote: Yes

Willing to relocate: No

Technologies: Python, Django, TypeScript, Haskell, Terraform, Ansible, NixOS, Docker, PostgreSQL, Azure, Oracle Cloud, AWS

Résumé/CV: https://pub-2e34f05858d2488ca9dbdad99dc1da3f.r2.dev/CV.pdf

Email: lucian at elbear dot com

Github: https://elbear.com/LucianU

I'm a software development generalist with over a decade of experience. My strong suit is my wide range of experience and versatility: I've done web (backend, frontend, scraping), infrastructure automation, tooling, functional programming (Haskell, NixOS).

I pride myself on having the courage to tackle any problem. For example, most recently, I added a feature to an open source client for SQL Server. The work involved dealing with binary protocols, which I hadn't done before, see here:

https://github.com/denisenkom/pytds/pull/182

I'm currently also pursuing a masters in applied math, where I'm learning topics such as Numerical Methods, Risk Theory, Game Theory, Stochastic Processes, Statistics and others.

See if this is it. I haven't used it yet, just know about it: https://github.com/block/goose

I don't know, for me it works, but I don't do anything fancy with it. I just put it on a server, so I can access it from all my devices. I don't even use tags, just tiddlers with sources which are other tiddlers or external web pages.

Tiddlywiki has two modes of running. In one, you simply save the file as HTML and all your content is saved inside the file.

The other mode is with a nodejs server (it's what I'm using). This allows me to access the wiki from all devices.

In other words, there's no incentive to become really good at what you do, if you're looking for a job. Employers won't appreciate it.

It's only worth it if you start your own thing, or if you specialise on something where you are judged based on measurable results.

Your site says Remote - US. Is that accurate?

I mean, if you publish something considered a breakthrough don't you also get glory?

Seems like their only motivation is their desire to succeed, glory, etc.