程序员的道路上，您迷失方向了吗？(299分)

Oracle、SQL Server
XHTML,
Java

http://www.delphibbs.com/delphibbs/dispq.asp?LID=894197
对了抱名方式表格：
（＊^_^＊）
姓名： 中文：______ 英文：_______
手机： ______________
呼机：_______________
商务通：_____________________
QQ：______________________
MAIL：__________________
随行人员：_____________
大家快点报名呀！
晚了没有的玩了！

我不想说什么。

辛苦并快乐着!

关注

改行！

哎感慨!!

[purple][/purple][]
其实呀，我看是这样。当程序员和其他的工作一样，在中国，搞钱的只有当官的，搞管理的
，贩毒的，黑社会的大哥。
一个人的收入的多少不是看他的技术怎样。一个人的收入的多少是要看社会的财富是怎样分配的。程序员，白领。。。也是在财富分配金字塔的最底层，因此
是不可能很富有。一个人要变富有，是要想办法改变自己的财富的分配层次，你要么当官，
要么做不正当的事。。。程序员是永远富裕不起来的，微软的程序员怎么样，还不是比不上一个
小小的商人。
真正的程序员是真正的知识分子，他们是追求知识中蕴藏的魅力和智慧，程序员是永远富不起来的
除非你不替别人打工

顺其自然吧，别攀比，心态平稳一些自己会绝对很幸福

没办法

我没有，因为我不是程序员。
我做程序只是为好玩，感到一点成就感而已。我受不了坐24小时的生活。

问题：.Net, Java or Delphi? ( 积分：1, 回复：14, 阅读：228 )
分类：前沿技术 ( 版主：robertcool, honghs )
来自：房客, 时间：2002-1-30 15:38:00, ID：895601 [显示：小字体 | 大字体]
.Net, Java or Delphi?
This is a response I gave to Mr. Angel Rosario, Jr. on borland.public.delphi.non-technical in regards of his concerns about the "best tool for the job".I wanted to include it in here for further reference.
"I will give you my personal point of view on the matter based on my history
and the things I have seen around me.
It is a difficult time but is possible to make technological decisions
*today*, that may turn good regardless of what is gonna happen. I made mine
and I will try to explain the whats and whys.
It's not easy to decide where to go and which boat to jump on. Neither one
of the two parties, Microsoft or Linux (let's put the others aside for a
second) are sure winners and I am not sure we should even attempt to predict
who will be the one at this point.
On this newsgroup the merits and the pitfalls of both have been discussed to
the extreme. Stability, scalability, speed, cost, etc etc etc have been the
heart of discussions for months in the non-tech.
Problem is that where the market will go is not about the most scalable or
stable system. It is about the perception the community has about that and
the services that it offers. The one that will do
minate in this two matters,
will probably be the real winner but this won't mean the other will
disappear.
The first concept (perception) is the heart of publicity and propaganda and
is the most important.
The second (services) backs the first up but is not a lead factor.
Consider what happened around us in our field in the past few years, and
then
look at history.
Windows 95 has taken the desktop, Office has become the fact the business
application suite everybody uses and finally Internet Explorer has won the
browser war with the 85% of installed and used browsers.
Has those products been an example of quality? I wouldn't say so, definitely
at the begin
ning. But even if they weren't, they had something to offer and
for sure they are not as bad as today's arguments make them appear. At least
they delivered a service and in order to do
that, they took advantage of a
favorable perception that Microsoft generated around them.
There are many reasons behind what happened but the do
minant is the
perception users have. AOL has become what it is for the same reasons.
Napster is not a real piece of art either but still, through perception and
services has became so strong to deserve to be world wide news when things
started to go bad.
History is made by 2000 years of examples of this pattern that drove masses
to any kind of things, good and bad.
This really took more lines than what I was originally thinking and I
probably have gone tangents...
Why I said what I said? Because at the end, no tool is gonna be so unique
and revolutionary to be the one and only one. Is not like the movie
Highlander. At the end, there will be more than one <G>
You mentioned Design Patterns and UML... That made me smile, because the
selling reasons behind VB, .Net and Delphi are everything but things like
that. The promise is about a RAD tool trough which you can develop your
applications in less than 15 minutes, not a tool that allows you to apply
design patterns, object oriented architectures and things like that. Is all
about the perception of faster time to market, which is wrongfully
associated with OnClicks.
Now, having RAD environments is a great thing. No questions about it. The
problem is that this allowed the spread of all kind of bad results around
us. This is not Delphi's fault but the user's. In the case of VB is a little
different but still the concept applies to some degree. Many people wouldn't
have that much of a problem moving their code if they would have followed
the rules.
A few months ago we had to decide if we wanted to use Delphi or Visual Basic
for our development. The main reason behind this question was that since we
are almost 90% Microsoft based, then
why shouldn't we go all the way? Well,
I tell you what: at the time .Net was one of the decisional points of
sticking to Delphi.
VB changed a lot in version 7. The kind of changes that have been made are
more important than abandoning a set of components or introducing new ones.
The changes affected the language in itself: things that are today present
in every OO language such as real inheritance and OO capabilities, were not
present in VB6 and would have led to a corrupted design. Code is easy to change,
if things are do
ne properly. Architectures are not.
In an ideal world, design would probably take 70% of the time while
implementation is just a mundane and repetitive task. Changing the second
should be easy, changing the first, most likely leads to disasters.
So we choose to Delphi because everything we do
today (architecture wise)
are portable to .Net, Java or whatever in the future, in case we need to. I
will probably embrace .Net in the future. It has a lot to offer and I can
guarantee that I'd love to do
that having Delphi as underlying language. But
this really do
esn't matter much.
Doesn't matter if it is called ADO, JDBC, ODBC or BDE... The principles
behind them are the same.
I use SOAP today. I have webservices regardless of Microsoft (although I use
their SOAP toolkit since mine is not finished yet <G>). We are developing a
system that is scalable, well designed and efficient in Delphi using
Microsoft technologies and I can assure you that the majority of the things
we are do
ing, are gonna stay the same even if we move to .Net. The
architecture is what really matters, not the tool you use to achieve the
result (take out from this VB6 and previous, PowerBuilder and a few other
languages).
Don't get fooled by perception, in either way. There's a lot of good stuff
in .Net as well in Delphi or Java and there are things that should be do
ne
better in all of them. Focus on the services they offer. See how you can
improve on what they offer if you need to. Borrow ideas from the others
because even if they are very similar, they are not the same.
Good luck"

