I was able to get on the 3g network here in DC and let me tell you its fast compared to Edge. I don’t have EVDO or any of the others so this isn’t a comparison. However, what I can tell you is that speedtest.net marked my speed at 500k on the highway moving at 80mph. Sitting here I am going to run another test now (hotel lobby - not they don’t have wifi that is affordable) : 278ms ping with 581k for download and 141k for upload.

Now I am not saying this is the beat all end all of wireless speed but wow have we come a long way.

I can foresee a very near future where people do not use land line internet but instead pair their laptop with their phone using bluetooth or some other technology and surf the internet wirelessly from anywhere at any time.

Can you spot the code problem below??


/*

Every algorithm might use
- any other algorithm (in this sense and also in this class)
- the types int, double, boolean
- type conversions between int and double
- arithmetic operations +-*/%
- boolean-arithmetic operations < > <= >= != ==
- boolean operations & | !
- if, while(), restricted switches, ?:
- all interfaces

An algorithm might not explicitly refer to specific classes,
arrays or other types.

*/

public class algorithm { /* todo */ }

Agile methods emphasize working software as the primary measure of progress. Combined with the preference for face-to-face communication, agile methods usually produce less written documentation than other methods. In an agile project, documentation, Gantt charts and other project artifacts all rank equally with working product. However, when stakeholders are asked to prioritise deliverables for demonstration at the end of the current iteration, they generally prefer to see working product. Stakeholders are encouraged to prioritise iteration outcomes based exclusively on business value perceived at the beginning of the iteration. If documentation represents higher business value than working software in any particular iteration then stakeholders give it a higher priority than working software. The (cross-functional) development team will accordingly produce that documentation instead of lower priority software.[citation needed]

Agile means being able to quickly change direction. In software development, it requires strong discipline to code for agility. It includes writing tests for functionality before coding. It calls for naming of functionality to exactly match the intent and the terminology of the problem domain. It demands cessation of coding when the tests pass. The sum total of all the disciplines delivers an ability to change direction quickly. New and unexpected functionality required to cope with a sudden change in the business landscape can be inserted in existing code using test-driven development and all the previous tests will pass or fail to instantly indicate where code needs to be refactored to stay functional. If functionality is added before it is required then it becomes “dead weight” when refactoring is called for.

You can check it out here: https://glassfish.dev.java.net/

Also some of the changes for 7 can be found here: http://www.jroller.com/scolebourne/entry/jsr_310_and_java_7

Our highest priority is to satisfy the customer
through early and continuous delivery
of valuable software.

Welcome changing requirements, even late in
development. Agile processes harness change for
the customer’s competitive advantage.

Deliver working software frequently, from a
couple of weeks to a couple of months, with a
preference to the shorter timescale.

Business people and developers must work
together daily throughout the project.

Build projects around motivated individuals.
Give them the environment and support they need,
and trust them to get the job done.

The most efficient and effective method of
conveying information to and within a development
team is face-to-face conversation.

Working software is the primary measure of progress.

Agile processes promote sustainable development.
The sponsors, developers, and users should be able
to maintain a constant pace indefinitely.

Continuous attention to technical excellence
and good design enhances agility.

Simplicity–the art of maximizing the amount
of work not done–is essential.

The best architectures, requirements, and designs
emerge from self-organizing teams.

At regular intervals, the team reflects on how
to become more effective, then tunes and adjusts
its behavior accordingly.

ref:http://agilemanifesto.org/principles.html

Today I decapitated a mouse and dropped its headless body at their feet. I had hoped this would strike fear into their hearts, since it clearly demonstrates what I am capable of. However, they merely made condescending comments about what a ‘good little hunter’ I am.  They continue to pick me up and handle me, an obvious attempt to subvert me.

There was some sort of assembly of their accomplices to night.  I was placed in solitary confinement for the duration of the event.  However, I could hear the noises and smell the food. I overheard that my confinement was due to the power of ‘allergies.’ I must learn what this means, and how to use it to my advantage.

Today I was almost successful in an attempt to assassinate one of my tormentors by weaving around his feet as he was walking. I must try this again tomorrow — but at the top of the stairs.

I am convinced that the other prisoners here are flunkies and snitches. The dog receives special privileges. He is regularly released — and seems to be more than willing to return. He is obviously retarded.

Tonight I will again lay on their heads while they sleep and hope to smother them.