In the “Get Noticed 2016” competition (original name in polish: Daj Się Poznać) I wanted to prove myself and people around that I can work hard for 3 months after hours. This year I started just because of desire to participate socially and meet people in the end of the competition. Also, this year I’ve gained a new perspective.
Everytime you think of Java you may think about types as of classes and primitive types. Not many, right? Well, there’s a major difference between the thing and handling it. The latter brings a lot of corner cases.
This is Serializing Java – a series about writing your own serializer in case you didn’t like other serializers.
This is the 2nd part of knowledge about rivets.js – a small JS library that binds data in web. While the first one was an introduction, this one treats about the details.
rivets.js – it’s not too popular but it works and it’s only 26 KB minified without gzipping (which would go to just 6 KB!). Let’s go through it’s features and see some snippets I’ve developed through few months.
Game development carries multiple issues about coding. I’ll cover some areas that game industry should explore to improve gamedev craft.
I have stopped using Angular 2 in the beginning of this year – near before the Angular 4 release. I’m not trying to convince anyone about the future but I’d like to express my thoughts after gaining some experience. Not only about syntax and performance but about whole thing as a development tool.
Every deserializer needs information about types – the data structure. In my serialization the deserializer can work behind network connection so it can’t count on Reflection mechanism. That’s why the serializer has to discover and serialize data structure that could be sent over the network and understood by deserializer.
This is Serializing Java – emerging series about writing your own serializer in case you didn’t like other serializers.
I needed tabs that would not be destroyed by Angular. As powerful as if I would code a normal application for Windows in C#. Here’s my solution.
Ideal programming language? What if we started from beginning having knowledge of current past? Throwing away “backwards-compability” to the furthest extends?
While coding we meet sometimes one of our deamons: should I refactor what I see? The dilemma: develop as it is or “rewrite” it?
Do operators have to be common between programming languages? Or do we even need symbols for adding numbers together? Let’s look at some weird differences!