Raimund Steger’s Business Homepage


  I am not for hire until further notice.


Custom and industry standard solutions

  • Open Systems (UNIX/Linux/Windows NT) software design and development
  • UNIX/Linux/Windows NT systems engineering
  • Networking


»steg0.de Bugzilla Service


About me

(My LinkedIn Profile · My CV · Project Experience)

I am a software engineer in network and system programming, distributed applications, formal language translation, and databases. I also have several years of experience as network administrator for Linux and MS-Windows environments. I currently work for Sopra Steria Consulting.

Here's what I follow:

  • F/OSS first
  • generalization where necessary, pragmatism where possible
  • zero fanboyism


  • Martin Fowler, Kent Beck (at the very least for the historic significance!), Adam Bien – sure thing, worthwhile reads all that.
  • Robert C. Martin (and the whole romanticized craftsmanship idea) – I've got real difficulties putting my weight behind this stuff. It seems intended for people looking for easy answers. I regard it a waste of time, but am sometimes amazed seeing how many people fall for it. You even read it in job ads!

I usually factor code in object-oriented or functional manner. I prefer to use object-oriented factoring for things that need to be stateful, where I, just as everyone else, factor along multiplicity, life span, and of course concern boundaries.

Software development today often is not about conquering new areas, but about maintaining and migrating existing solutions. This is where I have an eye on gradual evolution of the existing code with sustainability and maintainability in mind.

—   —   —

I used to write here that quality software development was primarily about creating formal artifacts (i. e. code) and cutting back on the non-formal ones. Now that agile methodologies have become commonplace it is quite unnecessary to specially mention that position. What's more, after ten years of experience in the field my view has sightly changed, too. With it I don't mean that people should climb their ivory towers again and fire up their planning tools to create elaborate charts before any code is written; this is not how I believe software architecture works.

But agile development does not mean that:

  • unit tests and coverage reports are all there is needed to control code quality (people are sometimes barking up the wrong tree here);
  • every API can be regarded as self-documenting.

Seemingly independent of the transition from heavyweight to lightweight processes, focus on quality control and documentation is still as absent as ever and is not incentivized in many environments. This is a systemic problem as well as a precursor to architectural debt.



Software Development

  • Agile modeling and development
  • Java SE, JEE, C/C++/C#
  • Python, Ruby, Scheme, Perl, JavaScript
  • Maintainable code and documentation
  • Adherence to industry standards

UNIX/Linux Networking

  • Heterogenous networks
  • Enterprise UNIX/Linux
  • UNIX/Linux desktops
  • Linux mobile

Software Development Areas Of Interest

  • Distributed, mobile and P2P application design
  • Platform-independent applications
  • Porting legacy applications to Linux/UNIX
  • Machine learning and reasoning
  • Data modeling, retrieval, management
  • Text processing, formal language translation
  • Software development tools
  • Database modeling and applications
  • Bluetooth technology

New location starting 2017-01-01:
Baumschulenstr. 93
12437 Berlin


The old location (post will be redirected):
Worringer Str. 31
40211 Düsseldorf
Explore the facility

Last Update 2016-12-31 Raimund Steger