technological principles
... or some echoes from Geeks’ Lair ;-)
Would you care for a giddy buzz-words stunning session?
If XHTML, CSS, RSS, DOM, XML, or Perl, JavaScript, SQL or Linux, Apache, MySQL make any sense to you then you’ll be happy to hear about our technological principles.
We are committed to Open Standards, with a high focus on Web Standards as The Web is our main communication/presentation channel.
Keeping up-to-date with ITC trends is our techies’ routine — W3C's progress, programming hypes, OSS news, etc — helping charging our “keep on evolving” principle ;-)
Interoperability, Performance, Portability, Reliability, Scalability, Security, Simplicity, Usability: key points in each and every project we develop. (Eventually The Client decides each item’s priority, so don’t blame us for arranging them in the “wrong” order).
Let's cut to the chase: how do we prefer to do things?
We like Linux. We love Perl. Web and Perl? Apache HTTPd and mod_perl.
Currently we are mostly using RedHat / Fedora Linux or FreeBSD based systems for production servers and various development workstations ranging from Microsoft Windows, Fedora/Gentoo/Debian Linux up to Apple *(Mac/Book).
On top of the above distributions there comes a myriad of perl modules, various software libraries, the Apache Web server and usually a RDBMS (often MySQL). All custom built packages are freely available in our reb00t.com repository.
If for web applications we prefer forging mod_perl & HTML::Mason based solutions, Gtk2-perl is our choice for desktop tools.
Web applications would miss a lot of their functionality without client-side scripting. But DOM scripting techniques are no secrets to us. Check some samples.
What do we do with all these thingies? NeoSystems :)
Basically, it’s just like playing some lego game on steroids. A NeoSystem is just like a “lego brick” — an useful piece for assembling creative constructions. Any NeoSystem is in fact just a plain old software project, but to whose creation process there are fancy principles attached. Hardly spectacular on first sight — coding guidelines, open design, extreme modularization (OOP/EBP methodologies mostly), mandatory API, etc — but try to imagine the joy when having around a bunch of such “bricks” which couple together like magic. :)
Interested? Ask us to work on your project, too. We're not greedy ;)