Skip to main content


Now here comes our offer to pull you into the robotics world:
Let us show you how to build your own robots through lectures, practical work and a competition at the end of many awards.

But we are limited to 30 people!
What are you waiting for?
Just apply via our website!!!
There you can find all the information needed.
And for those, who are already experienced in this field and want to apply for the competition only take your own robot with you and join us in RoboMAC!
We promise you lots of fun and awards.
Are you interested?
Go on reading…

From 22nd February - 1st March 2009, RoboMAC will take place at the Faculty of Electrical Engineering and Information Technologies in Skopje, Macedonia.

IEEE Student Branch Macedonia and BEST-Skopje want to give 30 engineering students the chance to apply for our 5 days training with professors from our University (23-27 February) and the competition (28 February).
For those lucky students, we will provide accommodation, food, local transportation, material for the robots, fun and much more...
Prior experience is required in one of these areas: Electronics, Programming, Automatics or, you guessed it, Robotics.

If you are not one of the lucky 30 you can apply for the competition (28 February).
We won’t leave you alone, of course, we will help you anyways with our unlimited Macedonian hospitality.
You can apply individually or as groups of 2-3 people and bring your own robots to exhibit during the competition and apply to any category that you are interested in. If you apply just for the competition that will take place on the 28th February write that under: Not listed experience.

The categories are as follows: mini-sumo, maze-solving, swarm intelligence, and humanoid. Regulations will be announced in English at

Application DL: Thursday, 29 January 2009 00:00 CET via our web-site!!!
The accepted students will be informed on the 1st February via e-mail.

You still haven't visited our site???
Open your browser and type:

Popular posts from this blog

HTML 5 data-* attributes, how to use them and why

It is always tempting to add custom attributes in HTML so that you can use the data stored there to do X. But if you do that there is no way of knowing if your HTML attribute will not be overridden in the future and used for something else and additionally you will not be writing valid HTML markup that can pass HTML 5 validator and with that you can create some very bad side effects. That is why there is a spec in HTML 5 called custom data attributes that enable number of useful features.

You may go around and read the specs, but the basic idea is very simple, you can add any attribute that starts with "data-" and that attribute will be treated as non-visible data for that attribute. By non-visible I mean that it is not something that gets rendered to the client so it does not affect the layout or style of the page, but it is there in the HTML so in no way this is private.
So let's get right into it, the following snippet is a valid HTML5 markup

<div id="aweso…

Basic Authentication with RestTemplate

Spring Rest Templates are very good way of writing REST clients. By default they work with basic HTTP so if we need to use Basic Authorization we would need to init the rest template with custom HttpClient. This way the Rest Template will automatically use Basic Auth and append to the HTTP headers "Authorization: Basic BASE64ENCODED_USER_PASS".

HttpClient client = new HttpClient(); UsernamePasswordCredentials credentials = new UsernamePasswordCredentials("USERNAME","PASS"); client.getState().setCredentials( new AuthScope("", 9090, AuthScope.ANY_REALM), credentials); CommonsClientHttpRequestFactory commons = new CommonsClientHttpRequestFactory(client); RestTemplate template = new RestTemplate(commons); SomeObject result = template.getForObject( "",SomeObject.class );

In EE application this would probably be managed by DI framework like Spring Core and only initialized once sin…

How to Not Hate JavaScript: Tips from the Frontline

This article was originally published on voxxed under,

In my work assisting teams with JavaScript related problems, I’ve noticed some common issues. If you're experiencing frustrations with the language too, this article might be of some assistance. Disclaimer: a few of my tips might be obvious to some of you, but hopefully you’ll find at least some useful nuggets of information here! These pointers are especially useful when dealing with enterprise applications and CMS solutions. This is where we have our code, the CMS code, the code from that team nobody wants to mention...and, of course, all of them are loaded asynchronously.
The Debugger Statement
This is one of the most underused features when dealing with JavaScript, especially since it’s supported by the majority of browsers. The debugger statement was part of the first edition of ECMA Script so it's been here for quite some time.