During my time at Promotor I used a lot of different computer programming languages on different computer platforms. I learned a lot about project management and professional business conduct, as well as the difficulties of making people in different parts of the country work together in spite of tight schedules, lack of time, conflicting personal chemistry and uncertain priorities. I also had the pleasure of tutoring a pair of undergraduate students through their thesis work titled "Single sign-on in corporate web portals".
I participated in several projects designing and scaling high-throughput
WWW-based services, such as portals, one-to-one business and intranet
solutions. This included system design as well as configuration of
third-party software, hardware and sometimes even networks.
Computer programming technology that I used range from user interface
design in HTML, client-side interactivity using Javascript and Java
applets and server-side interactivity using server-side Javascript,
Java Server Pages, Java servlets and Microsofts ASP.
C and C++ were also common in the server-side
interfaces to various support systems, LDAP directories and databases.
Some examples of projects I've been involved in:
I built a NT-Service-based translation server between a call-center
solution (CallGuide) and a telephony recording system. I used Visual C++ to
program the service, TAPI to route calls, and MFC for the Windows GUI where
the user could start, stop, and configure the service.
I installed a minimal Solaris on an old Sun Netra i to run a Kerberos server
for authentication and nothing else. I never got around to do peering with
a MS Active Directory or the domain at KTH but managed to authenticate a
client and get tickets from another machine.
As a computer software consultant I were often contracted to evaluate
the technical foundation of different businessplans on the aspects of cost,
performance, timeplans and general doability. I think my reports and
comments were appreciated because such work items kept dropping in at the
most inconvenient times during the other development projects.
For some small projects (< 10 developers) I did technical project
management besides the development work. This included meeting with
customers and the project board, keeping track of system requirements and
releases, bugs and their fixes, ordering equipment and licenses,
updating system documentation and so forth.
Once I was contracted to reinforce the second-line support of a telephony
service-based call center platform, but instead of just answering calls I
introduced several improvements to the process and the working environment
for the support staff. This included choosing an issue-tracking system,
establishing a routine for communicating work-arounds for known
errors to the first-line support, notifications to customers about known
errors (e.g. in the data-networks or firewalls) with estimated repair time,
checklists for diagnosing errors, and building a knowledge-base over
sites, customers and the specifics of their systems. The total number of
issues forwarded to the second line support went from 100 per day to 10 per
day, and only a few issues per month demanded the attention of the
developers. In a few months I had rendered myself superflous and could turn my
efforts to other contracts.
Maintained by Tobias Öbrink