Some branes need much more than one dimension.

@carlosdavidepto

You've reached 13brane.net, the web home of Carlos Davide (@carlosdavidepto).

13branet.net is a zone of the interwebs where spacetime is curvier than usual and all branes are twisted. Here you can navigate through all of the dimensions or read the various rants.

The opinions and views expressed in this website are solely my own and do not reflect official stances of any of my employers (past or future), my country, my family and friends or my pets. They should be taken with a grain of salt. And perhaps a shot of tequilla...


Latest rants:

  • 2018-12-23: 13brane's holidazed cavalcade of code shenanigans: the flavors of FizzBuzz - Days 17-24

    (Full source code for the entire series will be progressively published here, and the other days of the cavalcade are here: day 0, 1-8, 9-16) Welcome back to the last instalment of the cavalcade. This week we are going to do something evil. Something forbidden. Something so egregiously deranged it might cause uproar with religious leaders. Lo and behold, object oriented fizzbuzzing. Day 17 New tech lead is hired. Asks junior dev to convert the previous implementation of Fizzbuzz to OOP.[...]

  • 2018-12-16: 13brane's holidazed cavalcade of code shenanigans: the flavors of FizzBuzz - Days 9-16

    (Full source code for the entire series will be progressively published here, and the other days of the cavalcade are here: day 0, 1-8, 17-24) FizzBuzz is a problem that maps rather well into functional programming (at least as long as you don’t try to overcomplicate things), so it is completely appropriate that we forego all state manipulations and refuse to do anything with variables that could not be mapped directly to a let ...[...]

  • 2018-12-08: 13brane's holidazed cavalcade of code shenanigans: the flavors of FizzBuzz - Days 1-8

    (Full source code for the entire series will be progressively published here, and the other days of the cavalcade are here: day 0, 9-16, 17-24) The FizzBuzz cavalcade started with eight procedural solutions to the problem. In none of these does the code make use of anything you wouldn’t be able to code with relative ease in C or even Assembly. Simple, “straight out of college” level procedural code. Day 1 The no BS, competent junior dev approach.[...]

  •