Functional Programming, JavaScript and UI - some neophyte questions. What should every programmer know about web development. How do you manage your javascript unit tests. Microsoft's top developers prefer old-school coding methods. News By Eric Lai November 27, 2009 06:00 AM ET Computerworld - Microsoft Corp. has done more to popularize graphical programming than any other vendor.
The company's development tools, led by Visual Basic and Visual Studio, have been used by millions of software developers over the past two decades. But during a revealing and often humorous panel discussion on the future of programming at last week's Professional Developers Conference in Los Angeles, Microsoft's own superstar developers espoused their loyalty to old-school methods of coding software.
"I will fight you if you try to take away my text editor," said Don Box, a Microsoft distinguished engineer. "Do people want to draw pictures [to program]? "Graphical programming environments are usable when they are useless, but unusable when they would be useful," said Jeffrey Snover, another Microsoft distinguished engineer and creator of Microsoft's PowerShell scripting tool for Windows. Managed code runs inside a virtual machine. Stevey's Blog Rants.
Implement a Microsoft Word-like Object Model for Your .NET Framework Application. MSDN Library Articles and Overviews .NET General Enterprise Development Technology Map Smart Client Applications Technology Map Visual Basic .NET Technology Map Visual Studio .NET Technology Map Web Applications Technology Map Abortable Thread Pool The Analytic Hierarchy Process API Test Automation in .NET Application Resiliency: Unlock the Hidden Features of Windows Installer Asynchronous HttpWebRequests, Interface Implementation, and More Auto-Generating Wrapper Classes for Stored Procedures, Part 1: Using the AutoSproc Tool. A Laboratory For Teaching Object-Oriented Thinking.
Kent Beck, Apple Computer, Inc.
Ward Cunningham, Wyatt Software Services, Inc. From the OOPSLA'89 Conference Proceedings October 1-6, 1989, New Orleans, Louisiana And the special issue of SIGPLAN Notices Volume 24, Number 10, October 1989 Contents Introduction It is difficult to introduce both novice and experienced procedural programmers to the anthropomorphic perspective necessary for object-oriented design.
Welcome to retrospectives.com. Design Patterns Library. Catalog of Patterns of Enterprise Application Architecture. Last Significant Update: January 2003 A short summary of the patterns in Patterns of Enterprise Application Architecture (P of EAA). Links to Software Architecture Sites. How to Prove It. List of important publications in computer science.
This is a list of important publications in computer science, organized by field.
Some reasons why a particular publication might be regarded as important: Topic creator – A publication that created a new topicBreakthrough – A publication that changed scientific knowledge significantlyInfluence – A publication which has significantly influenced the world or has had a massive impact on the teaching of computer science. Artificial intelligence[edit] Computing Machinery and Intelligence[edit] The Humble Programmer. You ain't gonna need it. "You aren't gonna need it"[1][2] (acronym: YAGNI)[3] is a principle of extreme programming (XP) that states a programmer should not add functionality until deemed necessary.[4] Ron Jeffries writes, "Always implement things when you actually need them, never when you just foresee that you need them.
"[5] The phrase also appears altered as, "You aren't going to need it"[6][7] or sometimes phrased as, "You ain't gonna need it". YAGNI is a principle behind the XP practice of "do the simplest thing that could possibly work" (DTSTTCPW).[2][3] It is meant to be used in combination with several other practices, such as continuous refactoring, continuous automated unit testing and continuous integration.
Used without continuous refactoring, it could lead to messy code and massive rework. Continuous refactoring in turn relies on automated unit tests and/or static analysis tools as a safety net and continuous integration to prevent wider integration problems. Rationale[edit] Book Reviews. By Joel Spolsky Wednesday, March 13, 2002 “Pretty close to the perfect short list for any programmer” — Jan Derk You can learn a lot about somebody by the books they've read.
And I've always thought that if you read all the same books I read, you'll come to think like me, too. The Programmer Dress Code. The second part of this post is up, so after you finish reading, check it out! I really want to know what it is about programming, or computers in general, that makes people want to grow a beard, have long hair, and dress like a slob. C.R.A.P.:The Four Principles of Sound Design. By Daniel Scocco This is a guest blog by Jacob Cass.
Be sure to check out his $5000 prize giveaway. As a graphic designer, I could tell you if your website design is C.R.A.P. Not crap as in crap crap, but I mean C.R.A.P as in the underlying principles of good design. Pablo's Topic of the Month - March: SOLID Principles - Chad Myers' Blog - Los Techies : Blogs about software and anything tech! Over the next few days and weeks, the Los Techies crew will be writing a number of blog posts focused a particular subject in addition to their regular blogging.
Pablo’s Topic of the Month for the month of March is Bob Martin’s S.O.L.I.D. design principles. We’ll try to cover all of them by the end of the month or we might focus in on a few of them and go really deep. Please stay tuned and please give us some feedback of how you like this format because we’re considering doing it in upcoming months. If you haven’t already, please consider subscribing to the Los Techies Main Feed so that you can see the various post from the other Los Techies bloggers.
ArticleS.UncleBob.PrinciplesOfOod. The Principles of OOD What is object oriented design?
Project Euler. Programming Competition, Online Computer Programming, Programming Contest. Gild - Global Tech Elite: Career and Job Advancement for Technologists.