Best Carrots Cake



  • 400 g carrots
  • Juice of a lemon
  • 175 ml sunflower oil
  • 400 g flour
  • Pack of baking soda
  • 2 Packs of vanilla sugar
  • 200 g sugar
  • 100 g chopped almonds
  • 1/2 table spoon cinnamon
  • 2 cm ginger
  • pinch of salt
  • powdered sugar and lime juice


  • Preheat your oven to 165°C
  • Grate the carrots and ginger and mix it with the oil and lemon juice
  • Mix all dry ingredients (flour, sugar, almonds, baking soda, vanilla sugar, cinnamon and salt) in another bowl.
  • Add the mixed dry ingredients to the carrots and mix everything thoroughly.
  • Fill everything in your cake pan and bake at 165°C for 60 minutes
  • Mix powdered sugar and lime juice to a viscous liquid and spread if over the finished cake

Vegan Beluga Lentils Curry


Ingredients for 2-3 servings:

  • 1 Onion
  • 1 Garlic
  • 1 cm fresh ginger root
  • 1 Carrot
  • 3 table spoons Coconut oil
  • 1,5 table spoons red curry paste
  • 300 g Beluga lentils
  • 1 can tomatos (chunky or whole)
  • 1 can Coconut milk
  • 550 ml vegetable stock
  • 1 sweet potato
  • 2 table spoons lime juice
  • Salt and pepper


  • Peel and chop the onions, garlic, ginger root and carrots.
  • Fry for 2 minutes. Add curry and lentils and fry for a short time
  • Add Tomatos, coconut milk and 200 ml vegetable stock.
  • Cook for 10 minutes and peel the sweet potato
  • Add sweet potato and cook for 20 minutes. Add vegetable stock periodically
  • Add lime juice. Season with salt and pepper.

Debugging Web APIs with session based authentication in Postman

  • Open the web app in Chrome or Firefox and open the Developer Tools (F12 or Ctrl+Shift+I).
  • Login and look for an API call in the Network Tab of the Developer Tools.
  • Right click the request and select Copy -> Copy as cURL
  • Open Postman and use the Import Button -> Paste Raw Text
  • You can now execute the same request as done in the browser.
  • Start modifying it and happy hacking.

Lessons learnt: First Hackathon

  • Be prepared. In my case the material was sent out a week beforehand. Use the time to setup your machine(s) and code base so you can start directly.
  • Do research on the topic. I’ve not looked into state of the art algorithms for the problem beforehand. This cost me a lot of time in the Hackathon, to understand the algorithm we used.
  • Have compute resources ready. I could have used 2 further machines, but forgot to setup ssh, Teamviewer or any other remote control on them.
  • Do whatever you know best. Some of my team members had far more experience on the topic than me. I’ve tried to follow there example, which wasn’t successful. I think I would have been more successful using more basic approaches (which I have enough knowledge about) than trying to follow the “state of the art” approach. At the end I’ve tried to support them as best as I could (mostly doing evaluations).
  • Push for more organization. We quickly came to the conclusion that only 1 or 2 approaches (transfer learning on common models) would be feasible in the short time of a hackathon. This led to us being rather unorganized. Everybody tried to get the models running as fast as possible and tweaking them the rest of the time. I think we could have produced more insight on the topic with regular “stand ups”.