pram posted:

the only acceptable options in this thread are hilariously useless functional languages or full retard on the microsoft stack

pram posted:

Luigi Thirty posted:

i have dyslexia but with numbers so gently caress math

Space Whale posted:

Just imagine the elegance of our pissing matches though.

fleshweasel posted:

also, haven't seen anyone bitch about why += is used to add handlers to an event in .NET. it feels like one place where for whatever reason they went with these += and -= operators instead of AddHandler and RemoveHandler. I don't care myself and I think it's completely clear when I read it.

sarehu posted:

This is how you do it in Lisp:

(clp 1 2)
(clep 1 1)
(cgp 2 1)
(cgep 1 1)
(cllp 1 2 3)
(cllep 1 2 2)
(clelp 1 1 2)
(clelep 1 1 1)
(cggp 2 1 0)
(cgegp 1 1 0)
(cggep 1 0 0)
(cgegep 1 1 1)
(cgegggep 5 5 4 3 3)
(cep 1 1)
(ceep 1 1 1)
(celp 1 1 2)

Necc0 posted:

thread title

soy posted:

my first real code merged and went into production today I'm so happy

also nothing exploded as a result, a nice bonus.

quote:

today

Shaggar posted:

pwnt. next time use Path.GetTempFilename()

also you can do something like

C# code:

public class TempFile : IDisposable
{
	public TempFile()
	{
		TempFilename = Path.GetTempFilename();
	}

	~TempFile()
	{
		Dispose();
	}

	public string TempFilename { get; private set;}


	public void DIspose()
	{
		FIle.Delete(_tempFilename);
	}
	
}

Then you can treat it like any other disposable and wrap it in a using so it gets cleaned up automatically. or trust the destructor to clean it up (don't do that)

Luigi Thirty posted:

I read an article about how c# is dying do I have to learn a hipster JavaScript framework now!?

CPColin posted:

A good indicator that somebody is a particularly bad programmer is when he or she doesn't think to use programming to solve a repetitive task. I was in a graphics class once and we had to make an object in a washer shape. I used some sines and cosines and came up with a model whose polygon count was controlled by a constant. Then I got into the lab and saw everybody else's version. A few of them used graph paper and typed in the coordinates. A bunch more calculated the values correctly, but did it by hand, then typed them in.

Vanadium posted:

So hey anyway what's a good way to learn standard SQL without accidentally internalizing unportable bits? Like I can find my way around a couple simple joins, nothing fancy, but I don't have any idea if things that appear simple to do to me are portable or even possible at all

gonadic io posted:

visual studio has basically no support for f# though, that really sucks

like you need 3-4 addons before it becomes even tolerable

~Coxy posted:

I know you probably mean Join but the other day I did

code:

Enumerable.Repeat("intzone", 1).Union(elementVariables).Union(slopeVariables)

felt good but I wonder if there's a more expressive way than using Enumerable.Repeat

Shaggar posted:

ive never used SQLite. sql server merge works pretty well tho

Shaggar posted:

theres no really good way to do it, no. the problem is that Microsoft refuses to acknowledge the idea that the schema belongs to the database and not the application. this means there are no tools or extensions in sql server for doing schema versioning. you basically have to use external tools to manage schemas in source control and then make sure everyone puts their changes into source control after they enter them. its a lovely system but its the best you can do.

I really wish they would add versioning directly to sql server so the server would version schema elements any time they're changed automatically. otherwise you're relying on your team to follow the process and that's always bad.

fritz posted:

what kind of months do you have that have more than 65536 days in them

Soricidus posted:

that's your problem right there. use the standard yyyymmdd format and you don't run into problems with variable lengths or leading zeroes or ambiguous parses or anything

alternatively, posix timestamps

Symbolic Butt posted:

it still surprises me how much of my ~~coding style~~ came from working with legacy fortran code

Shaggar posted:

one of my favorite things about linq is that they use English terms for the method names instead of math terms.

eschaton posted:

it's also not hard to follow a few simple rules that will lead to always writing correct code

1. know if the platform you're working on imposes any major constraints

2. know the constraints for basic data structures on your platform

3. know the basic high-level constructs offered by your platform

4. you probably don't need to use any low-level constructs yourself, leave that for the implementors of the high-level constructs. really.

5. look up everything else. always. never assume anything, ever, you will get it wrong.

these rules should apply on pretty much any platform you see

DaTroof posted:

then again, if the test itself was up to me, it probably wouldn't exist

DaTroof posted:

our last 3 candidates for a junior dev position left the 4-question code test incomplete. None of them got through question #3, which asks them to implement a singleton in the language of their choice

e: they're allowed to use the internet during the test

Bloody posted:

I mostly don't use inheritance because it is frequently the wrong tool

CPColin posted:

"Rule of three" is a pretty good rule.

Bloody posted:

today, i extracted an interface from a class because i wanted to stub in a mostly-the-same-but-different-enough version of the class over it without getting rid of the original one. it leaves most of the methods undefined and i don't care worksformewontfix

pepito sanchez posted:

i mean

code:

	let rec quickSort = function
		| [] -> []
		| n::ns -> let lessthan, greaterEqual = List.partition ((>) n) ns
			quickSort lessthan @ n :: quickSort greaterEqual

why f# isn't used more with c# is a mystery to me? it's like a better LINQ i can use anywhere and has been kept a secret from me until recently. never die programming language

gonadic io posted:

I do. Gotchas in langs have easy solutions once you know what the problem is. That doesn't change the fact that it's nonobvious that there's a problem in the first place.

fritz posted:

it's used, yeah, like:

code:

{ 
int[] data = new int[BIG_NUMBER];
// call a jni function to fill data
// do stuff with data
}

and the size is a constant.

im coming to this from a c/c++ mindset and if i saw a

code:

 
{
   int* data = new int[BIG_NUMBER];
   memset(data, 0, sizeof(int)*BIG_NUMBER);	
   /// stuff
   delete[] data;
}

in a time-critical section of code i would start thinking along the lines of 'hey maybe we can hoist the allocation out and only do it once'

but (a) idk if the jit is smart enough to do that sort of thing and (b) see earlier comment re: not being set up for profiling

Funk In Shoe posted:

delphi code