April Update @ MIC UPB

Hello everybody ! We are super excited with what we accomplished this month, check out below. Stay tuned on this blog, check us out on Facebook and star the microsoft-dx organization on Github.

01. [MS Monday] C# Clean Coding Conventions

After the introduction in the clean code design workshop held in March, Oana continued to present various benefits of writing clean code, such as the clearance of the code, the low level of struggle that other people put in understanding your code – which is why this workshop was held, so that people start writing good, understandable code so that future readers/programmers can find it very easy to update and develop further their code. to It is very important to be a great developer – and that includes being a lot of things, not only to solve problems, one among which is to write good code. But what does it mean a code is good or bad? A bad code doesn’t try to kill anything (actually a good code kills bugs) and yet you have to understand what a bad code means so that you make your code better.

In the IT industry the way we write code is our signature, how other people from it see us. Think of it as your handwriting – how are appreciated bad hand writers and how good are those who write beautifully? Nobody likes a sloppy handwriting, with grammatical mistake – so why be that guy or girl?

After a little reminder of different principles discussed before (such as Lower Camel Case or Upper Camel Case) with many examples and parallels made between good and write code, the two series of about 25 to 30 students really started to realize how much bad code they used to write. They started asking a lot of questions and giving scenarios, too which Oana answered clearly and detailed so that it fold to other related scenarios.

After a short break, the students returned to their seats and Oana started talking about Design Patterns giving examples and explaining how they play a huge role in clean code – as mentioned before, writing good code is not just about the appearance of the code or how indented is, it’s more about the way every issue and special case is treated, and most important how concise and consistent.

Everything from how every type of special case and initial case should be treated the same, to how every class should be written and instantiated or constructor declared and use, all that is included in writing good code – especially using design patterns

Al the students were very excited about the last part which was a quick demo where they were able to clean a very bad code and apply what they have learnt in the theoretical part of the workshop, but also find other scenarios where they can clean, optimize and develop better and cleaner code.

02. [MS Monday] ImagineCup Presentation

In April, Radu Stefan, Technical Evangelist at Microsoft held a presentation about Imagine Cup. The event focused on delivering valuable information to the teams participated from the Politehnica University of Bucharest about registering, participating, key points of the presentation and so on.

Radu Matei made a brief introduction of Imagine Cup and set the scene for the rest of the event, where Radu Stefan went through all stages of the competition, from online registering to participating in the Seattle World Finals, which helped a team from our University going all the way to the Word Finals.

At the end of the event, we discussed with the interested teams about technical aspects of their ideas and real-life implementation using Microsoft Technologies. The key points of the discussion were Azure the Microsoft Cognitive Services.


03. [MS Monday] ImagineCup 2016

At the 2016 Imagine Cup National Finals, the Microsoft Innovation Center provided both support in marketing the event in the University and several teams that qualified and participated.

Microsoft Innovation Center’s members were very prepared with information about the event, as the whole year we presented it to different students who seemed very interested in it.

Our team presented Imagine Cup during the entire academic year in our faculty, during all the workshops and presentations we held in our laboratory (especially during Microsoft Monday sessions, where we gave details from our prior experience with the event).

We hosted an event where a member from the DX team (Radu Stefan) officially presented the competition, the rules and all necessary steps required to register and have a great presentation.

Our Innovation Center sent 9 teams (at least one in the team was part of the Innovation Center) to the National Finals, and while none of these teams managed to qualify for the Semifinals, all of them had plenty of great experiences, and lots to learn from them, and will definitely start working for the 2017 Finals.

The topics of the teams’ products varied from assistive technology for the blind (Interface), smartwatch for seniors that detects falls (AlertPlus), platforms for farmers (Farmers), social help apps (CodeJunkies), a social network for sports enthusiasts (Ludicon), all of them who received valuable feedback from the jury and will implement it in future ideas.


04. [MS Monday] Polifest

Between 20-22 April, 2016 the Microsoft Innovation Center team participated actively at Polifest 2016. An event at our university at which all the faculties and student organizations are being presented for potential future students.

With the help of LSAC (the students’ league) our lab and organization was included in the hourly tours they offered. Groups of high school students were brought in the lab and one or two members of the team would tell them about our organization, the events that take place there (Microsoft Week, Microsoft Monday, Microsoft Academy courses).

They were also told about the tech talks, hackathons and more important contests we participate at every year (Imagine Cup, Innovation Labs) and past projects.
We also had giveaways (hats, glasses, notebooks) for those who were able to answer some of our trivia questions about Microsoft and showed enthusiasm during the event.


About MIC Team

Leave a Reply

Your email address will not be published. Required fields are marked *