Showing posts with label evaluation. Show all posts
Showing posts with label evaluation. Show all posts

November 18, 2014

Algorithms, weather and politics

"Here I go again on my own..." as the song said. (Whitesnake for the curious ones).

It's announced a tiny-messy horrible weather pseudo storm with high speed winds, rain, and of course some lightning. And I love it! If I wasn't so determined to raise a "big" empire of software, mathematics (and maybe physics), I'd probably be studying weather algorithms. I even crushed on a few these days while waiting this storm to come. It's just fantastic. Did you know a guy could predict a storm almost two weeks before it happened back in the 18th century? (A little soon to be using iPhone or iPads while reading this article).

October 31, 2014

Improving skills. Improving the content


It's time to make things better. And i will, trust me.

I apologize if I've not been sharp enough, or detailed enough in this blog's past publications. That's gonna change now, since this blog is getting more trust, and more followers, so i am committing right here, right now, to do a trustable, decent quality, competent blog.

You may wonder what's my main subject on this blog: It's not a single thing, but a group of many. 

What you can find in here, is a day-by-day programmer's summary, along with actual subjects discussions, articles, links, and more. I use to put my personal touch on my words, and many times i try to encourage my public to keep fighting if you are on the same place i am now. That's not gonna change. But the deepness in some articles, or the sharpness in others, will adapt.

So, what's new?

October 23, 2014

A* algorithm to solve a K-th puzzle with artifical intelligence.

Climbing is sometimes rooting up around. What defines intelligence is something that can't be measured completely. As a matter of fact many sort of those exists and are well known.

What i had to do these past few days was driving me nuts. To program accordingly to a given API, 2 classes, 1 as a client, to automatically solve it and find the shortest path to the solution. This to be done in the smallest possible time. I won't say it was easy. My main problem is that i have to visualize internally what my program does, as if i was looking it at a screen, and this couldn't be done here until the very end. I didn't use the Solver Visualizer a colleague made,

September 28, 2014

Catching up

It's 7:32 in the morning, and i have just finished my algorithms assignment from Princeton University (Online assignment). It took me days to figure it out what i was failing about.
Well, to be honest those days