Why I Use A Top-Down Approach To Design Software | Drawing An Interface | StonkWatch Ep.3 

Hey, I love that you're doing this! As an experienced engineer who has had some familiarity with EventSourcing/DDD, Clojure, Java, Haskell, etc, I'm excited to see what you come up with! I'm not that familiar with F# in particular (other than buying Scott Wlaschin's book), so that will be super interesting to me. You're clearly using F# for fun and profit - keep it up!

"Most people really care about how things look.", I'd add a detail to this statement.... "Most people really care about how things look, EVEN if they say they don't." Everyone wants a cool looking UI, you don't need to overkill and focus too much on it but don't deliver an ugly looking system because "the backend is what really matters". BTW, I love the series! Dunno how far you were planning to reach but I'm following it from Brazil. Great job man!

I've never seen a dev tutorial starting out with the design. Well done! You also mentioned SignalR for real-time data transfer. Bolero (the F# port of Blazor, fsbolero.io/docs/) uses SignalR by default for the server-side model. This might be an option if you want to always show the latest data to the user.

Loving the journey youre taking us dude! :)

Nice. Coming from a bit of an OCaml background and fell in love with the ML style. Been reading Expert F# alongside this series. Your perspective on software design is very helpful

29:10 "Might be overselling myself here" 😂 Good job Ben, love that you tackled the problem from a UI perspective first :)

Nice 👍🏼

👍

Nice man! Looking good. dotnet new SAFE next? :)

4:06 ~ 5:49 I should have heard this sooner. Really 😂😂

Is that a google whiteboard thing?