Most of these tales are in a softcover book called the "Tolkien Reader". I picked up a copy of this a few months ago at my local chain bookstore, so it should be more easily found than "Tales from the Perilous Realm."
I have to agree with the reviewer about the poem section. I got the book wanting to read more about Bombadil but ended up quite disapointed. "Leaf by Niggle" was very enjoyable.
I've been following both of these projects for years.
The point that so many have missed is that this shows how close the GNU implementations are to be being a complete JDK replacement. Eclipse is a very complex beast that uses nearly all of the Java APIs. This achievement shows the quality of the years of work that has gone into these free projects. All of this work is now finally ready to pay off.
Congratulations to the whole ClassPath and GCJ teams!
-Avery Regier
Toughest thing to get rid of is deployment
on
Coder or Architect?
·
· Score: 1
I'm in the same boat. I'm 27 and have a similar role on a development team, and don't want to go into management. (I'd fail, miserably.)
We've recently transitioned to XP. It allows me to fulfill an architect role while continuing to code. I can mentor and transfer skills to other developers without jumping into management. Since my manager recognizes my worth (especially when out sick or on vacation and the fires come) I don't have to move to an official architect position and deal with all the negatives the title brings. So long as you enjoy what you are doing and you are good at it, stay where you are. The recognition and the raises will come.
The worst thing to get rid of, though, is deployment. I have found that if you know how to deploy and keep a production system running, two things happen:
1) You are invaluable (especially when the fires creep up)
2) No one else wants to learn how to do it, so you are stuck being the biggest bus risk.
We use a wiki for this purpose. The one we use is from devtools.org.
The advantage of this versus a static site is the ease of updating the information.
Updates do not have to go through any particular person(s).
An engineer can update the work directly through his browser.
Links amongst related documents are handled dynamically instead of explicitely. Thus pages can theoretically be updated with links to related information without actually manually changing the page.
Before everyone gets in a huff about Bush possibly winning the Presidency without winning the popular vote, remember that this is exactly what the Framers of the Constitution intended and what helped to allow these states to become united.
The Electoral College and the Senate were two concessions made to the smaller states such that they had a larger say in the Federal government than their population alone would merit. Each state gets a set number of votes based upon the number of seats that state has in the House of Representatives plus two for their two senators. It is that +2 that gives the smaller states a larger say in who the President should be.
Say Bush wins Florida after the recount and loses Oregon. If you take away those two EC votes from each state to account for that compromise, you get a Gore win (229 Gore/213 Bush), because he won the big states.
So ask yourself: Do you really want to get rid of the Electoral College? If so, are you willing to have candidates pandering to large poplulation centers at the expense of everyone else? Do you also want to rid the country of the Senate, which is also a concession to small states?
States' Rights is an important facet of our Constitution, and the states are speaking now.
I've had this problem several times over the past year and I've found that the best way to get out of it is to write something fun and interesting. Usually it just amounts to a new cool and useful but strictly unneeded feature in another project or in our application framework or library. Make it generic and reusable so that your mind isn't stuck thinking about just one use or project. (Make it nimble to get your mind nimble.) It needs to be small and be done in a day or two.
Then you tell the rest of your team about it and when you see it get used you feel like a programmer again.
That's OK, CmdrTaco, I was recently on vacation in Australia for three weeks on the edge of the rainforest, and I didn't see any roos until the last three days at a distance.
Slashdot Mirror
Most of these tales are in a softcover book called the "Tolkien Reader". I picked up a copy of this a few months ago at my local chain bookstore, so it should be more easily found than "Tales from the Perilous Realm."
I have to agree with the reviewer about the poem section. I got the book wanting to read more about Bombadil but ended up quite disapointed. "Leaf by Niggle" was very enjoyable.
I've been following both of these projects for years.
The point that so many have missed is that this shows how close the GNU implementations are to be being a complete JDK replacement. Eclipse is a very complex beast that uses nearly all of the Java APIs. This achievement shows the quality of the years of work that has gone into these free projects. All of this work is now finally ready to pay off.
Congratulations to the whole ClassPath and GCJ teams!
-Avery Regier
I'm in the same boat. I'm 27 and have a similar role on a development team, and don't want to go into management. (I'd fail, miserably.)
We've recently transitioned to XP. It allows me to fulfill an architect role while continuing to code. I can mentor and transfer skills to other developers without jumping into management. Since my manager recognizes my worth (especially when out sick or on vacation and the fires come) I don't have to move to an official architect position and deal with all the negatives the title brings. So long as you enjoy what you are doing and you are good at it, stay where you are. The recognition and the raises will come.
The worst thing to get rid of, though, is deployment. I have found that if you know how to deploy and keep a production system running, two things happen:
1) You are invaluable (especially when the fires creep up)
2) No one else wants to learn how to do it, so you are stuck being the biggest bus risk.
Before everyone gets in a huff about Bush possibly winning the Presidency without winning the popular vote, remember that this is exactly what the Framers of the Constitution intended and what helped to allow these states to become united.
The Electoral College and the Senate were two concessions made to the smaller states such that they had a larger say in the Federal government than their population alone would merit. Each state gets a set number of votes based upon the number of seats that state has in the House of Representatives plus two for their two senators. It is that +2 that gives the smaller states a larger say in who the President should be.
Say Bush wins Florida after the recount and loses Oregon. If you take away those two EC votes from each state to account for that compromise, you get a Gore win (229 Gore/213 Bush), because he won the big states.
So ask yourself: Do you really want to get rid of the Electoral College? If so, are you willing to have candidates pandering to large poplulation centers at the expense of everyone else? Do you also want to rid the country of the Senate, which is also a concession to small states?
States' Rights is an important facet of our Constitution, and the states are speaking now.
I've had this problem several times over the past year and I've found that the best way to get out of it is to write something fun and interesting. Usually it just amounts to a new cool and useful but strictly unneeded feature in another project or in our application framework or library. Make it generic and reusable so that your mind isn't stuck thinking about just one use or project. (Make it nimble to get your mind nimble.) It needs to be small and be done in a day or two.
Then you tell the rest of your team about it and when you see it get used you feel like a programmer again.
That's OK, CmdrTaco, I was recently on vacation in Australia for three weeks on the edge of the rainforest, and I didn't see any roos until the last three days at a distance.