Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Nadaka]

Shitdamn... I've completely forgotten the path to my own svn repo, and I no longer have any links to it.  I can log into the server, but I don't know how to get the information out of the damn thing.

woot. I spoke to soon. I HAVE NOT! Lost access the code for my abandoned projects.

[MadocComadrin]

So, here's a question for the professional programmers that visit here: Web resume: Yay or nay? (...in addition to the traditional paper resume)

[Nadaka]

So, here's a question for the professional programmers that visit here: Web resume: Yay or nay? (...in addition to the traditional paper resume)

Have your resume on linkedin as well as in a word document.

Have a short 1 page resume that hits the highlights. And have a full resume with details of jobs and projects, this one should come in at 2 to 4 pages but not more.

Hosting it on a website or file server is not necessary. Recruiters can find your resume on linkedin if you make it public, and otherwise you would just be emailing the word doc to people you are trying get a job from. Paper resume's only really have a place these days at job fairs.

[Skyrunner]

I am trying OpenCL right now.

My current state of mind can be best represented by my avatar. "What is going on I don't even help aghghh stay calm stay calm-"

>_> For some reason, using the CL_DEVICE_TYPE_DEFAULT makes it correct, but CL_DEVICE_TYPE_GPU yields incorrect answers and I can't tell why. It may be because of how the tutorial writer set up his C code, but I can't really tell. :S

[MagmaMcFry]

I am trying OpenCL right now.

Making your erosion simulation massively parallel you are?

[Skyrunner]

Yeah. It's already easy to parallelize, but I kinda broke myself over openCL. It has the worst documentation ever. And the C-style code doesn't help, since I'm not used to it ;_; High level languages spoil ya :v

Anyways, I'll try again whenever I have time. No idea when that'll be ;_; I can't tell why openCL code seems so tangled and hard to understand... And also so much boilerplate.

[olemars]

Cuda has a nicer and better documented API, if you have an NVIDIA gpu that is. Faster than openCL too.

[Max White]

You know, I noticed Magma did something in his game that I kind of like, and I'm wondering if anybody has any good reason for me to not use it. Basically using singleton, but having static methods wrapped around the instance object, a very quick example

Code: [Select]

class Example
{
private static Example _instance;
private static Example getInstance()
{
if(_instance == null) _instance = new Example ();
return _instance;
}

private int x;
private Example ()
{
this.x = 5;
}

public static int GetX()
{
return getInstance().getX();
}

private int getX()
{
return this.x;
}
}
I can still have all the advantages that singleton has over static classes, but I can just call Example.GetX() rather than having to always refer to the instance.
Why should I not do this?

[MorleyDev]

Well the implementation there isn't thread-safe, but that aside this is still a fairly standard singleton implementation. You still have all the pros and cons that go along with a singleton, though you do have a lot of what is essentially code duplication.

I'd recommend having the instance as just being a POCO/POJO the static functions use, to remove that duplication. Basically the instance is just a POCO/POJO that contains all the static variables.

[Max White]

Well yea, that one isn't tread safe, but it could easily be safed. I just wrote it up quickly without any thrills to make it as c#/java ambiguous as I could. I'm pretty sure that example would compile in both.
Although I did use c# naming convention...

As for code duplication, if I need a more complex method other than just returning a value, I have keep it all in the non-static method, so they won't be an issue.

[MorleyDev]

As for code duplication, if I need a more complex method other than just returning a value, I have keep it all in the non-static method, so they won't be an issue.

Then you have a bunch of private functions that exist just to be called internally without actually increasing clarity or readability, seems like just adding pointless extra jumps to me.

So more like:

Code: [Select]

class Example
{
private class Instance
{
public Instance()
{
X = 5;
}

public int X { get; set; }
}

private static Instance _instance;
private static Instance getInstance()
{
if( _instance == null )
_instance = new Example ();
return _instance;
}


public static int GetX()
{
return getInstance().X;
}

public static int GetDoubleX()
{
return getInstance().X * 2;
}
}
( And of course I'd always question the situations where you think you gain from using a singleton instead of an injected dependency...should be a very rare thing imho )

[Max White]

Often for inheritance. In the above example I can't sneakily use a subclass of Example to change the function of GetDoubleX(), but if GetDoubleX() returned the value of non-static getDoubleX() I can do as I like.

[MorleyDev]

Kinda seems like it's over-engineering a solution to a problem better solved by interfaces and dependency injection, but if you really think you need the singleton then yeah that's a valid reason.

[Max White]

Depends on the problem in question, but always nice to know I can do something in a way that just appeals to me more without shooting myself in the foot. If something is conceptually static, I like to be able to call it in a static manor, even if there is an object hiding in there.

[Putnam]

Okay, time to figure out a bunch of archaic C++ code to write a DFHack plugin!

Expect to see me often in the near future!