|
|
 |
|
Information Regarding Programmers In Web Development Forums on Software Development Register |
| News And Tips, Drivers, Desktop Wallpapers, Links To Updates, Software Utilities. In 1995 There Were Fewer Than 1,000 Web Development Companies In The United States Alone, But By 2005 There Were Over 30,000 Such Companies. |
|
For you information -
If you own a website that related to programmers you are welcome to participate in our website.
Contact us to be participate in the project and join our partner list: Web Development Wiki, Web Development Online Portal, Web Development Central, etc.
|
 |
| Website about Software Developers - online portal of Internet Technology Architecture and Development. Other useful information:
hanging out with other programmers. But by "effective", I mean the
programmers need to realize bug reports are a good thing, if they
time for all the other programmers, and this programmer was able to
Keeping your code out of the official build means that programmers
Many Windows programmers wonder why grumpy old Unix/Mac/Amiga/Lisp
programmers rail against Win32/MFC/.NET, but if all the API's you've
it said that good object-oriented programmers, in particular, are born
"Refactoring" is all the rage, now, but programmers often take it to
And then there are programmers who are unable to come up with time
Sometimes programmers are reluctant to commit to a schedule because
And if anything differentiates programmers who can just put together
J2EE: EJB, JSP, Servlets, JSF, JSTL, JCA, JMS, JTA, JNDI, JDBC, JMX, RMI, etc.
Frameworks: Struts, Hibernate, JPA, iBATIS, JBoss AOP, Spring, JSF, AJAX, GWT, YUI, Flex/Flash, JUnit, and Jakarta common libraries.
Integration: Web Services on Axis and WebMethods; as well as the Web Service Standards such as SOAP, WSDL and UDDI.
| |
Seven Habits Of Highly Effective Programmers
- hanging out with other programmers. But by "effective", I mean the
/* */
@import "../skin/tigris.css";
@import "../skin/quirks.css";
@import "../skin/inst.css";
/* */
Seven Habits of Highly Effective Programmers
Search... The technicat site The web for
Technicat Game Developer Open Source Software Essays
Section
Software Essays
Preface
Project Design
Programming
School
Management
Driving
Chess Lessons
Meetings
Schedules
Game Dev
User Interface
Sys Admin
QA
Employment
Consulting
Startup
Agile
Lisp
Page
Publication Informa...
Understand Your Req...
Keep It Real
Understand Your Cod...
Optimal Programming...
Manage Thyself
Continuous Educatio...
R-E-S-P-E-C-T
Products
technicat
PDF
Seven Habits of Highly Effective Programmers
Publication Information
Copyright ©2004-2008 by
Philip Chu
All rights reserved.
As a software engineer, you might want any number of things out of
your job - a steady paycheck, the opportunity to work on interesting
projects, a springboard to the next better job, or maybe you just like
ability to complete projects in a timely manner with the expected
quality. After working on dozens of software releases, I believe the
following practices will bring you there, and while they may involve
sticking your neck out, I'd like to think they will also advance your
professional reputation, career longevity, and personal satisfaction.
Understand Your Requirements
The first step in becoming an effective programmer is to ensure that
you are spending your time wisely. And there is no greater waste of
time than in working on something that is not useful or never shipped.
Build Early
Get a demonstrable system working as early as possible. This means
establishing the interface first, whether it's an API or user
interface, and stubbing the encapsulated functionality as
necessary. This allows your "customers" to check it out, by exercising
the user interface or writing code to the API, and any inconsistencies
or omissions in the initial spec can be detected early. Chances are,
you will notice problems or potential improvements even before
releasing this first deliverable.
There is a classical school of thought that believes if you design
everything up front, then all you have to do is write the code and
you're done. That works great if you've done the exact same project
before. Otherwise, it's more likely you'll run into a point where
you're just guessing or operating on questionable assumptions.
Upon joining an early-stage wireless internet startup, I found myself in
two months of design meetings for a wireless portal and gateway
due to launch in six months. Eventually we got tired of meeting and
finally started coding. Within two weeks, my part of the project had
no resemblance to the original design, and the first wireless
connection test two months later revealed a fundamental
misunderstanding of the wireless protocol.
This is not to say that design is unnecessary. But after a certain
|
|
| |
|
