Decided to tag this as "Off Topic" and not "Linux" because it's not really about linux as it is about good ol' Linus. Other mods or OP, feel free to disagree and change it.

So this is kind of like crowd-funded investing?

I use Source Code Pro, which looks quite similar but maybe is a little wider.

SPJ always seems very intelligent and measured.

If the wrapper is pretty much 1:1 then you shouldn't have any problems with it, except for the fact that sometimes 1:1 wrappers can be a little slow.

If it tries to abstract the underlying lib then it can be prone to errors, like all code, but I'd say just try it and see.

Always makes me laugh, this one.

I'll endofunctor your monoids in a minute if you're not careful ;)

'Lo everyone. I can only speak for myself but I'm only here to tag posts correctly, remove spam, and help keep stuff on topic. I do of course have my own opinions relating to "SJW drama" and all sorts of stuff but I'm not here to censor anything, just keep the sub running. Peace! :)

If you ask me the best way to be good at building new things is to have lots of experience in building new things - but generally a lot of people will tell you that reinventing the wheel and not using third-party libs is always a bad idea. So it's an interesting catch-22.

I've build "new things" all of my career so far and each time I get a little better at it.

To be honest if I ever had a horrible accident I'd be super happy something like this exists :)

Could C#'s LINQ be considered a form of reactive programming, considering that everything in LINQ is lazily evaluated? Or is that a similar, but different paradigm?

Does windows still use NTFS? I don't know much about OSs...

Could you elaborate on why voat is superior? Technology-wise, we're far behind. We don't have much tools.

Maybe, in terms of tools, but we still have specific up/down vote counts, moderation logs, ability to block subreddits, a better karma system, better userpages, and some RES-like features built in (expansion of image links in comments for example). But as well as that, the community is better and the moderators in most subs (with some serious exceptions) seem to be more reasonable people. Most importantly, Atko seems to have his head screwed on right, if you ask me. Will Voat remain that way in the long-term? I don't think it's impossible, actually.

Could we maybe overcome the current shotcomings using creative work-arounds?

Isn't that the essence of being a programmer? :D I would hope we could try. :P

Do you think that it's okay, unfair, or maybe sometimes required, to have internal 'meetings' on /v/programming without letting the community know about their outcome?

It's hard to give a definitive answer because of course it all depends on context but as a general rule I'd say... No. It's okay to have internal meetings but then the outcome should be made public, and discussed within the community. We're not here to coerce the discussion or make behind-the-scenes rules; we should only really be here to help nurture the growth of the sub (and remove bogus content like blogspam).

As for what I'd do if I had a disagreement with the outcome of those talks - honestly, if I thought it was serious I'd probably post a metapost (trying to reason with the other mods notwithstanding, of course). :)

Atko's post literally made me so happy. It's so... Reasonable, and seemingly written by someone who actually thought for five minutes before taking the decision. Which should be the norm, but common sense is in short supply these days...

Hey, applying to mod here!

Your time zone and active hours

I'm a UK guy, so GMT. I'm active on and off throughout the day (basically when compiling or need a 10 minute break) and moreso in the evening.

Why you think you'd be good at this. You don't need prior experience, so newbies are welcome too.

Honestly? Because I'm not doing it for a power kick (not implying anyone else here is, of course). I want to do this because I want voat to succeed, I think it's vastly superior to Reddit. But the biggest thing for me was seeing /r/programming mods removing stuff with no transparency (not just spam, but hugely upvoted submissions with tons of comments, usually about github). Also I own /v/csharp so you can go check that place out and see what kinda shindig I like to run.

Your programming related knowledge. You don't have to be a senior, but knowing what you're interested in would be interesting.

So I have a 1:1 in CS with Games Development. After university I started programming defensive systems using Java and lasers (that's not a lib, I mean actual f*cking lasers, it was awesome :D). My job was basically to suck data out of our hardware fast enough in Java and without invoking the GC (or we'd drop packets). Since then I quit my job to try and start my own games company; also writing my own parallelized game engine with C++ and C#. I've also done webdev and commandline tools and yada yada in the past. I also have a brand new blog (only one post so far, but more coming soon!) at http://www.egodystonic.com/blog/

Discuss the above rule change. What do you think? Do you think it's the right call? Or a bad idea? I know you'll hate this one. There's no correct answer to this. As stated above, you don't have to answer all questions, so if you don't feel comfortable, don't answer it.

I think a dedicated sub makes the most sense. Drama has a tendency to spread like wildfire over everything it touches, and I'd much prefer this sub stay as industry news and learning resources. Honestly my favourite sort of submissions is stuff like this. Edit: Just thought I'd point out that I am still interested in reading the github drama, very much so... I just think it can consume the sub if we're not careful.

Anything else you feel you want to say.

Although I have my preferences I'd mostly try to be "hands-off". I believe a little transparency can go a long way, as well as not talking down to people or acting like "the all powerful mod" or whatever. I don't think a sub or comment should ever be deleted without a reason given publicly. Also, being able to admit fault is important :)

Yes, I agree, and think it's relevant to a lot of programmers, but only the major stuff (like Github's "retard" fiasco- I don't want blow-by-blow updates of the SJW war here).

FWIW I'm 100% with you on deleting low-quality blogspam and advertisments, Reddit's programming sub on any given day is likely to be 90% crap like "Why I'm the best programmer in the room" or "How to speak to programmers if you're a manager" (usually full of egotistical bloviating) etc.

Excellent - feel free to ask any questions you like there!

