It’s been a busy couple of months at Colenso BBDO Auckland, Aim Proximity and Clemenger BBDO Wellington. We thought we would showcase some of digital work in Q3 2007.Duration : 0:3:30

Video Tutorial for installing Visual Studio 2005 C++ Express EditionDuration : 0:8:13

ANIMATION AND CREATION IN VUE 6 XSTREAM, CONCEPT AND DESIGNS.Duration : 0:1:37

Ported my Bcode TI-83+ pattern generator program to python using pygame. With simple rules you get these beautiful patterns. The patterns generated look like bugs/organisms. Dont know maybe its just me.Duration : 0:2:24

This Tutorial is meant for people who are thinking of making a game review.
I havent been doing reviews long, but i have been on youtube for quite some time now.
I think i have learnt alot from it, and id like to share it with you guys.
Here are the links which i said id post here.
camstudio screen recording software:
http://camstudio.org/
Gens emulator:
http://gens.consolemul.com/downloads.shtmlDuration : 0:9:58

Broadband Conference, Bucureşti, 23-25 octombrie 2007.

Dieter Angerer, Country Manager Nokia Siemens Networks Romania, a prezentat in standul de la Broadband Conference o centrala WiMAX de ultima generatie.Duration : 0:1:16

www.mylivelessons.com

Stephen Walther, the world’s leading ASP.NET authority introduces his new LiveLesson- DVD-ROM hands-on personal video instruction comprised of full motion video, audio and screencasts.

SELF-PACED, PERSONAL VIDEO INSTRUCTIONS FROM THE WORLD’S LEADING ASP.NET Trainer

4 + Hours

http://www.informit.com/store/product.aspx?isbn=0672329522

Data Access in the ASP.NET 2.0 Framework will show you everything you need to know to start building database-driven web applications using the Microsoft ASP.NET 2.0 framework and the Microsoft Visual Studio 2005 development environment.

Your instructor Stephen Walther–honored by Microsoft as both an ASP.NET MVP and “Software Legend”–guides you through building two fully functional, database-driven applications. Learn at your own pace with video lessons covering every main ASP.NET data access control: GridView, DetailsView, FormView, Repeater, DataList, and SqlDataSource.

One step at a time, you’ll learn how to build robust data access components, provide graceful error handling, handle user concurrency issues, and much more.

Looking for a better way to master today’s rapidly changing programming technologies? Want expert help, but don’t have the time or energy to read a book? Can’t find classroom training worth the money? Discover LiveLessons: self-paced, personal video instruction from the world’s leading experts.

LiveLessons are video courses, on DVD with a book supplement, that are organized into bite-sized, self-contained sessions–you’ll learn key skills in as little as fifteen minutes!

Track your progress as you follow clearly defined learning objectives.
Follow along as your instructor shows exactly how to get great results in your real-world environment.

Professional author and instructor Stephen Walther provides an introduction to the core concepts of Data Access in the ASP.NET 2.0 Framework. Click play to follow along with Stephen as he explains the ins and outs of creating database-driven dynamic web applications in this LiveLesson.

Workbook Introduction vii

Module 1: Getting Familiar with the Visual Studio 2005 Development Environment 1

Module 2: Creating an Employee Directory Application 7

Module 3: Using the ASP.NET 2.0 Data Access Controls 17

Module 4: Advanced Topics 39

Module 5: Creating a Guestbook Application 43

Bonus 1: An Introduction to SQL: The Language of Databases 49

Bonus 2: An Introduction to the Microsoft ASP.NET Framework 71Duration : 0:2:5

Here is some code written in Fortran IV (which I think is the same as Fortran 66). FORTRAN IV is a “subset” of natural language, in the sense that one can simply describe in natural language, what any given statement in a FORTRAN IV program does. This does not mean that it is necessarily easy to read code written in FORTRAN IV. As an analogy, let us look at someone solving a Rubik cube. They have memorised a method (known to them) for solving the cube. But an onlooker may have no idea why the particular moves are being made.

In writing code in Fortran IV, it would be possible to provide parallel documentation to explain every step that had been taken and why. (Just as this could be done for each step to solve a Rubik cube). But the developer, given time constraints, may not have provided this very extensive documentation. (Hardly anyone ever does — I have never seen it done, except in books teaching a programming language).

