When ted was a kid the rule was to go to school, get a good job an make good money.
But the formula is changing. In countries like India, China or Poland developers get a lot less than in the western countries.
But automation threatens programmers more than all the other outsourcing sources ever could.
But there is a guy who had an idea, that make a million dollars. You can be that guy, an iconoclast.
A iconoclast in Teds definition is a person who does something that others say can’t be done.
This, then, to overcome the automation trap is your goal: become an iconoclast.
There are three things for iconoclasts to do:
- seeing differnetly – To see different, you must change your perception.
- overcoming fear – Fear can drive bad decision-making. It’s ok tho feel it. But don’t let the fear win.
- use social intelligence – For an iconoclst social interaction and reputation is important. Talk about what you do, or nobody will ever notice it.
Rachel is an agile Coach. She helps teams to work with agile technics. In Kent Becks book the agile coach was
described as somebody who helps the team. And try to help from the back.
Agile coaching is like planting. Create an environment for the team to grow their own agile practice.
Where to start. Use your agile technices for planing. And introduce new things in every sprint.
- Get to know the team.
- Agile is not usually the real goal. Ask for the goal.
- People resist change. Focus on benefit to the team.
- Don’t make a plan how to transform the team. Do what the team want to try out.
- Give advice sparingly. Leave room for team ideas.
- Respect experience. Tap into the team wisdom.
- Ask questions.
- Be an example.
- Identify concerns. Make blockers visible.
- Differnt angles. Step back to see the big picture
- Take time out to reflect
- Changes takes time. Be patient. (Thats the hardest part of agile coaching)
Java EE and OSGi comparison:
|Logical component – level dependencies||Package level code dependencies|
|Unit of deployment: JAR||Unit of deployment: Bundle|
|Interface-based services as EJB components||Interface based services as classes in bundles|
|Component life cycle callback hooks||Bundle and framework life cycle callback notification|
|JNDI under container control||Service registry shared bundle access|
|Application code strictly controlled||No real application coding constraints|
Enterprise Spec (JSR 291 – OSGi as part of JCP) goal is to provide a way to host Java EE technologies on OSGi.
Jutta gaves an excellent talk about distributed teams in agile projects. These are the key success factor to make a global team effective:
- building trust
- encouraging open communication
- building personal relationships
- bridging cultural differnces
To achieve this factor with your team you have to do face to face meetings. Frequency and duration depend on the distance. A good idea are differnt meeting locations. Change who will be the host and who needs to travel.
You should pay attention to your vocabulary. Nightly build, morning call or remote site are mostly the termes are used from the sight of the headquarter.
Teams should be responsible to deliver a feature. Not responsible for middleware or userinterface. If you have middleware people at location A and userinterface people only in location B you have to build a dispersed feature team. Disperse teams split accros different locations.
To overcome cultural differences you have to foxus on similarities rather than on differences. You have to create a joint project culture with a common vision, rules values and mututal respect.
Clojure is a Lisp for the jvm. Ted gaves a short introduction into this language.
Here are Teds points:
- For There’s a lot great features in clojure but the syntax sux.
- The syntax is Differnt syntax than common lisp.
- Running on the jvm and takes advantage of the jvm.
- Clojure comes with software transactional memory (STM)
Why would you like to use Clojure?
Because you want to…
- use the metaobject protocol (MOP)
- be highly dynamic
- use code as data
- work functional
- write highly concurrent code
Java EE6 Goals and Highlights
- Add features already in popular use
- current technology
- easier to use
- more flexible packaging and delivery options
- Make old technologies optionally supported
These are the JAVA EE 6 – Major New Features
- JSF 2.0 (JSR 314)
- Servlet 3.0 (JSR 315)
- EJB 3.1 (JSR 318)
- JPA 2.0 (JSR 317)
- Java Connectors 1.6 (JSR 322)
- Dependency Injection 1.0 (JSR 299)
- Bean Validation 1.0 (JSR 303)
- Make was a revolution in 1977.
- Ant was build for building apache tomcat.
- Then the world got antified.
- Human beeings should never write xml.
- Russel Winder released Gant 2006
- Gant is a lightweigth wrapper around AntBuilder.
- Gant are groovy scripts
- Gradle is the place to go