Dev Blog

A blog about stuff I find interesting as a developer

MVC is the Real MVP

- Divide and conquer -

And... We're back! This time I'm really relieved as the last few months were a super intensive cocktail of excitement and exhaustion. Now that it's done though I'm relieved to have passed the block on Advanced Object Oriented Programming as well as have a really cool Augemented Reality app built, tested and ready to ship to the app stores. This finally gives me some time to leave the Java for a bit and try Swift. I found this really neat series of lectures from Stanford on iTunes U and now finally I've got the time to check them out. Aside from wanting to get deeper into the native developing (statically typed and compiled), I was drawn to the big portion of the course devoted to the Model View Controller architecture. This structure really helped us develop the augmented reality app rapidly whilst keeping things clear and scalable. For the View we used React-Native, for the Model Redux and for the Controllers we made classes with static functions. Because these functions are static we make sure the Controllers only deal with logic and all updates are dispatched to the Redux store. By doing this we keep the app neat and tidy whilst keeping state neatly in one place. When a View receives an event that needs dealing with outside a simple component we can just call the Controller and continue business as usual until the Model updates and React re-renders the view. It's a very nice architecture and I'm excited to see how they use it at Stanford in the world of Swift. 🤓

Divide and conquer

Exciting times and interesting endeavours

- Pick your own pieces puzzle -

Things are going really well and I’m really happy. It’s good to remember once in a while that the main (if not only reason) to code is probably because it’s just super fun and rewarding to stick at something until it works. Be it an Arduino, an app or a data pipeline, it's like doing a puzzle where you get to pick your own pieces. I’m particularly chipper however because as of last week I also started working at Rotterdam’s premiere Creative Digital Agency: IN10. It’s pretty astounding to see the perfect match between their cultural and creative projects, technology stack and my passions and ambitions. Asides from this there is the spot of good luck that they let me get cracking on a React-native app they are building for the Kinderdijk windmills. This is great as I’ve spent the last few months exclusively studying on Object Orientation structures and doing a React & Redux course on the side. Now I get to combine the studies in practice whilst tinkering with this amazing app that even incorporates augmented reality and will be enjoyed by people from Korea to Copenhagen. Amazingly this app is built for the two concurrent app platforms using their respective native codes - Java and Swift - and all from one code base written solely in JS. It’s not as easy as copy-pasting what you learned on the web, but with a bit of React or Vue experience, React-native really does let you get you apps deployed in record time. You can check out the app right now by looking for Kinderdijk in the App-store. Again thanks for reading and talk to you soon 🤓

Pick your own pieces puzzle

Test-Driven Development

- Take your app for a test-drive -

Now that I have gotten properly stuck into Java and enjoyed making multiple code challenges for the University, I’m really happy to share what I have learned about test-driven development. It’s funny that even though Java is the strictest language I’ve ever used, our goal is now to it even stricter by also enforcing semantic logic through tests. This practice has been a complete eye-opener and I really think it has to be a part of any solid code project. Just to give a bit of background: test driven development sets out to first define and write tests for all the things you do not want to happen in your app. You write these seemingly simple tests that control for code that is perfectly valid on a syntax level a.k.a. the compiler gobbles it up no problem, but that that does insane things on semantic a.k.a. on a real-world level does strange stuff. A nice example is when I was modelling a simple bank transaction and I had built in a test to make sure that if a customer did not have funds greater than 0 after transaction, the transaction would not go through. Funnily enough I had placed the test to high up in the transaction process which had the nasty side-effect of also apply to incoming transfers. This meant that a customer with say €20 could not receive €2000 because 20 - 2000 < 0. Building in tests that check for things as simple as this constantly helps not only yourself as your application grows and you lose sight of the details you were focussed on weeks or months ago. It also offers an amazing support to developers who may come in years later and write code that could undermine the goals you set out to solve.

Take your app for a test-drive

Keeping State Up To Date in React

- The Christmas Holiday Catch up -

