Skip to content
Free planNo credit card requiredStart writing
AI for Research home
AI for Research home
Dashboard
Sign inGet started

Search 250 million research papers

Read the abstract, see who wrote it and who cites it, and get the citation in APA, MLA, Chicago or Harvard.

About 10,000 papers for “Programmer”

Programmer

Bulletin of Miscellaneous Information (Royal Gardens Kew)

Cited by 0

Programmer

Bulletin of Miscellaneous Information (Royal Gardens Kew)

Cited by 0

Dari Programmer untuk Programmer Visual Basic

Marlon Leong · 2006

Buku ini memperkenalkan dasar-dasar pemrograman visual basic secara komprenhensif, baik dengan visual basic 6 maupun visual basic.NET, termasuk didalamnya visual basic. NET 2002 dan visual basic.NET 2003. Semua disajikan dalam bentuk kode program yang lengkap dan bervaiasi, dari tingkat dasar sampai tingkat lanjut.

Cited by 2

Programmer productivity

Mehdi Jazayeri · 1977

As a solution to the problem of program maintenance, it is proposed to maintain a program in several versions. Relevant areas of current research are discussed.

Cited by 28Open access

Écrire/programmer

Bardiot, Clarisse · SPIRE - Sciences Po Institutional REpository · 2006

Cited by 0

FPGA programmer

Jan Sedlář · Digital Repository (National Repository of Grey Literature) · 2016

The work deals with the analysis of the realization of FPGA programmers. Its aim is to create a functional programmer. The proposal aims to minimize the components, their cost and area. The programmer should support chips from manufacturers Altera, Lattice and Xilinx. The programmer should enable support functions such as data transfer, virtual switches and the programming button.

Cited by 0

Programmer Worlds

Bialski, Paula · Alexandria (UniSG) (University of St.Gallen) · 2018

Cited by 0

Novice Programmer.

Wayne D. Gray, Neal C. Goldberg, Santa A. Byrnes · 2007

this paper. Teaching children thinking is inspiring and motivating. A lot of the points which Papert made here in 1972 are still being asserted under the banner of the educational restructuring movement (Collins, 1992). Papert is best when railing against the passive view of the child as subject (why?) or a means to mastering metacognitive skills? [Review of the book Studying the recipient of knowledge (the empty vessel view) versus the child as an active learning agent (the constructivist or learning by doing view). He also makes some nice points (likewise embraced by the restructuring movement) against the short term "problem" focus of many classroom activities in favor of "projects" that extend for days, weeks, or months and in which the student can become actively committed. (For a modern update on the success of such approaches see Collins, Hawkins, & Carver, 1991.) Learning-by-doing per se is no longer controversial. Anzai and Simon (1979) showed conclusively that people can learn problem solving strategies by doing. But while learning by doing has been vindicated, Papert's "how" and "what" have not. Papert's "how" or "what children should do to learn" is very close to undirected discovery learning while his "what" or "what they are learning" is general thinking or problem solving skills. As mentioned above, this division lacks a section on "teaching programming to encourage transfer" or "how to learn by doing." This omission is a pity as by the mid-80's there were papers that suggested that very directed forms of learning-by-doing produced spectacular results (see for example, Anderson, Boyle, & Reiser, 1985 or Carver & Risinger, 1987). In contrast, the "what they are learning" part of Papert's assertions is discussed by the four papers in the section on Transfe...

Cited by 0

Écrire/Programmer

Bardiot, Clarisse · HAL (Le Centre pour la Communication Scientifique Directe) · 2007

Cited by 0

Écrire/programmer

Clarisse Bardiot · SPIRE - Sciences Po Institutional REpository · 2006

Cited by 0

Research Programmer

Supervisor Dr. Rachel Pottinger, Google Inc, Host Carl Hamilton et al. · 2007

Software Engineer • Designed and implemented visual tool for locality based summarization and comparison of large geographic data sets. Google Inc.

Cited by 0

Programmer l’interface

Jean-Paul Fourmentraux · Questions de communication · 2005

L’interface informatique joue un rôle clé dans le contexte de la création numérique pour l’internet du fait du dialogue qu’elle installe entre l’œuvre d’art, l’artiste et un public dont on attend qu’il participe activement au procès créatif. En effet, celle-ci doit constituer la médiation par laquelle transiteront les diverses traductions du projet artistique, ajustées aux contraintes techniques et dirigées vers l’action du public. De ce fait, il est fréquent de réduire l’œuvre d’art interactive à son interface, ou de décrire le résultat de la créativité avec les nouvelles technologies de l’information et de la communication (NTIC) comme un art de l’interface. Pourtant, cette dernière semble paradoxalement prise dans une tension irréductible entre les différentes polarités des programmes, actions et réactions, qu’elle est censée afficher et traduire pour l’utilisateur. On propose donc une première mise en perspective des ressorts et tensions du fragile équilibre sur lequel repose la conception et l’usage des œuvres d’art numériques interactives. On s’attache aux aspects concrets de ce travail de l’interface en offrant d’en éclairer les modalités d’action artistique.

Cited by 4Open access

FPGA programmer

Sedlář, Jan · Brno University of Technology Digital Library (Brno University of Technology) · 2016

Práce se zabývá rozborem realizace FPGA programátorů. Jejím cílem je vytvořit funkční programátor. Návrh je zaměřen na minimalizaci součástek, jejich ceny a plochy. Programátor by měl podporovat obvody od výrobců Altera, Lattice a Xilinx. Programátor by měl umožňovat podpůrné funkce jako například přenos dat, virtuální přepínače a programovací tlačítko.

Cited by 0

The Programmer

Joseph S. Fulda · ACM SIGCAS Computers and Society · 1997

No abstract available.

Cited by 1Open access

Programmer Anarchy

George, Fred · TIB KMO / FLOWWORKS GmbH · 2012

The Agile movement shifted the relationship between clients and developers in a profound way. In waterfall processes, clients specified large amounts of functionality, then nervously faded into the background until the fateful day-of-delivery. With Agile, developers strove to engage with clients continuously, and delivered much more frequently against their needs. A new trust was established. At the Forward Internet Group in London, we are implementing a second major shift between clients and developers. The trust of the clients in developers evolves into a broader trust of the developers to deliver business value without resorting to a series of well-defined stories. In essence, the business has empowered the developers to do what they think is right for the business. This model, popularized by Facebook, has several labels, but the one we prefer for our flavor is Programmer Anarchy. We will start with stock Agile, and begin to apply environmental factors that led us to drop “standard” Agile practices. We will also watch as well-defined Agile roles evaporate completely as other environmental factors are applied. Finally, we will arrive at Programmer Anarchy, an organization often following none of the standard Agile practices, having no BA or QA roles, and even missing any managers of programmers. We will summarize our environmental factors, and postulate on the required and optional factors. We will make bold, controversial assertions. We will back up these assertions with actual experiences. Programmer Anarchy has garnered rave reviews at every conference venue, and is provoking the intended debate on our current Agile thinking. Target Audience Agile-Lean practitioners who are feeling the "warts" in their implementations; programmers and project managers.

Cited by 0Open access

Practical programmer

Marc Rettig · Communications of the ACM · 1991

How one team made software testing an integral part of the development process.

Cited by 13Open access