4,506 reputation
11623
bio website swolter.sdf1.org
location Wurzburg, Germany
age 30
visits member for 3 years, 4 months
seen Jan 8 at 22:35

Currently working on my PhD at the Sauer Lab for Biophysics in Würzburg, mostly working on and maintaining the open source program rapidSTORM for super-resolution microscopy.


Sep
11
awarded  Good Answer
Aug
1
awarded  Yearling
May
2
awarded  Good Answer
Aug
1
awarded  Yearling
Feb
20
awarded  Enlightened
Feb
20
awarded  Nice Answer
Feb
18
awarded  Caucus
Feb
18
comment Nested Enum type in C++ or C#?
@anaximander: The problem is that enums call for switch statements to handle them. And switch statements are a nightmare when you need to extend the enum. If your enum is large enough that it needs subcategories, it is certainly large enough to expand regularly. Here is the advantage of OOP: You can define all necessary operations (such as isMovement(), isInteraction(), isCombat()) and your application scales completely differently when you add new actions.
Feb
17
answered Making things just work and then improve them, or attempt to make them “perfect” from the beginning?
Feb
15
awarded  Nice Answer
Feb
15
awarded  Nice Answer
Feb
15
comment How to write useful Java programs without using mutable variables
@AndresF.: More than two years of coursework in Haskell. I don't say FP is bad. However, there is a tendency in many FP-vs-IP discussions (such as the linked article) to condemn the use of re-assignable named entities (AKA variables), and to condemn without good reason or data. Unreasonable condemnation is hatred in my book. And hatred makes for really bad code.
Feb
15
comment How to write useful Java programs without using mutable variables
@AndresF.: Functional programming languages take some pride in not needing variables for most tasks, so I assume that the above functions don't need variables (as opposed to constants) to do their job.
Feb
15
comment How to write useful Java programs without using mutable variables
@Blrfl: The "behind the scenes" argument kills all language-based debates, since every piece of code is ultimately translated to x86 machine code. x86 code is not object-oriented, not procedural, not functional, not anything, but these categories are valuable tags for programming languages. Look at the language, not the implementation.
Feb
15
answered How to write useful Java programs without using mutable variables
Feb
15
comment requirements for software quality for internally developed / shared software?
The text field on StackExchange sites is not remotely large enough to hold a good answer to your question. There are shelves at your local library filled with attempted answers. Can you narrow it down?
Feb
15
answered Is it a acceptable approach to put try catch wherever null pointer exception occurs?
Feb
15
awarded  Good Answer
Feb
14
awarded  Nice Answer
Feb
14
comment Many small classes vs. logical (but) intricate inheritance
@user969153: That being said, the "reason of change" is a heuristic. It helps you to decide, nothing more.