Personally I thought the book was great. I got the PDF version. The free documentation while it could be better is still okay however I'd recommend just getting the book.
I'm been working with an agile team for the past 6 months. As a contractor I've seen a lot of different development environments. This project has the highest quality of any project I've worked with.
I'm getting about 15% processor utilization on my P4 2.4Ghz. Loads really quickly and the video quality seems pretty good.
I'd bet that a lot of the CPU utilization comes from the fact that it wouldn't be using direct draw like most players would rather than any codec issues.
Exactly... just read it too. If anything is was a rant rather than a bug report. Bugs reports contain information about specific problems and how to reproduce them. What he was saying may have been true but really it was completely useless as a bug report.
Lost attitude control didn't sound too minor. I also think there's a level of difference between the testing you do for a typical business app and a mission critical system MS or not.
If you can get gzip compression turned on it makes a huge difference. The main downer is that if you're sending over HTTP the overhead of the constant connects and disconnects is pretty large.
Re:Journaling File System: for those who don't kno
on
Looking at Longhorn
·
· Score: 1
It would be cool but would cause a lot of issues with concurrency and locking.
Mozilla is a good example of an over engineered solution. This is why it's still not available. Instead of going for a simple design they became a bit too clever.
This is why need constant direct contact with the customer. The customer should always be made aware of the impact of their changes to the schedule. With XP, this is done by writing up a new card with a description of the change and an estimate of the time required. This is placed into one of the future iterations (How soon depends on importance to the customer and the risk).
...because everything has to be documented because everyone has to work on it...
This doesn't sound like XP to me. XP has very few official documents that it keeps. It uses cards extensively but these are not kept as official documentation.
To a large extent the XP treats the code as the documentation. This is not as bad as it sounds because there is a lot of emphasis on making the code as readable as possible. Pair programming and refactoring are designed to help here.
XP has the following characteristics:
It deals rapidly with a changing environment.
Done right it produces very clear code
It avoids over-engineering code.
It makes programming fun!
It increases quality through testing.
It increases communication (both with the customer and among team members).
The trouble is that thin client is one of those overused buzz words that has completely lost it's meaning.
I guess what I would be looking for is something that runs most of it's core logic on the server side and only has presentation on the client side. I would also be looking for something that would automatically upgrade itself when new changes are released. Those new Sun Rays offer a nice model.
After forking out up to $1million for being a Java Licensee - and then seeing it given away under the community license this must be a real kick in the teeth.
This not quite true. They are not giving away licenses. You still have to pay. The difference is that you don't pay until just before you're ready to ship a product.
I guess now the netbeans "open" IDE API will become more of a standard now.
Slashdot Mirror
If you want a good example of what makes emacs so powerful you might want to watch this video:
https://www.youtube.com/watch?v=p3Te_a-AGqM
That's not very nice.
Personally I thought the book was great. I got the PDF version. The free documentation while it could be better is still okay however I'd recommend just getting the book.
>If Java is faster than C, we should rewrite the Java VM...in Java! Interpreted
>code running in an interpreter...that is *also* interpreted!
>Just think of the speed increase! It would be like using uranium to fuel the
>space shuttle! Awesome <i>multiplied by awesome.
Been done.
http://jikesrvm.org/
You do know that Java hasn't been interpreted for a long long time right?
Hotspot JIT compilers are pretty cool. You should check them out sometime.
Free-trade: Were we are free to trade our laws for Americas.
I'm been working with an agile team for the past 6 months. As a contractor I've seen a lot of different development environments. This project has the highest quality of any project I've worked with.
It actually goes year then month where 2004 = 4
I'm getting about 15% processor utilization on my P4 2.4Ghz. Loads really quickly and the video quality seems pretty good.
I'd bet that a lot of the CPU utilization comes from the fact that it wouldn't be using direct draw like most players would rather than any codec issues.
Wonder if jdk 1.5 would make a difference in CPU.
Exactly... just read it too. If anything is was a rant rather than a bug report. Bugs reports contain information about specific problems and how to reproduce them. What he was saying may have been true but really it was completely useless as a bug report.
Lost attitude control didn't sound too minor. I also think there's a level of difference between the testing you do for a typical business app and a mission critical system MS or not.
You're kidding right? If I get bugs in my programs I just fix them and move on. If there's bugs in a test flight people can die. BIG BIG difference.
Yes. It does suck. The good thing is that there's plenty of different debian installers to choose from.
http://linuxmafia.com/faq/Debian/installe rs.html
If you can get gzip compression turned on it makes a huge difference. The main downer is that if you're sending over HTTP the overhead of the constant connects and disconnects is pretty large.
It would be cool but would cause a lot of issues with concurrency and locking.
I dream for a day when I can get my processes and testing so finely tuned that I don't need QA at all. But for now... thanks guys.
Less is more.
This is why need constant direct contact with the customer. The customer should always be made aware of the impact of their changes to the schedule. With XP, this is done by writing up a new card with a description of the change and an estimate of the time required. This is placed into one of the future iterations (How soon depends on importance to the customer and the risk).
The problems with analysis and design documents are that you can't run or test them. Therefore how do you know they are correct?
I have seen some studies. There's a link somewhere on c2.com but I can't think of the page at the moment.
This doesn't sound like XP to me. XP has very few official documents that it keeps. It uses cards extensively but these are not kept as official documentation.
To a large extent the XP treats the code as the documentation. This is not as bad as it sounds because there is a lot of emphasis on making the code as readable as possible. Pair programming and refactoring are designed to help here.
XP has the following characteristics:
I guess what I would be looking for is something that runs most of it's core logic on the server side and only has presentation on the client side. I would also be looking for something that would automatically upgrade itself when new changes are released. Those new Sun Rays offer a nice model.
This not quite true. They are not giving away licenses. You still have to pay. The difference is that you don't pay until just before you're ready to ship a product.
I guess now the netbeans "open" IDE API will become more of a standard now.
I've got to wonder how many of you champions of open source actually practice what you keep ranting on about.