conference:committee:proposals-2013

Backlinks

This is a list of pages that seem to link back to the current page.

2013:advanced_ios_development
2013:adventures_in_data
2013:agile_contracts
2013:agile_developers_-_your_country_needs_you
2013:agile_teams:value-focused_values-driven
2013:allocators_for_shared_memory_in_c_03_c_11_and_boost
2013:an_exploration_of_the_phenomenology_of_software_development
2013:an_integrated_programming_language
2013:an_undecided_customer
2013:applied_hierarchical_reuse_-_capitalizing_on_bloomberg_s_foundation_libraries
2013:auto_-_a_necessary_evil
2013:a_framework_for_growing_effective_software_teams
2013:back_to_the_future_-_re_learn_smalltalk
2013:bad_test_good_test
2013:batoo_jpa_-_the_new_java_persistence_api_implementation_-_15_times_faster_then_the_alternatives
2013:becoming_a_better_programmer
2013:beyond_mocking-sustainable_unit_testing
2013:beyond_mocking:sustainable_unit_testing
2013:brutal_refactoring_game
2013:c-sharp_is_a_doddle
2013:catch:a_natural_fit_for_automated_testing_in_c_c_and_objective-c
2013:catch_-_a_natural_fit_for_automated_testing_in_c_c_and_objective-c
2013:cheating_decline:acting_now_to_let_you_program_well_for_a_really_long_time
2013:clanging_effectively_with_legacy_code
2013:clang_considered_helpful
2013:cleaning_code_-_tools_and_techniques_for_legacy_restoration_projects
2013:code_as_a_crime_scene
2013:coding_dojo_challenge-refactoring
2013:coding_dojo_challenge-solid_design_principles
2013:concepts_lite-constraining_templates_with_predicates
2013:crossing_the_chasm_from_web_to_windows_8_development
2013:culture_hacking
2013:c_11:user-defined_literals_and_literal_types
2013:c_11_features_and_real-world_code
2013:c_11_for_the_rest_of_us._simpler_code_with_more_power
2013:c_11_rescues_allocators
2013:c_11_the_future_is_here
2013:c_11_user-defined_literals_and_literal_types
2013:c_14_early_thoughts
2013:c_for_very_small_embedded_systems
2013:c_in_the_21st_century._extensible_languages_with_mps
2013:c_pub_quiz
2013:c_unit_testing_with_the_fake_function_framework
2013:dataflow_is_the_architecture_you_need
2013:death_by_dogma_versus_assembling_agile
2013:designs_for_human_minds
2013:design_is_a_joke
2013:diagnoses_for_your_project
2013:dynamic_c
2013:effective_gof_patterns_with_c_11_and_boost
2013:embedded_development_what_s_changed_in_30_years
2013:ephemeral_unit_tests_using_clang
2013:exception-safe_coding_in_c
2013:exceptional_handling
2013:extreme_startup
2013:faking_stubbing_and_mocking_in_c
2013:fast_enough_vms_in_fast_enough_time
2013:fear_and_loathing_on_the_agile_trail
2013:fork_--_exploring_a_separate-process_async
2013:from_plans_to_capabilities
2013:functional_programming_for_the_dysfunctional_programmer
2013:generic_programming_in_c_a_modest_example
2013:getting_legacy_c_c_under_test
2013:git_-_everyday_recipes_for_you_and_your_team
2013:git_-_why_should_i_care_about_the_index
2013:groovy_is_a_high_performance_language
2013:groovy_programming
2013:growing_cross-functional_teams_in_the_public_sector
2013:growing_c_software_guided_by_tests
2013:growing_software_from_examples
2013:gumption_traps_reloaded
2013:hands_on_continuous_deployment
2013:hardware_for_softies:physical_computing_with_the_raspberry_pi
2013:health_and_hygiene_in_the_modern_code_base
2013:how_to_narrow_down_what_to_test
2013:how_to_program_your_way_out_of_a_paper_bag
2013:hybrid_programming
2013:implementing_smart_use_cases_on_the_windows_8_platform
2013:improving_application_efficiency_on_arm_-_what_app_developers_need_to_know_about_hardware_systems
2013:incremental_software_delivery
2013:inspiring_future_generations_with_open_hardware_-_the_raspberry_pi
2013:in_credible_leadership_for_agile_engineering_teams
2013:is_extreme_programmers_still_alive_and_kicking
2013:java_8_a_new_beginning
2013:java_a_new_beginning
2013:java_ee_handbook_7
2013:just_agile-there_is_more-establishing_the_creative_team_space
2013:key_habits_of_highly_successful_agile_organizations
2013:lean_principles_for_leading_organizational_change
2013:learning_ruby_through_tdd_and_katas
2013:lightning_talks
2013:live_from_the_trenches._building_.net_web_applications_on_top_of_cobol
2013:location_location_location
2013:logic_programming_and_test_data_generation
2013:look_ma_update_db_to_html5_using_c_no_hands
2013:making_cross-shore_time-zone-spanning_teams_work
2013:managing_from_the_mountaintop
2013:measure_and_manage_flow_in_practice
2013:methodology_a_la_carte
2013:more_effective_presentations
2013:move_noexcept_and_push_back_and_how_it_relates_to_each_other
2013:multicore_parallelism_for_c_with_intel_r_threading_building_blocks
2013:open_source_patterns
2013:organizational_influence_hacks
2013:otp_the_middleware_for_concurrent_distributed_scalable_architectures
2013:parallelism_in_c_1y
2013:pattern-oriented_software_architecture
2013:professional_css_for_developers
2013:real_architecture-engineering_or_pompous_bullshit
2013:refactoring_to_functional
2013:restful_objects_-_a_hypermedia_api_for_domain_object_models
2013:robust_software_dotting_the_i_s_and_crossing_the_t_s
2013:ruby_and_rails_for_n00bs
2013:scrum_and_evolution_-_what_can_we_learn
2013:server_login_considered_harmful_-_introduction_to_devops_practices
2013:sfinae_functionality_is_not_arcane_esoterica
2013:surviving_long-running_agile_projects._agile_by_example
2013:taking_scala_into_the_enterprise
2013:test_driven_development_on_the_raspberry_pi
2013:the_111111_unity_method_for_decomposition_of_projects_in_to_an_agile_value_stream
2013:the_actor_model_applied_to_the_raspberry_pi_and_the_embedded_domain
2013:the_art_of_reviewing_code
2013:the_bright_side_of_exceptions
2013:the_c_11_standards_experience
2013:the_evo_agile_method_-_a_front_end_to_scrum_and_other_agile_methods_for_focussing_on_stakeholder_value
2013:the_git_parable
2013:the_history_of_a_cache
2013:the_impact_estimation_tool_for_management_of_design_and_projects_-_a_real_software_engineering_approach
2013:the_national_museum_of_computing
2013:the_phb_transmogrification_kit_-_10_shamelessly_pragmatic_ways_to_convert_meddling_managers_into_helpful_heroes
2013:the_story_of_raspberry_pi
2013:the_true_cost_of_software_bugs_and_what_to_do_about_it
2013:thoughts_on_error_handling
2013:transactional_memory
2013:transactional_memory_for_c
2013:understanding_the_evolution_of_whole_teams_using_the_dreyfus_model
2013:unspecified_and_undefined
2013:user_requirements_for_the_21st_century_user-centred_design_in_agile
2013:use_the_source
2013:using_data_to_understand_how_you_develop_software
2013:using_fluent_interfaces_to_solve_everyday_problems
2013:visualizing_legacy_code_and_data_using_moose
2013:what_c_11_means_for_class_and_framework_designers
2013:what_s_that_smell_-_refactor_away_that_nasty_odo
2013:what_s_that_smell_-_refactor_away_that_nasty_odor
2013:what_the_lwg_did_next
2013:why_is_c_11_library_code_impossible_to_read_and_understand
2013:worse_is_better_for_better_or_for_worse