Choose an application

• Reference Manager
• EndNote
• RefWorks (Direct export to RefWorks)

Deze handleiding hoort bij boek 1 tot en met 4 van Programmeren kun je leren. De handleiding is bedoeld voor leerkrachten (en ouders) die kinderen begeleiden bij het leren programmeren. Handleiding per boek, stap voor stap Met deze handleiding kunt u kinderen stap voor stap begeleiden bij het leren programmeren, ook als u zelf geen kennis heeft van programmeren. De handleiding volgt de indeling van boek 1 tot en met 4: de betreffende pagina's worden steeds in het klein afgebeeld. U kunt de voortgang van de kinderen bijhouden. Meer uitdaging biedt u met de extra opdrachten. In de handleiding vindt u ook de leerdoelen van elk boek en uitleg over de belangrijkste programmeerconcepten die aan bod komen. Tip: vraag de kinderen u uit te leggen waarmee ze bezig zijn - daar leren ze veel van! En probeer vooral zelf ook eens te programmeren! Technische beschrijvingen In de technische beschrijvingen vindt u uitleg over de vijf gebruikte programmeertalen: Logo, Scratch, Python, HTML en JavaScript. Met deze informatie kunt u bijvoorbeeld storingen en problemen oplossen. Naast de technische beschrijvingen vindt u een vergelijking van de programmeertalen. Achter in de handleiding staan suggesties om met kinderen 'veiligheid op internet' te bespreken, en verwijzingen naar websites met lesmateriaal.

Programmeren --- Programmeren ; kinderen.

Choose an application

• Reference Manager
• EndNote
• RefWorks (Direct export to RefWorks)

Programmeren --- Internet

Choose an application

• Reference Manager
• EndNote
• RefWorks (Direct export to RefWorks)

W elcome to Beginning XSLT 2.0, a comprehensive introduction to the Extensible Stylesheet Language: Transformations 2.0. This book introduces you to transforming XML with XSLT 2.0, helping you to create tailored presentations for all the information you have accessible as XML. I wrote this book, like Beginning XSLT, based on my own experience as an XSLT user, but also based on my familiarity, from training people in XSLT, with the practical and conceptual hurdles that newcomers often face. My aim is to provide a step-by-step, how-to manual for the kind of the real-world transformation problems that you will come across. Who This Book Is For This book is primarily for newcomers to XML and XSLT. It's particularly aimed towards web developers who have some knowledge of HTML, CSS, and a smattering of JavaScript; but none of these are essential, and the techniques you learn in this book can just as easily be applied to transforming between XML-based markup languages as to web pages. Seasoned users of XSLT 1.0 will learn about the new datatypes, expressions, and functions of XPath 2.0 and the new facilities in XSLT that make tasks such as text processing, grouping, and creating multiple documents much easier. Although much will look familiar, there are also some fundamental changes in the XPath data model and the XSLT processing model that may take you by surprise.

Programming --- programmeren (informatica)

Choose an application

• Reference Manager
• EndNote
• RefWorks (Direct export to RefWorks)

It's hard to believe now, but there was a time when writing jokes about multi-dispatch inheritance in dynamically typed languages simply wasn't the glamorous, highly paid profession that it is today. Before Slashdot, before User Friendly and the Joy of Tech, before Futurama, before Old Man Murray, before Dilbert, and before 1001 Surefire Gags about C++ That Will Wow Your Klingon Wedding Guests,  funny for geeks was a criminally underserved market sector. Biro-drawn cartoon strips were the typical fare, all called something like Just Byting Around! or Giga-giggles! These would run for a few months in Practical Computing or PC Handholder or some such ma- zine. After recycling gags revolving around hard drives and floppy disk entendres, these wretched specimens died for lack of inspiration and, I would hope, some vestigial sense of shame. And then there was, thank God, Verity Stob. I remember the first time I read the Stob column. It was 1988, and I was hiding in a fluorescent-lit dungeon in the heart of my university, strumming futilely through the lower-rent academic journals and controlled-circulation tech mags. The first few lines some throwaway comment about Lisp, I think had my snorts echoing across the library.

Programming --- programmeren (informatica)

Choose an application

• Reference Manager
• EndNote
• RefWorks (Direct export to RefWorks)

Rigor Without the Mortis Many people (especially agilists) associate a high-ceremony software development process with a dead project (i.e., rigor mortis), and this association is not entirely incorrect. Our approach aims to put back the rigor while le- ing out the mortis that is, we can do rigorous analysis and design without killing the project with an excessively high-ceremony approach. The goal of this book is to describe that process in full detail. Agility in theory is about moving ahead at speed, making lots of tiny course corrections as you go. The theory (and it's a good one) is that if you spend months or years producing dry specifications at the start of the project and then set them in concrete,  this doesn't necessarily (and in practice, doesn't) lead to a product that meets the c- tomer's requirements, delivered on time and with an acceptably low defect count. It's likely that the requirements will change over time, so we need to be prepared for that, and it's likely that a lot of the original requirements will turn out to be wrong or new requirements will be discovered after the requi- ments concrete  has set. Agile methods answer this problem in a number of different ways, but the overriding principle is to break things down into smaller chunks and not to go setting anything in concrete (least of all your requirements specs).

Programming --- Agile --- programmeren (informatica)