- I decided to give up on new development after the shortly forthcoming 2.0 version
- Our usage of the Russian Doll model and where we fell in the balance between repetitive ceremonial code and using conventions for cleaner code
- Command line bootstrapping, polyglot programming, and the value in standardizing codebase layout for the sake of tooling (I say yes, .Net community says no)
- Lots of DevOps woes trying to develop across multiple repositories using Nuget, TeamCity, and our own Ripple tool.
- Strong naming woes and workarounds
- The importance of Semantic Versioning
- Integration testing in process with OWIN worked out well
(Maybe) Yet to Come:
These are the subjects I’m thinking about writing about later. Honestly, these blog posts have been cathartic for me. Other than being constantly slammed for poor documentation and whining about us using Rake instead of [fill in the blank] build tool, the response has been mostly positive.
- Routing and Url Resolution (why I think FubuMVC did it better than Web API does it)
- FubuMVC’s approach to diagnostics. Our diagnostics didn’t overlap much with Glimpse and I think other fx’s could benefit
- IoC integration into frameworks and why I hate almost every IoC abstraction ever written
- Using strong typing advantageously
- The value of an underlying Semantic Model for frameworks
- A lot more on modularity
- More on “one model in, one model out”
- Working with HTTP (we could have done it much better)
- My thoughts on OWIN (hate using it, love the possibilities) and why ASP.Net itself needs to go to the source control repository in the sky
- FubuMVC’s approach to middleware w/ the Russian Doll model
- Using Convention over Configuration effectively
- Redirects and Transfers in a testable way
- Collapsing an application down into a single process for testing
- Automated Testing w/ FubuMVC. How we built testability features directly into the framework itself.
- Making distributed development easier w/ Bottles and multiple AppDomain’s
- Content negotiation. I think a lot of the .Net web fx’s have struggled with this a bit and we did too.
- Asset management and integration w/ the server side framework. Discussing what our original asset pipeline was and how it fell down, then the newer lightweight asset pipeline for 2.0 I’m excited about and our integration w/ Mimosa.js for the real heavy lifting.
- FubuTransportation — the service bus we wrote on top of FubuMVC