Horrible, blatant shilling for /v/csharp incoming - I've spent some time making the sub look nice, added links to blogs and tutorial resources in the sidebar, and added a few flairs for different topics. Also I'm in the middle of writing some C#-related blogposts to add some original content there over the next few weeks (and continuing over time). Plus we have a dedicated questions thread! :)

Good post, but my golden rule is: extremely applying some guidance never bring any good. YAGNI is one. If you develop something without at least researching and developing some of useful-simple features then you will be faced with refactor-intensive code or WET (write everything twice) code out there.

I agree of course - taking any advice to its extreme is pretty much always harmful. I wasn't saying you shouldn't think hard about your code before you implement things; more that you should be careful not to 'value-add' along the way.

And you get it wrong on flexibility. Flexibility can be achieved by many things, clean or ugly. Reflection flexibility is imho ugly, unless you know what you are doing with it (dynamic code compiler is one thing that can be helped with reflection). Reflection also slow for large data operation (AutoMapper suffer from this).

Flexibility isn't impossible, but makes everything harder. I do believe that in a lot of cases it is also unnecessary, but if you are writing an API that will be consumed by the public I understand (and agree) that you must consider it. Though I will point out that the particular type of reflection I was referring to wasn't C# reflection but HLSL Reflection in this case.

I think perhaps by saying that I think people should strive to make their APIs less flexible I might be accused of trying to give one-size-fits-all advice, and I understand your concern there. I do stand by my assertion that in general that is a good rule, though. Also as a side-note, I hate DI :) And DI really is just a form of reflection-based flexibility, also.

Thanks for the comments! And glad you enjoyed the post.

If I can suggest anything, it's to show people (or make blog posts detailing your failures, haha ;)). You'll learn about yourself as you write about yourself, and perhaps more importantly, opening yourself up to criticisms is the best way to learn (as long as you can stomach the harsher stuff).

Originally our goals were for something simple, and not to compete with a larger, more established engine like Unreal or Unity- after all, that would be madness. Instead we were aiming for something in-between a big game engine and and stuff like XNA - basically a C# version of LibGDX.

Now we're not aiming to release the engine with the game it makes life a lot easier. We only need to support exactly what we require - and must-haves like documentation and API flexibility (which take up a lot of time) are no longer necessary.

Fascinating, TIL of 'edges'!

Of course knowing this sort of thing is good for gaining a deeper understanding, but trying to code towards an x86 memory model in anything but assembly will fail for two reasons:

1. You might suddenly have to target another architecture (ARM for example), and more importantly,
2. Your compiler will have its own 'memory model' that you can't preempt. For example, you might know that a given write will not be executed out-of-order with a given read on an x86 CPU; but the compiler is still free to elide a non-protected access to memory if it doesn't change the semantics of the program from a single threaded point of view. So it's more important to learn the compiler's 'view' of memory models anyway.

There's always a relevant XKCD :P

Thank you!

Yes, and with the parallelization it was the same sort of thing. I already knew not to prematurely optimise but I didn't even see it that way. This was the engine's core thread management pipeline - it had to be 'designed right from the beginning', right? Again, retrospect is a bitch, haha. :)

"Big O". Doesn't mean a really great orgasm. Actually refers to the way the time (or occasionally space) taken by an algorithm increases as it has to compute over more data.

Third-party libraries who think dumping the API/Class Diagram on a website == documentation!

I hope the right people see your reply because this is the best idea imo- best of both worlds! Only thing is it makes it harder for question-askers to search previous questions and find out if what they're asking has already been answered... But I guess with stackoverflow and google out there already, most of the common questions should (in theory) not be being asked anyway.

Also I don't want the choice of having to run the realtime static analysis (e.g. the warning/error squiggles) either on the server (therefore waiting 1sec for updates) or in Javascript in some clunky web browser. I think online IDEs might have a place integrated in to things like github, for quick edits etc, but Visual Studio stays on my SSD for now. :P

I call myself a C# expert - I know every keyword, I know some IL hacks, I know a lot of the core .NET framework, and I understand the performance implications of pretty much any code you give to me (Database/Web service optimisation notwithstanding). I have written code covering almost every aspect of 'Core C#' including P/Invoke, unsafe, advanced generics, attributes, thread safety, LINQ, parallelization, etc. etc.

But as many guys here already said, part of being an 'expert' or 'senior' programmer, I think, is knowing that you are still very capable of making mistakes and that there is always more to learn. I want to improve my understanding of IL and CLR's execution model, for example (just... Where does the time go?). And every time I start a new project I think I've designed the perfect OO architecture, but it always turns out to have flaws (though I do get better every time).

Also, some people may in fact call me a beginner because I don't know very many .NET libraries and I know almost nothing about the web-sphere (I don't even know what the difference is between ASP.NET and err... The other one). So to finally answer your question, I would say that being an expert is where you feel confident in your abilities, and that they are relevant to your niche, but you understand you will never know everything or be perfect. Then again, ask me in 10 years, I'm only 25 and when I'm 35 I might laugh at what I wrote here. :D I call myself an 'expert' and not a 'senior' because my years of experience are small still (only 3).

Oh and I wouldn't sweat it about keeping up with JS frameworks, just work on your core skills and then you can learn what you need when you have to.

See, I'm not sure about that. The problem as I see it is that by allowing beginner questions, you'll turn /v/programming in to /v/programminghelp. And of course, I have no problem with there being a place for beginners to get help - but I feel like /v/programming should be more about the general industry/domain of programming. If you allow beginner questions I guarantee that's all you'll get too - because there's 10 beginners for every 1 not-beginner (same in any hobby/skill).

Then again, you could look at it the other way around and do as /u/swagath said already and have a /v/advancedprogramming instead.