The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

  • Twitter Updates

  • My Flickr Stream

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 1,769 other followers

Archive for the ‘Agile’ Category

Great Innovators Start with Customer Struggles (Not Customer Needs)

Posted by jpluimers on 2019/11/14

Two very important quotes of a must-read article (reading of it takes ~5 minutes):

  • Teams create the most value for customers when they know the difference between customer needs and struggles
  • If we align our mental model to needs, we are missing opportunities to solve the underlying struggles in innovative ways.

Source: [Archive.isGreat Innovators Start with Customer Struggles (Not Customer Needs)

Via: [WayBack] Talking in terms of what customers need, limits options. Great Innovators Start with Customer Struggles (Not Customer Needs) – Marjan Venema – Google+

–jeroen

Read the rest of this entry »

Posted in Agile, Development, Software Development | Leave a Comment »

Tech Debt by MonkeyUser

Posted by jpluimers on 2019/11/07

[WayBack] Tech Debt (by MonkeyUser: Software development satire) is one of the best images on Tech Debt I ever encoutered (via[WayBack] Tech Debt by @ismonkeyuser https://www.monkeyuser.com/2018/tech-debt – ThisIsWhyICode – Google+):

–jeroen

Posted in Agile, Conference Topics, Conferences, Development, Event, Software Development, Technical Debt | Leave a Comment »

Software quality: economics of formality

Posted by jpluimers on 2019/11/06

Interesting read: [WayBackSoftware quality: economics of formality

At one time formal methods were thought to be the only hope for software development. That did not turn out to be the case.

Via: [WayBack] Software quality is better in practice than in theory. Formal methods improve software quality, but at a high cost that is sometimes worthwhile and some… – Jeroen Wiert Pluimers – Google+

Comment there:

Pedro Marcal:

+Jeroen Wiert Pluimers +John Cook , I think that when a code has been in service for even a short time, we can divide the code into two classes. The first is that part that has been executed at least once. The other code has never been executed. The latter code has an error rate that may be measured as a function of the language used. In the old days Fortean had a bug in every seven lines. C used to be 100 to 200 lines. We set up instrumentation to determine the number of lines tested in the first class and found that it was a linear function of the new bugs found. This was a good way to ensure a high quality code.

Related:

–jeroen

Posted in Agile, Code Quality, Development, Software Development | Leave a Comment »

Meeting Ticker – the real cost of a meeting visualised

Posted by jpluimers on 2019/11/04

Ever figured out how costly meetings are?

Show the [WayBackMeeting Ticker during a meeting and be amazed after filling in just a few fields:

Of course it is open source: github/tobytripp/meeting-ticker

And I also found who originally referred me to it: [WayBack] Weekend Reader 2017.48 – reality-loop

–jeroen

Posted in Agile, Development, LifeHacker, Power User, Software Development | Leave a Comment »

Taking short 5m breaks throughout the day isn’t such a bad idea at all…

Posted by jpluimers on 2019/10/28

Interesting that the world at large found out about the 1980s Pomodoro Technique:

[WayBack] Taking short 5m breaks throughout the day isn’t such a bad idea at all: “on average, mindfulness participants gained 62 minutes of productivity a week, … – Marjan Venema – Google+

She refers to [WayBack] The Busier You Are, the More You Need Mindfulness which states You can get benefits in as little as two minutes.

–jeroen

PS: she means 5 minute breaks, not 5 meter breaks (:

Posted in Agile, Development, LifeHacker, Power User, Software Development | Leave a Comment »

 
%d bloggers like this: