Friday, April 25, 2014

Myco - Mushroom Guide for Android

Last week we* released Myco for Android.


Myco is the perfect app for people who collect mushrooms. It contains information about more than 250 types of mushrooms. You can store mushroom locations with GPS position and identify mushroom with a classification scheme. Additionally you can learn to identify mushrooms with a quiz:

The app is available in three editions: Free, Standard and Pro and supports the languages English, German, French and Italian.

For more information please visit the Myco product page.

The app is also available for the iPhone and for Windows Phone.

*Actually the work on Android was almost exclusively done by Stefan... I was too busy otherwise.

Sunday, April 20, 2014

Weekend Reader, Week 16

IMG 0163

About the Software Architect:

"Software Architect" places in the top ten of most annual surveys of best jobs, yet no clear path exists from Developer to Architect.

Do we really need that path? Is anybody expecting a clear path from plumber to architect in the construction analogy?

Are architects just a concept to offer developers a career path?

I have been in the industry for a long time now, and I did not see two companies/projects where “Architect” had the same interpretation. But do we really need architects? I am sceptical … I would argue that we need people that care about stuff. And not everybody can care about everything, so the “Architect” should care more about the high-level, holistic perspective while others care more about low-level perspectives. But I doubt there should be a clear path that leads from the one to the other. It’s just an agreement that somebody should care about this and somebody else should care about that.

And the role of an architect in Agile is another interesting topic:

Putting an architect in a scrum team is like putting mayonaise in cake - Christin Gorman from Roots conference on Vimeo.


About the Foreman

Uncle Bob (Robert Martin, one of the authors of the Agile Manifesto) has some come up with an interesting interesting idea: Software projects needs a foreman. In the initial proposal of Uncle Bob, the foreman is the only person that commits code to the project, other developers send him pull requests. In a follow-up post 'Oh Foreman, Where art Thou?’ Uncle Bob relaxes his initial proposal a bit: The foreman has the ultimate responsibility over every commit, but others might commit directly.

For me this is a drastic departure away from the notion of an empowered, self-organizing team that is the foundation of Agile software development. In my opinion, if we introduce the notion of the foreman, then we build a big obstacle in fostering an intrinsically motivated, self-organising and responsbility-embracing team and take a big step back towards tayloristic understanding to work and responsibilities. I don’t believe the tayloristic approach fits an industry relying on knowledge workers.


The obligatory quote of Steve Jobs: 

Great companies have to be run by ideas not by hierarchy. Otherwise good people won’t stay.


However it seems a bit contradictory to the general myth of the management style of Steve Jobs vs. Bill Gates, i.e. voiced in episode 963 of .NET Rocks:

Steve Jobs ruled by dictatorship while Bill Gates ruled by committee, which allowed Apple do do things that Microsoft could never do.


The demise of "The Enterprise" 

In Consumerization of Computing (german) Philip asks how long the enterprise will still be relevant for vendors like Apple and Samsung.

'The Enterprise’ has lost its grace big time in the last decade. When I started my career over a decade ago, the big challenges for a programmer seemed to be in big enterprise systems. Nowadays the big challenges and innovation seems mostly to be in consumer facing applications on the web and in mobile.

The most tragic manifestation of the descent of the enterprise is the “Enterprise Mode” in Internet Explorer 11, which basically allows enterprises to remain in the stone-age of Internet Explorer 8.

The notion  of "the Enterprise" already became a running gag in the industry:

Jeff Attwood on Stackoverflow Podcast 41.

In corporate environments the product don't have to be good. Sometimes they don't even have to exist ... if you are a thoughtful developer, you are in the wrong place!


The Story of Ashton by Joel Spolsky:

On the morning of his two year anniversary at the cubicle company, Ashton was driving to work when he realized something.
Not one line of code that he had written had ever run.
Not one thing he had done in two years of work made any impact on the world.


It Takes 6 Days to Change 1 Line of Code

It's the first Enhancement in the Developer Queue, after 14 Bug Reports.


Herding Code 102:

Scott: What is the penetration of Node.js into the "enterprise"? 
Tim: It depends on what you mean by "enterprise"?
Scott: Large, slow moving corporations.


Martin Fowler defining Enterprise Systems:

Business rules are given to you as they stand, and if you want to change them you need sixty-seven meetings and three vice-presidents retiring.


Final Gem: Mr. Hanselman is just a great presenter:

Saturday, April 5, 2014

Weekend Reader, Week 14

WeekendReader14 9

L.A.F.A.B.L.E: Large Agile Framework Appropriate for Big, Lumbering Enterprises

I would consider it a very funny April Fools' joke if I would not know how close this carricature actually describes the reality in many enterprise environments.


Signs you might be in survival mode

Roy Osherove concisely identifies when a software delivery team is in survival mode. Does it somewhat sound familiar?


Agile Adoption is Fool's Gold (and other Stories from the Coal Face)

After initial Scrum successes teams usually find out, that blocking obstacles lie outside of the team.

Scrum is like training wheels. At some time they come off.


Enterprise Scrum

Yet another approach to scale agile? Just what the enterprise needs? I have not yet found the time to read the whole 76 pages to make up my opinion ...


Radical Management

Nothing really new here, these ideas are taught in most leadership and management courses … but reality still looks different. So the ideas of Steve Denning are certainly worth to ponder over.

However the introductory video makes me think of … hmm …  a cheap tv show blended with advertisements I usually see on shady torrent  pages:

I liked the TED talk a bit better, but I still would have expected deeper insights:

 Finally I am still wondering about the connection to the german book: Radikal Führen by Reinhard K. Sprenger


Final Gem: Wow, pair programming has come a long way since ‘83...


Related Posts Plugin for WordPress, Blogger...