Thanks for taking time to read my posts.
Hm, I’m kind of dissapointed that code development is already finished. I can imagine that negative feedback may cause people to stall, but you already did an internal review of your own right?
Ayende’s post inspired me because he clearly takes the voice when he sees things that upset him. That is the case with _parts_ of silk in my case. Silk is a guidance coming from P&P that means devs should look at it, learn and write apps in same
(or close) way. I would expect it to be elegant, clear and not over-engineered(again i’m talking about parts, not app as the whole). Now, when beginner starts to learn develop software with Microsoft technologies she looks at the guidances and apps from
Microsoft( at least I did) and tries to create software in similar way, but when those apps contain stuff that is questionable it’s repeated over and over (I also did). So such guidance’s should be top notch in any way.
I can understand that Microsoft teams may a bit frustrated that some of the apps which get published( for example: silk, that guidance from ayende’s post or that wcms system but I forgot the name ) cause stirr and discussion, but hey we expect the
best from you guys.
Ok, Win 8 similarity may be just a coincidence.
We didn’t spend a lot of time on the server-side part of Mileage Stats. Most of the team still thinks we spent too much time there. Based on what we were primarily focused on, we should have just used MVC Scaffolding and called it a day so we could
get back to the front-end.
I definitely agree that Silk would benefit from focus on UI and using only simple CRUD on the server side, without DDD-esque or CQRS-esque architecture, and call it only frontend guidance or composite js guidance.
Thanks for feedback!
I also published it on my blog: http://bartekszafko.pl/2011/07/19/project-silk-subjective-review-part-1/comment-page-1/#comment-526