Create mobile apps with HTML5, JavaScript and Visual Studio

DEVWEEK

20 | DEVWEEK | http://www.devweek.com | @DevWeek

AGILE/

OO-DESIGN,

FROM START

TO FINISH

BUILDING

SCALABLE

JAVASCRIPT

APPS

DELIVER

DOMAIN-

DRIVEN

DESIGNS –

DYNAMICALLY!

Building and

maintaining

large and

scalable

JavaScript

web apps is not at all easy.

So how you build such

things without being driven

into madness? Using and

combining proven JavaScript

patterns will do the trick.

In this one-day

workshop, Fink will

talk about the patterns

behind some of the largest

JavaScript apps, such as

Gmail and Twitter, and

how to apply them in your

own apps. He will start

from object patterns and

then focus in on module

patterns, promises, timers

and more.

¡

DAY 5 AGENDA: ALL-DAY POST-CONFERENCE WORKSHOPS

WORKSHOP REF: F1

SHAREPOINT

2013 APP

DEVELOPMENT

WORKSHOP REF: F2

How do you statically model

an ever-changing world? The

approach of domain-driven

design (DDD) describes the

codification of perspectives of

reality into a domain model,

which is in turn realised as

a software system around

which valuable services can

be constructed. As business

and physical domains evolve,

our requirements, models and

implementations must follow

if they are to remain relevant.

Dynamic languages, such

as Python are a great match

for the dynamism of the real

world. It is perhaps surprising

then, that for much of the

decade since its inception,

DDD has manifested its

results in rigid relational-

database schemas, object

relational mappers pushed

beyond reasonable limits and

inflexible object models in

statically typed languages such

as Java or C#.

In this hands-on

workshop, participants

will work together to

implement a domain

model in Python using

nothing more that plain

old Python objects.

Bingham and Smallshire

will show how core DDD

concepts, such as entities,

immutable value objects,

aggregates and repositories,

can be implemented in Python.

They will build declarative

tools from scratch to facilitate

model implementation, and

they’ll evaluate persistence

solutions, including object

databases, graph databases,

“traditional” RDBMSs and

document stores.

¡

WORKSHOP REF: F3

Apps

enable any

developer

to deliver

SharePoint

functionality. They allow you

to use things such as MVC,

TDD and everything else you

like with SharePoint. Apps

are the single biggest change

between SharePoint 2010

and 2013. Is it surprising,

then, to discover that the apps

platform is full of gaping holes

• missing functionality and

pitfalls – things you need to

watch out for?

In this session, Malik

will cover all those topics

that you won’t read on

MSDN, but that you

will discover in your

projects. No stone will

be left unturned.

Those who will get the

most out of this session are

those who are either .NET

developers who don’t want

to learn SharePoint – or are

clinging on to best practices

as they are being forced

into delivering SharePoint

functionality – or seasoned

SharePoint developers who

want to know the real deal

on apps.

¡

Many people

who think

they’re

doing OO

aren’t. For

example, the dynamic model

(that shows how run-time

objects interact) should drive

the design process; the class

diagram is an artefact you

build while doing dynamic

modelling. Fixating on the

class diagram renders your

program, at best unwieldy,

at worst non-functional.

Similarly, basic OO

architectural goals (such

as eliminating getter/setter

functions) seem impossible to

do unless you understand how

the design process actually

works. It turns out that the

process you use influences

both the quality and the basic

structure of the design.

In this workshop,

Holub will cover an agile

version of the OO-design

process, with an emphasis

on how to arrive at an

optimal design.

He’ll provide a quick

overview of the process,

then spend much of the class

working through one (or more

if we have time) real-world

examples that show you the

entire process, from front to

back: requirements gathering

and problem-statement

definition, use-case analysis

(story development), and the

simultaneous construction of

the dynamic and static models

using UML.

¡

WORKSHOP REF: F4

Gil

Fink

Rober t

Smallshire

Sahil

Malik

Allen

Holub

Austin

Bingham

Friday 4th April

THE FOLLOWING

WORKSHOPS RUN

FOR A FULL DAY,

FROM 09.30 TO

17.30 WITH A

SHORT BREAK

IN THE MORNING

AND AFTERNOON,

AND A LUNCH

BREAK AT 13.00.

UNLESS

OTHERWISE

NOTED IN THE

DESCRIPTION,

THEY ARE

PRESENTATION-

BASED IN STYLE

RATHER THAN

‘HANDS-ON’ LABS.

Please refer to page 2

for guide to colour symbols.

BOOK

NOW

BOOK YOUR PLACE BY

31 JANUARY AND SAVE

UP TO £200

Untitled-6 20 1/16/14 1:45 PM