Redirecting port 80

Solution had been found on how to re-direct port 80 to any custom port:

You can redirect connections on port 80 to some other port you can open as normal user.

Run as root:

# iptables -t nat -A PREROUTING -p tcp --dport 80 -j REDIRECT --to-port 8080 

From source: http://serverfault.com/questions/112795/how-can-i-run-a-server-on-linux-on-port-80-as-a-normal-user

Monday April 25th, 2011

Lecture Notes:

• Next week - presentations following NW Angels presentation format
• Rehearsing for presentation is highly important
• Role of the slide is to support spoken points
• 5 maximum bullet points per slide
• Avoid any clip arts
• Flow presentational guidelines: http://www.nmangels.com/entrepreneurs/presentation-guidelines/
• Each point said has a maximum amount of information without a feel that it is spoken out fast
• Summary on 2 pages to take away with them (Bring about ~15 copies)
• Intellectual property - what level of disclosure this presentation will be held at
• Watermarking, tracking of documentation
• How to approach copyright and idea protection with tact
• Re-iterate the key three points though out presentation and repeat at th bottom of the talk
• Pain points - what caused, what were the symptoms for this project to start
• Names: Joe Chavez president of NM Angles, Bob Coraley(sp?), Zack Grafe.

Monday April 18th, 2011

Lecture Notes:

• Big picture, how it is different, where is this product fit in to be compatative
• Specific presentation format ("New Mexico Angels presentation") that captured here http://www.nmangels.com/entrepreneurs/presentation-guidelines/
• How things changed?
• In-class presentation week.
• Final is on ....
• 10 minutes presentation + 10 minutes for questions and feedback
• Dead week - 2 presentations Monday and Wednesday, one on Friday.
• Every week must be prepared for Monday
• Be prepared for a set of questions that might be asked and answers, how requirements met, how they thought through
• Wrap up the SW and give the demo
• Polish SW
• "Looking at the team as a whole"
• Well transitioning, well placed and well-driven demos

Monday April 11th, 2011

Lecture Notes:

• Prioritization of the tasks helps with successful delivery of the product
• Rational for prioritization
• Iteration at the abstract level
• Design patterns and programming approaches used for product development
• Part of agile SW development is to have working code on each step
• Delivery of SW - demonstrable product, a professorial looking polish
• Set of the demos that will be shown in final demo
• Test first is on the top of the list for chosen SW Development process
• Find a set of users for testing the system
• What is done vs. proposed
• What changes were done, how it was tracked
• How far off we are on the estimates? Matrix on the difference is a plus
• What had been neglected and what was mentioned over several weeks in the row in the meetings
• Test first and acceptance criteria
• User doc, Developers Documentation, SW Process, Accounting how you and team worked together, Demo, Secret Sauce(something that can be pulled and re-used)

Monday April 4th, 2011

Lecture Notes:

• System needs to be ready for demonstration with all of the requirements fulfilled
• Secret sauce of the project to progress - true bit of intellectual property that we are generating during this semester (Key intellectual property - what is that you understand more than anyone else, what is that special about it that no one done before)
• How to do group evaluation? Velocity is one of the metrics. Online evaluation resources. Set some goals to improve and exploit. Be objective with tact.
• The biggest value in criticism is that is opens up the main flaws and areas for improvements
• Self-evaluation ( looking for big delta, big accomplishments, how to make the self-eval better)
• Recognizing in yourself what are the areas for improvement, ability to look at yourself objectively, understand the reader self-eval was prepared for
• Make short and easy to read ( in consideration that the prof. have to read 30 of self-evaluations)
• Necessary and sufficient conditions ("overly completed is less complete")
• If you know how to do it right, then you should understand better how to do it even better next time
• "Verification and Validation" method (doctest in python) - demonstrated by Jacob
• 
  

Monday March 28th, 2011

Lecture Notes:

• Analysis of the progress and visual measurement of thus is a must for Wiki
• Verifiability of correctness and completion of the requirement
• Consistency: reference to original requirements
• Traceability: a creditation for the work done.
• User stories/cases describe user events and how the system responds to an event
• User cases should be short clear and consistent in the format
• Realistic expectations
• Measurement of project velocity is highly meaningful
• Design patterns, coding standards
• "Every cut and paste code is a newly introduced bug to the code"
• As an exercise -- Pick large task and complete by the end of the week no matter what - test sprint
• Understanding clearly the boundary of the the problem, understanding of protocols on server/client communication
• Re-factor code and try to build into components
• Centralize, localize code and run tons
• UML diagrams
• Other team project disc.: proposed content is too broad; too vague; it was had to summarize and give a description of the project.

Remote Desktop as another way of pair programming

Today, I was able successfully configure Ubuntu OS sharing desktop option that will not just enable us to use our web portal PC with all it's available tools and widgets remotely, but also do some pair programming as we navigate through the same space with enabled Skype communication.

Just for any of my personal future reference, I would like to post the link with simple step by step instructions on how to set up remote desktop from Ubuntu OS:

http://www.ubuntugeek.com/share-your-ubuntu-desktop-using-remote-desktop.html