I would rather start out with sequence diagrams myself.
These are the ones, in my mind, that are the closest to actual OO code.
I believe the class definitions a lot more after they have made it through some sequence diagrams without missing methods/Operations.
Software Development Life Cycle would support starting with use cases. This is based on the
idea that requirements analysis should precede design.
I have not yet had the experience of working with business analysts that knew how to do use case analysis.
Maybe that would change my mind.
But as an experienced programmer, I mostly like
UML as a tool to help me think through and
capture my design.
Are you talking about the Sun JNDI browser.
I ran this recently and it has an LDAP through JNDI browsing capability.
I remember being able to search through global groups, for example, and other lists.
I had to download the JNDI 1.2.1 stuff, and all the various JNDI plugins (including the LDAP one).
I suspect it was not designed as a sysadmin tool, but one could be written with the JNDI API.
I have been working in IT for 20 years and have rarely had to work 60 hours.
If someone have IT skills and their employer mandates 60 hours, look for another job.
I suspect some people stay for the inflated sense of self importance.
"This place would fall apart without me."
You have to realize you are making choice.
To those that are working 60+ hours: find some other way to feel good about yourself and get a life.
So if you repeat the name 3 times, and you have an update screen for individual records, what do you do?
1) find all the other records with the same name and change them as well.
2) change only the name that was selected
3) offer the user of changing the name for the one record or all of them.
So let's say you let the user change on of three Bill Smith entries to William Smith, then you have
the problem of trying to recall all the records for that person.
Do you query for first name = 'Bill' or first name = 'William' ?
If you use normal form, you avoid all these problems.
I just love people who denormalize tables early in a project over concerns about performance.
They don't consider the costs of having to fiddle
with all the data problems that result.
An engineer's opinions about perforamnce may have been formed back when we were all useing 80286 chips and 8 bit disk controllers.
I would like to encourage people to at least try
a normalized database.
Get a competent DBA to help you with indexes to make sure your queries run fast.
Try different things and measure them.
You would be amazed what a DBMS can do with your joined tables
on a well tuned database on good modern hardware.
That's odd. I have used STL with threads under MSVC 6.0.
I didn't have any problems. I did use Windows critical sections for methods of my classes
that added or removed things from collections.
The critical sections were declared as data members of the class, not at global scope.
One of the patches on the dinkumware site fixes a bug that affects the map class when you use it
in a dll.
We applied that fix and it took care of that problem.
So when we were done, it worked great.
Perhaps we were already at service pack 6.
One caveat with STL is this. If you start with
the GNU C++ compiler, then it is possible to
write STL code without specifying namespaces.
This non-standard code, which compiles on g++,
will not compile on MSVC 6.0.
It did compile on MSVC 4.2 though.
So I turned off the scripting settings in IE 5.0.
And I did a reload.
And I can read the bulletin just fine.
It just doesn't display the table of contents.
So slashdot is not your best source of technical information for Microsoft products. (Duh!)
I got my degree in Physics. I have been making a living in programming ever since.
A degree in a field un-related to the job you are applying for is still worth more than no degree.
Although there are a lot of very bright and capable people without degrees, there are also
a lot of places that will either not hire them
or will take unfair advantage of them.
Once you have the degree, you can persue work in Computer Science, persue work in some other area,
or persue another degree.
So you don't think that the ability of the post office to deliver your bills and payments
helps the economy?
The private sector is not even interested in carrying letters.
Even if you do your ordering and bill payment online,
the highways and roads that the government
builds and maintains help companies deliver
the goods you ordered.
And if you think that the private sector is usually better, cheaper, faster, then you have not worked
for a large corporation.
How many industries would not even exist if there was no public investment in infrastructure.
That goes for roads and for the Internet as well.
I think the poster is responding to an attitude I picked up some years ago at the first Linux conference I went to.
That is that in the Linux community there is a large anti-OO, anti-C++, anti-Java sentiment.
I went to a talk on the subject of CASE tools and was suprised to find a discussion of
Linux/Free Software Package manipulation tools.
When I and one other participant asked about something akin to Rational Rose available for Linux.
Instead of saying "No there isn't", we heard why you shouldn't want to have something like Rational Rose.
The speakers stated that OO was a proven failure.
This comes as a suprise to many professional developers that have been succeding with OO for years.
The question is not whether or not OO is better.
The question is why does the Linux community keep telling people
that they shouldn't want GUIs, they shouldn't want GUI based Integrated Development Envrionments,
and why they shouldn't want UML design tools
on Linux.
It apparently easier to say you shouldn't want these things than it is to admit that those tools
aren't there yet.
It is easier to say Object Oriented languages are bad than for some to admit that they haven't had time to learn how to do OO programming.
Because they wrote it. They hold the copyright.
They can release it under a different license.
They just can't remove your ability to modify the any of the GPL released versions.
I beg to differ about OO being only usefull for GUI programming.
At my last job, we impelemnted a factory automation system with a fairly large inheritance hierarchy.
The main areas of the heirarchy were business classes (thinks like equipment, lots), process classes and message classes.
The project was successful and ran in 4 plants in four seperate countries.
The classes were all implemented in Delphi/Object Pascal. Everything was designed with UML in Rational Rose.
So I would have to agree with you that Delphi is a great tool.
OO is also a great tool, but you may have a hard time finding someone that knows how to apply it correctly -- especially in the Linux/Unix world.
So take your own time to learn marketable skills in an area unrelated to your current job.
There is no point in picking up skills related to your job, since they have told you "hands off".
When you feel comfortable with your new skills, go off and start contracting.
You may be able to find a job with overlap between what you are doing currently and your
newly developed skills.
Maybe you should be working for a company like the one your employer hired to do the "meaty" work.
You cannot always expect your employer to develop your career.
Check out their public filings for yourself. I would be suprised if they were making a profit on
selling hardware.
Re:Difference between "adjusted" and "reported"?
on
Red Hat In The Black
·
· Score: 1
Sooner or later, RedHat will be making a profit un-ambiguously.
When that happens, a lot of people will be disappointed.
Some of them are Pro-Microsoft people.
Some of them are folks in the Linux communitity who hate to see someone else succeed in business or hate to see
a Linux distribution other than their favourite succeed.
They will succeed with or without YOUR faith.
Don't worry, you'll get over it.
The advantage of using the threads, though, is that you don't arbitrarily couple the code for all the
thinkgs that you are select()ing or WaitingForMultipleObjects() on.
Each thread can be a reusable class that doesn't depend on what other things you are waiting for.
I know on Windows, with Visual C++, debugging multiple threads in the IDE is a piece of cake.
Maybe it is harder with the command line based tools in Unix/Linux.
Also, Microsoft provides thread safe versions of the runtime library.
But if you are writing portable code, then you don't know if you can depend on the runtime library or not.
You could always synchronize the calls in your application code.
Then you are not dependent on the thread safety of the runtime library.
DEC put many man years into optimizing the VAX FORTRAN compiler.
How optimized their compiler was determined whether
or not people bought their hardware.
Slashdot Mirror
I would rather start out with sequence diagrams myself.
These are the ones, in my mind, that are the closest to actual OO code.
I believe the class definitions a lot more after they have made it through some sequence diagrams without missing methods/Operations.
Software Development Life Cycle would support starting with use cases. This is based on the
idea that requirements analysis should precede design.
I have not yet had the experience of working with business analysts that knew how to do use case analysis.
Maybe that would change my mind.
But as an experienced programmer, I mostly like
UML as a tool to help me think through and
capture my design.
YMMV.
Are you talking about the Sun JNDI browser.
I ran this recently and it has an LDAP through JNDI browsing capability.
I remember being able to search through global groups, for example, and other lists.
I had to download the JNDI 1.2.1 stuff, and all the various JNDI plugins (including the LDAP one).
I suspect it was not designed as a sysadmin tool, but one could be written with the JNDI API.
To quote the web site:
Achtung is a presentation program which is still in early stages of its development.
So come back in a couple of years. Unless, of course, you feel like writing a lot of code for free.
I prefer setjmp(3C) and longjmp(3C).
Besides goto home; sounds a lot like "go home".
I would have to agree with this poster.
I have been working in IT for 20 years and have rarely had to work 60 hours.
If someone have IT skills and their employer mandates 60 hours, look for another job.
I suspect some people stay for the inflated sense of self importance.
"This place would fall apart without me."
You have to realize you are making choice.
To those that are working 60+ hours: find some other way to feel good about yourself and get a life.
What about updates?
So if you repeat the name 3 times, and you have an update screen for individual records, what do you do?
1) find all the other records with the same name and change them as well.
2) change only the name that was selected
3) offer the user of changing the name for the one record or all of them.
So let's say you let the user change on of three Bill Smith entries to William Smith, then you have
the problem of trying to recall all the records for that person.
Do you query for first name = 'Bill' or first name = 'William' ?
If you use normal form, you avoid all these problems.
I just love people who denormalize tables early in a project over concerns about performance.
They don't consider the costs of having to fiddle
with all the data problems that result.
An engineer's opinions about perforamnce may have been formed back when we were all useing 80286 chips and 8 bit disk controllers.
I would like to encourage people to at least try
a normalized database.
Get a competent DBA to help you with indexes to make sure your queries run fast.
Try different things and measure them.
You would be amazed what a DBMS can do with your joined tables
on a well tuned database on good modern hardware.
That's odd. I have used STL with threads under MSVC 6.0.
I didn't have any problems. I did use Windows critical sections for methods of my classes
that added or removed things from collections.
The critical sections were declared as data members of the class, not at global scope.
One of the patches on the dinkumware site fixes a bug that affects the map class when you use it
in a dll.
We applied that fix and it took care of that problem.
So when we were done, it worked great.
Perhaps we were already at service pack 6.
One caveat with STL is this. If you start with
the GNU C++ compiler, then it is possible to
write STL code without specifying namespaces.
This non-standard code, which compiles on g++,
will not compile on MSVC 6.0.
It did compile on MSVC 4.2 though.
So I turned off the scripting settings in IE 5.0.
And I did a reload.
And I can read the bulletin just fine.
It just doesn't display the table of contents.
So slashdot is not your best source of technical information for Microsoft products. (Duh!)
I got my degree in Physics. I have been making a living in programming ever since.
A degree in a field un-related to the job you are applying for is still worth more than no degree.
Although there are a lot of very bright and capable people without degrees, there are also
a lot of places that will either not hire them
or will take unfair advantage of them.
Once you have the degree, you can persue work in Computer Science, persue work in some other area,
or persue another degree.
So you don't think that the ability of the post office to deliver your bills and payments
helps the economy?
The private sector is not even interested in carrying letters.
Even if you do your ordering and bill payment online,
the highways and roads that the government
builds and maintains help companies deliver
the goods you ordered.
And if you think that the private sector is usually better, cheaper, faster, then you have not worked
for a large corporation.
How many industries would not even exist if there was no public investment in infrastructure.
That goes for roads and for the Internet as well.
Someone passed this amusing satire of HP.
http://www.satirewire.com/news/0105/loyal.shtml
If a company has not implemented an Internet security program, what makes you think they can implement
a migration from IIS to Apache?
I think the poster is responding to an attitude I picked up some years ago at the first Linux conference I went to.
That is that in the Linux community there is a large anti-OO, anti-C++, anti-Java sentiment.
I went to a talk on the subject of CASE tools and was suprised to find a discussion of
Linux/Free Software Package manipulation tools.
When I and one other participant asked about something akin to Rational Rose available for Linux.
Instead of saying "No there isn't", we heard why you shouldn't want to have something like Rational Rose.
The speakers stated that OO was a proven failure.
This comes as a suprise to many professional developers that have been succeding with OO for years.
The question is not whether or not OO is better.
The question is why does the Linux community keep telling people
that they shouldn't want GUIs, they shouldn't want GUI based Integrated Development Envrionments,
and why they shouldn't want UML design tools
on Linux.
It apparently easier to say you shouldn't want these things than it is to admit that those tools
aren't there yet.
It is easier to say Object Oriented languages are bad than for some to admit that they haven't had time to learn how to do OO programming.
It sounds like you need a new vendor.
They have more or less told you they can't be bothered with your hardware combination.
You can't force them to behave they way they want you to.
You can only change what you do.
If your boss won't switch vendors, you still can only change what you do, not what your boss does.
It is easy to compare some new technology (eBooks) to an old technology that is still around (trains).
But what about all the old technologies that failed.
Like the machines that used to measure your shoe size using x-rays?
Not all technology has staying power.
Because they wrote it. They hold the copyright.
They can release it under a different license.
They just can't remove your ability to modify the any of the GPL released versions.
The same thing has been done with Tripwire.
Thats funny, I never shut down that way.
I just hit ctrl-alt-del then press the shutdown button.
Of course, the target market for GNOME will also have the same problem -- pre-conceived notioins of how the interface should work.
We heard about it last month and patched our servers within a few days.
Last time I checked, we were still up.
I beg to differ about OO being only usefull for GUI programming.
At my last job, we impelemnted a factory automation system with a fairly large inheritance hierarchy.
The main areas of the heirarchy were business classes (thinks like equipment, lots), process classes and message classes.
The project was successful and ran in 4 plants in four seperate countries.
The classes were all implemented in Delphi/Object Pascal. Everything was designed with UML in Rational Rose.
So I would have to agree with you that Delphi is a great tool.
OO is also a great tool, but you may have a hard time finding someone that knows how to apply it correctly -- especially in the Linux/Unix world.
So take your own time to learn marketable skills in an area unrelated to your current job.
There is no point in picking up skills related to your job, since they have told you "hands off".
When you feel comfortable with your new skills, go off and start contracting.
You may be able to find a job with overlap between what you are doing currently and your
newly developed skills.
Maybe you should be working for a company like the one your employer hired to do the "meaty" work.
You cannot always expect your employer to develop your career.
Subject says it all.
Check out their public filings for yourself. I would be suprised if they were making a profit on
selling hardware.
Sooner or later, RedHat will be making a profit un-ambiguously.
When that happens, a lot of people will be disappointed.
Some of them are Pro-Microsoft people.
Some of them are folks in the Linux communitity who hate to see someone else succeed in business or hate to see
a Linux distribution other than their favourite succeed.
They will succeed with or without YOUR faith.
Don't worry, you'll get over it.
The advantage of using the threads, though, is that you don't arbitrarily couple the code for all the
thinkgs that you are select()ing or WaitingForMultipleObjects() on.
Each thread can be a reusable class that doesn't depend on what other things you are waiting for.
I know on Windows, with Visual C++, debugging multiple threads in the IDE is a piece of cake.
Maybe it is harder with the command line based tools in Unix/Linux.
Also, Microsoft provides thread safe versions of the runtime library.
But if you are writing portable code, then you don't know if you can depend on the runtime library or not.
You could always synchronize the calls in your application code.
Then you are not dependent on the thread safety of the runtime library.
Or the FORTRAN compiler was really optimized.
DEC put many man years into optimizing the VAX FORTRAN compiler.
How optimized their compiler was determined whether
or not people bought their hardware.