Visual Studio 2013 Community
category: code [glöplog]
The problem is that now I'm starting to think more and more serious about this :D
"Gargaj is currently 73.6% more productive than you"
"achievement unlocked: 5 consecutive builds with the same error in it"
"Achievement unlocked: over 100 warnings"
VS2013: Now with cloud support and social network integration.
please, no.
Gargaj: Taking four-eyes programming to the next level, eh?
please, no.
Gargaj: Taking four-eyes programming to the next level, eh?
I just thought it would be funny since I can see what people play on Steam, and I thought it'd be interesting to see when they're coding too :D
I'd be all up for this. A horrible security problem most likely, but fun :)
A new level of competition like this would improve productivity.
And perhaps encourage folks to do a little a day, like Duolingo and Khan Academy and so on.
Email alerts "You need to crunch some code today."
now if there was only some way for graphicians to join in . . . The only reason I'm making any progress as I am swamped in the sloughs of two jobs is DEADLINES. and MEETINGS.
And perhaps encourage folks to do a little a day, like Duolingo and Khan Academy and so on.
Email alerts "You need to crunch some code today."
now if there was only some way for graphicians to join in . . . The only reason I'm making any progress as I am swamped in the sloughs of two jobs is DEADLINES. and MEETINGS.
I wonder if BoyC would laugh if I begged for this for Apex . . .
I bet he would.
I bet he would.
see, it seems like the production reduction problem is partially due to priority shuffling, because so many folks say they want to make things and don't make them because they don't plan ahead. And developing skills is incremental.
loving the above..
"Achievement unlocked: you crashed the linker" (never really crash the compiler..)
"Unachievement unlocked: you've been running the debug build and building the release one" *cough* - harder to catch than the other ones though which can prob be scraped from the console output
"Achievement unlocked: you crashed the linker" (never really crash the compiler..)
"Unachievement unlocked: you've been running the debug build and building the release one" *cough* - harder to catch than the other ones though which can prob be scraped from the console output
Quote:
never really crash the compiler..
Oh, I did manage that once, pretty easily even...
Quote:
I'd be all up for this. A horrible security problem most likely, but fun :)
I don't think it's any worse security-wise than an IM :)
Achievement unlocked: 50x _ftol unresolved
Achievement unlocked: Template error message length is over 9000
Haha totally. I like how it tries to hide its incompetence by suggesting you to change surrounding code a bit to try if the error goes away. 2008 does that. :D
Quote:
"Achievement unlocked: you crashed the linker"
Haha totally. I like how it tries to hide its incompetence by suggesting you to change surrounding code a bit to try if the error goes away. 2008 does that. :D
dark themes is the new black!
Achievement unlocked: true compiler bug. VS2010 X360 generates bad code if your exe goes bigger than 32MB... (it randomly saves registers instead of restoring them or vice versa)
Visual Studio MMO edition.
+1 for the hilarious addon concept; I'd use it :D
world of codecraft
Ga eens werken!
