Sebastian Freundt
(aka hroptatyr)

Myself …

In real-life most of the time I destroy^Wdevelop fabulous code for Computer Algebra Systems. I'm a mathematician at the Technical University of Berlin (Germany), thus my code is fancy. ;) So on the other hand, in my _real_ real-life, I'm occupied with fancifying code of several other projects, amongst them, apparently, The One True Editor^TM.

Did I mention you can visit me along with some hardware donations? :)

My role …

My personal goal in this subtle project is to hack up some real fancy crypto cruft which'll enable SXE to have something like secure symbol content. Furthermore, I'll go to any lengths to weld SXE and postgres (actually there is no, repeat _no_ difference between them). And now that I'm currently planning my future, I'd like to add I'll certainly do some cosmetical changes to SXE, such as

• scaling SXE to use large grid/cluster computing techniques
• profiling SXE to be an effective script interpreter
• intelligentising SXE to be my personal companion bot
• establishing kinda group-lens for SXE dotfiles
• implementing the global mood-based behaviour mode

My tips …

… to always provide the fanciest code of them all:

Preparations

• close all windows -- also, and more important, close Windows >8]
• draw the curtains (the less light is there the more your inner irrationilty is enlightened)
• ensure you have loads of smokes (to cause a slight fog around sane thought clouds)
• grok some spam mails (to establish some degree of annoyance)
• read some n00bs' mailing list (to clearly spot the enemy)
• fetch some beer from the fridge (to lose the rest of your sanity)

Mind profiling

• You revise someone else's code? … Start bitching at every single line, it's probably written by a moron.
• You look at someone else's implementation? … Think over! Re-inventing the wheel is a must!
• You examine someone else's concept? … Steal the best issues and bitch loudly at the rest!
• You cooperate on common code? … Insert bugs into the other's code and get terribly steamed up about the instability!
• You revise your own code? … You look at the best code ever, just try to make it a little more best!
• You look at your own implementation? … There are definitely no errors, just unusual coincidences!
• You examine your own concept? … It is definitely fail-safe, only morons and n00bs can crash it!

Coding standards

• There is a more general way which makes things more foggy for others? … Do it!
• There is a comment on possible faults? … Delete it!
• There is an interaction with the user? … Dismantle it!
• There is a ui element which makes things obvious? … Uglify it!
• There is a documentation especially for new users? … Flush it!