问题：.Net, Java or Delphi? ( 积分：1, 回复：14, 阅读：228 )
分类：前沿技术 ( 版主：robertcool, honghs )
来自：房客, 时间：2002-1-30 15:38:00, ID：895601 [显示：小字体 | 大字体]
.Net, Java or Delphi?
This is a response I gave to Mr. Angel Rosario, Jr. on borland.public.delphi.non-technical in regards of his concerns about the "best tool for the job".I wanted to include it in here for further reference.
"I will give you my personal point of view on the matter based on my history
and the things I have seen around me.
It is a difficult time but is possible to make technological decisions
*today*, that may turn good regardless of what is gonna happen. I made mine
and I will try to explain the whats and whys.
It's not easy to decide where to go and which boat to jump on. Neither one
of the two parties, Microsoft or Linux (let's put the others aside for a
second) are sure winners and I am not sure we should even attempt to predict
who will be the one at this point.
On this newsgroup the merits and the pitfalls of both have been discussed to
the extreme. Stability, scalability, speed, cost, etc etc etc have been the
heart of discussions for months in the non-tech.
Problem is that where the market will go is not about the most scalable or
stable system. It is about the perception the community has about that and
the services that it offers. The one that will do
minate in this two matters,
will probably be the real winner but this won't mean the other will
disappear.
The first concept (perception) is the heart of publicity and propaganda and
is the most important.
The second (services) backs the first up but is not a lead factor.
Consider what happened around us in our field in the past few years, and
then
look at history.
Windows 95 has taken the desktop, Office has become the fact the business
application suite everybody uses and finally Internet Explorer has won the
browser war with the 85% of installed and used browsers.
Has those products been an example of quality? I wouldn't say so, definitely
at the begin
ning. But even if they weren't, they had something to offer and
for sure they are not as bad as today's arguments make them appear. At least
they delivered a service and in order to do
that, they took advantage of a
favorable perception that Microsoft generated around them.
There are many reasons behind what happened but the do
minant is the
perception users have. AOL has become what it is for the same reasons.
Napster is not a real piece of art either but still, through perception and
services has became so strong to deserve to be world wide news when things
started to go bad.
History is made by 2000 years of examples of this pattern that drove masses
to any kind of things, good and bad.
This really took more lines than what I was originally thinking and I
probably have gone tangents...
Why I said what I said? Because at the end, no tool is gonna be so unique
and revolutionary to be the one and only one. Is not like the movie
Highlander. At the end, there will be more than one <G>
You mentioned Design Patterns and UML... That made me smile, because the
selling reasons behind VB, .Net and Delphi are everything but things like
that. The promise is about a RAD tool trough which you can develop your
applications in less than 15 minutes, not a tool that allows you to apply
design patterns, object oriented architectures and things like that. Is all
about the perception of faster time to market, which is wrongfully
associated with OnClicks.
Now, having RAD environments is a great thing. No questions about it. The
problem is that this allowed the spread of all kind of bad results around
us. This is not Delphi's fault but the user's. In the case of VB is a little
different but still the concept applies to some degree. Many people wouldn't
have that much of a problem moving their code if they would have followed
the rules.
A few months ago we had to decide if we wanted to use Delphi or Visual Basic
for our development. The main reason behind this question was that since we
are almost 90% Microsoft based, then
why shouldn't we go all the way? Well,
I tell you what: at the time .Net was one of the decisional points of
sticking to Delphi.
VB changed a lot in version 7. The kind of changes that have been made are
more important than abandoning a set of components or introducing new ones.
The changes affected the language in itself: things that are today present
in every OO language such as real inheritance and OO capabilities, were not
present in VB6 and would have led to a corrupted design. Code is easy to change,
if things are do
ne properly. Architectures are not.
In an ideal world, design would probably take 70% of the time while
implementation is just a mundane and repetitive task. Changing the second
should be easy, changing the first, most likely leads to disasters.
So we choose to Delphi because everything we do
today (architecture wise)
are portable to .Net, Java or whatever in the future, in case we need to. I
will probably embrace .Net in the future. It has a lot to offer and I can
guarantee that I'd love to do
that having Delphi as underlying language. But
this really do
esn't matter much.
Doesn't matter if it is called ADO, JDBC, ODBC or BDE... The principles
behind them are the same.
I use SOAP today. I have webservices regardless of Microsoft (although I use
their SOAP toolkit since mine is not finished yet <G>). We are developing a
system that is scalable, well designed and efficient in Delphi using
Microsoft technologies and I can assure you that the majority of the things
we are do
ing, are gonna stay the same even if we move to .Net. The
architecture is what really matters, not the tool you use to achieve the
result (take out from this VB6 and previous, PowerBuilder and a few other
languages).
Don't get fooled by perception, in either way. There's a lot of good stuff
in .Net as well in Delphi or Java and there are things that should be do
ne
better in all of them. Focus on the services they offer. See how you can
improve on what they offer if you need to. Borrow ideas from the others
because even if they are very similar, they are not the same.
Good luck"
是什么意思?

不错

我的经历
http://www.8421.org/article.php?id=58

痛并快乐着

写程序只是业余，而且我只学DELPHI，其他的我都不学！我要一直跟着DELPHI走下去！我
不会写程序谋生的，呵呵，好象也没有这个能力哦，都23岁了哦！
我就喜欢DELPHI！

我做工业控制（单片机），硬件+软件一起来才能赚钱，编点好看的、花哨的程序只是业余，
管它什么新技术，新的技术名词是用来朦那些客户的，可别把自己也朦了。
我到现在用的DELPHI还是3.0的，不是一样赚钱，事实上，目前主要赚钱的设计还是用DELPHI
1.0开发的 For Windows 3.1 的机床控制程序呢。

赚几年钱就改行吧，呵呵

要想高工资就要自己当老板，你的获利是最大的，
你要想靠技术吃饭，你就要把所需的技术要精而且很通，到了你可以选择
别人而不别人选择你的时候，你就成老板了，你的工资也会高起来。
呵呵，经济和技术不是成正比的，相信吧