I never wanted to be a specialist as a programmer. I always strived for the “generalist programmer” title. Know it all and do it alone. No human dependencies. All questions answered internally. The all-seeing eye in the world of tech. And guess what, I think I didn’t fail too much on it. But hear me out.

Lately I had too much time and wanted to entertain myself by making a small game. Coincidentally, the js13k 2019 game jam was about to start. It’s themed around games made for popular web browsers that would fit in 13 kB (after compressing to .zip file). Since I am not a fan of JavaScript I decided to explore a topic I was interested in for a long time. WebAssembly. What’s the state of it, how does it work and what can we expect from it by coding in C++?

Let’s say you have a project hosted somewhere and want to publish it in a production manner. Meaning, it’s gonna get SSL. But, you also don’t want to modify your host server too much so you’d use the Docker for it, right? Aaand, want to have some mini continuous deployment where a merge action to default branch on GitHub would rebuild and restart the whole thing. Let’s make this real.

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.

Serializer can detect cyclic dependencies in two essential phases:

1. inspection of data structure
2. data serialization

Let’s dig into both of them.

This is Serializing Java - emerging 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.

→ Part 1: My small secret web weapon to bind things - rivets.js

Hey, I need something. Uumm. Yeah, I need… JavaScript template engine! No? Something more? A small library that would bind data to existing DOM, locally! Yes!

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 over all the years. I’ll cover some areas that game industry should explore to improve the craft.

A collection usually contains multiple elements. Let’s pick one element to observe it. What happens if it moves inside the collection? Or disappears from it?

This is Serializing Java - emerging series about writing your own serializer in case you didn’t like other serializers.

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? When the dilemma grows it goes into: develop as it is or completely “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!

Forget Grid Layout, forget the Flexbox, remember old browsers. I’ll show an example for frontend-based relayouting. No more stupid IFs in backend templates!

Why reinventing the wheel again? Why popular serializers are useless to my project - Entity Tracker?

This is Serializing Java - emerging series about writing your own serializer in case you didn’t like other serializers.

In previous week I had to resign from using Kotlin in one of my game projects. By porting the code manually I can point out what I didn’t like about Kotlin. Let’s see few differences between Kotlin and Java.

All your Java fields belong to us. Reflection is powerful but you have to remember a few rules before dealing with class fields.

This is Serializing Java - emerging series about writing your own serializer in case you didn’t like other serializers.