I've got to throw in a plug for the Spiffy UI framework. It's a set of build utilities, security libraries, REST integration and a whole lot more on top of GWT. It scales up well for large teams and large projects and let's you build awesome web applications in a strongly typed environment.
http://www.spiffyui.org/
I've worked in a virtual team for over 10 years and the short answer is that making it work takes work. Most engineers are solitary and it takes a lot of communication to keep a virtual team together.
I wrote a book about it. The One Minute Commute. It is available free.
I completely understand what you mean here. I was really torn about what to say. I went the way I did because I was the creator of the project. I wanted to highlight not only programming skills, but organizational and product design skills as well.
Designing an open source project and getting it off the ground takes a different set of skills than contributing to an existing project. If you're the creator of the project you should highlight that.
Having said all of that, I really like your copy. It is tight and clear while doing a good job describing what you did.
Keeping a portfolio of your open source contributions is a wonderful idea. Creating a narrative really shows that you can speak well about your projects. This is what hiring managers are looking for, strong coders who can speak English and communicate well.
You can also make your own open source projects. If it is something big put it out on SourceForge. If it is something small just put it into a blog. A blog is a great place to show your skills. Not only will you show some code, but you will show your communication skills. The ability to frame a problem's scope, solve the problem, and communicate well about your solution is what most companies are looking for.
My real concern about tunneling everything through a single port or protocol is that it makes network auditing much more difficult. If there is a security problem, or just a general network problem, the fact that everything looks like HTTP doesn't help track down the problem.
However, there is a flip side to this. I have been in the position of trying to convince large companies to change their firewall configurations. It would be easier to make lead in to gold than to get a large company to allow communications through a new port on their firewall.
This basically means that putting everything through port 80 serves two purposes. It give people the perception of security, and it lets the project actually happen. It is the case that not having to change your network configuration is a powerful marketing tool, but it doesn't make anything more secure. All of these issues are addressed in just about every networking book out there.
What Kind of Developer are You?
on
Java IDEs?
·
· Score: 1
I use an editor and an IDE. The editor I use is Visual SlickEdit. It is light, fast, and runs on every platform I've ever heard of. I also use an IDE that can generate code and manage J2EE archives. The IDE I use is the SilverStream eXtend Workbench. (I would note that I am a little biased since I was one of the people who wrote this IDE).
Slashdot Mirror
I've got to throw in a plug for the Spiffy UI framework. It's a set of build utilities, security libraries, REST integration and a whole lot more on top of GWT. It scales up well for large teams and large projects and let's you build awesome web applications in a strongly typed environment. http://www.spiffyui.org/
I've worked in a virtual team for over 10 years and the short answer is that making it work takes work. Most engineers are solitary and it takes a lot of communication to keep a virtual team together. I wrote a book about it. The One Minute Commute. It is available free.
I completely understand what you mean here. I was really torn about what to say. I went the way I did because I was the creator of the project. I wanted to highlight not only programming skills, but organizational and product design skills as well. Designing an open source project and getting it off the ground takes a different set of skills than contributing to an existing project. If you're the creator of the project you should highlight that. Having said all of that, I really like your copy. It is tight and clear while doing a good job describing what you did.
Keeping a portfolio of your open source contributions is a wonderful idea. Creating a narrative really shows that you can speak well about your projects. This is what hiring managers are looking for, strong coders who can speak English and communicate well.
You can also make your own open source projects. If it is something big put it out on SourceForge. If it is something small just put it into a blog. A blog is a great place to show your skills. Not only will you show some code, but you will show your communication skills. The ability to frame a problem's scope, solve the problem, and communicate well about your solution is what most companies are looking for.
You look at my attempt if for inspiration: http://zgrossbart.blogspot.com/
My real concern about tunneling everything through a single port or protocol is that it makes network auditing much more difficult. If there is a security problem, or just a general network problem, the fact that everything looks like HTTP doesn't help track down the problem.
However, there is a flip side to this. I have been in the position of trying to convince large companies to change their firewall configurations. It would be easier to make lead in to gold than to get a large company to allow communications through a new port on their firewall.
This basically means that putting everything through port 80 serves two purposes. It give people the perception of security, and it lets the project actually happen. It is the case that not having to change your network configuration is a powerful marketing tool, but it doesn't make anything more secure. All of these issues are addressed in just about every networking book out there.
I use an editor and an IDE. The editor I use is Visual SlickEdit. It is light, fast, and runs on every platform I've ever heard of. I also use an IDE that can generate code and manage J2EE archives. The IDE I use is the SilverStream eXtend Workbench. (I would note that I am a little biased since I was one of the people who wrote this IDE).