Contact

  • Email
    • primary: patrik.svestka [at] gmail[dot]com
    • secondary: patrik.svestka [at] svestka[dot]biz
  • My always incomplete Curriculum Vitae (CV)

Little bit about my interests

  • I love to dig deep into interesting problems and try find solutions.

  • One should always try to find an best solution for the given time. Don’t compromise on quality because in the end it will come back to haunt you.

  • I love with Smalltalk, but I think it needs to move out of its shadow - there were many new developments during the last 40 years and Smalltalk should reflect that.

Smalltalk has had a difficult history. First of all, it has been born way ahead of its time. It has met many obstacles (like IBM implementing it and then leaving it be) on its way but it is still alive today, but the number of programmers are diminishing.

These are my ideas what needs to be done for the Smalltalk to flourish again:

1) Create new Smalltalk projects
2) Predictable development cycle and standardization
3) The development environment must be stable - every crash should be examined and fixed
4) Some great ideas at that time should be innovated - yes, image I'm talking about you, use CVS (e.g. mercurial or git), etc.
5) Release code and libraries under open-source license like MIT
6) Every bug in the VM or core libraries should be fixed as a priority
7) New features can be added after the VM and the core libraries are stable
8) New features should bring considerable improvement(s) or add some missing functionality and must not break the old code
9) No tests = no merge -> Every code written should be properly tested with test cases and have documentation
10) The Smalltalk community should be welcoming to the newcomers + experienced programmers should be nurtured and valued

Where to get help with Smalltalk

If you have a question on Smalltalk don’t hesitate to ask on Stackoverflow