Functional architecture - The pits of success - Mark Seemann
NDC Conferences · 4 位 HN 用户推荐 · 2018–2021
unctions. Now, depending on your problem domain, your core can be small or huge compared to the shell. Your question was all about IO/effects. They are impure and belong to the shell. If what you work on does mostly IO then you will have a lot of impure code lying around by definition. Still, the idea is that you should keep the amount of time spent in impure land minimal, ie. drop into pure struc
— pwm, 2018Of course, this isn't the solution to every problem (it obviously depends on the domain you are working in, for me its webDev and backends), but I think maybe its a good way for people to start. Edit: Here is a great talk demonstrating that by following a simple functional approach, your code can naturally fall into a “pit of success”: [link]
— adamkl, 2020His videos about functional programming are amazing (Mark Seemann). "Pit of success" is one of the best. [link]
— Xunjin, 2021Mark Seemann has a good talk on this called the "functional pits of success" -> [link]
— kirse, 2021