This is an example from code written at DAS (Specifications were given to me in late 1975. I cannot give the specifications here, as they have not been kept. However, we can “reverse engineer” the specifications from the code.

SUBROUTINE PRFORM
C USE: process columns of data repeatedly
C till end of data.
C then print out the partly filled last
C page (if it exists).
C
COMMON/CEOF/EOFIN
COMMON/CERR/ERROR
COMMON/CCOL/ICOL
LOGICAL EOFIN, ERROR
ICOL = 1

10 IF (EOFIN) GO TO 20
IF (ERROR) RETURN
C process one column of data
CALL PROCC GO TO 10
C print last page if present

20 IF (ICOL.NE.1) CALL WRIT
RETURN
END

The flag EOFIN is set by another subroutine, if we have run out of data.
Subroutine PROCC sets the flag EOFIN if it detects that data is missing.
ICOL is the column of data on the outpage page.
We loop, processing one column of data each time.

What I have written, effectively, in the above, code, is specifications that the subroutines PROCC and WRIT have to meet. I am required to write subroutines PROCC and WRIT so that the PRFORM function works correctly.

It is possible that a more advanced approach to specifying the output could have been taken — could we have defined the input and output files using a grammar? Yes, I think the developer would be free to use this idea, if they wanted to, in their development of the subroutines PROCC and WRIT.

The subroutine PRFORM above did not do very much. It assumes that PROCC will maintain the ICOL value, and that error and eof flags will be set as required.

Is this good design? I recently asked Professor William Waite (from Colorado) for his ideas on how to assess the quality of Fortran IV code. He said that “quality is in the eye of the beholder” — he did not think, that Dijkstra would have made any judgements about the quality of specific programs in Fortran IV, except to say that Fortran was “an infantile disorder”. But I am not certain that Dijkstra knew much about Fortran IV - I think he had abandoned Fortran many years before Fortran IV arrived.Duration : 0:0:37

I suspect that languages like Prolog do not fit into the mould of today’s business hierarchies. However languages like Prolog have a future — they will still be here when today’s business management models have been abandoned and replaced.

It is said that Ken Thompson, the inventor of Unix, wrote the first version of Unix in assembly language in 1969. He begain to rewrite it in Fortran IV but gave up after a day or a week, and used C which was derived from Martin Richards’ language B, derived from BCPL. (B is still available (2007) free as a download from Richards at Oxford or Cambridge). As far as is known, no one has yet implemented Unix in Fortran (or Java).
Fortran was fairly portable. However, different computers had different word sizes, so it was easy to write Fortran code that was not very portable. Waite’s SIMC and STAGE2 systems were “portable” (though they took about a week’s work, by an expert, to get them to run on a new computer). Unix is much more portable than this. Today we expect “portable” to mean that a program will run correctly with absolutely no changes, and completely automatically.Duration : 0:0:10

Sam Guckenheimer describes key concepts from his latest book, Software Engineering with Microsoft Visual Studio Team System.

Get the book:

http://www.informit.com/store/product.aspx?isbn=0321278720

Get all the OnMicrosoft Vidcasts FREE:
http://www.informit.com/podcasts/channel.aspx?c=3761c00b-ef8f-4385-9b08-a6e1c7a9a35f

Subscribe Now:

http://www.informit.com/podcasts/index_rss.aspx?c=8

Readers will learn what they need to know to get started with VSTS, including:

The role of the value-up paradigm (versus work-down) in the software development lifecycle, and the meanings and importance of “flow”
The use of MSF for Agile Software Development and MSF for CMMI Process Improvement

Work items for planning and managing backlog in VSTS

Multidimensional, daily metrics to maintain project flow and enable estimation

Creating requirements using personas and scenarios

Project management with iterations, trustworthy transparency, and friction-free metrics

Architectural design using a value-up view, service-oriented architecture, constraints, and qualities of service
Development with unit tests, code coverage, profiling, and build automation

Testing for customer value with scenarios, qualities of service, configurations, data, exploration, and metrics

Effective bug reporting and bug assessment

Troubleshooting a project: recognizing and correcting common pitfalls and antipatterns

This is a book that any team using or considering VSTS should read.Duration : 0:10:35