So the first block is done and I've learned a lot of interesting insights into modularity in software design. So as a small holiday break I thought it would be nice to learn more about the React JavaScript library and how it uses components and classes to manage state. A lot of the basics that have been laid down by Java 25 years ago are still in use today and have been adapted to different languages such as JavaScript for use in frameworks like React and Vue. However, there is also a big push now for languages such as Haskell that completely abandon the OO setup and opt for a functional style. In this post I thought I would share some insights into my research of OO, Functional and the React library I have been toying with. Even though JavaScript is not a strictly OO language the current release of ES6 added the “syntactic sugar” that makes class based definitions and import and export statements really easy, especially on the backend. Along with the new spec you saw an even sharper rise the popularity of the frameworks as React, Vue and Angular (even though Angular builds on TypeScript). I think this is at least partially because the maintainers of the language showed that they were incorporating the direction that the developers where pushing for: a more modular, backend capable, OO version of JS. Now for all the praise I like to foster on the benefits of properly splitting up, encapsulating and managing state in an OO fashion, there is a huge trend online now to put it down. On the one hand this is just the kind of typical echo chamber of condescension you always get when something becomes so mainstream that being against it is the hip thing to be, but on the other hand there a a lot of legitimate drawbacks to OO that I do think have merit to mention. In one youtube video that has become quite infamous - - Brian Will explains that the foundations of OO sound good, but only hold up to the basic degree that you can explain a class as a metaphor (warning: wildly simplifying his view here). Watch the whole video to get a way better explanation, but in short he is saying that we humans like OO because our minds are OO, we see the world and interact with it in this way. But actually computers have no such conception and what we are doing is forcing our perspective on them in a way that stops being useful when the concepts we are modelling surpass the complexity of the visual physical world around us. The solution he proposes is a kind of combination between OO and functional, which is kind of obvious considering the ubiquity of OO and the (currently) niche needs for the functional paradigm. I feel the need is most apparent in data science and machine learning, but none the less it set me to thinking about OO in React. Half way into the video - - he brings up his serious gripes with “encapsulation” and how state is managed in OO. He goes about explaining really well how a system that starts of simply enough soon evolves to a point where objects are starting to have send parameters or references along with their requests, so that in turn the system is actually working not as a set of individual and independent nodes, but in a kind of hot mess of interdependence. The funny part I think is that when he addresses the solution, he basically explains exactly how React works. The solution is obviously to “lift the state” up the hierarchy to the point at which both objects (or components) can get an instruction from a common ancestor as to what the state of the system is. In React this happens very beautifully because you can define components either as a class or as a function. When I make this setup I just pass the call back to managing the state to the respective components as a prop and when one of them is called on by a user to change something, they are actually calling the root function. Anyway, I thought it was an interesting example of how things never really change when it comes to programming. Even when they do. Thanks for reading 🤓

The Christmas Holiday Catch up

Agile Use Cases

- Modelling much? -

After getting into the groove of modeling everything as attribute-only classes in domain models, we are now looking at extracting methods from use cases and creating sequence diagrams to model the communication between objects in a system. Just to recap the impressive speed of the stuff we are learning: in two sessions we have passed from the basic concept of objects instantiated from classes, to seeing how we can model the classes in a domain models and class diagrams along with object diagrams and sequence models. What I found a particularly interesting exercise was defining proper use cases and thendeducting methods from these use cases. It's surprisingly tricky to succinctly describe the functionality of a system without becoming too specific for a use case. The exercise is particularly good though, because often you will find yourself developing in a diverse team with different skillsets. Being able to clearly define use cases, is already helping me better agree with the instructional designers on the requirements and functionality that I need to develop. As for the UML notation, it's pretty tedious and I wonder how often I will encounter it in the wild, but I think for enterprises it's definitely a good tool to track, coordinate and document development. UML can definitely help to do this comprehensively and without too much overhead. It would be great to see a UML diagram for something like the Django framework just to get a quick overview of how the application is setup. In summary, I'm really impressed with the amount of tools and techniques there are to model systems. I think they take quite a bit of legwork up front, but are definitely a good way to save a lot of headaches down the road.

