DDevelopment & Design

Friday hackathon

Every month we have a Friday Hackathon, where we can code or create anything we want. That’s for the purpose of evaluating new technologies, doing crazy stuff or just having fun.

Beneath that we develop our skills and gain new experience.

Today we have 5 teams, that are doing following projects in various technologies:

  • Ping-pong scoring – we play ping pong a lot, so an app is a must! – Java (Dropwizard), Mongo
  • TouK’s library – we have dozens of books but currently we have a chaos who lends what – Clojure
  • ToukApi – access all internal data (about people, salaries, holidays, auth, projects people are in etc) through REST api – vert.x
  • ID / Drivers license recognition on Mobile – just shoot a photo of an ID and have all data and photo in a few seconds – Kotlin, Android
  • jaIde – I’m going for a sandwich – you can inform other employees that you go for a morning sandwich – that means – Mr Sandwich has just arrived at the kitchen – it’s like a snowball, the more people go for a sandwich the more confident you can be that there are actually sandwiches waiting :) – Swift/Scala/Java

At 4:30 PM we have hackathon summary. Let’s see what projects we will manage to accomplish…

 

rd

DSC_3057 DSC_3056

— Previous article

How to recover after Hibernate's OptimisticLockException

Next article —

Kotlin's extensions for each class

You May Also Like
DDevelopment & Design

33rd Degree day 3 review

At the last day of the conference, I've decided to skip the first presentations, and get some sleep instead. I was afraid that Venkat's show is going to be too basic, I will see Jacek Laskowski talking about closure at 4Developers, which I'm kind of s...
DDevelopment & Design

Context menu or Action buttons ?

Recently I was drawn into one of those UI "religious" disputes that has no easy answers and usually both sides are right. One of our web developers was trying out new web tech (with pretty rich widget library) and started to question himself about some basic usability decisions. The low level problem in this case is usually brought to "which widget should I use ?". I'm not fond of bringing the usability problems to questions: Should I use Tabs over Menu ? Or should I use Context menu instead of buttons panel ? But sometimes if time is crucial factor and other usability levels are by default not addressed at all - better developer that asks those basic questions than developer that do not question himself at all.