Featured post

c# - Usage of Server Side Controls in MVC Frame work -

i using asp.net 4.0 , mvc 2.0 web application. project requiremrnt have use server side control in application not possibl in noraml case. ideally want use adrotator control , datalist control. i saw few samples , references in codepleax mvc controllib howwver found less useful. can tell how utilize theese controls in asp.net application along mvc. note: please provide functionalities related adrotator , datalist controls not equivalent functionalities thanks in advace. mvc pages not use normal .net solution makes use of normal .net components impossible. a normal .net page use event driven solution call different methods service side mvc use actions , view completly different way handle things. also, mvc not use viewstate normal .net controlls require. found article discussing mixing of normal .net , mvc.

Agile practices on embedded software development -


i have had great success e.g. fast development cycles , continuous integration.

however, think pair programming or continuous customer communication less useful due issues specific of embedded software programming.

what think? useful agile practices on embedded software development?

i have disagree. i've done it, , 10 years ago co-founded agile coaching company specializing in embedded (we're no longer company the website still up several useful resources). helped company adopt agile embedded project, , worked them.

agile practices short iterations, pair programming, , frequent communication customer even more important embedded software because there's more @ stake, both because embedded systems harder/more expensive update in field, , because used in mission-critical applications.

as pair programming, if company has 1 person knows first thing component of software, that's huge risk, , pair programming great way of doing cheap knowledge transfer. both developers don't have experts in part of code. can have primary , secondary isn't. secondary partner able offer on program structure, compare design decisions, ensure proper testing , documentation, etc. of course each developer has primary , secondary other times make crosstraining effective. effective way of bringing new developers speed on products.

lastly, customers care features , plans, not code. embedded doesn't change this. showing off have far , plan next ensures you're working on you're supposed to.


Comments

Popular posts from this blog

c# - Usage of Server Side Controls in MVC Frame work -

cocoa - Nesting arrays into NSDictionary object (Objective-C) -

ios - Very simple iPhone App crashes on UILabel settext -