- .NET
- .NET Core 1.1
- 3D
- Android
- Angular
- Angular2
- AngularJS
- apps
- Architecture
- array
- ASP .NET
- async
- await
- Azure
- binding
- C#
- changes
- closure
- cocoa
- code
- collection
- components
- composition
- cross-platform
- delegate
- dependency injection
- design
- desktop
- Development
- escaping
- events
- exception
- for
- generalization
- git
- Holographic
- HoloLens
- HTML
- iCloud
- INotifyPropertyChanged
- iOS
- iPhone
- JavaScript
- learn
- learning
- Mac
- macOS
- Mobile
- mocking
- multi-threading
- MVC
- PC
- properties
- quality
- SQL Server
- Surface
- Swift
- target
- technologies
- technology
- testing
- tools
- types
- TypeScript
- unit tests
- Unity
- UWP
- Visual Studio
- WebAPI
- Windows
- Windows 8
- Windows 10
- Windows Phone
- WPF
- xCode
Archives
Top 10
- Want to learn WPF? Get a book
- How to write good code on first attempt
- Don't set NSPopupButton's menu.items!
- Books do make a difference
- Developing HTML UI for SQL Server data with no middle code (or just a few lines)
- XAML element properties and cut-paste refactoring
- macOS milestone
- How to improve your good code further
- Embedding custom Cocoa macOS views with xibs into frameworks
- Generically handling multi-threading exceptions in WPF
- Follow Code {Sections} on WordPress.com
Tag Archives: Architecture
Waterfallish isn’t [always] foolish!
Your first goal is an MVP – minimum viable product [not Microsoft’s most valuable professional.] You define a few features and envision a few screens. Sure, without going into any details. And you go with scrum from the beginning. You’re … Continue reading
Posted in Development
Tagged Architecture, design, Scrum, software development, waterfall
Leave a comment
Creating great products requires outstanding functional design
(I’ve recently twitted two examples, but I think it the idea deserves a more general blog post, so here we go.) It’s not enough to be an outstanding developer to be able to create great software (that sells). You need to also … Continue reading
Posted in Development
Tagged Architecture, capture, design, Development, functional, user
Leave a comment
On onion (cone?) architecture
“High level modules should not depend on low level modules. Both should depend on abstractions.” The first three circles starting with the central Domain define the application core. Each of these is a collection of high level modules. The outer-most … Continue reading
Stop over-abstracting
Developers are very good when it comes to abstracting things, be this: 1) generating base or generic classes to inherit from or reuse; 2) generic or overloaded functions called with arguments instead of standalone ones; or 3) reusing code under multiple technologies even if it’s … Continue reading
Posted in Architecture
Tagged abstracting, Architecture, cross-platform, generalization, refactoring, reusing, technologies
3 Comments
Unit of work over Entity Framework
Many unit of work and repository implementations over Entity Framework do not respect the interfaces of the patterns correctly, and therefore the abstractions do not serve any purpose. In my opinion, the single reason for (and goal of) abstracting unit of work and … Continue reading