Re: Engineering Value of Functional Programming

https://en.wikipedia.org/wiki/Curry%E2%80%93Howard_correspondence

The program is the proof of the (problem-related) theorem.

One can use type classes and HOT to express *requirements* and protocols of
various parts of the program and then fill implementation details. Types
allow for *tracking requirements* inside the implementation.

Basically, by applying type systems like Haskell's one gets a requirement
tracking system for free. And requirements' tracking is a very hard task.

But it is a "waterfall" on steroids and as unhip as one can only imagine.

вт, 10 дек. 2024 г. в 17:29, Mostafa Touny via Haskell-Cafe <
[email protected]>:

> Thank you all for your comments.
>
> The closest thing I found related to project management and haskell was
> Serokell's blog: https://serokell.io/blog/haskell-in-production
>
> I feel there is a space for designing new project management methodologies
> based on type and category theory.
>
> Let me know if anyone is curious to explore that.
>
> Best,
> Mostafa Touny
> _______________________________________________
> Haskell-Cafe mailing list
> To (un)subscribe, modify options or view archives go to:
> http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe
> Only members subscribed via the mailman list are allowed to post.

_______________________________________________
Haskell-Cafe mailing list
To (un)subscribe, modify options or view archives go to:
http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe
Only members subscribed via the mailman list are allowed to post.