jbandi

↗ HN profile [ 72.8 ms ] full profile
Karma
144
Created
November 3, 2008 (17y ago)
Submissions
0
  1. The Angular 2 Router Debacle (blog.jonasbandi.net)
  2. The Software Grief Cycle (blog.jonasbandi.net)
  3. This post lists my favourite examples that demonstrate impressively the power of JavaScript.

  4. In this post I show how to run simple Node.js applications with Nashorn on the JVM using Avatar.js

  5. Performance: Nashorn vs. Node (blog.jonasbandi.net)

    I am naively playing around with Nashorn the JavaScript runtime of Java 8. Out of the box the performance of Node seems to be almost a factor 1.6 better than of Nashorn.

  6. I think the ultimate consequence of embracing Agility is not scaling it to the big corporation, but denying the reason for corporations altogether.

  7. Not happy with Agile, but why? (blog.jonasbandi.net)

    From a developers perspective: what went wrong with Agile and why? Criticising and pointing out problems is easy. But finding the root cause for being unhappy requires more reflection.

  8. Scrum is not what it used to be ...

  9. Thoughts about the analogy between an idolized backlog in Scrum and the Underpants Gnomes in South Park (originally by Jeff Patton)

  10. Enterprise IT is a simple domain. We don't really deal with substantially complex or challenging problems, at least not in technical the realization. We mostly deal with trying to understand technology that has been…

  11. Despite the seemingly striking dominance of Git, there are still brave contenders sprouting out of the dvcs land.

  12. In the last few years I have come to the conclusion, that the most important aspect of TDD is the mindset that comes along with TDD. With the right mindset we can practice TDD even in environments where we can't write…

  13. Is the original test automation pyramid still matching the current software development landscape?

  14. Two recent blog posts seem to indicate that there are software development environments where core agile development practices like TDD and especially BDD do not fit. Those "high-ceremony" practices are even considered…

  15. As a consultant I have seen almost no project that did not run into troubles with their ORM infrastructure at some point in time ... Maybe it is the ORM frameworks that are the problem? Could this be a general advise:…

  16. BDD looks incomplete from a testing perspective? Try to look at it from a requirements engineering perspective!

  17. Top 24 Agile Web Testing Tools (blog.jonasbandi.net)

    The current situation around this type of tools is quite entangled, some tools are extending or complementing others, some are competitors and new ones are sprouting out of others... The following post tries to get some…

  18. Classifying unit-, integration-, end-to-end and acceptance tests.

  19. In death-march projects the developers are often suffering from the cassandra syndrome: They know that the project is doomed to fail, but they gave up on trying to change anything long ago.

  20. When is Scrum successful? (blog.jonasbandi.net)

    An interesting question from my Scrum in Depth course last week: When is Scrum successful?

  21. SpecFlow aims at bridging the communication gap between domain experts and developers by binding business readable behavior specifications to the underlying implementation. SpecFlow provides a pragmatic and frictionless…

  22. Accepting dysfunctional environments is a sign of resignation, it means that you accept that you will never deliver what you are capable of, in essence you are giving up on being a professional.

  23. Business readable examples have to be an artifact that business cares about! Else there is the imminent risk that the whole BDD effort degrades to a petty effort of over-eager developers...

  24. SpecFlow 1.3 using the official Gherkin parser from Cucumber & new features. SpecFlow aims at bridging the communication gap between domain experts and developers by binding business readable behavior specifications…