Modelling much?

Everything is an object

- Why we are surrounded by objects (for now)... -

In this first week of self study for the Java Certification the material has focussed on some basic tools and practices to map the world our us in the Unified Modelling Language. This is a very perspective to think about as you start getting really philosophical really quick. In Object Oriented Programming every Object is instantiated or constructed from a Class. This Class is like the essential idea of an Object. Sounds pretty vague at first but anyone who has had a 101 in Philosophy in high school will quickly recognise Plato's cave. Take for instance the chair you are sitting on right now. You know it's a chair because it has four legs and a flat bit you can sit on, maybe it even has upholstery but it doesn't have to. It Could also be a chair if it had one leg or 10, as long as you could sit on it it would be a chair. This idea of kind of pealing away the Attributes from an Object until you get to a Class is what I've been getting to grips with this week. An important key for this process (and your sanity) is to keep a keen eye on the system you are trying to model so you don't start tying to exhaustively trying to Model every single Attribute of the world around us in a system. An interesting thing I have also come across lately online is a sense of cynicism on the future of Object Oriented Programming and how it's going to be replaced by Functional Programming. Having just started the study these aren't exactly the headlines that cause you to jump up and down clapping, but after having read in to it a bit I got quite excited. Functional programming seems to complement Object Oriented in that it can offer better concurrency and multi threading when dealing with heavy data processing. This has lead to a myriad of languages springing up to offer a sound basis for these concepts. Some like Scala build on Java other like Haskell take a fully functional approach. Obviously nothing is going to replace anything, there are just more and more techniques and tools being developed to solve different challenges. As a student I'm obviously eager to learn and in the future I will surely turn my attention to FP but for now it's fine to focus on the paradigm that has lead the last 30 years of computer programming and rests at the core of pretty much every electronic device in the world today. One thing is for sure; I've still got a little ways to go until I master OOP to such a degree that I need the benefits of FP for multi-threading my heavy data processing 🤓

Why we are surrounded by objects (for now)...

Java Dev: Day One

- An exciting challenge and a great place to start a blog -

So last Thursday the time had finally come to start a new challenge and take the train to Utrecht for the introduction session of the Java Certified Developer course of the Open University. After months of weighing the pro's and con's of committing to a study that would require 1,5 years, significant study hours and a tidy sum of money, the moment was finally there to see if it was all going to be worthwhile. I'm glad to say it definitely is. There is of course quite little to say about a whole course just based on the first session, but as the instructor sketched his fields of interest (encryption, privacy and eHealth amongst others) and laid out the structure, I knew this was going to be a really cool challenge. After the first session I decided to start a blog on my experiences to keep track of all the things I learn from UML modelling to advanced object oriented programming - through data structures and algorithms - to the app lab with colleagues who specialise in everything from network architecture on trains to banking apps. So in short this blog is the first instalment of a series in which I will try to some up and condense the interesting stuff I learn along the way to becoming a certified Java developer. In doing so I will try to give some insights into the why's and how's of Java and how the new knowledge fits in with the skills I have already built up while focussing mainly on the front-end and JavaScript. For one (and if you got this far I'm guessing you already knew this) but Java and JavaScript are not the same thing. That doesn't mean they don't share similarities, ECMAScript 2015 introduced a form of Class into JavaScript, but in essence the languages a constructed very differently. One thing is for sure: Java is way more verbose as everything is statically typed. This make the code seem more daunting to a novice developer (me). I'm still getting used to the thicker syntax but I do see the advantages and even necessity for enterprise stacks. In dynamically typed languages like JavaScript and Python you let the interpreter figure out what kind of variable you a declaring. I can imagine this becoming increasingly confusing when a return function gives back a 0 or undefined the JavaScript interpreter inferring this as a False. Anyway, for now we are still on getting to grips with the concepts of class, object, encapsulation and inheritance so no need to worry about all that just yet. Thanks for reading this - I'm back to the books 🤓

An exciting challenge and a great place to start a blog