Skip to main content

a walk in the dark side

Previously I got my first version of simple todo rest service working with scala and play framework and had some ideas what to do next. Since then I've implemented a second version of the rest service, this time backed by MongoDB. I also managed to create a simple web application as a user interface for the service.


TL;DR;


https://github.com/jorilytter/simple-todo/tree/mongodb-integration
https://github.com/jorilytter/simple-todo-ui


MongoDB with scala


This was a idea that I had earlier and the actual implementation was pretty straightforward with the help of salat library. Integrating salat with play framework required me to implement a custom context but salat documentation already provided this solution so it was just a matter of reading the documentation.

Other issue that I faced was with reading and writing json documents but that's where play's documentation provided the needed answers after some initial searches with google.

Like before the implementation is shared at my github account https://github.com/jorilytter/simple-todo/tree/mongodb-integration.


Walking in the dark side


It's been a long time since I've done anything related to user interfaces let alone created one from the scratch. I had decided that my todo application will have a user interface and it will be done with something out of my comfort zone.

The idea had been in my head for a while. I've seen and heard how modern javascript frameworks can do pretty nice things and easily interact with rest services. I asked my colleagues what was the hip javascript framework for interacting with rest services and got to work.

The choice was AngularJS as I was told that rest integration with it would be easy to implement. Sure the implementation was easy after series of trial and error and the fact that AngularJS is evolving fast also means that Q&A found in various blogs or at stackoverflow were partly outdated even if they were just a few months old.

I don't believe my implementation follows the best practices but with my lack of expertise with javascript I'm just happy I got it working.

This is also shared at my github account https://github.com/jorilytter/simple-todo-ui. If you feel the need to comment please be gentle, as I said this is way off my comfort zone.

In the end I'm happy that I went out of my comfort zone and actually managed to get something that works and I'm definitely going to do it again.
Labels:

Popular posts from this blog

Simple code: Naming things

There are two hard things in programming and naming is one them. If you don't believe me ask Martin Fowler https://www.martinfowler.com/bliki/TwoHardThings.html . In this post I'll be covering some general conventions for naming things to improve readability and understandabilty of the code. There are lots of things that need a name in programming. Starting from higher abstractions to lower we need to name a project, API or library, we probably need to name the source code repository, when we get to the code we need to name our modules or packages, we give names to classes, objects, interfaces and in those we name our functions or methods and within those we name our variables. Overall a lot of things to name. TLDR; Basic rule There's a single basic convention to follow to achiveve better, more descriptive naming of things. Give it a meaningful name i.e. don't use shorthands like gen or single letter variables like a, x, z instead tell what it represents, what it does...
Read more

DIY home automation, new generation

I've had my DIY home automation system for controlling outlets and reading sensor data running for about two years now. The system has been working fine and I haven't had any need to touch the code since I added the sensor reading to it, until a few months back. Need for new functionality Few months ago I got a new IoT toy for a lend from a friend until I'd get my own toys, a ruuvitag sensor beacon. Ever since I found the ruuvitag for the first time from kickstarter I had the idea of getting a bunch of ruuvitags and adding their weather station sensor readings as part of my home automation system. The original home automation backend included only tellstick compatible devices and was written in Python, and in my mind it was kind of a hack. The ruuvitag beacons communicate via BLE i.e. Bluetooth Low Energy and that meant that I needed to add functionality to read the beacon data via bluetooth. I found a ruuvitag Python library and initially thought that I'd just...
Read more

Simple code: Unit tests

Unit tests are the developers number one safety net. Let that sink in. This is the number one reason for writing unit tests. Unit tests are written by developers for developers to ensure that the code works as expected and handles happy and sad paths correctly. With enough unit test coverage the tests enable a safe environment for refactoring and rewriting code. Unit test scope Unit test should test a single thing, a method or function call and it should test only one use case within. In other words a unit test should test a function with a single input. This is a important guideline to understand. When a unit test tests a function with single input it makes the test isolated, repeatable and predictable. Example of good tests: @Test fun findsAddress() {   val address = findAddress("Stevens street 35", "Southport", "Australia")   assertThat(address).isNotNull() } @Test fun doesNotFindAddress() {   val address = findAddress("Stevens street 697", ...
Read more