DEV Community: Kodengo

Clean code gamified

Kodengo — Mon, 27 Aug 2018 15:02:56 +0000

invert a random if statement
run the unit tests
if the tests pass, drink

Rock bandify your team

Kodengo — Wed, 15 Aug 2018 09:42:57 +0000

What would be the codified rock band name of your team?

I'm thinking "The cyclic dependencies", "The unclosed brackets".

I've added karaoke and firebreathing to my linkedin skills.

Kodengo — Wed, 20 Jun 2018 15:38:18 +0000

None of the recruiters or companies that contact me ever have questions on any of these topics. Is anyone actually reading stuff on linkedin profiles?

If your project was to be linked to an art style, which one would it be?

Kodengo — Thu, 14 Jun 2018 06:21:09 +0000

At the moment I have a Baroque one in front of me.

How long does it take to build your project?

Kodengo — Mon, 28 May 2018 19:45:39 +0000

A project I'm currently working on takes around 2.5h to build. That's mostly because the code base is huge (1.2m LOC) and the tests are mostly slow. The coverage isn't even that big (around 20% unit and ITs).

Whats the build time of the projects you are working on?

How do you feel, and whats your reaction when people are referred to as "Resources"?

Kodengo — Thu, 17 May 2018 07:58:44 +0000

A recruiter sends you a job proposal with "URGENT" in the subject. What do you think and how do you respond?

Kodengo — Wed, 02 May 2018 06:34:15 +0000

What is architecture?

Kodengo — Fri, 27 Apr 2018 17:57:44 +0000

Let me setup the database migration for the deployer of the code generator for the class for summing integers.

Kodengo — Wed, 25 Apr 2018 06:46:29 +0000

How do you know if you have overengineered a solution?

Should bugs be discovered in a code review?

Kodengo — Mon, 23 Apr 2018 12:40:13 +0000

On a project I've worked on, a lot of effort was put into verifying that the code in the merge request was bug free.
This meant that when doing code reviews one would not just review the code structure, class responsibilities, code readability etc, but also the correctness of the code logic.
In my opinion the code logic and code behavior should be described and documented in the automation tests making the code review all about the code, and not about the business.

I would appreciate your thoughts on this.

Are you aware of the performance capabilities of the system you build?

Kodengo — Mon, 23 Apr 2018 10:34:07 +0000

Working on different systems, more often than not I see that the performance capabilities of the system are either not clearly visible and defined or they are completely missing.
A lot of the developers developing features are not aware of the impact their code does to performance. By Impact I mean visible numbers of the load the system can take that go together with every build.

So the question here is:

Is performance testing your system a part of the continuous delivery pipeline or is it done as a periodical effort separated of the release process?

Whats the most irritating "if statement condition" that you've come across?

Kodengo — Thu, 12 Apr 2018 19:56:24 +0000

Inspired by the Pinocchio's discussion with prince charming in "Shrek":

Prince Charming: You! You can't lie. So tell me, puppet, where is Shrek?
Pinocchio: Uh, I don't know where he's not.
Prince Charming: You're telling me you don't know where Shrek is?
Pinocchio: It wouldn't be inaccurate to assume that I couldn't exactly not say that it is or isn't almost partially incorrect.