Posted by Arjan Molenaar in the early morning: March 31st, 2011
When it comes to distributing Python packages, Python has its own mechanism. The tooling (either easy_install or pip) allows you to install a Python package and its dependencies. Typically, those packages are installed as Python Eggs (Java has Jars, Ruby has Gems and Python has Eggs). However, one can not expect Mac users to use these command line tools to download and install Python applications, especially GUI applications.
Posted by Robert van Loghem just before lunchtime: March 23rd, 2011
Last time I explained why I think doing TDD for mobile is imperative, and why I do it. But now it’s time to get technical, and explain to you how to set up, GHUnit in XCode 4 and run unit tests, not only in the iPhone and iPad simulator but also on your own physical device!, it’s in text and images but also in video form on YouTube.
Note, if you want to know why i chose GHUnit over OCUnit, just scroll down to the end of the post.
Posted by Olav Maassen in the early afternoon: March 21st, 2011
When hiring a new member to your team, how do you find out if she is really as good as she says? Currently the interview is a standard practice and an assessment is gaining popularity. Thanks to social networks like linkedin.com other intangible factors previously unused come into play: respect and reputation. These can now seriously effect your career (both positive and negative). Let’s take the next step: learn from games and introduce achievements.
Posted by Urs Peter mid-afternoon: March 20th, 2011
This week I visited the stronghold of Scala, EPFL, in order to certify as ‘official’ Scala Trainer. It was an impressive visit, whose highlights I have transformed into this blog.
(more…)
Posted by Maarten Winkels in the late evening: March 18th, 2011
RESTEasy is a Framework for building RESTful applications in Java. In this blog I will show how to easily build RESTful webservices that accept data from an HTML Form. We will also explore the possibilities to extend RESTEasy to handle more complex cases.
(more…)
Posted by yamsellem in the early morning: March 17th, 2011
As an ubiquitous exchange format, XML is well implemented in java. But those implementations hide how they perform the data binding from a XML structure to an object graph. It leaves us helpless in front of an application giving XML as a plain old string. Because low level API (DOM, XPath) — focused on document structure — are tedious, major JAX-RS implementation (Jersey, CXF) have chosen the same high level API — focused on data —: JAXB. Let’s do the same.
Posted by Mark Bakker mid-afternoon: March 15th, 2011
Last week I got a presentation for a security device I had never heard about.
Most times this means it is something which is not commodity, or has no real use-case.
But this time I was really impressed. The device is a possible replacement for IBM Datapower XML Security Gateway. But the way they designed the device is totally different.
What CrossCheck networks did was creating a device with just security as main use case. First of all it was an XML gateway, nowadays is does support HTML, XML, SOAP, FTP, JMS and others.
It also translates different flavors of JMS to each other, it can even convert from IBM MQ to JBoss MQ directly.
Posted by Robert van Loghem around lunchtime: March 9th, 2011
Since a couple of months I’ve been developing mobile applications, some are for the business at home (girlfriend-shopping-list app that actually works and augmented reality garden iPad app) and some are for work. I have experienced that TDD and Continuous testing (Test Driven Development) is a way of working that leads to fewer bugs and regression problems and better design in my software, it’s my preferred way of programming, not testing.
And to start off, here’s how I benefit from doing TDD:
- Robust
- Better code design, no really!
- Find regression problems early on
and you can read more on TDD and Continuous testing here.
The thing is, writing a mobile app takes about 20% of the time it would take me to write a web+client+server based app. Which of-course is really nice, because I can write lots of apps. It also means that whenever i need to fix a bug or add new functionality, I need to have developed it in a TDD fashion, otherwise i cannot guarantee reliability. So let me explain why…
Posted by Laurens Bonnema mid-afternoon: March 4th, 2011
- Create a list of all your requirements in Epic format (think Product Breakdown).
- Break down each Epic into work items in User Story format (think Work Breakdown).
- Determine which Epics and/or User Stories have dependencies.
- Visualize dependencies in a network diagram.
- Create an estimate for each User Story using Planning Poker Points, NESMA Function Points, Gummy Bears, anything but time and/or money.
- Assign business value to all Epics and divide this value between the User Stories based on their point-estimate.
- Sort the list of User Stories based on priority, dependencies and business value per point-estimate (triage). Having trouble sorting the list using triage? Pick another prioritization technique.
- Take an educated guess (assumption) about the number of hours per point you’re likely to spend, based on a representative sample of User Stories taken at random.
- Calculate duration based on your assumption.
- Use the calculated duration as input for a Monte Carlo analysis to create your first rolling wave planning.
- Correct the assumption every sprint based on the progressive average of the actual hours per point ánd a new Monte Carlo simulation for the remaining duration.
- Report regularly, preferably in a reporting format currently in use by the organization.
Categories
- Java (311)
- Agile (181)
- General (136)
- Scrum (67)
- Architecture (64)
- Testing (59)
- Performance (46)
- Middleware (55)
- Deployment (37)
- Xebia Labs (38)
- SOA (31)
- Podcast (31)
- Project Management (28)
- Tools (25)
- Uncategorized (20)
- lean architecture (20)
- Quality Assurance (17)
- Articles (13)
- Virtualization (19)