@Opiop glad to hear that!
hm, we need new line near profile:
Give away Medals: xxx
^^
Finished level 25 of 0xf.at just to come back and see the site down :’(
uploaded another random screen capture to youtubes.
i call it “brute force cpu reference 512 rays per voxel face progressiv refined by frustum in 8 rays packs occlusion raytracing”.
even with the progressive refining it runs at 3 to 4 kk rays/sec over a 1024^3 space. which is not too bad i guess. usable for tree-preprocessing or background updates, maybe not that strongly visible but that gave me a good insight into the algorithm. it’s no cone-tracing, noise goes away when cranking up to 8k rays per face, which is too much
the pause at the end was actually a breakpoint which if forgot to remove, silly me.
C7aGIqEOXrwMmB9b5njVbA
Went to IGDA gathering and had a beer with the face of Max Payne (Sami Järvi) and other Game developers. So yeah. Today was a good day 8)
Finally got around to working on my non-existent web development skills :).
Learning project 1: ‘Welp’
I learned how to use some of Express, Node.js, Nginx and others. Very fun; I will probably work on this more in the future.
Having a car is pretty cool.
It’s a super fun place with a lot of work too. It has and is changing fast. Almost too fast even.
Pretty solid backend tools those you listed - they work well together. Careful when jumping into front-end with the myriad of frameworks available (most of which are basically new programming languages in themselves) - learn the basics first (i.e., stay away from front-end frameworks).
Also unless you locally have something similar installed you may find this helpful: http://devdocs.io/
Working with the backend is also a good time to get familiar with Vim. It may or may not change your life forever.
Went and got contacts today (also ordered red tinted aviators ), and now it’s hard to keep my eyes focused on my monitors at work… today was supposed to be refactoring day but oh lord this is hard! Almost crashed a couple times coming in to work today because my depth perception is completely wacky!
@Opiop
Hah I know how that is! I first got contacts a few years ago and it took a few days to adjust. Now I most definitely prefer them to glass, but make sure you don’t keep them in for too long… your eyes get incredibly dry after a full day
@ra4king
I’ve actually had contacts a couple of times! Tried them out when I was a lot younger and hated sticking my finger so close to my eye so I gave up I think this is my 3rd or 4th time going back to them, I’m finally comfortable with them and it’s a great feeling! Glasses are ok, but contacts are far better IMO and the level of definition that you can see is just… astounding!
Luckily my eyes are adjusting pretty good, I’m still having a little trouble with reading text on my monitor but everything else is crystal clear
Been working more on my game. Ladders fully working. Got tiles and objects set up so adding more of them and making them function will be a breeze.
What program are you guys using to record your GIFs? I cba to use camtasia for simple things like that. Lol.
Ah thanks, appreciated.
Since monday I’m studying again. This time it is Human-Centered Computing to get my Master’s degree.
The difference between a Bachelor’s course and the Master’s course is amazing
Now I can finally work with high end technology. The Bachelor’s course was merely the basics.
Looking forward to work in the virtual reality lab!
Found some nice syntactic sugar in Java today:
int example = 0;
switch(example) {
case 0:
case 1:
case 2:
doThis();
break;
case 3:
case 4:
dotThat();
break;
...
}
Don’t know how I never came across this, but cases ‘0’, ‘1’, and ‘2’ will execute ‘doThis()’ (provided the variable we are switching on evaluates to that case of course), while ‘3’ and ‘4’ will execute ‘doThat()’. Really saved me some time today when I ran into a situation where this was very useful!
Also bought some red-tinted aviators, I like to think I look like this infamous movie character :

Found some nice syntactic sugar in Java today:
[snip]
In addition, you can also do some cool things like this:
int example = 0;
switch(example) {
case 0:
doThisSpecialThing();
case 1:
case 2:
doThis();
break;
case 3:
doThatSpecialThing();
case 4:
doThat();
break;
...
}
In this case, 0 will call [icode]doThisSpecialThing();[/icode] then [icode]doThis();[/icode], while 1 & 2 will just call [icode]doThis();[/icode]. Same with how 3 will call [icode]doThatSpecialThing();[/icode] then [icode]doThat();[/icode] while 4 will just call [icode]doThat();[/icode].
Switch-case “fall-through” is generally possible, yes, and attributed to the way it is implemented in native code from the native language it was borrowed from, C, but generally this would be considered bad practice, because it is easier to understand when each case is isolated in behaviour from all other cases and no case can magically be reached by fall-though from other cases above it.
The Eclipse IDE for once (and I am sure others too) has the option to flag this as “Potential programming problems.”
In my opinion, fall-through should not be adopted and excercised by programmers.
falling through in a rather large set of programming problems makes the code easier to read, write, maintain and faster. Classic example is state-machine related.
Agreed on all points except “easier to read/understand.” And imho state machines, like a language parser, should not be hand-written but generated from another easier to understand representation.