In my experience, the best option by far is to put your SQL in procedures. Besides being more efficient, it gives your dba a chance to check out your queries and alter them easily. This is very important when you have a large team with varying degrees of ability (and probably none of them knows as much about the database as the dba does).
A bit offtopic, but I find it amusing how Brazil's banking system is so much more advanced than the US's. In Brazil all banks are interconnected electronically and checks are cleared in a day (for those few who still use them!).
People who fall for these scams are not only dumb, they are also greedy. The best scams are the ones that make people feel like they have the upper hand. So I don't think that these people are entirely without fault. After all, they did agree to play part in a crime.
Two very simple ways of bypassing Brazil's import tariffs are to declare only the price of the media ($1 a CD) or to declare the package as containing books, if you are shipping manuals too. Books are exempt from all taxes and tariffs even if they have 'complimentary' CDs.
HR is in a worse situation than IT. I have met exactly one HR professional whom I consider serious. The rest have no clue about how to select and keep good professionals.
If you have some many cores and unless they are purely crunching numbers (even then they'll have to spit something out some time), isn't access to RAM going to limit the throughput of your system?
You can make good money if you specialize in a tool like BizTalk or Commerce Server. You'd have to code a bit, mas you'd probably spend more time with consulting: helping people set up their environment, teaching the basics, and helping with optimizations.
Iterative development does not exclude deadlines. The main ideia is that you have to constantly review your plans, adjust to new information, and incrementally build your understanding of the product as well as the product per se. Of course some managers prefer to just lay the plan down and shout at you until you make it happen: it is easier for them not to have to think and replan all the way. I like to emphasize the point that your understanding of the problem at hand evolves along with the project. Building software is a creative process all the way, so it makes no sense to make all your plans upfront. Nobody tells an architect when to have the design for the doors, and then when to have the designs for the windows, then the bathroom, etc, etc.
If your knowledge is incipient and your tool provides an inadequate abstraction, you will veer towards bad habits. If you're good at OO, you can do it even in Perl. But if you're not, you will probably get some nasty habits.
In some countries you have to submit a project in order to enroll into a doctorate programme, in others you become part of an ongoing project and your work will be a spinoff from that. Either way, I can't see how you are already working on your PhD and still making these sorts of questions.
I think we have too many already. The real problem is either that they don't say what needs to be said because they don't want to make waves (they'll twiddle with their Project schedule and pretend that all will be alright) or that upper management simply won't take no for an answer (and will tell them to twiddle with their Project schedule to make it alright).
I agree, I just gave my overall impression. I think women are capable of writing good code and men can be good testers, but generally you can't rule out that there are differences between the genders, both in their habilities and in their interests.
I have the impression that women tend to see coding only as means, therefore they don't really put in all the care that some men do. On the other hand, they are awesome at testing, because they really look at the details.
I think this is one of the basics of constitutional law everywere. The law is bounded _mostly_ by area not citizenship. If it were simply bound to citizenship, foreigners would have either a great advantage over locals (not pay taxes, drive as fast as they want, etc.) or disadvantage (could be killed for nothing) and would keep away.
Slashdot Mirror
Every well-tempered programmer knows their C# from their Db.
If you are truly worried about your impact on the environment, use public transportation.
You really should use some XML to configure this application.
In my experience, the best option by far is to put your SQL in procedures. Besides being more efficient, it gives your dba a chance to check out your queries and alter them easily. This is very important when you have a large team with varying degrees of ability (and probably none of them knows as much about the database as the dba does).
A bit offtopic, but I find it amusing how Brazil's banking system is so much more advanced than the US's. In Brazil all banks are interconnected electronically and checks are cleared in a day (for those few who still use them!).
People who fall for these scams are not only dumb, they are also greedy. The best scams are the ones that make people feel like they have the upper hand. So I don't think that these people are entirely without fault. After all, they did agree to play part in a crime.
Hey, they should have weight categories for dance, as well, so we could have medals for Heavywheight Mambo or Flyweight Waltz.
Twice, actually.
Two very simple ways of bypassing Brazil's import tariffs are to declare only the price of the media ($1 a CD) or to declare the package as containing books, if you are shipping manuals too. Books are exempt from all taxes and tariffs even if they have 'complimentary' CDs.
HR is in a worse situation than IT. I have met exactly one HR professional whom I consider serious. The rest have no clue about how to select and keep good professionals.
Yes, the Pentagon is investigating training sites for suicide bomber sheep.
That proves that 64KB really ought to be enough for anyone.
I don't want to pay for porsche!
If you have some many cores and unless they are purely crunching numbers (even then they'll have to spit something out some time), isn't access to RAM going to limit the throughput of your system?
You can make good money if you specialize in a tool like BizTalk or Commerce Server. You'd have to code a bit, mas you'd probably spend more time with consulting: helping people set up their environment, teaching the basics, and helping with optimizations.
Iterative development does not exclude deadlines. The main ideia is that you have to constantly review your plans, adjust to new information, and incrementally build your understanding of the product as well as the product per se. Of course some managers prefer to just lay the plan down and shout at you until you make it happen: it is easier for them not to have to think and replan all the way. I like to emphasize the point that your understanding of the problem at hand evolves along with the project. Building software is a creative process all the way, so it makes no sense to make all your plans upfront. Nobody tells an architect when to have the design for the doors, and then when to have the designs for the windows, then the bathroom, etc, etc.
If your knowledge is incipient and your tool provides an inadequate abstraction, you will veer towards bad habits. If you're good at OO, you can do it even in Perl. But if you're not, you will probably get some nasty habits.
MS Project paves the way to waterfall projects, mainly because most managers don't understand iterative development.
Republicans already nationalized Iraq's oil.
In some countries you have to submit a project in order to enroll into a doctorate programme, in others you become part of an ongoing project and your work will be a spinoff from that. Either way, I can't see how you are already working on your PhD and still making these sorts of questions.
For portability, there's no way Java could beat Perl: http://www.cpan.org/ports/
I think we have too many already. The real problem is either that they don't say what needs to be said because they don't want to make waves (they'll twiddle with their Project schedule and pretend that all will be alright) or that upper management simply won't take no for an answer (and will tell them to twiddle with their Project schedule to make it alright).
I agree, I just gave my overall impression. I think women are capable of writing good code and men can be good testers, but generally you can't rule out that there are differences between the genders, both in their habilities and in their interests.
I have the impression that women tend to see coding only as means, therefore they don't really put in all the care that some men do. On the other hand, they are awesome at testing, because they really look at the details.
I think this is one of the basics of constitutional law everywere. The law is bounded _mostly_ by area not citizenship. If it were simply bound to citizenship, foreigners would have either a great advantage over locals (not pay taxes, drive as fast as they want, etc.) or disadvantage (could be killed for nothing) and would keep away.