get stuck, their musings may be overheard by someone else in the work area who can contribute...

Odnośniki

Smutek to uczucie, jak gdyby się tonęło, jak gdyby grzebano cię w ziemi.
The smallest oceansStiII get big, big waves...
After you build the system and get it running, it’s important to do a reality check, and here’s where the requirements analysis and system specification comes in...
string ob_get_length ( void) ob_implicit_flush Włącza lub wyłącza ukryte opróżnianie bufora wyjściowego (jeżeli nie podany został znacznik...
We have seen that chloramphenicol is a drug which can have dangerous side-effects and which should only be used for a narrow range of life-threatening diseases, most...
Every programming language enables some method for declaring local (or global) variables that can be used to store data...
You can create delegates for each operation and add them to an ordered collection, such as an array, in the order you'd like them to execute...
WITH SUFFICIENT NOTICE THEY CAN BE MADE AVAILABLE IN DRUMSFROM LOS ANGELES...
such as views, procedures, and synonyms, can provide location transparency...
philosophy-russell, bertrand, why i am a rationalist women may be allowed to think, the young, at any rate, ought to believe a whole lot of absurdities, and that it...
"Can you take her away?" I whispered to Mark...

Smutek to uczucie, jak gdyby się tonęło, jak gdyby grzebano cię w ziemi.

Working in pairs keeps things flowing and on
track. Probably more important, it makes programming a lot more social
and fun. Feedback
I’ve begun using pair programming during the exercise periods in some of
my seminars and it seems to significantly improve everyone’s experience.
Feedback
Strategies for transition
If you buy into OOP, your next question is probably, “How can I get my
manager/colleagues/department/peers to start using objects?” Think
about how you—one independent programmer—would go about learning
to use a new language and a new programming paradigm. You’ve done it
before. First comes education and examples; then comes a trial project to
give you a feel for the basics without doing anything too confusing. Then
comes a “real world” project that actually does something useful.
Throughout your first projects you continue your education by reading,
asking questions of experts, and trading hints with friends. This is the
approach many experienced programmers suggest for the switch to Java.
Switching an entire company will of course introduce certain group
dynamics, but it will help at each step to remember how one person would
do it. Feedback
Guidelines
Here are some guidelines to consider when making the transition to OOP
and Java: Feedback
1044
Thinking in Java
www.BruceEckel.com

1. Training
The first step is some form of education. Remember the company’s
investment in code, and try not to throw everything into disarray for six to
nine months while everyone puzzles over unfamiliar features. Pick a small
group for indoctrination, preferably one composed of people who are
curious, work well together, and can function as their own support
network while they’re learning Java. Feedback
An alternative approach is the education of all company levels at once,
including overview courses for strategic managers as well as design and
programming courses for project builders. This is especially good for
smaller companies making fundamental shifts in the way they do things,
or at the division level of larger companies. Because the cost is higher,
however, some may choose to start with project-level training, do a pilot
project (possibly with an outside mentor), and let the project team
become the teachers for the rest of the company. Feedback
2. Low-risk project
Try a low-risk project first and allow for mistakes. Once you’ve gained
some experience, you can either seed other projects from members of this
first team or use the team members as an OOP technical support staff.
This first project may not work right the first time, so it should not be
mission-critical for the company. It should be simple, self-contained, and
instructive; this means that it should involve creating classes that will be
meaningful to the other programmers in the company when they get their
turn to learn Java. Feedback
3. Model from success
Seek out examples of good object-oriented design before starting from
scratch. There’s a good probability that someone has solved your problem
already, and if they haven’t solved it exactly you can probably apply what
you’ve learned about abstraction to modify an existing design to fit your
needs. This is the general concept of design patterns, covered in Thinking
in Patterns with Java at www.BruceEckel.com. Feedback
Chapter 16: Analysis & Design
1045

4. Use existing class libraries
An important economic motivation for switching to OOP is the easy use of
existing code in the form of class libraries (in particular, the Standard
Java libraries, which are covered throughout this book). The shortest
application development cycle will result when you can create and use
objects from off-the-shelf libraries. However, some new programmers
don’t understand this, are unaware of existing class libraries, or, through
fascination with the language, desire to write classes that may already
exist. Your success with OOP and Java will be optimized if you make an
effort to seek out and reuse other people’s code early in the transition
process. Feedback
5. Don’t rewrite existing code in Java
It is not usually the best use of your time to take existing, functional code
and rewrite it in Java. (If you must turn it into objects, you can interface
to the C or C++ code using the Java Native Interface or XML) There are
incremental benefits, especially if the code is slated for reuse. But chances
are you aren’t going to see the dramatic increases in productivity that you
hope for in your first few projects unless that project is a new one. Java
and OOP shine best when taking a project from concept to reality. Feedback
Management obstacles
If you’re a manager, your job is to acquire resources for your team, to
overcome barriers to your team’s success, and in general to try to provide
the most productive and enjoyable environment so your team is most
likely to perform those miracles that are always being asked of you.