kyran / tags / development

Tagged with “development” (14)

  1. Stanford’s Entrepreneurship Corner: Joel Peterson, Peterson Partners - Stan Christensen, Stanford Technology Ventures Program; Arbor Advisors - Secret to Successful Negotiations

    Joel Peterson, founder of Peterson Partners, discusses the secret to successful negotiations. He reminds us that negotiation is how one navigates their way through life, and in order to have successful negotiations, people must be empowered, have high character, and confidence. Peterson draws from his experience as CEO of one of the world's largest real estate development firms and most recently founded Peterson Partners- an equity fund in search of talented and visionary CEOs.

    http://ecorner.stanford.edu/authorMaterialInfo.html?mid=1573

    —Huffduffed by kyran

  2. Episode 33 – Client-side Components – (40 minutes)

    Kerry and Rinat return from their summer break to discuss their initial explorations into client-side development.

    This episode, and the two episodes after it, cover a two month period in which Rinat and Kerry went off to write some new client code for their Getting Things Done(tm) sample project.

    They start this three-part spike with a simple WinForms client, and end it with the beginnings of their cross-platform mobile application.

    Download (mp3): Episode 33 – Client-side Components – (40 minutes)

    Subscribe via RSS | Subscribe for free in iTunes

    Episode References:

    BTW Sample Code for E33 on GitHub

    Staged event-driven architecture

    Model–view–controller (MVC) pattern

    Model View ViewModel (MVVM) pattern

    Event Store

    Feedback and Finding Us

    What do you think?

    http://beingtheworst.com/2013/episode-33-client-side-components

    —Huffduffed by kyran

  3. Episode 34 – Model View Who? – (41 minutes)

    This episode is the second of a three part series on client-side development.

    Kerry and Rinat discuss the changes that were made to the sample’s WinForms client to make it easier to add new features.

    They review the three main contexts in their GTD sample, the benefits of passing around immutable state, and dig into graphical user interface architectures like MVC and MVVM.

    This sets them up for the next episode where they apply MVVM to the sample’s cross-platform mobile application.

    Download (mp3): Episode 34 – Model View Who? – (41 minutes)

    Subscribe via RSS | Subscribe for free in iTunes

    Episode References:

    BTW Sample Code for E34 on GitHub

    Martin Fowler’s article on GUI Architectures

    Free MvvmCross Training Videos compliments of @slodge – Stuart Lodge

    MvvmCross code on GitHub

    @mvvmcross on Twitter

    Micorsoft’s Roslyn compilers

    Model–view–controller (MVC) pattern

    Model View ViewModel (MVVM) pattern

    Feedback and Finding Us

    What do you think?

    http://beingtheworst.com/2013/episode-34-model-view-who

    —Huffduffed by kyran

  4. 010 RR Personal Design Rules

    Podcast: Play in new window | Download (Duration: 59:55 — 82.3MB) Panel Avdi Grimm (twitter github blog book) Charles Max Wood (twitter github Teach Me To Code) David Brady (blog twitter github ADDcasts) James Edward Gray (blog twitter github) Josh Susser (twitter github blog) Discussion Premature optimization is the root of all […]

    http://rubyrogues.com/personal-design-rules/

    —Huffduffed by kyran

  5. Core Intuition » Episode 126: A Perfect Storm Of Two Or Three Problems

    Manton and Daniel reflect upon the first week of the Core Intuition job board, Daniel’s introduction to Ruby programming, and Apple’s obligation to ensure quality of their security libraries.

    Download (MP3, 49 minutes, 24 MB)

    Core Intuition Jobs – Our (fairly!) new job board.

    Dashcode User Guide – Apple’s documentation for their neglecting web-technologies development IDE.

    SQLite – Famously reliable open source project with questionably conventional code style.

    A Single Bad ‘Goto’ – Wired article summarizing the Apple SSL security issue.

    goto fail; – The simple source code mistake that caused the issue.

    Sponsored by Crashlytics: The most powerful and lightweight crash reporting service. Also check out the open-source Crashlytics Services on GitHub.

    http://www.coreint.org/2014/03/episode-126-a-perfect-storm-of-two-or-three-problems/

    —Huffduffed by kyran

Page 1 of 2Older